Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

* * * * - 3 votes

How To Find Bsod Error Messages

  • Please log in to reply
No replies to this topic

#1 usasma


    Still visually handicapped (avatar is memory developed by my Dad

  • BSOD Kernel Dump Expert
  • 25,091 posts
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:01:07 PM

Posted 09 December 2006 - 12:44 AM

How to Find BSOD (Blue Screen) Error Messages

Guide Overview

This guide will explain how to locate and analyze BSOD error reports. There are 4 places (by default) where Windows presents this information. If you've disabled the Error Reporting Service or the Event Viewer, then I'm afraid that you're just SOL :huh:

The Blue Screen of Death (also known as the BSOD) is a screen that Windows shows you when it shuts down your computer in order to prevent damage to it. It's also known as a STOP error or as a BugCheck Code. It is a hardware error by definition - but this doesn't mean that it's caused by faulty hardware. Viruses, corrupt drivers, and even poorly written programs can cause it.

Here's an example of the screen with some notations on what to look for:

Posted Image

Finally, a note on shorthand. A STOP 0x0000007a error is referred to (in shorthand) as a STOP 0x7a error. It's just a way of not having to write all them zero's out each time that you refer to it.

How To Disable Automatic Restarts
How To Use The Event Viewer
How To Debug Memory Dumps

  • The first place to get the information is from the Blue Screen itself. Write down all of the long numbers, the description that's in all Caps with underscores ( _ ) between the words, and any file names that may be mentioned (be sure to note if there wasn't a filename in your post). A more in depth look at this is included in the second reference ( How To Use The Event Viewer ).

    In the event that the BSOD flashes by too fast to read, use the first reference to disable the Automatically Restart function ( How To Disable Automatic Restarts ).

  • The next place to find the information is in the Event Viewer. Use the mini-guide in the second reference to see how to do this ( How To Use The Event Viewer ).

  • The last place to find the information is on your hard drive. Search your hard drive for files ending in .dmp and .mdmp. You're looking for the most recent file (or the one closest to the last BSOD that you experienced). Once you find it, use the third reference ( How To Debug Memory Dumps ) to perform an analysis of the memory dump. Be sure to use the !analyze -v command in the bottom of the Debugger's window before closing out your session. Then copy and paste the results into your next post. Someone will have a look at it to see if we can figure out what's gone wrong.

  • Sometimes, when Error Reporting is enabled, the dump files will be stored temporarily on your system and are erased once the report is sent. To save this info, you'll have to copy the dump file before sending the report. To do this, just click on the "Details" link in the error report and you'll see some file locations listed. Choose the one that ends in .dmp or .mdmp, locate it in Windows Explorer, and copy it to your Desktop (you'll have to enable viewing of hidden files to do this). Here's an example of the Details:

    ERROR REPORT CONTENTS Following files will be included in this error report
    C:\DOCUME~ 1\Owner\ LOCALS~1\Temp\WER7fde.dir00\Mini112706-02.dmp

Edited by usasma, 01 November 2008 - 08:48 AM.
Changed links

My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

BC AdBot (Login to Remove)


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users