How to Generate a "dump_crash" for SSMS, Including Add-in Tools
If SQL Server Management Studio (SSMS) crashes, it’s possible to configure your system to automatically generate a memory dump file. This file is essential for identifying issues related to both SSMS and integrated tools such as SQL Complete. This article explains how to configure Windows to capture crash dumps for ssms.exe using the Windows Error Reporting (WER) registry settings.
This method is compatible with all major SSMS builds, including installations performed using the SSMS installer or the latest SSMS 21 download.
Steps to Configure Automatic Dump File Creation for SSMS
1. Open the Registry Editor
- Press Start, type Regedit, and press Enter to open the Registry Editor.
2. Navigate to the Following Path
- HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting
3. Create a New Key
- In the Windows Error Reporting folder, right-click and select: New > Key
4. Name the New Key LocalDumps
- Within LocalDumps, create a new subkey: ssms.exe — this is the executable for SQL Server Management Studio.
5. Add the Following Values to the
ssms.exe Key| Name | Type | Data | Description |
|---|---|---|---|
| DumpFolder | String Value | D:\SSMS_Crashes | Folder where the dump files will be saved. |
| DumpType | DWORD (32-bit) Value | 2 | Value 2 indicates a full dump. |
| CustomDumpFlags | DWORD (32-bit) Value | 1124 | Additional custom dump configuration. |
Instructions for Adding Values
1. Create the DumpFolder Value
- Select the newly created ssms.exe subkey.
- Right-click on the right pane and choose: New > String Value
- Name it: DumpFolder
- Double-click and set the data to: D:\SSMS_Crashes
2. Create the DumpType Value
- Right-click again on the right pane: New > DWORD (32-bit) Value
- Name it: DumpType
- Double-click and set the data to: 2
3. Create the CustomDumpFlags Value
- Right-click again: New > DWORD (32-bit) Value
- Name it: CustomDumpFlags
- Double-click and set the data to: 1124
Final Result
After setup, the registry path should appear as:
- HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps\ssms.exe
Once SSMS (and any add-in, such as SQL Complete) crashes, a dump file will be automatically saved to the folder specified in DumpFolder. You can then forward the file for analysis or technical support via our contact form.
Related Articles
How to Create a Dump File from Task Manager for SSMS and Integrated Add-ins
In cases where SSMS (SQL Server Management Studio) or any integrated add-ins freeze or stop responding, a dump file can be generated for debugging purposes. This applies to both SSMS and the following dbForge add-ins for SQL Server: dbForge SQL ...How to Automatically Create a Dump File on Crash for Studios, Standalone Tools, and MiniTools
If a crash occurs, you can configure the system to automatically create a dump file for debugging purposes. Follow the steps below to create the required registry keys for different products, such as dbForge Studio, Standalone Tools, and MiniTools. ...How to Enable Logging for SSMS Add-ins Without Built-in Logging
Logging is essential for diagnosing complex issues and capturing technical details that may not be immediately visible through the user interface. When troubleshooting failures or unexpected behavior in SSMS add-ins that do not provide built-in ...How to Create a Dump File from Task Manager for Studios, Standalone Tools, and MiniTools
If you encounter issues with Studios, Standalone Tools, or MiniTools, you can generate a dump file using Task Manager for further troubleshooting. Follow these steps to create a dump file. Steps to Create a Dump File from Task Manager: Reproduce the ...What is the difference between Standalone applications and Add-Ins?
dbForge offers a suite of powerful MiniTools designed to streamline database development and administration. These tools come in two primary forms: standalone applications and add-ins, each catering to distinct user needs and workflows. 1. dbForge ...