To read minidump files on Windows 10, install WinDbg from the Microsoft Store, open it as administrator, click File > Open dump file, and choose a .dmp file from C:\Windows\Minidump. When it loads, type !analyze -v in the command box and press Enter. Look for the bug check name (like DRIVER_IRQL_NOT_LESS_OR_EQUAL) and the Probably caused by line, which usually names the driver behind the crash.
Below you’ll learn where minidumps are saved, how to read the results, and what to do next, including a simpler tool if WinDbg feels like too much.
What is a minidump file?
When Windows crashes with a blue screen, it saves a small crash report called a minidump in C:\Windows\Minidump. The file name includes the date, such as 092426-12031-01.dmp for September 24, 2026. It records the error code and which drivers were running, which helps you find the cause.
If the folder is empty, check that small dumps are turned on: search for View advanced system settings, click Settings under Startup and Recovery, and set Write debugging information to Small memory dump or Automatic memory dump.
How to read a minidump with WinDbg
- Open the Microsoft Store, search for WinDbg, and install it.
- Right-click WinDbg in the Start menu and choose Run as administrator (needed to read the Minidump folder).
- Click File > Open dump file and browse to C:\Windows\Minidump. Choose the most recent file.
- Wait for it to load. WinDbg downloads symbol files from Microsoft automatically, which can take a minute.
- Click the command box at the bottom, type !analyze -v, and press Enter.
How to understand the results
| Line | What it tells you |
|---|---|
| Bug check name and code | The type of crash, like MEMORY_MANAGEMENT or DRIVER_POWER_STATE_FAILURE |
| Probably caused by / IMAGE_NAME | The file most likely responsible, often a driver (.sys) |
| PROCESS_NAME | The program running when it crashed |
| STACK_TEXT | Technical details of what was happening. Useful for experts. |
Search the driver name to find what hardware it belongs to. For example, files starting with “nv” usually relate to graphics drivers, and files from your network or audio maker point to those devices. If it blames a core Windows file like ntoskrnl.exe, the real cause is often a driver or faulty RAM.
What to do after you find the cause
- Driver named: Update it from the device maker’s website, or roll it back in Device Manager if the crashes started after an update.
- Memory errors: Run Windows Memory Diagnostic (mdsched.exe).
- Different causes every time: Suspect hardware, like RAM, overheating, or the power supply. Run your PC maker’s diagnostics.
- Recent software: Uninstall antivirus, VPN, or system utilities installed around the time crashes began.
A simpler option: BlueScreenView
If you just want a quick summary, BlueScreenView from NirSoft lists each crash with the error and the driver involved, without commands. Download it only from the developer’s official website. It shows less detail than WinDbg but is much easier to read.
Frequently asked questions
Can I delete minidump files?
Yes. They’re only for troubleshooting. Disk Cleanup can remove them under System error memory dump files.
What’s the difference between a minidump and MEMORY.DMP?
MEMORY.DMP in C:\Windows is a larger dump with more detail. WinDbg opens both the same way.
Does this work on Windows 11?
Yes. Minidumps are in the same folder, and WinDbg works the same way.
Kermit Matthews is a freelance writer based in Philadelphia, Pennsylvania with more than a decade of experience writing technology guides. He has a Bachelor’s and Master’s degree in Computer Science and has spent much of his professional career in IT management.
He specializes in writing content about iPhones, Android devices, Microsoft Office, and many other popular applications and devices.