TOP: C0000218 {Registry File Failure): how to fix it in Vista Ulti

G

Guest

Final release Vista Ultimate took a long time calculating remaining time to
copy a file. when I rebooted, I got the blue screen with this message:
TOP: c0000218 (registry File Failure}
The registry cannot load the hive (file):
SystemRoot\System32\Config\SOFTWARE or its log or alternate.
It is corrupt, absent, or not writable.

How do I recover the registry from a possible automatic system registry
backup file somewhere in the hard drive? Windows repair could not fix the
problem. Or, how to extract this bad registry file from the Vista DVD to its
directory? Or do I have to reinstall vista again. I am at the 2nd install.
Thanks!
 
R

Rick Rogers

Hi,

Try swapping the 2GB you are using out for the 2GB that you are adding and
see if the system boots ok. I suspect that you will find that either the
additional 2GB is faulty, or that it is incompatible with the original 2GB.
0xC0000218 is a common result of memory parity errors.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
 
C

cquirke (MVP Windows shell/user)

You can, but there is now an onboard memory diagnostic tool. Just type
'memory diagnostic' into the search box.
Click to expand...

I'd use MemTest86, as it is MUCH safer.

The onboard tool works as follows:
- may require Windows to launch
- writes to the installation so that it runs next boot
- starts to run after the next boot
- does a quick test and then stops, unless you "etc."
- writes results to the HD installation's even log

In contrast, MemTest86:
- boots off the CDR
- repeats tests until stopped by the user
- accumulates test results on screen
- does not write to the HD at all

When RAM is bad, all bets are off. Not only can stuff being written
to disk be corrupted, but where they are written on disk can be
corrupted, too (e.g. you can splat over NTFS's MFT, etc.).

Also, most "read disk" calls are one bit-flip away from being "write
disk" calls, so you don't want an OS that requires thousands of read
operations off HD to boot (not to mention all the automatic write
operations; temp, page file, directory access timestamps, etc.)

When BIOS detects a memory parity error, it halts the system, because
it "knows" this is the only safe thing to do.

Similarly, Windows will halt the system when errors are such that
context loss makes it unsafe to continue; BSoDs in 9x, STOP in NT.

MS is either losing this clue, or is treating us with contempt (e.g.
it's more important to cut support calls than to preserve user's HD
contents) when they move from halting on BSoDs to automatically
restarting the system (effectively, hiding these errors).

So when MS designs a RAM tester specifically for use where RAM quality
is suspect, and this process makes liberal use of both read and write
traffic on HD, one wonders if they've completely lost the plot.


--------------- ----- ---- --- -- - - -
Click to expand...
To one who only has a hammer,
everything looks like a nail
 
C

cquirke (MVP Windows shell/user)

On Wed, 1 Aug 2007 07:28:37 -0500, Mick_B
cquirke
Hi!

That comment does not make sense. "I'd use MemTest86, as it is MUCH
safer" - "In contrast, MemTest86"
Click to expand...

Wrong grouping - it's supposed to read as...

I'd use MemTest86, as it is MUCH safer.

The onboard tool works as follows:
<blah blah>
In contrast, MemTest86:
<blee blee>

IOW, the initial assertion does not run into the others (hence ended
as a sentence via . rather than linked forward to one item via : or a
sequence of items via ... )

Sorry if I threw your parser ;-)


--------------- ---- --- -- - - - -
Click to expand...
Saws are too hard to use.
Be easier to use!
 
X

XS11E

tommiy said:
Gigabyte finally got back to me. Useless questions and no real
suggestion of any thing that hasn't been done before.

This was my first venture into a non-ASUS mb.....do I regret that
decision now. As there is little help from gigabyte on the matter I
think its a throw away job and return to a ASUS mb to fix the issue.
Its not like I'm even oc'ing.

Anyone have a recommendation?
Click to expand...

Yes, I recommend you hang on a bit. I use ASUS mbs and prefer them to
others but Gigabyte is recommended by quite a few so wait some more and
see if an answer pops up.
 
X

XS11E

tommiy said:
well this mb is almost useless...one out of 20 restarts with 4g in
it works...memtest works flawlessly for 4 straight days response
from gigabyte support is non-existent....should I say bloody
hopeless.....on the weekend this board is going to the trash.
Click to expand...

I wonder if it's a defective board? Can you get them to replace it?
Maybe a new one would work properly.
 
X

XS11E

tommiy said:
guess that gigabyte is just a dud mb and I should have stayed with
ASUS....seems I've done my money. Last time I try gigabyte. Off to
buy a ASUS board this week.
Click to expand...

I'm sorry you had such awful results with Gigabyte but I can't quarrell
with your choice of ASUS, I don't think I'd want to use any other MB.
I did a LOT of research before buying my current computer and one thing
that sold me was that HP uses ASUS MBs in the model I now have.
 
X

XS11E

tommiy said:
Before I absoultely gave up ...after installing the beta bios and
still having trouble I installed hotfix 940105 because I have a
nvidia card...guess what 9 days later and the machine is still
booting ok with 4gigs of ram installed!!! Keeping the fingers
crossed!!
Click to expand...

Good news! Maybe it's fixed? I sure hope so, Gigabyte has been
reported here and elsewhere as being a good board so let's hope all
will continue to be well.

I'm still loyal to ASUS but when I considered updating rather than
buying a whole new computer, I considered Gigabyte because it seemed a
better deal for the money. As it turned out, buying a whole new
computer was cheaper than trying to upgrade so I didn't have to make a
decision....
 
X

XS11E

cooncheese70 said:
I installed hotfix 940105, but unfortunatly I am still getting a BSOD
now and then :-(
Click to expand...

Did you run a memory test? That's probably the first place to look for
BSOD problems, next is to update video drivers.
 
R

Rick Rogers

Hi,

If it is a registry file failure, then it's a software problem. Rolling back
via System Restore to an uncorrupted state is the first step. If that
doesn't resolve it, then a reinstall to a fresh folder is the most likely
solution.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
 
R

Rick Rogers

Hi,

Again, it does not sound to me like you need new hardware as the error code
indicates corruption within the operating system files. A reinstall, cleanly
to a fresh folder, is what is warranted. If you can't find your OEM media or
have a friend who has one you can copy, then you'll need to purchase one
(even if you replaced the motherboard, which to my knowledge is not an
issue, you'd still need a reinstall disk).

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Stop: C0000218 1
Stop: c0000218 7
STOP: C0000218 {egistery File Failure} 1
Vista x64 c0000218 error while booting 2
Need Help with Registry File Failure 4
STOP: c0000218 {Registry File Failure} 3
c0000218 registry file failure 0
StoP c0000218(Registry file failure) 2

Top