# Collect crash dumps

This section describes how to collect crash dumps in the following scenarios:

- Application crashes during launch
- Application crashes after launch (during runtime)

## Application crashes during launch

Startup crashes are crashes that occur before the UI appears or immediately after the app starts.  Use either of the following methods to collect dumps for startup crashes:

- Use Registry Editor for registry-based local crash dumps.
- Use ProcDump and image file execution options (IFEO) to automatically capture crash dumps when the app starts.

### Registry Editor

This method configures Windows to automatically collect crash dumps for all user-mode applications. Once set up, any app crash automatically generates a dump file.

1. Open Registry Editor (regedit.exe.).
2. Go to HKEY\_LOCAL\_MACHINE/SOFTWARE/Microsoft/Windows/Windows Error Reporting/LocalDumps.
3. Create or update the following:

    - DumpFolder (REG\_EXPAND\_SZ): Example: `C:\CrashDumps`
    - DumpCount (DWORD): 10
    - DumpType (DWORD): 2 (full dump)
4. Restart the system and then the app.

### ProcDump using IFEO

ProcDump is a command-line utility from Windows used for real-time monitoring and debugging. Use the image file execution options (IFEO) with ProcDump to automatically start debugging when a specified app starts. To generate dumps using ProcDump and IFEO, do the following:

1. Download [ProcDump](https://learn.microsoft.com/en-us/sysinternals/downloads/procdump) ![devhw](data:image/png;base64,UklGRt4AAABXRUJQVlA4TNIAAAAvD8ADED/BoG0jSe5SXP5I7gkNRG3byLnX4Tn+2K4I2raNw5/iqPxlEwBAGlwuj8BNBPpnsblrANx3P36s+DHQIcQ0dmEfEGPc8WEcCCcO/M2hXv3rDJTcHCTB1es7l9P2UoywA2a3jSW/pp77EhxGkq1E8zjH3R3e/fxjREOI6P8EcH+lqu/oTK/6kS+YwlHVAMjkP0ErP1UNIZZmnsB32Y2lZjNPO7HUUA1HkVWz73lAIiWM6WaegFcHzNOJ3bv89WhdNu1TDx/txhT2np2bzWU=).
2. Set IFEO debugger:

reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\<AppName>.exe" /v Debugger /t REG_SZ /d "C:\Tools\procdump.exe -e -ma"
        Copy to clipboard
3. Launch the app and ProcDump captures the crash dump when the app crashes.

## Application crashes after launch (during runtime)

These crashes occur after the app has launched, typically during user interaction or specific workflows. Use any of the following methods to collect dumps for crashes after launch:

- Use ProcDump (manual or triggered)
- Use Task Manager dump
- Use Registry-based local dumps
- Use Visual Studio for live debugging

### ProcDump (manual or triggered)

- Use the following command for on-demand or event-based dump collection.

procdump -e -ma <ProcessName or PID> <DumpFilePath>
        Copy to clipboard

    Example:

procdump -e -ma notepad.exe C:\CrashDumps\notepad.dmp
        Copy to clipboard

### Task Manager dump

To use Task Manager for a quick manual dump collection, do the following:

1. Open Task Manager.
2. Right-click the name of process you want to dump.
3. Select **Create Dump File.** The file is saved to %TEMP%.

### Registry Editor

This method also works for runtime crashes. Once configured, Windows automatically generates dumps when any user-mode app crashes, whether during start or runtime.

1. Open the Registry Editor (regedit.exe).
2. Go to HKEY\_LOCAL\_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps.
3. Create or update the following:

> 
> 
> - DumpFolder (REG\_EXPAND\_SZ)
> 
> 
>         Example: `C:\CrashDumps`
>     - DumpCount (DWORD)
> 
> 
>         Example: 10
>     - DumpType (DWORD)
> 
> 
>         2 for full dumps (recommended), 1 for mini dumps
4. Optionally, configure per-app settings by going to HKEY\_LOCAL\_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps\&lt;AppName&gt;.exe.
5. Restart the system and the app to apply the changes.

### Visual Studio live debugging (crash capture during execution) (no offline dump needed)

This method uses Visual Studio to run the application inside the debugger. If the app crashes during launch or runtime, Visual Studio breaks into the faulting code, allowing immediate inspection of the call stack, exception, and loaded modules.

Use this method to catch crashes as they happen, without needing to configure dump collection. This method is useful for both startup crashes and runtime faults.

To use Visual Studio for live debugging, do the following:

1. Open Visual Studio.
2. Go to **File &gt; Open &gt; Project/Solution.**
3. Select the .exe or associated project.
4. Press **F5** or click **Start Debugging.**
5. If the app crashes, Visual Studio breaks into the debugger. A dialog appears where you can see the call stack, exception info, and possibly the faulting DLL or module.

Last Published: Jun 16, 2026

[Previous Topic
Debug](https://docs.qualcomm.com/bundle/publicresource/80-62010-1/topics/debug.md) [Next Topic
Analyze crash dumps](https://docs.qualcomm.com/bundle/publicresource/80-62010-1/topics/debug-analyze-dumps.md)