Unsolved
This post is more than 5 years old
7 Posts
0
4752
November 20th, 2002 14:00
Hive file corruption on Windows 2000
I've been having serious problems with the hive file getting corrupted on my system. I'm running W2K. I took it to a local shop and they found a bad memory module but removing that hasn't solved the problem. I've also noticed when this usually happens the cooling fan (or possibly the harddrive?) sounds like it's slowing down. I've been able to recover so far using the emergency repair disk but of course that trashes a lot of my settings and drivers and I have to spend a half hour setting everything back up.
Could this be indications of a more serious CPU problem?
Thanks,
Michael
No Events found!
Pamela
638 Posts
0
November 20th, 2002 15:00
Michael,
A corrupted Registry often results in a STOP error or blue screen of death at startup. Damage to the Registry can be physical or logical. Physical damage means that something (usually disk-related corruption) has scrambled the Registry hive files (e.g., the SOFTWARE or SYSTEM files in the \%winntroot%\system32\config folder). Logical damage means that a third-party application, a user, or NT has written invalid data to the Registry, which can trigger an NT startup failure if the logically damaged Registry entry is critical. The STOP error might identify a telltale sign such as a hard Registry error or a reference to a particular damaged hive file. What does your STOP error say exactly?
An example: STOP 0xC0000218
Information on that particular error:
http://support.microsoft.com/default.aspx?scid=KB;en-us;q156640
Pamela
lwman
7 Posts
0
November 20th, 2002 16:00
Hi Pamela,
Unfortunately I haven't written it down yet but I will the next time it happens. I've been leaving my machine on all day until I go to bed in order to reduce the number of times I have to boot up. I've recently replaced my harddrive and this problem started before then so I don't think it's the harddrive itself.
Thanks,
Michael
Dampco1
112 Posts
0
November 21st, 2002 12:00
Michael,
Have you tried running the Dell Diagnostics? It's on the resource CD and should identify any hardware related problems so you can rule that out. Try the link below for information on how to run the delldiag.
Select your system here and on the next page select "Solutions". Then choose your option (ex.FAQ's, KB, or Reinstall) and you will be directed to your systems custom info.
This article might also be of interest to you.How to troubleshoot start-up problems in Win 2K