Sysadmin Blog Just another IT Blog

2Aug/100

Find out what caused a BSOD

Of course you can use good old Google and find out what the BSOD stands for but this only gets you so far. (my favorite site with most BSODs on it is this one: http://www.aumha.org/a/stop.php)

If you want more and your computer has its pagefile on the C drive it will try to create a Crash dump Memory file under C:\Windows called Memory.dmp

This file you can analyze. I followed this instructions:
http://www.brighthub.com/computing/windows-platform/articles/29860.aspx

However you can simplfy this:

Go to this page: http://www.microsoft.com/downloads/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b&displaylang=en

Download the utility and run it. It will automatically detect the right version and guide you through the install.

Select components

On this screen only select the Common Utilities (I installed the Redistributable packages as well just to make sure everything works)

After it downloads and installs everything go into your start menu and open up WinDbg. Now click on File - Symbol File path and paste the following into the window:

SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

and click ok.

Now just open the crash dump .dmp file with file - open crash dump. Once analyzed it will let you know what file it thinks the problem file was.
( I in the past had a lot of luck when there were corrupt or buggy drivers on the system) If you end up with a .sys file you can usually Google it to find out what driver it is.

When it is down with analyzing you can click on the links in blue to get more inept (hint the "!analyze -v" is very helpful)

I hope that helps somebody with a BSOD problem

Andreas

UPDATE:

Correction from before: The only thing required to run the debugging  tools is the actual debugging tools under Common Utilities. Also the .net 4.0 is not required.

Tagged as: , , No Comments