What a DMP file is and why you might need to view one

A DMP file is a memory dump — a snapshot of everything your computer's RAM was holding at a specific moment, usually when a program crashed or your system froze. Windows creates these files automatically when something goes wrong. The file contains raw data about what was running, what went wrong, and where the problem occurred.

You might need to view a DMP file if your computer keeps crashing and you want to understand why, or if technical support asks you to send one so they can investigate. DMP files are technical documents — they're not meant to be read like a text file. You need specific tools to translate the raw data into something readable.

The most common DMP files are minidump files (usually around 64 KB to a few MB) and full memory dumps (which can be several gigabytes). Windows stores these in your system folders, and you can find them without special permissions.

Key Takeaways

  • DMP files are created automatically by Windows when programs crash or the system fails, and they contain a record of what was in memory at that moment.
  • You can view DMP files using the Windows Debugger (WinDbg), which is free from Microsoft, or by opening them in Notepad to see partial text information.
  • Minidump files are stored in C:\Windows\Minidump on most systems, and you can navigate there using File Explorer without any special tools.
  • If you're sending a DMP file to technical support, compress it first because full memory dumps can be several gigabytes in size.

Finding DMP files on your computer

Windows stores minidump files in a specific folder that you can reach through File Explorer. Open File Explorer, type C:\Windows\Minidump into the address bar at the top, and press Enter. You'll see a list of DMP files with names like "Mini010124-01.dmp" — the numbers indicate the date they were created.

If that folder is empty or doesn't exist, your system may not have created minidumps yet, or they may be stored elsewhere. You can also search for DMP files across your entire drive by opening File Explorer, clicking the search box, typing *.dmp, and waiting for results. This takes longer but finds all dump files on your computer.

If you want to check what's causing crashes before a DMP file is created, you can also look at the Event Viewer. Press the Windows key, type Event Viewer, and open it. Navigate to Windows Logs > System, then look for entries marked "Error" or "Critical" — these often reference crash information without needing a DMP file.

Using Windows Debugger to read DMP files

The Windows Debugger (WinDbg) is the standard tool for reading DMP files, and Microsoft provides it for free. read it from the Microsoft Store by searching for "Windows Debugger" or from the Windows SDK website. Once installed, right-click any DMP file, select "Open with", and choose Windows Debugger from the list.

When you open a DMP file in WinDbg, you'll see a command window at the bottom. Type !analyze -v and press Enter — this command tells WinDbg to examine the dump and explain what caused the crash in plain language. The output will show the faulting module (the program or driver that failed), the exception code (the type of error), and often a description of what went wrong.

The analysis output can be technical, but the key information is usually near the top: look for "Faulting Module" to see which program crashed, and "Exception Code" to see what type of error occurred. If you're sending this to support, you can copy the entire output and paste it into an email — that's more useful than the raw DMP file for most situations.

Reading DMP files in Notepad for quick information

If you don't want to install WinDbg, you can open a DMP file in Notepad to see partial information. Right-click the DMP file, select "Open with", and choose Notepad. You'll see a mix of readable text and unreadable characters — the readable parts are strings that were in memory when the crash happened.

Scroll through the Notepad window and look for program names, file paths, or error messages. You might see something like "ntdll.dll" or "kernel32.dll" (Windows system files) or the name of a program that was running. This won't give you the complete picture like WinDbg does, but it can sometimes point you toward the problem — for example, if you see a specific program's name repeated, that program was likely involved in the crash.

This method is useful for a quick look, but it's not reliable for diagnosing the actual cause. If you need real answers, WinDbg is worth the few minutes it takes to install.

Understanding what the crash information means

When WinDbg analyzes a DMP file, it shows you several pieces of information. The Faulting Module is the program or driver that was running when the crash happened — this is often (but not always) the cause. The Exception Code is a number that describes the type of error: 0xC0000374 means heap corruption, 0xC0000005 means an access violation (the program tried to read or write memory it shouldn't have), and 0x80000003 means a breakpoint was hit.

Look for the Bugcheck Code if it's a full system crash rather than a single program crash. Common codes include DRIVER_IRQL_NOT_LESS_OR_EQUAL (usually a bad driver), MEMORY_MANAGEMENT (RAM or storage problem), or CRITICAL_PROCESS_DIED (a Windows system process failed). WinDbg usually provides a brief explanation of what each code means.

If you see the same faulting module or exception code across multiple DMP files, that's a strong clue about what's wrong. For example, if five crash dumps all show "nvidia.sys" (the Nvidia graphics driver) as the faulting module, updating or reinstalling that driver is likely to fix the problem.

What to do after you've viewed the DMP file

Once you know which program or driver is causing crashes, you have several options. If it's a third-party program, try updating it to the latest version — crashes are often fixed in updates. If it's a driver (you'll see .sys in the filename), visit the manufacturer's website and read the newest driver version for your hardware.

If the faulting module is a Windows system file like ntdll.dll or kernel32.dll, the problem is usually not with Windows itself but with something conflicting with it — often a driver, antivirus software, or a program that modifies system behavior. Try uninstalling recently installed programs or drivers, or boot into Safe Mode to see if the crashes stop (Safe Mode loads only essential drivers).

If you're sending the DMP file to technical support, compress it first using Windows' built-in compression. Right-click the DMP file, select "Send to", and choose "Compressed (zipped) folder". This reduces a large file to a fraction of its size, making it easier to email or upload.

Frequently Asked Questions

Can I delete DMP files safely?

Yes. DMP files are only useful for diagnosing crashes after they happen. Once you've reviewed them or sent them to support, you can delete them to free up disk space. If your computer crashes again, Windows will create new DMP files. You can also disable DMP file creation in System Properties if you don't want them at all, though keeping them enabled is usually harmless.

Why is my DMP file so large?

Full memory dumps capture everything in your RAM at the moment of the crash, so they're as large as your installed RAM — if you have 16 GB of RAM, the DMP file will be roughly 16 GB. Minidumps are much smaller because they only capture essential information. You can change which type Windows creates in System Properties under "Startup and Recovery".

What if WinDbg won't open my DMP file?

The DMP file may be corrupted or incomplete. Try opening it in Notepad first to confirm it contains data. If Notepad shows mostly unreadable characters, the file is likely valid but just needs WinDbg. Make sure you've installed the latest version of Windows Debugger from the Microsoft Store, and try restarting your computer before opening the file again.

Do I need to be an administrator to view DMP files?

No. Minidump files in C:\Windows\Minidump are readable by any user account. Full memory dumps stored elsewhere may require administrator permissions, but you can usually take ownership of the file or copy it to a location you have access to. Right-click the file, select Properties, and check the Security tab if you're denied access.