• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Win2k Registry Cannot load hive

T

tes177

Member
When I booted up my computer last night, I got this error to effect of saying, Win 2000 registry is unable to load hive. Please restart your computer. Well, I restarted, and got the same error, So I went through the repair function in Win2k and it fixed it ok with my system disk. I just wanted to know what could be giving me this error, is there a problem with a program I might have installed or what.


System Specs
1ghz Athlon at 1200mhz
Epox 8K7a
Geforce Pro 64
Santa Cruz Sound Card
Win2k Sp2
 
Did you copy the exact wording of the error message? Could be very useful. Also, you said you ran a repair. Exactly what did you do to repair the system, an actual repair installation or a "boot with last known good" or something else? Does all of your software still work, or have some apps stopped working, even though they are still physically present on the drive?

BTW, you might wish to post this in the Operating Systems forum. This isn't really a General Hardware question. Might get more answers over there.
 
I agree with above. What is hive? If it's not something you need to run at startup, you can remove it from the registry, and not worry about it.
 
This happened several times with a new DELL system. After reinstalling
several times with there "BS" resource CD (in place of a real W2K CD)
The problems always seemed to return. So after hanging up with DELL support (which just wanted me to reinstall yet again). I did a clean format/fdisk and installed with a real W2K CD and all has been fine
since. If this is an OEM system and all you have the a resouce/system CD (not a real W2k CD) borrow a real CD from a friend (not illegal because you did buy a W2K license) and do a clean install.
Also check out (search) Microsoft support. There is some info there on this (hive problems)
 
I have the error at home so I will get it when I go for lunch, thanks for your help so far. This is a home built system, and I didn't loose any programs, but windows doesn't see any. I used the repair ability through the win2000 setup cd and a recovery disk.


Thanks again.

Tom
 
I'm not exactly sure from your description, but it sounds like the dreaded SYSTEMced error message. This happens with some systems that shut down so rapidly that power-down occurs before the disk write-through cache has been cleared to the hard drive. W2K writes changes to the current SYSTEM hive to disk just before it closes shop. If that process doesn't get completed, that "hive" of the registry gets corrupted and can't be loaded at the next startup. You can recover by doing a repair install. (Sometimes you can just a boot with last known good configuration.) In either method of recovery recent changes to the registry may have been hosed, so you wind up still having an application existing on the system, but it won't run properly because all of the relevant registry information for running it has been lost. If this is what's happening with your system, it's likely to be fixed by simply installing the proper controller drivers.

But there are a lot of other possibilities, so get that information posted for us. Maybe someone will be able to help.

I'm on my way to the airport now, so not sure when I'll be checking back in. But there should be plent of people here who are thoroughly familiar with this -- more thoroughly familiar than I am, since I haven't had it happen on any of my systems. 😀

Regards,
Jim
 
All I could find out at the moment was that it was that I get a "STOP: 0x0000001E" Error Message when I try to start windows, and it attemps to load the Windows 2000 System Registry Hive. It goes to a blue screen and asked me to restart. I did use the recovery tool and got windows back, but this is the second time it has happened, the first time I did a clean istall. I am using a regular Win2k Pro install cd and such. I am wondering what could be causing this problem, and how to stop it from occuring again.
 


<< All I could find out at the moment was that it was that I get a &quot;STOP: 0x0000001E&quot; Error Message when I try to start windows, and it attemps to load the Windows 2000 System Registry Hive. It goes to a blue screen and asked me to restart. I did use the recovery tool and got windows back, but this is the second time it has happened, the first time I did a clean istall. I am using a regular Win2k Pro install cd and such. I am wondering what could be causing this problem, and how to stop it from occuring again. >>



How are you correlating a STOP 1E and an &quot;attempt to load the Windows 2000 System Registry Hive?&quot;

Unless you've done a kernel mode debug on this STOP error, you probably have no idea what's causing the STOP and you're guessing.

What are the bugcheck parameters (in parentheses on the STOP screen)?
 
Sorry, but I need more of the error message to have any idea as to what to suggest. The whole message can be important.

You can also search on &quot;STOP 0X0000001E&quot; at the MSKB. You'll get a lot of hits. There's a lot written about it. But there are a lot of subtypes of this error, so you'll need to get more specific in order to diagnose its cause.

Regards,
Jim
 
I finally got home to get the information here it is

Stop: C0000218 {Registry File Failure}
Cannot load the hive(file)
\systemroot\system32\config\software
or its log in alternative


that is the error that I got last night when I tried to boot up my system


thanks
 


<< So I went through the repair function in Win2k and it fixed it ok with my system disk. >>



Someone actually made a rescue disk?!?!!!
 
Ouch!

Like a ghost from the past. See this MSKB article. No, I know you're not running NT 3.1. But I suspect the issue is, indeed, caused by a hardware compatibility issue of some kind. Was something new installed recently, just before the problem occurred? Had you edited the registry manually just before the problem occurred? If so, were you using regedit.exe or regedt32.exe? The other error you mentioned, in conjunction with anything you might get from the Event Viewer logs, could help you triangulate on whatever it is that's messing up your software hive. You would be looking for something in common among the causes listed in the MSKB for the various errors. Do you have any such other information?

Since you were able to recover using a repair install, and the file system and everything else seem okay, you can choose to simply re-install your software. I suspect, however, that something is present hardware-wise that may continue to farkle the system. I'd suggest working diligently to find any incompatible hardware / drivers on the system and either get rid of any culprit devices found or update their drivers so as to eliminate any possible incompatibilities.

If you haven't done so already, it's very important for you to back up your data to external media. Even if this isn't a hardware compatibility issue, it might be an incipient hardware failure.

I guess you probably will want to re-install the OS from scratch, though a re-installation of all software is a possibility. But I wouldn't do it until I found the source of the trouble. Otherwise, it's all likely to circle the drain again.

Regards,
Jim
 
Oh, good call, MulLa! I didn't even pay attention. I'd at least back off on the OC until this is straightened out. W2K is very timing critical. If one device or another is made to run just a little out of kilter... It's at least worth the trouble to see if it could be an issue.
 
I'm going to try to a little less overclock, and to set my ddr ram timing setting to auto. Right now I have them at 8882222. Thank You for your help, guess will see what happens.

Tom
 
Please let us know how things are going. And, BTW, did you ever find the rest of that STOP: 0X0000001E error? As a couple of us have mentioned, that could be pointing right at the culprit device on your system. The hive loading error is just basically telling us how badly that part of the registry is hosed, but doesn't really suggest the cause.

Regards,
Jim
 
Registry errors can be caused by OCing RAM too much. A OCed CPU can cause it, but its not very likely its almost always the RAM.
 
i set my RAM timing to auto now, and started to reinstall some software. I didn't install windows yet, just waiting to see what works. And thanks again for all you help.


Tom
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top