What a dump file is and why your computer created one
A dump file is a snapshot of your computer's memory at the moment something went wrong — usually a crash, a frozen program, or a system error. Windows and many programs automatically create these files so that engineers can figure out what caused the problem. The file itself is not dangerous; it is just data.
Dump files have names like "memory.dmp" or end with ".dmp" or ".hdmp". They are usually large (often hundreds of megabytes) and sit in folders you do not normally see, like C:\Windows\Minidump or inside a program's own folder. You do not need to open one unless you are trying to understand why something crashed, or a support person asked you to find one.
Most people never need to read a dump file. If your computer is running smoothly now, you can safely delete old dump files to free up space. If a problem keeps happening, a dump file can help you or a technician understand the pattern.
Key Takeaways
- Dump files are created automatically when programs crash or your system encounters an error, and they contain memory data from that moment.
- You can view dump files using the Windows Debugger (a free tool from Microsoft), but the information inside is technical and meant for support specialists.
- If your computer is working normally, you can delete dump files to recover disk space without any harm.
- Most dump files live in C:\Windows\Minidump on Windows, and you may need to show hidden files to see them.
- If a crash keeps repeating, saving the dump file and sending it to support can help identify the root cause faster than describing the problem alone.
Finding dump files on your Windows computer
Dump files are usually hidden by default, so your first step is to make hidden files visible. Open File Explorer, click the View tab at the top, then check the box next to "Hidden items". Now you can navigate to the folders where dump files typically live.
For system-level crashes, go to C:\Windows\Minidump. For program-specific crashes, look in the program's own installation folder — for example, C:\Program Files\ProgramName. Some programs also store dump files in your user folder under AppData\Local. If you are not sure where a program installed itself, right-click its shortcut, select Properties, and look at the "Start in" field.
Dump files are usually named with the date and time they were created, like "Mini010124-01.dmp" or "memory.dmp". If you see many of them, the oldest ones are probably from crashes you have already forgotten about.
Opening a dump file with Windows Debugger
The only tool built into Windows that can read dump files is the Windows Debugger, a free read from Microsoft. Go to microsoft.com, search for "Windows Debugger", and read the installer. Run it and follow the setup steps — you do not need to change any settings.
Once installed, right-click the dump file you want to open, select "Open with", and choose "Windows Debugger" from the list. If it does not appear, click "Choose another app", scroll down, and look for "WinDbg" or "Debugger".
When the Debugger opens, it will load the dump file and display technical information about what was running in memory when the crash happened. Most of this output is meant for programmers — you will see memory addresses, function names, and error codes. If you are sending this to a support person, you do not need to understand it; just let them open it themselves.
Reading the information a dump file contains
At the top of the Debugger window, you will usually see a line that says something like "EXCEPTION_ACCESS_VIOLATION" or "DRIVER_IRQL_NOT_LESS_OR_EQUAL". This is the error code — it tells you what type of problem occurred. A support person can use this code to narrow down the cause.
Below that, you will see a stack trace, which is a list of programs and drivers that were running when the crash happened. The name at the top of the list is usually the one that failed. If you see a driver name like "nvlddmkm.sys" (graphics driver) or "ntfs.sys" (file system), that is a clue about which part of your system caused the problem.
If you do not recognize the names or error codes, take a screenshot and send it to the support team for the program that crashed. They can interpret it much faster than you can, and they may already know the fix.
Deleting dump files to free up disk space
Dump files can be large, and old ones are safe to delete. If your computer crashed months ago and you have already fixed the problem, there is no reason to keep that dump file. Deleting it will not affect your computer's ability to create new ones if another crash happens.
To delete a dump file, right-click it and select Delete, or select it and press the Delete key. If you want to clean up all old dump files at once, go to C:\Windows\Minidump, select all the files (Ctrl+A), and delete them. Windows will ask for confirmation; click Yes.
If you are running low on disk space and want to prevent new dump files from being created, you can turn off automatic dump file creation in Windows settings. Go to Settings, search for "System Protection", click "System Protection" in the results, then click "Configure". Select "Disable system protection" and click OK. This is not usually necessary unless you are extremely short on space.
When to save a dump file for support
If the same crash keeps happening, do not delete the dump file — save it instead. Copy it to a folder on your desktop or a USB drive so you do not lose it. When you contact support for the program, tell them you have a dump file and ask if they want you to send it.
Most support teams prefer a dump file over a written description of a crash, because the file contains the actual data from the moment it happened. You can usually email it or upload it to a support portal. If the file is very large (over 25 MB), ask support how they prefer to receive it — some teams have a file-sharing service or an FTP upload.
Include the date and time the crash happened, what you were doing when it occurred, and any error message you saw on screen. This context helps support narrow down the cause even faster.
Dump files on Mac and Linux computers
Mac computers create crash logs instead of dump files, and they are much easier to read. When a program crashes, macOS usually shows you a dialog with an option to "Report" the crash. You can also find crash logs in Library/Logs/Diagnostic Reports. These are text files you can open in any text editor.
Linux systems create core dumps, which are similar to Windows dump files but are less commonly used for troubleshooting. Most Linux users rely on system logs instead, which you can view with the command "journalctl" in the terminal.
Frequently Asked Questions
Is it safe to delete dump files?
Yes, dump files are safe to delete. They are just data snapshots and do not affect how your computer runs. Deleting old ones will not prevent new ones from being created if another crash happens. If you are trying to troubleshoot an ongoing problem, keep the most recent dump file and delete the older ones.
Why is my dump file so large?
Dump files can be hundreds of megabytes because they contain a copy of your computer's entire memory at the moment of the crash. The more programs you had open, the larger the file. You can reduce future dump file size by turning off automatic dumps in System Protection settings, though this is rarely necessary.
Can I open a dump file in Notepad?
No, dump files are binary data and will show as gibberish in Notepad. You need the Windows Debugger or a similar specialized tool to read them. If you try to open one in Notepad, you will see random characters and symbols that are not useful.
What should I do if I cannot find the dump file?
Make sure hidden files are visible in File Explorer (View tab, check "Hidden items"). Check C:\Windows\Minidump first, then look in the program's installation folder. If the program crashed very recently, the dump file may still be writing to disk — wait a minute and refresh the folder. If you still cannot find it, the program may not have created one, or it may have been automatically cleaned up.
Do I need to send every dump file to support?
No, only send a dump file if the crash keeps happening or if support specifically asks for one. If your computer crashed once and has been fine since, there is no need to investigate further. Dump files are most useful for recurring problems that support needs to diagnose.