"Stop: 0xc0000218 {Registry File Failure}

[nbk]

Hi

I found this at startup this morning

"Stop: 0xc0000218 {Registry File Failure}
The registry cannot load the hive (file):
\SystemRoot\System32\Config\SYSTEM or its log or
alternate.
It is corrupt, absent, or not writable."

It constantly reboots and i cannot go into safe mode at
all.

I have had this before and i had to clean install win2k.
I left off
Norton SystemWorks 2001 and Take2 from Easy
CD-Creator 5 w/o patches.
My install ran fine for approximately 3 weeks.

My Config:
Abit BE6-II rev2.0, Win2k Pro SP#2, Plextor 12/10/32a
CDRW, ATI RageFury

32Mb with driver 5.13.01.192, Pioneer DVD-115 16x40,
Creative SB
LIveValue, ViewSonic A70 monitor, Enlight 7327 case
w/Enlight 300watt
PS, APC Back-UPS 500, Maxtor 40Gb Hard Drive on
the HighPoint 370
controller, HighPoint 370 driver v1.0.3b, Quantum 6Gb
on the
non-HighPoint controller, P-III 800 slot 1 not o/c'ed,
Ericsson Cable
Modem, 2x256Mb PC-133 and 1x128Mb RAM PC-100

Any ideas? I am suspecting the Highpoint Controller
or Easy CD Creator
5.x?

.

[J. M. De Moor]

nbk

>
> I have had this before and i had to clean install win2k.

If you did not make an ERD and backed up the registry hives, you will have
to reinstall again.

This problem involves a combination of a large disk cache and fast
processor, where the hive in question is not properly saved before the
system auto shuts down. If you can't disable the auto-shutdown in the BIOS
(Abit is notorious for leaving this setting out...claiming that it is part
of an agreement with M$), the best workaround to prevent this problem is to
Restart instead of shutting down and powering off your computer when the
POST messages appear.

Joe

[Robin]

yes, this is what we suspect also. MS has a patch, but as
i stated a couple days ago when I also asked the STOP
question, the patch also fails. I use Asus products, and
also have no control over the shutdown. This is a big
problem for my networks and i hope that MS can produce an
effective patch, or that Award can incorporate a delay
setting into a bios flash. The answer, and the knowledge
base article (which, btw, I had already seen, given by the
tech who answered my post was just not the answer that I
had hoped or wanted to get. So, thanks, Joe, you have
only verified what I suspected to be the cause, and have
given me a workaround.

Regards,
Robin

>.
>