What a DMP file is and why you might have one

A DMP file is a dump file — a snapshot of your computer's memory at a specific moment, usually captured when a program crashes or stops responding. Windows creates these files automatically when something goes wrong, and they sit on your hard drive as evidence of what happened. You won't need to open one unless you're troubleshooting a recurring crash, a technician asks you to find one, or you're trying to understand why a program keeps failing.

DMP files are technical in nature and not meant to be read like a document. They contain raw data in a format that requires special tools to decode. The good news is that you don't need to buy anything — Windows includes free tools that can read them, and you can also send them to someone who knows how to interpret the results.

Key Takeaways

  • DMP files are automatically saved by Windows in the Minidump folder when a program crashes, and you can find them by searching your hard drive.
  • The easiest way to read a DMP file is to open it with the Windows Event Viewer, which shows you what program crashed and when it happened.
  • For more detailed information about what caused the crash, you can use the free WinDbg Preview tool from Microsoft, though the output is technical and harder to interpret.
  • If a technician or support team asks for your DMP file, you can locate it, copy it to a USB drive or cloud folder, and send it to them for analysis.

Finding your DMP files on Windows

Windows stores DMP files in a specific folder on your hard drive. The location depends on which version of Windows you're running, but the process to find them is the same on all versions. Open File Explorer (the folder icon on your taskbar), then click the address bar at the top and paste this path: C:\Windows\Minidump. Press Enter, and you'll see a list of all the dump files your computer has created.

If that folder is empty, your computer hasn't experienced a crash that triggered a dump file, or the files were deleted. You can also search for DMP files across your entire hard drive: click the search box in File Explorer, type *.dmp, and Windows will show you every dump file stored anywhere on your computer. Each file is named with a date and time stamp, so you can identify which one corresponds to the crash you're investigating.

Opening a DMP file with Event Viewer

The quickest way to see what caused a crash is to use the Windows Event Viewer, which is built into every version of Windows. Right-click the Start button and select Event Viewer, or press the Windows key and type Event Viewer and press Enter. Once it opens, navigate to Windows Logs on the left side, then click System.

Look for entries marked as Error (shown with a red X) that occurred around the time your program crashed. Click on one of these entries and read the details in the panel below. The information will tell you which program crashed, what error code was generated, and sometimes a brief description of what went wrong. This is often enough to understand the problem without needing to decode the raw DMP file itself.

Using WinDbg Preview for detailed crash information

If you need more detailed information about what's inside a DMP file, Microsoft offers a free tool called WinDbg Preview. Download it from the Microsoft Store by opening the Store app, searching for "WinDbg Preview," and clicking Install. Once installed, right-click any DMP file, select Open with, and choose WinDbg Preview.

WinDbg will load the dump file and display technical information about the crash. The output includes memory addresses, function names, and a stack trace — a record of what the program was doing when it stopped. This information is dense and technical, meant for programmers or experienced support technicians. If you're not familiar with debugging, the Event Viewer approach above will give you the practical answer you need without the technical noise.

Sending a DMP file to a technician or support team

If a technician or software support team asks for your DMP file, you'll need to locate it and send it to them. Navigate to the Minidump folder (C:\Windows\Minidump) or wherever you found the file, right-click it, and select Copy. Then paste it into a USB drive, cloud storage folder like OneDrive or Google Drive, or attach it to an email if the file is small enough (most DMP files are under 100 MB).

Before you send it, ask the technician or support team what format they prefer — some may want the file uploaded to a secure portal, others may want it emailed directly. Let them know the date and time of the crash, what program was running, and what you were doing when it happened. This context helps them narrow down the cause faster than the DMP file alone.

What to do if you can't find your DMP files

If the Minidump folder is empty or doesn't exist, your computer may not be configured to save dump files automatically. You can turn this on in Windows settings. Right-click This PC or My Computer on your desktop, select Properties, then click Advanced system settings on the left. In the System Properties window, click the Advanced tab, then click Settings under "Startup and Recovery."

In the Startup and Recovery window, look for the section labeled "Write debugging information." Make sure the dropdown is set to something other than None — Small memory dump (256 KB) is a good choice that won't take up much space. Click OK and restart your computer. The next time a crash occurs, Windows will save a DMP file that you can examine.

Understanding what the crash information means

When you look at crash information in Event Viewer or WinDbg, you'll see an error code — a number like 0x0000007E or 0x00000050. These codes correspond to specific types of failures. A quick internet search for the error code plus "Windows" will usually point you toward common causes: a driver conflict, corrupted software, or a hardware problem. Write down the error code and the name of the program that crashed, and you'll have enough information to search for solutions online or describe the problem to a support team.

Keep in mind that a single crash doesn't always mean something is seriously wrong — programs can fail for temporary reasons that never happen again. If the same program crashes repeatedly with the same error code, that's a stronger signal that something needs to be fixed, such as reinstalling the program, updating drivers, or replacing hardware.

Frequently Asked Questions

Can I delete DMP files to free up space?

Yes, DMP files are safe to delete. They're only useful for troubleshooting, and once you've addressed the crash or sent the file to a technician, you can remove them. Right-click any DMP file and select Delete, or select multiple files and delete them all at once. Deleting them won't affect your computer's performance or stability.

Why is my DMP file so large?

The size depends on how much memory your computer was using when the crash happened. A full memory dump can be several gigabytes, while a small memory dump is usually under 256 MB. If you're having trouble sending a large file, ask the technician if a small memory dump is sufficient for their analysis, or use cloud storage instead of email.

What if WinDbg won't open my DMP file?

The file may be corrupted, or WinDbg may need to download symbol files from Microsoft to decode it properly. When you open the file in WinDbg, it will prompt you to download symbols if needed — allow it to do so. If the file still won't open, try Event Viewer instead, which requires no additional setup.

Do I need to send the DMP file if I already know which program is crashing?

Not necessarily. If you know the program and the error code, you can often find solutions online without the DMP file. Send the file only if the support team asks for it, or if you've tried basic troubleshooting (reinstalling the program, updating drivers) and the crashes continue.