Corrupt SOFTWARE hive keeps recorrupting

  • Thread starter Thread starter jbclem
  • Start date Start date
J

jbclem

I was able to get my Win2000 to boot by replacing the corrupt SOFTWARE hive
with the original one from the WinNT/repair folder. But a day later when I
tried to go back into this Win2000 setup, the SOFTWARE hive was corrupt
again and I couldn't get into Win2000. I've replace the SOFTWARE hive
again, and am writing this from the working Win2000, but I need to find out
what could be causing this re-corruption...I expect it will keep occuring
until I can figure out the cause.

Any ideas about this...when it happens the Win2000 logo screen will come up
and just before it ends, up pops a blue screen (for 1/2 second) with an
error message about the corrupt SOFTWARE hive.

jc
 
jbclem said:
I was able to get my Win2000 to boot by replacing the corrupt SOFTWARE hive
with the original one from the WinNT/repair folder. But a day later when I
tried to go back into this Win2000 setup, the SOFTWARE hive was corrupt
again and I couldn't get into Win2000. I've replace the SOFTWARE hive
again, and am writing this from the working Win2000, but I need to find out
what could be causing this re-corruption...I expect it will keep occuring
until I can figure out the cause.
Click to expand...

Very often it's caused by RAM or disk controller malfunction. For more
information see "How to troubleshoot registry corruption issues" -
http://support.microsoft.com/kb/822705
 
From: "Arkadiusz 'Black Fox' Artyszuk" <[email protected]>

|
| Very often it's caused by RAM or disk controller malfunction. For
more
| information see "How to troubleshoot registry corruption issues" -
| http://support.microsoft.com/kb/822705
|
It can also be caused by the Registry file being located in an area of
the hard disk with a bad sector.
Click to expand...

This was the cause on one of the systems I use. The hard drive was going
bad and while I was able to recover the hive once (long enough to get some
data off), the next time I booted the system the error re-occurred. Replaced
the hard drive, re-installed the OS, and all is well.


K. Brian Kelley, brian underscore kelley at sqlpass dot org
http://www.truthsolutions.com/
 
From: "K. Brian Kelley" <[email protected]>


| This was the cause on one of the systems I use. The hard drive was going
| bad and while I was able to recover the hive once (long enough to get some
| data off), the next time I booted the system the error re-occurred. Replaced
| the hard drive, re-installed the OS, and all is well.
|
| K. Brian Kelley, brian underscore kelley at sqlpass dot org
| http://www.truthsolutions.com/
|

Often this kind of problem can be corrected by obtaing the manufacturers diagnostic
software. For exmple in the case of IBM/Hitachi hard disks, the Drive Fitness Test (DFT).
Then the software will detect bad sectors, move the data to good sectors and then block-out
the bad sectors so thet won't be used again.

This approach is good if it is a only a sporadic problem. If the problem is ongoing with
Bad Sectors then a new hard disk would be warranted. However one can use software such as
Drive Fitness Test (DFT), repair the problem and then proceed to Ghost the disk to a
replacement hard
drive. Thus, hopefully, there will be no data loss.
 
Often this kind of problem can be corrected by obtaing the
manufacturers diagnostic software. For exmple in the case of
IBM/Hitachi hard disks, the Drive Fitness Test (DFT). Then the
software will detect bad sectors, move the data to good sectors and
then block-out the bad sectors so thet won't be used again.

This approach is good if it is a only a sporadic problem. If the
problem is ongoing with
Bad Sectors then a new hard disk would be warranted. However one can
use software such as
Drive Fitness Test (DFT), repair the problem and then proceed to Ghost
the disk to a
replacement hard
drive. Thus, hopefully, there will be no data loss.
Click to expand...

Very true. In our case we had several previous laptops with the same hard
drives go bad and we knew this one was due. So rather than go through running
the diagnostics, we got the laptop to boot and pulled the data off. Had it
been a new HD, we probably would have gone with the approach given here.

K. Brian Kelley, brian underscore kelley at sqlpass dot org
http://www.truthsolutions.com
 
Back
Top