Vista x64 c0000218 error while booting

[Tim]

I've installed Vista x64 Business edition on the following pc:
C2D E6600
GigaByte P35-DS3P
4x1 GB DDR2 800
HD2900XT 512 MB

Now, when I boot the system, the following BSOD occurs:
STOP: c0000218 {registry file failure}
The registry cannot load the hive
\SystemRoot\System32\Config\SECURITY
or its log or alternate.
It is corrupt, absent, or not writable.

On the internet you can find a BIOS settings for motherboards like mine, to
solve the problem. unfortunately, that doesn't solve the problem for me.

I tried booting with 2 GB RAM and then Vista works fine. But there is no
such thing as too much memory when running Vista, so I would really
appreciate using 4 GB.

Does anyone have clue how to solve this problem?

[freddy]

Tim,

Here is what I found on the Internet, quote:

0xC0000218: UNKNOWN_HARD_ERROR
(Click to consult the online MSDN article.)
A necessary Registry hive file couldn’t be loaded. The file may be corrupt
or missing (requiring either an Emergency Repair Disk or a Windows
reinstallation). The Registry files may have been corrupted because of hard
disk corruption or some other hardware problem. A driver may have corrupted
the Registry data while loading into memory, or the memory where the Registry
is loading may have a parity error (turn off the external cache and check the
physical RAM).
0xC0000218: UNKNOWN_HARD_ERROR {KB 156640} Win NT, Win 2000
How to Recover from a Corrupted Registry that Prevents Windows XP from
Starting {KB 307545} Win XP (includes error messages that \WINDOWS \ SYSTEM32
\ CONFIG \ SYSTEM or \WINDOWS \ SYSTEM32 \ CONFIG \ SOFTWARE is missing)
How to Troubleshoot Registry Corruption Issues {KB 822705} WinNT 4.0, Win
2000, Win XP Pro, Server 2003 (computer will not restart due to corrupt
Registry hive)
How to Troubleshoot a Stop 0xC0000218 Error {KB 314874} Win XP

unquote

It's likely these appoly to Vista as well.

--
freddy

[freddy]

Tim,

Here is the the link to the source of that (obove) information:

http://aumha.org/a/stop.htm

Rind the error on the right, and then click on it. You then can more easily
link to the corrective steps contained therein.
--
freddy