CODEWITHSUNDEEP
visual-studiodebuggingcrash-dumpsbsod
Dims
Dims

Reputation: 51039

How to debug / analyze BSOD dump in Visual Studio?

I had BSOD and it created DMP file in C:\Windows\Minidump. Then I opened this file with Visual Studion with File -> Open -> Crash Dump. It opens something, but nothing reasonable can be seen.

Is this correct way to start analyzing crash dumps?

What should I see in VS for it?

Can I see call stack for example?

The following appears in Debugger Immediate Window:

enter image description here

The similar appears with WinDbg:

enter image description here

No any keys or commands can be entered anywhere.

Upvotes: 2

Views: 2124

Answers (2)

Jack Zhai
Jack Zhai

Reputation: 6436

Based on the "Requirements and limitations" in this document here: https://msdn.microsoft.com/en-us/library/d5zhxt22.aspx, when a kernel-mode error occurs, the default behavior of Microsoft Windows is to display the blue screen with bug check data, to debug kernel-mode dump files in Visual Studio 2013, you need to download the Windows 8.1 Version of Debugging Tools for Windows.

About how to perform kernel-mode debugging in Microsoft Visual Studio:

https://msdn.microsoft.com/en-us/library/windows/hardware/hh451163(v=vs.85).aspx

About how to debug the windows dump file using the Windbg tool, you could get detailed steps here:

http://timtrott.co.uk/debug-windows-crash-dumps-minidump/

Like haindl's suggestion, you have to download the symbols from the Microsoft Server.

Upvotes: 1

magicandre1981
magicandre1981

Reputation: 28776

Analyze the dmps in Windbg. Get WinDbg via the Windows 10 SDK. During Setup select the Debugging Tools for Windows.

Now run Windbg.exe, load the dmp, fix your debug symbol path and run !analyze -v to start the automatic debugging. Look in MSDN documentation what the STOP code means and the other commands that you can use to debug the issue deeper.

Upvotes: 3

Related Questions