BSOD unreadable as system reboots before I can read it

[Guest]

Computer has suddenly started rebooting itself. This occurs when the
progress line gets to the end on the Windows 2000 screen. A BSOD appears for
less than a sceond and the computer reboots.

It happens if I try Safe mode as well.

I've absolutely no chance of reading the message.

I've tried different memory, removing the modem and disconnecting the HDD.

I put attached another HDD, and that booted up with no problems.

Can anyone suggest how I can find out what the error message on the BSOD is
please.

Thanks

JAckie

 

[Pegasus \(MVP\)]

Computer has suddenly started rebooting itself. This occurs when the
progress line gets to the end on the Windows 2000 screen. A BSOD appears for
less than a sceond and the computer reboots.

It happens if I try Safe mode as well.

I've absolutely no chance of reading the message.

I've tried different memory, removing the modem and disconnecting the HDD.

I put attached another HDD, and that booted up with no problems.

Can anyone suggest how I can find out what the error message on the BSOD is
please.

Thanks

JAckie

You can run the problem disk as a slave disk in some other Win2000/XP
PC, then edit the registry in off-line mode and set AutoReboot=0 here:
HKLM\SYSTEM\CurrentControlSet\Control\CrashControl

 

[Dave Patrick]

From a parallel install, run regedt32.exe, then from the Local Machine Hive,
choose Registry|Load Hive, then navigate to the
%systemroot%\system32\config
directory on the other install, and find the system file, then Open, in the
Key Name box give it some temp name, then under tempname, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\Select
and look in the Reg_Dword value of "Current", this is the current
controlset, then navigate to
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00x\Control\CrashControl
Where x = the value of "Current" (found above) and set the values as follows

"AutoReboot"=dword:00000000
"CrashDumpEnabled"=dword:00000001
"LogEvent"=dword:00000001
"Overwrite"=dword:00000001
Then navigate back up to "tempname" and choose Unload Hive, and boot your
original install, Autoreboot is now turned off so you should be able to read
the stop error.

Bug Check Codes
http://msdn.microsoft.com/library/e..._f55acfed-3296-4e84-8885-c3162fd0ddbf.xml.asp

If nothing else you can at least recover your data from the parallel install
prior to rebuilding the operating system.

This article may also help you.

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


--

Regards,

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

:
| Computer has suddenly started rebooting itself. This occurs when the
| progress line gets to the end on the Windows 2000 screen. A BSOD appears
for
| less than a sceond and the computer reboots.
|
| It happens if I try Safe mode as well.
|
| I've absolutely no chance of reading the message.
|
| I've tried different memory, removing the modem and disconnecting the HDD.
|
| I put attached another HDD, and that booted up with no problems.
|
| Can anyone suggest how I can find out what the error message on the BSOD
is
| please.
|
| Thanks
|
| JAckie

 

[Guest]

This worked, many thanks.

The problem is a registry error. I've tried the repair feature on the W2K
CD but that failed, so will reinstall.

Thanks again.

 

[Dave Patrick]

Glad to hear it helps.

You didn't mention the hive. Assuming the system hive and you already tried
LKG, 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.

If the software hive, it may be possible to rename the software hive found
in;
%windir%\system32\config\software
to software.old
then copy the most recent backup found in
%windir%\repair\regback
as
%windir%\system32\config\software

If that fails you can copy/ use the file
%windir%\repair\software
This file is an image of the hive at the time the OS was installed, so you'd
have to reinstall all software. This being the case you might just as well
blow it away and start a new install. (note: this would at least allow you
to start the OS to make any necessary backups prior to wiping the drive.)

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

:
| This worked, many thanks.
|
| The problem is a registry error. I've tried the repair feature on the W2K
| CD but that failed, so will reinstall.
|
| Thanks again.