How to generate "dump_crash" for SSMS , including ADD-in Tools
In case SSMS (SQL Server Management Studio) crashes, you can set up your system to automatically create a dump file for debugging purposes. Follow these steps to create the necessary registry keys.
Open the Registry Editor:
- Press Start, type Regedit, and press Enter to open the Registry Editor.
Navigate to the following path:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting
Create a new key:
- In the Windows Error Reporting folder, right-click and select New > Key.
- Name the new key LocalDumps.
Create a subkey for SSMS:
- Inside LocalDumps, create a new subkey named
ssms.exe
(the name of the executable file for SQL Server Management Studio).
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 | 2 for a full dump. |
CustomDumpFlags | DWORD (32-bit) Value | 1124 | Additional custom dump settings. |
Instructions for Adding Values:
Create the DumpFolder value:
- Select the newly created subkey (
ssms.exe
) in the tree on the left. - Right-click on the right side of the Registry Editor window and choose New > String Value.
- Name the value DumpFolder.
- Double-click the new DumpFolder value and set the data to:
D:\SSMS_Crashes
.
Create the DumpType value:
- Right-click again on the right side and choose New > DWORD (32-bit) Value.
- Name it DumpType.
- Double-click the new DumpType value and set the data to:
2
.
Create the CustomDumpFlags value:
- Right-click once more and choose New > DWORD (32-bit) Value.
- Name it CustomDumpFlags.
- Double-click CustomDumpFlags and set the data to:
1124
.
Final Result:
After completing these steps, your registry should look like this:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting\LocalDumps\ssms.exe
After the application finishes running, the dump will be placed in the specified folder. Please send it to us.
Related Articles
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 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 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 ...
dbForge SQL Tools Missing After Installing or Updating SSMS
Typically, upon the initial launch of SSMS after you install SQL Tools for the first time, there is a brief registration process that takes no more than 1-2 minutes, depending on your system's performance. If SQL Tools are still missing after this ...
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 ...