Need help debugging BSOD

Forums › Microsoft Windows › Need help debugging BSOD

andreashagen

18 posts

Geek

#38814 4-Aug-2009 17:28

That got your attention

Please help, I have a computer that keeps on blue screening and I want to learn how to analyze its' crash dump.

I have an idea how to collect the dump but would appreciate some guidance on analyzing the results. Are there any utilities that can automate this task? (wishful thinking).

Any assitance greatly appreciated.

A.

nate

6473 posts

Uber Geek
+1 received by user: 458

Retired Mod

Trusted

Lifetime subscriber

#242763 4-Aug-2009 23:56

andreashagen: I have an idea how to collect the dump but would appreciate some guidance on analyzing the results. Are there any utilities that can automate this task? (wishful thinking).

Write down whatever codes are displayed on screen and start Googling.

eXDee

4033 posts

Uber Geek
+1 received by user: 1070

Trusted

#242815 5-Aug-2009 08:19

Download debugging tools for windows. Install.
Google "microsoft symbol server", and find a line that says something like SRV*F:\Localsymbols*microsoft.com etc. Change the F to C (or any other drive).
Paste that whole line (without .sympath in the front), into "symbol file path" in the debugging tools menu.
Once done, go file, open crash dump > C:\WINDOWS\Minidump. Pick one.
It'll come up with some information, click analyse. It will show more, and look closer to the bottom for IMAGE_NAME, it'll be a .sys or .dll file.

garvani

1873 posts

Uber Geek
+1 received by user: 83

Trusted

#242828 5-Aug-2009 08:46

eXDee: Download debugging tools for windows. Install.
Google "microsoft symbol server", and find a line that says something like SRV*F:\Localsymbols*microsoft.com etc. Change the F to C (or any other drive).
Paste that whole line (without .sympath in the front), into "symbol file path" in the debugging tools menu.
Once done, go file, open crash dump > C:\WINDOWS\Minidump. Pick one.
It'll come up with some information, click analyse. It will show more, and look closer to the bottom for IMAGE_NAME, it'll be a .sys or .dll file.

Thats it.. I use ERD commander to automate this process, but its the same thing. If you posted what the bluescreen was we could tell you if its a specific problem such as unmountable_boot_volume which is a 10 minute fix.