Skip to content
PCTestHub
Home/Minidump analyzer

Minidump analyzer (.dmp): what caused your blue screen

Load the files Windows saves after a blue screen and see the error code, what it means and what to do, which Windows version it happened on and when. The file is read in your browser: it is never uploaded.

They are in C:\Windows\Minidump. If Windows will not let you open them there, copy them to your Desktop first (it asks for administrator permission). Only the first 8 KB of each file are read.

What the analyzer shows

  • The blue screen code (for example, 0x0000009F) with its name and a link to our page about it, with the most common causes and the steps to fix it.
  • The four parameters Windows saves with the code. A technician uses them to see which driver or memory address was involved.
  • The Windows version it happened on (from the build number) and whether that version still gets updates.
  • The date and time of the crash, the architecture (x64 or ARM64) and the number of logical processors.
  • If you load several files, which code repeats the most: it is the best clue to the cause.

Where the blue screen files are

After a blue screen, Windows saves a small memory dump in C:\Windows\Minidump, with a name like 112025-12345-01.dmp (the date comes first). If your settings save a complete or kernel dump, the file is C:\Windows\MEMORY.DMP and it can be several GB: the analyzer reads it too, because it only needs the header.

  1. Open File Explorer and go to C:\Windows\Minidump. If it asks for permission, accept it as an administrator.
  2. Copy the .dmp files to your Desktop or Documents.
  3. Drag them into the box above.

If the Minidump folder is empty

Windows may not be set to save dumps, or a disk cleanup may have deleted them. To save them next time: search for “View advanced system settings”, open Startup and Recovery → Settings and under Write debugging information choose Small memory dump (256 KB) or Automatic memory dump. Microsoft explains each option in its memory dump guide.

What it cannot tell you

The file header says which error happened, but not always which driver caused it: that takes analyzing the call stack with Microsoft's debugger (WinDbg, command !analyze -v). So we do not guess a culprit: you get the code, its page with the likely causes, and the data a technician needs to take it from there.

Frequently asked questions

Is the file uploaded to a server?

No. It is read in your browser with JavaScript and sent nowhere. Only the first 8 KB are read, where Windows stores the code and the crash data.

It says the file starts with “MDMP”. What is it?

That is a dump from a program that crashed (a game or the browser, for example), not from a blue screen. Programs or Windows Error Reporting save those. For a blue screen, look in C:\Windows\Minidump.

What does it mean when the same code repeats?

If every file has the same code, a single cause is most likely (a driver, the RAM or the drive, depending on the code). If each blue screen has a different code, it often points to hardware, such as the RAM or the power supply: check the page for each code.

Does it work on Windows 10 and Windows 11?

Yes. The header format has been the same for many years, on x64, ARM64 and 32-bit PCs.