How to collect a WinDbg dump of a Visual Studio crash

Updated October 16, 2026 10:52

Install WinDbg

Run winget install Microsoft.WinDbg, or follow the steps in Install WinDbg from Microsoft.

Record a crash log

Create the C:\logs\ and C:\dump\ folders.
Start Visual Studio.
Start WinDbg.
Press F6 and attach to the devenv.exe process.
Enter these commands one by one:
```
sxd av
.logopen /t c:\logs\Output.txt
```
Press F5 to resume Visual Studio.
Reproduce the crash.

When Visual Studio crashes, enter these commands one by one:

.loadby sos clr
!PrintException
!ClrStack
~* e !ClrStack
~* k

Enter .logclose to save the log. The log file is in C:\logs\, and its name starts with Output.

Save a dump file

If JetBrains support asks for a dump file, enter one of these commands after step 8.

For a mini dump:

.dump /mdhiptu c:\dump\windbg_crash_dump.dmp

For a full dump:

.dump /map c:\dump\windbg_crash_fulldump.dmp

Send the files

Upload the log file, the dump file, and sos.dll from your machine to uploads.jetbrains.com, then share the Upload ID with JetBrains support. For Visual Studio 2022 and later, sos.dll is in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\. For Visual Studio 2019 and earlier, it is in C:\Windows\Microsoft.NET\Framework\v4.0.30319\.

For more details, see Uploading Large Files for JetBrains Support Team.

6 comments

Pat Tormey

Updated April 12, 2017 17:15

"start "windbg x86" executable file"

How would I do that?

Permanently deleted user

Updated April 21, 2017 10:18

To get WinDbg, you have to install WDK from Microsoft.

You can download wdksetup.exe from here: https://go.microsoft.com/fwlink/p/?LinkId=845980

Edited by Permanently deleted user April 21, 2017 10:18

Waleed El-Badry

Updated May 28, 2017 15:09

Whenever I try to follow the steps:

0:065> .logopen /t c:\logs\Output.txt
Log file could not be opened

Is that normal? After following steps, no log file is provided

Permanently deleted user

Updated August 09, 2017 16:49

0:065> .logopen /t c:\logs\Output.txt
Log file could not be opened

Is that normal? After following steps, no log file is provided

Probably the reason in why the logopen command is failing is basic you don't the need directory created. In this case, the directory is called logs. Had the same problem, I simply resolved it using the following command (.logopen /t c:\output.txt)

Vidanovicd

Updated November 29, 2021 09:09

Enter following commands:

"enter the following commands:

sxd av
.logopen /t c:\logs\Output.txt

Enter them where?

Permanently deleted user

Updated January 22, 2019 03:38

Summary of this Thread

Start with x86 verion WinDbg as below, Visual Studio run in x86 mode, not x64, otherwise you can't load sos.dll clr.dll to print exception
If you don't have WinDbg, download WDK(Windows Driver Kits) from Microsoft
Make sure the log folder is existing and you have permission of that folder
If you don't know how to use WinDbg, it has local document, just press F1 to read it.

Please sign in to leave a comment.

Have more questions?

Submit a request