The file c:\windows\system32\config\system is corrupted.

[GoodRevrnd]

The file c:\windows\system32\config\system is corrupted.

I don't really need help w/ the problem... more with finding the cause. This happened once before and you can see the partial results in this thread. I didn't replace the file this time, after a number of reboot attempts and last known good config I managed to get into windows w/ the message "an alternate copy of registry has been loaded" or something.

So... what's causing this and how do I fix it? Each time it happened after a massive crash where it would say "____ needs to close" for each program. If I had to guess I'd say the mobo or the memory, am I correct? Should I just run memtest and see if I get errors (never used it before)? And will that be able to accurately tell me what the problem is? My newest piece of hardware is a stick of memory, but I've had it since Dec/Jan and the first crash occurred in April.

EDIT: Also if last time is any indication, I'll be screwed the next time i reboot with the same error message.

 

[Sianath]

What's the OS?

Couple of things will give you that error on startup. The hive actually being corrupt is one, if the hive is too large (>11 or 12 MBs or so) you'll receive the same error.

Physical corruption that happens to be where those files are stored will also cause it.

If you go into your system32\config folder, what's the size of the system hive? If it auto-loaded the other "backup" of the hive and you booted, it's probably not a size issue, but actual corruption. The other possibility is physical disk errors where the hive is located that prevented us from loading one, but not the other.

If you have XP Pro SP1 or Server 2003, try opening up regedit and loading the suspected bad hive. They have a built in registry repair utility that will try and fix any corruption that is detected.

While the most current version isn't external, you can use chkreg as well.
- http://www.microsoft.com/downloads/details.aspx?familyid=56D3C201-2C68-4DE8-9229-CA494362419C&displaylang=en

just run:

chkreg /f <file path> /r

🙂

 

[GoodRevrnd]

WinXP

How do I load the old hive? I don't see any file in there that looks like a backup of the old one. Also the current system file is 3.5mb.

 

[Sianath]

Size is fine then.

Easiest method is just boot to the recovery console, change into the windows\system32\config folder, then type:

copy system system.old

Reboot back into windows, then try loading your system.old.

 

[Smilin]

Originally posted by: GoodRevrnd
WinXP

How do I load the old hive?

Bring up help in regedit. Use the search index to look for "load hive".

Do what Sianath said, he fixes these things for lunch. Use the above to load your windows\system32\config\system.old file into regedit under XP or 2003.

 

[NogginBoink]

I'm guessing disk corruption.

Start doing regular system state backups if this is happening to you often.

And run chkdsk to ensure the filesystem is healthy.

 

[Sianath]

Click Start, Run, type Regedit

Highlight HKEY_LOCAL_MACHINE

Click File, Load Hive

Browse to the c:\windows\system32\config folder, and select your system.old file

Give it any name you want when prompted. This name will show up as it's own branch underneath HKLM.

If there is corruption, it will be detected after you "name" the hive you are loading and regedit tries to mount it.

I'm warning you now... if the hive is very badly corrupted, you may very well bugcheck the box when you load the hive. You'll be fine when you reboot, but if that happens, you'll need to use chkreg to try and repair the corruption.