Cannot load the Hive

  • Thread starter Thread starter DL
  • Start date Start date
D

DL

win2ksp4
Was having problems, decided to reinstall. All OK but on reboot and starting
win receive the blue screen msg
'Cannot load the hive
\system root\system32\config\default'
Then dump.
Have run chkdsk from recovery consul, all ok
Not sure how to procede, an guidence?
TY
 
DL said:
win2ksp4
Was having problems, decided to reinstall. All OK but on reboot and starting
win receive the blue screen msg
'Cannot load the hive
\system root\system32\config\default'
Then dump.
Have run chkdsk from recovery consul, all ok
Not sure how to procede, an guidence?
TY
Click to expand...

Press F8 during the early boot phase, then try booting
into "Last known good configuration" or into "Safe Mode".

When you "re-installed", did you do a clean installation
or did you install Win2000 over the top of the existing
installation?
 
You can restore the default hive using the most recent backup found in
%windir%\repair\regback


If no backups use the
original-as-installed default hive from
%windir%\repair\default
to
%windir%\system32\config\default

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup CD,
use another Windows 2000-based computer to create the Setup floppy disks. At
the "Welcome to Setup" screen. Press F10 or R to repair a Windows 2000
installation, and then press C to use the Recovery Console. The Recovery
Console then prompts you for the administrator password. If you do not have
the correct password, Recovery Console does not allow access to the
computer. If an incorrect password is entered three times, the Recovery
Console quits and restarts the computer. Note If the registry is corrupted
or missing or no valid installations are found, the Recovery Console starts
in the root of the startup volume without requiring a password. You cannot
access any folders, but you can carry out commands such as chkdsk, fixboot,
and fixmbr for limited disk repairs. Once the password has been validated,
you have full access to the Recovery Console, but limited access to the hard
disk. You can only access the following folders on your computer: drive
root, %systemroot% or %windir%

--

Regards,


Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
Background:
Using Sil mirror raid, started getting intermittent event errors on Sil
controller eg 'did not start'
Certain apps exhibited odd behaviour.
Broke the mirror, rebooted extreamly! slow boot.
Rebooted a number of times with differing err msgs.

Used last good config, ERD, Erdnt and recovery consul to restore backup and
default hives, all to no effect.
Tried a win reinstall on one hd, still get hive err.msgs.

Run hd manu checking utility over both disks for a number of loops, all ok
Run chkdsk all ok.

At this stage I'm tending towards mobo problem.
What think you?
TY

Dave Patrick said:
You can restore the default hive using the most recent backup found in
%windir%\repair\regback


If no backups use the
original-as-installed default hive from
%windir%\repair\default
to
%windir%\system32\config\default

To start the Recovery Console, start the computer from the Windows 2000
Setup CD or the Windows 2000 Setup floppy disks. If you do not have Setup
floppy disks and your computer cannot start from the Windows 2000 Setup
CD, use another Windows 2000-based computer to create the Setup floppy
disks. At the "Welcome to Setup" screen. Press F10 or R to repair a
Windows 2000 installation, and then press C to use the Recovery Console.
The Recovery Console then prompts you for the administrator password. If
you do not have the correct password, Recovery Console does not allow
access to the computer. If an incorrect password is entered three times,
the Recovery Console quits and restarts the computer. Note If the registry
is corrupted or missing or no valid installations are found, the Recovery
Console starts in the root of the startup volume without requiring a
password. You cannot access any folders, but you can carry out commands
such as chkdsk, fixboot, and fixmbr for limited disk repairs. Once the
password has been validated, you have full access to the Recovery Console,
but limited access to the hard disk. You can only access the following
folders on your computer: drive root, %systemroot% or %windir%

--

Regards,


Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

DL said:
win2ksp4
Was having problems, decided to reinstall. All OK but on reboot and
starting win receive the blue screen msg
'Cannot load the hive
\system root\system32\config\default'
Then dump.
Have run chkdsk from recovery consul, all ok
Not sure how to procede, an guidence?
TY
Click to expand...
Click to expand...
 
Used both repair and clean install on one hd

Pegasus (MVP) said:
Press F8 during the early boot phase, then try booting
into "Last known good configuration" or into "Safe Mode".

When you "re-installed", did you do a clean installation
or did you install Win2000 over the top of the existing
installation?
Click to expand...
 
Might be time for that clean install.

