Stop Errors and the System Log

Written by on Saturday, March 1, 2008 2:06 - 0 Comments

How to troubleshoot stop errors using the system log.

Usually when your system blue screens and you get a stop error, an event is written to your System log. This even is Event ID 1003 and has the event source System Error and it contains the error code and the four parameters from your start screen. It’s important to check for this event in Event Viewer if you have your system configured to automatically restart after a stop screen (this is the default) as you may never actually see the stop screen, but you’ll need the error code at the minimum in order to try and troubleshoot.

Just a warning though—not all stop screens write this event to the System log. Sometimes your system crashes in such a way that it simply can’t do this! If you think this is happening, configure your system *not* to automatically restart after a stop screen (unless it’s a mission critical server).

Article written by MyComputerAid.com



Leave a Reply

You must be logged in to post a comment.

2003 server - Sep 30, 2008 22:34 - 0 Comments

instant messaging srv records

More In Computers & PC


Microsoft Outlook - Mar 22, 2009 11:22 - 0 Comments

Outlook: Duplicates in Mailbox

More In Computers & PC