Computer Hope

Microsoft => Microsoft Windows => Windows XP => Topic started by: GelatinGhost on April 02, 2009, 04:42:04 PM

Title: Corrupt Registry on OEM
Post by: GelatinGhost on April 02, 2009, 04:42:04 PM
When I booted my dell vostro 1000 today, I got the BSoD:

STOP: c0000218{Registry File Failure}
Cannot load the hive (file):
\systemRoot\system32\config\SOFTWARE
or its log or alternative.
It is corrupt absent or not writeable.

I turned it off and tried booting it normally, but I got the same thing. Then I tried booting with Last Known Good Configuration, and wouldn't you know it, it worked. But, being the stupid person I am, I turned it off again in order to test if the problem was gone for good. Ironically, I can't log in at all anymore, and am strictly worried about all my data and files I somehow failed to backup (even though I had the chance). I'm typing on a different computer right now.

So, I found this webpage http://support.microsoft.com/kb/307545, but unfortunately it says it only applies to non-OEM computers. It is still safe to do it, or is there any other better option? I do still have the installation/recovery cd that came with the computer, but reformatting is not an option until I recover all my data.

Thanks for anybody who can help with this.
Title: Re: Corrupt Registry on OEM
Post by: Broni on April 02, 2009, 05:26:06 PM
1. If you have Windows CD, follow the steps from here: http://icrontic.com/articles/repair_windows_xp

2. If you don't have Windows CD...
Download Windows Recovery Console: http://www.thecomputerparamedic.com/files/rc.iso
Download, and install free Imgburn: http://www.imgburn.com/index.php?act=download
Using Imgburn, burn rc.iso to a CD.
Boot to the CD...let it finish loading.
When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
Then, follow the steps from here: http://icrontic.com/articles/repair_windows_xp, starting below this picture on page 1:
(http://icrontic.com/draco/images/articles/repairing_windows_xp_in_eight_commands/xp_src_welcome.gif)
Title: Re: Corrupt Registry on OEM
Post by: GelatinGhost on April 02, 2009, 06:28:12 PM
Thanks a lot, it appears this may work! However, before I go ahead with it, I want to ascertain whether the amd athlon 64 x2 has the nx buffer overflow protection. According to the official site it has Enhanced Virus Protection which protects against "buffer overrun attacks", although I don't think this is the same thing.

Here's the official site by the way: http://www.amd.com/us-en/Processors/ProductInformation/0,,30_118_9484_15670,00.html
Title: Re: Corrupt Registry on OEM
Post by: Broni on April 02, 2009, 06:30:26 PM
I have no idea, but why is it important?
Title: Re: Corrupt Registry on OEM
Post by: GelatinGhost on April 02, 2009, 06:39:58 PM
On the site you gave me, it says if you have nx buffer overflow protection you must set the os load option to /noexecute=optin

I believe now (due to wikipedia) that evp is nx overflow protection, so I'll just turn it on I suppose.
Title: Re: Corrupt Registry on OEM
Post by: Broni on April 02, 2009, 06:53:18 PM
Oh, I see...
Title: Re: Corrupt Registry on OEM
Post by: GelatinGhost on April 02, 2009, 08:04:26 PM
Hey, thanks a lot, it actually worked! Now to back up everything just in case this happens again...
Title: Re: Corrupt Registry on OEM
Post by: Broni on April 02, 2009, 08:18:49 PM
Nice job ;D