How to collect WinDBG dump for VS/ReSharper crash

Alexander Kurakin

Updated December 29, 2022 12:08

To download and install the WinDBG tool, please follow the steps from the article.

To collect a WinDBG dump you need to:

create c:\logs\ and c:\dump\ folders
start "windbg x64" executable file
hit F6 to attach to Visual Studio
enter the following commands:

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

hit F5 so Visual Studio will be running again
execute the repro steps
after it crashes, please enter the following commands one by one:

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

Then send Output file to ReSharper support.

Dump files:

In case you were asked to collect a mini dump file, please execute the following command:
```
.dump /mdhiptu c:\dump\windbg_crash_dump.dmp
```
Please create "dump" folder in a C disk root before executing a command.
In case you were asked to collect a full dump file, please execute the following command:
```
.dump /map c:\dump\windbg_crash_fulldump.dmp
```
Please create "dump" folder in a C disk root before executing a command.

Note: attach "C:\Windows\Microsoft.NET\Framework\v4.0.30319\sos.dll" from your machine to a support ticket

Hint: 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?

Christoph Moser

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 Christoph Moser 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

Shawn Girard

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