What a .dmp file is and why you might have one

A .dmp file is a memory dump — a snapshot of everything your computer's RAM was holding at a specific moment, usually when something crashed or froze. Windows creates these files automatically when your system has a serious problem. You will find them in your system folders, often named something like "Memory.dmp" or with a date stamp.

Most people never need to open one. They exist for troubleshooting: if your computer blue-screened, restarted without warning, or locked up completely, the .dmp file contains clues about what went wrong. The file is raw data, though — not a document you can read like a text file or PDF.

Key Takeaways

  • A .dmp file is a memory dump created when Windows crashes, containing technical data about what your system was doing at that moment.
  • You cannot open a .dmp file in Notepad or Word; the data is binary and unreadable without specialized tools.
  • The Windows Debugger (WinDbg) is the standard tool for reading .dmp files, but it requires some technical knowledge to interpret the results.
  • For most users, sending the .dmp file to a technician or uploading it to a diagnostic service is faster than learning to read it yourself.
  • Your .dmp files are stored in C:\Windows\Minidump or C:\Windows\Memory.dmp, depending on your Windows version and settings.

Where Windows stores .dmp files on your computer

Windows saves memory dumps in specific folders depending on which type of dump your system created. Small dumps (minidumps) go to C:\Windows\Minidump. Full memory dumps go to C:\Windows\Memory.dmp. Kernel dumps may appear in either location.

To find your .dmp files, open File Explorer and navigate to C:\Windows. You may need to enable viewing hidden files: click the View tab at the top, then check "Hidden items". If you do not see a Minidump folder, your system has not created one yet, or dumps are being saved elsewhere due to your settings.

Why you cannot open .dmp files in Notepad or Word

.dmp files contain binary data — the raw contents of your computer's memory at the moment of the crash. Opening it in Notepad or Word will show you garbage characters and symbols because those programs expect text, not machine code. The file is not corrupted; it is straightforward not meant to be read as plain text.

Think of it like trying to read a photograph as if it were a book. The file exists and contains real information, but the tool you are using cannot translate it into something human-readable. You need a tool designed to parse binary memory dumps.

Using Windows Debugger (WinDbg) to read .dmp files

Windows Debugger, or WinDbg, is Microsoft's official tool for opening and analyzing .dmp files. You can read it free from the Microsoft Store or from the Windows SDK website. It is the standard tool used by technicians and system administrators.

After installing WinDbg, open the program and go to File > Open Dump File. Navigate to your .dmp file and select it. WinDbg will load the dump and display technical information about the crash: which driver or program was running, what error code occurred, and what was in memory at the time.

Reading the output requires technical knowledge. You will see memory addresses, hexadecimal values, and driver names. If you see something like "DRIVER_IRQL_NOT_LESS_OR_EQUAL" or "KERNEL_DATA_INPAGE_ERROR", those are the actual error codes that caused the crash. Searching those codes online often leads to solutions or known issues with specific hardware or software.

Sending your .dmp file to a technician instead

If WinDbg feels overwhelming, the faster route is usually to send the .dmp file to someone who reads them regularly. A local computer repair shop, your company's IT department, or a remote support service can open the file and tell you what went wrong in plain language.

To send a .dmp file safely, compress it first: right-click the file, select "Send to" > "Compressed (zipped) folder". This makes it smaller and easier to email or upload. Include information about when the crash happened and what you were doing at the time — that context helps a technician narrow down the cause.

What to do if you cannot find your .dmp files

If you have had crashes but cannot find .dmp files, Windows may not be configured to create them. Go to Settings > System > About, then click "Advanced system settings" on the right. In the System Properties window, go to the Advanced tab and click "Settings" under Startup and Recovery.

In the Startup and Recovery window, look for the "Write debugging information" dropdown. If it is set to "None", change it to "Small memory dump (256 KB)" or "Kernel memory dump". Click OK and restart your computer. The next time a crash occurs, Windows will create a .dmp file you can examine.

If crashes are happening frequently, do not wait to analyze the dump file yourself. Repeated crashes often point to failing hardware (bad RAM, overheating), driver conflicts, or malware. A technician can help you narrow down the cause faster than you can alone.

Frequently Asked Questions

Is it safe to delete .dmp files?

Yes. .dmp files are diagnostic snapshots, not system files your computer needs to run. Deleting them frees up disk space and does not harm your system. If you are having ongoing crashes, keep the most recent dump and delete older ones. Once you have fixed the problem, you can delete all of them.

Can I open a .dmp file on a Mac or Linux computer?

Not directly. .dmp files created by Windows are Windows-specific. If you need to analyze a Windows dump on a Mac, you would need to run Windows in a virtual machine or use specialized tools like Volatility, which is designed for memory analysis but requires command-line knowledge.

What does it mean if WinDbg shows "DRIVER_IRQL_NOT_LESS_OR_EQUAL"?

This error usually means a driver (software that controls hardware like your graphics card or network adapter) tried to do something it should not have. Search the error code online along with your hardware model — often the solution is updating or replacing the problematic driver.

How big are .dmp files?

A minidump is usually 256 KB to a few MB. A full memory dump can be as large as your total RAM — if you have 16 GB of RAM, the dump could be 16 GB. Most systems are set to create minidumps because they are small enough to store and email, but still contain the most useful crash information.

Do I need to do anything special before sending a .dmp file to someone?

Compress it to make it smaller, and let the person know roughly when the crash happened and what you were doing. You do not need to worry about privacy — .dmp files contain technical system data, not your personal files or passwords. If you are concerned, ask the technician to delete it after they analyze it.