Hi Guys I thought someone might find this helpful. I came across a customers PC which would boot into Windows XP then flash a blue error screen very quickly and then restart. I video taped the error and played it back in slow speed and found the following.
Stop c0000218 (Registry file failure)
Registry cannot load hive
systemroot\system32\config\security
or its log or alternative etc.....
After some research ( Google really is your friend lol ) I found there may be a problem with ram or the hard drive. I loaded Barts PE disk and ran the scandisk utility and wow..... a lot of errors are on the hard drive. This definitely points to the hard drive as being the source of the problem as I had only formatted and reinstalled the OS 2 days ago. You can try and run the repair installation option off your Windows XP cd, just boot the PC with Win XP disc wait for it to load then select the repair option. This seems to be a rare problem and I hope this info helps someone out in the future. I also found this link on a forum which may help Link Here .
If your hard drive is OK then try using utilities found on various boot CD's to fix the registry or worst case reinstall Windows XP. Search for UBCD or Bart PE in your favourite torrent directory for the boot CD's
Good Luck
Peter Parry
c0000218 does anyone have a fix
Desparate
Posted by: Lorne Bruce | August 04, 2006 at 01:41 PM
Hi, Problem you have is with the hard drive. Errors on the hard drive have damaged the registry, may be fixed with scandisc but in most cases the hard drive needs to be replaced. Hope this helps.
Posted by: Peter Parry | August 04, 2006 at 03:46 PM
Hi, Problem you have is with the hard drive. Errors on the hard drive have damaged the registry, may be fixed with scandisc but in most cases the hard drive needs to be replaced. Hope this helps.
Posted by: archlord gold | June 19, 2010 at 12:29 AM
Best thing to do here is replace the hard drive, if that does not fix the problem then replace the motherboard.
Posted by: Peter | June 22, 2010 at 10:56 PM
I have 10 xpsp3 machines that have popped this error message up over the course of 4 days. far too many for it to be simultaneous coincidence.
Posted by: dan | September 04, 2010 at 02:59 AM