Please help - how to "see" stop error

  • Thread starter Thread starter Steve Miner
  • Start date Start date
S

Steve Miner

have a windows 2000 server machine that has the most
recent patches (updated the most recent (5) critical
updates last night). Today the machine, after working
fine for most of the day, is continously rebooting (have
anti-virus software and it's in a secure environment).
It loads bios and boot up sequence, gets to Windows 2000
screen and then just before the CTRL-ALT-DEL screen is to
show it hangs then gives a STOP error then reboots.

Problem is that the previous IT folks set it to reboot
(why is this the default Microsoft) when "system failure"
occurs. When the stop error shows (for a NANO second)
and reboots I obviously can't read the error message. My
question is how can I do this? Can I boot to the recover
console and use dumpchk to read the memory.dmp file or
can I read the system log within the recovery console???

Thanks in advance
 
From a parallel install, run regedt32.exe, then from the Local Machine Hive,
choose Registry|Load Hive, then navigate to the
%windir%\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.

Or possibly use a camcorder to catch the stop error.
 
To change the default reboot on fatal error, go to Control Panel, System Advanced tab, Startup and Recovery button. That should keep the blue screen up so you can write down the details. See this page for more information, http://www.mvps.org/marksxp/windowsxp/bsod.htm, and check the link there to Jim Eshelman's web page with extensive information on troubleshooting Stop messages.

--

Bill James
Microsoft MVP - Shell/User

Win9x VBScript Utilities » www.billsway.com/vbspage/
Windows Tweaks & Tips » www.billsway.com/notes_public/
 
Thanks for the help however two problems
This is a server using a Perc3di SCSI so booting up in
parallel is going to be tricky.
As for changing the configuration I would except the
problem is it never boots all the way up so I can't
change that setting
-----Original Message-----
From a parallel install, run regedt32.exe, then from the Local Machine Hive,
choose Registry|Load Hive, then navigate to the
%windir%\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\CrashCont rol
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.

Or possibly use a camcorder to catch the stop error.


--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft MVP [Windows NT/2000 Operating Systems]

Steve Miner said:
have a windows 2000 server machine that has the most
recent patches (updated the most recent (5) critical
updates last night). Today the machine, after working
fine for most of the day, is continously rebooting (have
anti-virus software and it's in a secure environment).
It loads bios and boot up sequence, gets to Windows 2000
screen and then just before the CTRL-ALT-DEL screen is to
show it hangs then gives a STOP error then reboots.

Problem is that the previous IT folks set it to reboot
(why is this the default Microsoft) when "system failure"
occurs. When the stop error shows (for a NANO second)
and reboots I obviously can't read the error message. My
question is how can I do this? Can I boot to the recover
console and use dumpchk to read the memory.dmp file or
can I read the system log within the recovery console???

Thanks in advance
Click to expand...


.
Click to expand...
 
Inline reply:

Steve miner said:
Thanks for the help however two problems
This is a server using a Perc3di SCSI so booting up in
parallel is going to be tricky.
Click to expand...
* What concerns?
As for changing the configuration I would except the
problem is it never boots all the way up so I can't
change that setting
Click to expand...
* Hence the reason for the parallel install.
 
Back
Top