Guide Overview

The purpose of this guide is to teach you how to use the Event Viewer to find technical information on errors and crashes in your system. Please check the subsequent posts for updates to this guide - IE7 and non-BSOD errors in particular.

By default Windowswill log an event to the Event log when a system crashes. This tool can be used to find the Blue Screen of Death (BSOD) information if you didn't write it down. It's good for other crashes also. Here's a picture of a BSOD that I've annotated for your reference:



FWIW - this is also referred to as a STOP 0xD1 error (shorthand for the long stuff), and also is referred to as a BugCheck Code (BCC). They all mean the same thing for our purposes here.

Tools Needed
  • None

Windows Versions
  • Windows NT
    Windows 2000
    Windows XP
    Windows 2003
    Windows Vista

Instructions
  1. Go to Start, then to Control Panel, then to Administrative Tools, then to Event Viewer. Alternately, got to Start, then to Run, and type in "eventvwr.msc" (without the quotes) and press Enter. You'll see this:
  2. When the Event Viewer window opens, you'll see 2 panes (see picture above). The pane on the left will contain the 3 categories of events (they are Application, Security, and System). The pane on the right will reflect the messages for the category that is selected on the left. They will be listed as Information, Warnings, or Errors. Errors are what will concern us here.
  3. Left click once on the Application category in the left hand pane - then check the right hand pane for errors. Locate an error (example in the System description below) that occurred around the time of the problem (there may or may not be one here depending on the type of error). Then, right click on it and select "Properties". The information in the resulting window may be able to be used by board members to help troubleshoot your problem. Here's an example of it:
  4. Next, we'll do the same thing for the Security category. You'll left click on the Security category in the left hand pane, then will check for errors in the right hand pane. Locate an error (example in the System description below) that occurred around the time of the problem (there may or may not be one here depending on the type of error). Then, right click on it and select "Properties". The information in the resulting window may be able to be used by board members to help troubleshoot your problem. An example:
  5. Now, we'll do the same thing for the System category. You'll left click on the System category in the left hand pane, then will check for errors in the right hand pane. An example:

  6. Locate an error that occurred around the time of the problem (there may or may not be one here depending on the type of error). Then, right click on it and select "Properties". The information in the window may be used by board members to help troubleshoot your problem. Here's an example:
  7. Sometimes there will just be too many errors for you to pick just one out. In this case, generate a report using the "Action" menu item. Select "Export list" from the dropdown menu, and save it as a text file (that's the default). Then, open the text file by double clicking on it. Select the lines around the time that the error occurred by highlighting it with your cursor. Then, right click on the blue highlighting and select "Copy". Now, when you reply to your post, you can right click on the post and select "Paste" to insert the lines into your post. With this information, someone will be able to suggest which errors should be checked in detail.
  8. Lastly, a quick word about error messages. Often they will come in a format similar to this:
    STOP: 0x0000007B (0xEB82784C, 0xC0000034, 0x00000000, 0x00000000)
    These numbers are very important when diagnosing a problem with your system. They're written in hexadecimal notation, so they don't make much sense to most of us - but they do point to the errors and where they occur. Also, often a filename will be mentioned along with all these numbers. It's important so that we can tell where the error occurred (this isn't the same thing as what caused the error BTW)