If the system hive is corrupt, and assuming you already tried LKG (F8 and
choose Last Known Good), It may be possible to rename the system hive found
in
%windir%\system32\config\system
to system.old
then rename
%windir%\system32\config\system.alt
to
%windir%\system32\config\system
You can also try using the most recent backup found in
%windir%\repair\regback
If that fails you haven't much choice but to copy/ use the
original-as-installed system hive from
%windir%\repair\system
to
%windir%\system32\config\system
You'll need to reinstall the device drivers for any hardware added since the
original OS install.
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.
Press ENTER at the "Setup Notification" screen. Press 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%
To start the recovery console 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"
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
:
|
| I just had this problem on a Windows 2000 server this morning. How did
| you get into DOS? I'm running a Dell
| and it allows me into a setup utility and a RAID
| config utility, but upon escape it just attempts another
| re-boot. I cannot break out to DOS, I just see a C:
| prompt fly by before it starts the RAID utility.
|
|
|
| Jon wrote:
| > *From a cold startup my Windows 2000 system starts to bootup. It
| > gets to the graphical windows 2000 start up screen (the white blocks
| > get right to the end) just before the GUI appears and it reboots. It
| > does this 3 times and then goes into Windows normally. A blue screen
| > briefly appears with the following information before it reboots:
| >
| > STOP: c0000218 (registry file failure)
| > The Registry cannot load the hive (file):
| > \systemRoot\System32\config\SOFTWARE
| > or it's log or alternate.
| > It is corrupt, absent or not writable
| > Beginning dump of physical memory
| > Physical memory dump complete.
| > Contact your system technical support group.
| >
| >
| > When I finally get into Windows The event log has recorded the
| > following:
| >
| > The computer has rebooted from a bugcheck. The bugcheck was:
| > 0xc0000218 (0xe166e148, 0x00000000, 0x00000000, 0x00000000).
| > Microsoft Windows 2000 [v15.2195]. A dump was saved in:
| > C:\WINNT\Minidump\Mini010405-01.dmp.
| > Any ideas what this might be to do with?
| >
| > It always happens each day on a cold startup. It doesn't tend to
| > happen if I reboot it whilst it's been on for a while.
| >
| > Any ideas what might be causing this? *
|
|
|
| --
| uldmjl
| ------------------------------------------------------------------------
|
| ------------------------------------------------------------------------
| View this thread:
http://www.mcse.ms/message1326358.html
|
0xe166e148, 0x00000000, 0x00000000, 0x00000000). Microsoft Windows 2000