Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Once I have a dump of a computer crash/freeze, what are some tools and steps to take in order to troubleshoot crash based off of the dump itself?

I am looking for tools to isolate what processes or issues are causing the crash, and also good techniques in troubleshoot the actual dump itself. Once I've determined what the "troublesome" process has been, what do I do to troubleshoot the issue?

For example if I determine process foo.exe or bar.dll etc, is the problematic file how do I determine what can be done?

share|improve this question

I use these procedures :

Install Tools If you havn't got the windows debugging tools installed, then install the Microsoft Debugging Tools (Direct Link) Analyse The MiniDump To extract useful information out of the minidump file created:

  1. Open a command prompt (Start -> Run -> "cmd")
  2. cd \program files\debugging tools (Or wherever they are installed to)
  3. kd -z C:\WINDOWS\Minidump\Mini???????-??.dmp
  4. kd> .logopen c:\debuglog.txt
  5. kd> .sympath srv*c:\symbols*
  6. kd> .reload;!analyze -v;r;kv;lmnt;.logclose;q
  7. You now have a debuglog.txt in c:\, open it in a text edit (Notepad?).
share|improve this answer
If you'd rather not use the command line, you can launch WinDbg, set the Symbol path in the options, and just drag and drop the dump file in. (Bonus - the debugging log shows up right there.) – Shinrai Dec 21 '10 at 15:25

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.