[Ham-Computers] RE: Boot and reboot

[Hsu, Aaron (NBC Universal)]

The rebooting might be "normal behavior".  It depends on exactly what's going on.

By default Win2K/XP are configured to automatically reboot the system after a STOP error (aka B.S.O.D. or Blue Screen Of Death).  If what's causing the BSOD is loading during boot, then the system will be locked into an endless boot/reboot cycle until manual intervention.

Try booting into Safe Mode (press <F8> after the hardware POST, but before you see the Windows banner).  It should bring up a menu with options to boot into Safe Mode.  If you're able to boot into Safe Mode without problems, then the Windows kernel itself is fine and some other service/app that loads up in "normal" mode is causing the BSOD.  Note, however, that malware is known to mark itself as a "critical" component that also loads in Safe Mode - in these situations, you might be SOL - it would require more intervention that e-mails could provide.

Once in Safe Mode, you can configure Windows to actually stop (not reboot) after a STOP error (BSOD) - this will give you the ability to see exactly what STOP error occured.  To do this, open the System Properties control panel (Control Panel -> System) and click on the "Advanced" tab -> "Startup and Recovery <Settings>", and uncheck the box labeled "Automatically restart".  Then click OK to save the setting.

BTW, when Windows BSOD's, it also attempts to create a "dump" file for debugging purposes.  The default for Win2K/XP Pro is to create a "mini" dump in C:\WINDOWS\Minidump (or C:\WINNT\Minidump for Win2K) - this is basically just a simple stack and register dump, but it's usually enough (but not always) to at least identify what process killed Windows.  The minidumps are named using the date of the dump plus a sequential number.  The Windows debugging tools are needed to decode the dump.

So, David, boot into Safe Mode, configure Windows to actually stop on the STOP error, and write down the STOP code and any parameters it displays on the BSOD screen.  Ignore the "fluff" - you just need the STOP error number itself plus anything in the parenthesis "()" and the faulting module, if shown.  Then Google the STOP code or post it here.  If you find any dump files, e-mail me the latest one or two and I'll see if the Windows debugger gives shows me any clue as to what happened.  If you can, ZIP the file(s) first and then rename it to .PIZ as they filter ZIP attachments here.

73,

  - Aaron, NN6O


-----Original Message-----
Sent: Tuesday, November 06, 2007 11:06 AM
Subject: [Ham-Computers] Boot and reboot

I have had a Compaq, 500 mhz, running Win2000, computer running Echolink 
for over a year now. Last week the HD died so I replaced it with 80 gig 
HD. Installed Win2000 with no problems and shut it down. The next day I 
turned it on and it would boot, then reboot, boot, and reboot, on and on. 
I reformated the HD, installed Win2000 again and it was ok. It ran 6 
hours and then started to shut down and reboot, and boot and reboot.
This was a good running computer until I changed the HD.
Any ideas, David, K3ASI

--