You'll want to boot the Windows 2000 setup disks or CD-Rom. The set of four
install disks can be created from your Windows 2000 CD-Rom; change to the
\bootdisk directory on the CD-Rom and execute makeboot.exe (from dos) or
makebt32.exe (from 32 bit) and follow the prompts.

Then *F6* very early and very important (at setup is inspecting your system)
in the setup to prevent drive controller detection, and select S to specify
additional drivers. Then later you'll be prompted to insert the manufacturer
supplied Windows 2000 driver for your raid controller in drive "A"

If you wait and then S to specify additional drivers, then it may be too
late as Windows 2000 Setup at this point may have already assigned the
resources your drive's controller is wanting to use.

When you get to the point, delete the existing NTFS and or other partitions
found. After you delete the partition(s) abort the install, then again
restart the pc booting the CD-Rom or setup disks to avoid unexpected drive
letter assignments with your new install.

Be sure to apply these to your new install before connecting to any network.

http://download.microsoft.com/download/E/6/A/E6A04295-D2A8-40D0-A0C5-241BFECD095E/W2KSP4_EN.EXE
http://www.microsoft.com/technet/security/bulletin/MS03-043.mspx
http://www.microsoft.com/technet/security/bulletin/MS03-049.mspx

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
Done the clean install, still gives hive errs,and others eg
Stop inaccessible boot device,
winnt/systm32\config\systemced missing or corrupt
Used a single good hd, no raid.


Dave Patrick said:
Might be time for that clean install.

You'll want to boot the Windows 2000 setup disks or CD-Rom. The set of
four install disks can be created from your Windows 2000 CD-Rom; change to
the \bootdisk directory on the CD-Rom and execute makeboot.exe (from dos)
or makebt32.exe (from 32 bit) and follow the prompts.

Then *F6* very early and very important (at setup is inspecting your
system) in the setup to prevent drive controller detection, and select S
to specify additional drivers. Then later you'll be prompted to insert the
manufacturer supplied Windows 2000 driver for your raid controller in
drive "A"

If you wait and then S to specify additional drivers, then it may be too
late as Windows 2000 Setup at this point may have already assigned the
resources your drive's controller is wanting to use.

When you get to the point, delete the existing NTFS and or other
partitions found. After you delete the partition(s) abort the install,
then again restart the pc booting the CD-Rom or setup disks to avoid
unexpected drive letter assignments with your new install.

Be sure to apply these to your new install before connecting to any
network.

http://download.microsoft.com/download/E/6/A/E6A04295-D2A8-40D0-A0C5-241BFECD095E/W2KSP4_EN.EXE
http://www.microsoft.com/technet/security/bulletin/MS03-043.mspx
http://www.microsoft.com/technet/security/bulletin/MS03-049.mspx

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

DL said:
Background:
Using Sil mirror raid, started getting intermittent event errors on Sil
controller eg 'did not start'
Certain apps exhibited odd behaviour.
Broke the mirror, rebooted extreamly! slow boot.
Rebooted a number of times with differing err msgs.

Used last good config, ERD, Erdnt and recovery consul to restore backup
and default hives, all to no effect.
Tried a win reinstall on one hd, still get hive err.msgs.

Run hd manu checking utility over both disks for a number of loops, all
ok
Run chkdsk all ok.

At this stage I'm tending towards mobo problem.
What think you?
TY
Click to expand...
Click to expand...
 
DL said:
win2ksp4
Was having problems, decided to reinstall. All OK but on reboot and starting
win receive the blue screen msg
'Cannot load the hive
\system root\system32\config\default'
Then dump.
Have run chkdsk from recovery consul, all ok
Not sure how to procede, an guidence?
TY
Click to expand...
time to run your harddrive and ram diagnostics
 
I believe the drive controler is faulty. ie
prior to win collapse I found numerous Event Log errors re drive controller
ie
'did not start within time out period' (from recollection)

Also I tried to instal an Adaptec controler card, however this could'nt be
installed. I tested this on another sys. and it was fine.
I therefore believe mobo is faulty.
TY

Dave Patrick said:
Make sure write cache is not enabled.

Possible Data Loss After You Enable the "Write Cache Enabled" Feature
http://support.microsoft.com/?id=281672

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q233541

You may have some bad RAM. The drive controller may be faulty.

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

DL said:
Done the clean install, still gives hive errs,and others eg
Stop inaccessible boot device,
winnt/systm32\config\systemced missing or corrupt
Used a single good hd, no raid.
Click to expand...
Click to expand...
 
Back
Top