View Single Post
Old 12-06-06, 01:02 PM   #8
theluckyone17
Captain
 
Join Date: May 2006
Location: Niskayuna, NY
Posts: 482
Downloads: 103
Uploads: 0
Default

Quote:
Originally Posted by von Zelda
Thanks for the suggestion.

But there's never any message with a stop code. The screen goes blue with random letters for a second or two, then the computer reboots. Was never a real problem until it corrupted a audio driver last night. Did a restore and I back up with sound.
The BSOD should be listed in the Event Log (assuming WinXP here)... Off the top of my head, go to the Control Panel, open the Administrator's Tools, then the Event Log. You'll be looking in the System category. Might be easier to sort the events by the first column, and look at the red errors. Somewhere there should be an error with the same time as the BSOD occurred, and that'll give you the details.

Darn MS for that default "reboot on a BSOD" behavior...

I wouldn't blame SH3, SH3Commander, FS Autostart, etc. Usually (at least in XP), BSODs tend to be more driver or O/S related than higer level applications.
theluckyone17 is offline   Reply With Quote