What a DMP file is and why you have one

A DMP file is a memory dump — a snapshot of your computer's memory at a specific moment, usually captured when something went wrong. Windows creates these files automatically when your system crashes, a program stops responding, or you manually force a memory dump for troubleshooting. The file contains technical data about what your computer was doing at that moment.

You will most often find DMP files in your Windows folder after a crash, or in a folder you specified if you triggered the dump yourself. They are not documents you open to read like a text file or PDF. Instead, you open them with a debugger — a tool designed to read the technical information inside and help identify what caused the problem.

Key Takeaways

  • DMP files are memory snapshots created during system crashes and are opened with debugging tools, not standard programs.
  • Windows Debugger (WinDbg) is the official Microsoft tool for reading DMP files and is free to download.
  • You can also use third-party tools like BlueScreenView to view crash information without learning debugger commands.
  • The file location depends on the dump type: system crashes go to Windows\Minidump, while application crashes may be elsewhere.

Using Windows Debugger to open a DMP file

The official way to open a DMP file is with Windows Debugger (WinDbg), a free tool from Microsoft. Download it from the Microsoft Store or from the Windows SDK website. Once installed, right-click the DMP file, select "Open with", and choose Windows Debugger from the list. If it does not appear, click "More apps" and browse to find it.

When WinDbg opens your file, it will load the memory dump and display technical information in the command window. At the bottom, you will see a prompt where you can type commands. For a quick overview without learning commands, type !analyze -v and press Enter. This command tells WinDbg to analyze the dump and display a summary of what caused the crash, including the name of the driver or program involved.

The output will include a "Bugcheck" code (a number that identifies the crash type), the module that failed, and sometimes a description of the problem. This information is technical, but the module name alone often tells you which driver or program was responsible — for example, if it says "nvlddmkm.sys", that is your graphics card driver.

Using BlueScreenView for a simpler view

If you find WinDbg confusing, BlueScreenView is a free alternative that reads DMP files and displays the information in a clearer format. Download it from Nirsoft (search "BlueScreenView Nirsoft"), run the installer, and open the program. It will automatically scan your system for DMP files and list them with the crash date, crash code, and the driver or module that caused the problem.

Click any crash in the list to see more details in the lower pane. You will see the exact module name, memory address, and sometimes a description of what went wrong. BlueScreenView does not require you to learn debugger commands — it translates the technical data into a readable list. This makes it useful if you just want to know which driver crashed without diving into command-line tools.

Finding your DMP files on disk

Before you can open a DMP file, you need to know where it is. System crash dumps (the ones created when Windows itself crashes) are usually stored in C:\Windows\Minidump. Open File Explorer, paste that path into the address bar, and press Enter. You will see a list of files named something like "Mini010124-01.dmp" with the date in the filename.

If you do not see any files there, crashes may not have been saved. Go to Settings > System > About, scroll down and click "Advanced system settings", then click the "Advanced" tab. Under "Startup and Recovery", click "Settings". Make sure "Write an event to the system log" is checked and "Automatic memory dump" or "Small memory dump" is selected. Then click OK.

Application crashes (when a single program stops responding) may be stored elsewhere. Check the program's own folder, your Documents folder, or the AppData folder. Some programs save crash dumps in C:\Users\[YourUsername]\AppData\Local\[ProgramName]. If you triggered a manual dump, check whatever folder you specified when you created it.

Understanding what the dump tells you

Once you have opened the DMP file and run the analysis, you will see a module name — usually a .sys file (driver) or .dll file (program component). This name tells you what failed. Common examples include graphics drivers (nvlddmkm.sys for NVIDIA, amdkmdag.sys for AMD), network drivers, or Windows system files.

If the same driver appears in multiple crashes, that driver is likely the problem. You can update it, roll it back to an earlier version, or uninstall and reinstall it. If the module is a Windows system file like ntfs.sys or hal.dll, the problem may be hardware failure (bad RAM or a failing drive) rather than software. In that case, running a memory test or disk check is the next step.

The Bugcheck code is also useful. Common codes include 0x0000007E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED), 0x0000001A (MEMORY_MANAGEMENT), and 0x000000D1 (DRIVER_IRQL_NOT_LESS_OR_EQUAL). You can search the code online along with the module name to find more specific information about what went wrong.

When you cannot open or find a DMP file

If you have a DMP file but cannot open it with WinDbg or BlueScreenView, the file may be corrupted or incomplete. Try copying it to a different folder and trying again. If that does not work, the file may not be a valid memory dump — some files with a .dmp extension are not actually Windows memory dumps.

If you are looking for a crash dump but cannot find one, Windows may not be saving them. Check your Startup and Recovery settings as described above. You can also force Windows to create a dump by holding Ctrl+Scroll Lock+Scroll Lock on your keyboard (on some keyboards, you may need to hold Ctrl+Alt+Scroll Lock). This triggers a manual dump, which will be saved to your Minidump folder.

If you still cannot locate or open the file, consider taking a screenshot of any error messages you see and posting them in a tech support forum. The error message itself is often more useful than the dump file for getting help.

Frequently Asked Questions

Can I open a DMP file on a Mac or Linux computer?

DMP files are Windows-specific memory dumps and cannot be opened on Mac or Linux. If you need to analyze a dump on a different system, you would need to transfer it to a Windows computer first. Some online tools claim to read DMP files, but they are unreliable and may not work with all dump types.

Is it safe to delete DMP files?

Yes, DMP files are safe to delete. They take up disk space (sometimes hundreds of megabytes) and are only useful for troubleshooting. Once you have identified and fixed the problem, you can delete old dumps. To free up space automatically, go to Disk Cleanup (search for it in the Start menu), select your C: drive, and check "Recycle Bin" and "Temporary files". This will remove old dumps and other temporary files.

What if the DMP file is too large to open?

Large DMP files (over 1 GB) can take a long time to load in WinDbg or BlueScreenView. Make sure you have enough free RAM and close other programs first. If the file still will not open, try BlueScreenView instead — it is often faster with large files. If neither tool works, the dump may be corrupted.

Do I need to be an administrator to open a DMP file?

No, you do not need administrator rights to open a DMP file with WinDbg or BlueScreenView. However, you do need administrator rights to change Startup and Recovery settings or to trigger a manual memory dump using the keyboard shortcut.