Windows crash help: read a blue screen minidump or MEMORY.DMP in your
This is a minidump reader online that never uploads your file. Drop a blue screen minidump or a full MEMORY.DMP and the parser reads it on your own PC, inside the browser tab.
Five steps
How the minidump reader online reads your dump
Same order every time, whether the file is a 300 KB minidump or a 16 GB MEMORY.DMP.
Find the dump file
Look in C:\Windows\Minidump for the small per-crash files, or C:\Windows\MEMORY.DMP for the full one. Sort by date and take the file written at the minute the machine went down.
Drop it on the analyser
The file is opened in place on your PC. Reads are byte-range on a background thread, so a full memory dump is handled the same way as a minidump. Nothing uploads and nothing installs.
Read the verdict and the reason
You get a plain sentence with a confidence level and why it landed there, then the fix plan, then the details. Where ntoskrnl.exe sits on the stack is explained rather than blamed.
Do it again after the next crash
One dump is one moment. If the PC keeps crashing, keep every dump Windows writes and read them all, because a module that turns up in three crashes matters more than one that turned up once.
Take the report with you
Copy, download or print it as Markdown or plain text, then paste it into a forum post or a support ticket instead of retyping a stop code from a phone photo.
03
How we work
A clear path from first conversation to finished work.
BSOD Dump Analyzer
Read a blue-screen minidump or MEMORY.DMP in the browser. Returns the stop code, the blamed driver, a fix plan and the evidence behind it, and explains why ntoskrnl.exe is usually the victim rather than the root cause.
WER and App Crash Reader
Open Windows Error Reporting files and app-crash minidumps to find the faulting module and exception code. Explains that a .wer file is a summary, not a full dump.
Certificate Decoder
Decode SSL and X.509 certificates, CSRs, keys and PFX files to show subject, issuer, expiry, SANs and fingerprints. Works offline, so there is no revocation check and the issuer signature is not proven against a trusted root.
.reg File Viewer
Read a registry file before you run it, with the keys, value types and locations laid out in plain language. Never stamps a file safe, and notes that a merge cannot be undone.
We will not ask you to hand a crash dump to a stranger, and we will not ask a language model to guess at a driver. The answer comes from the bytes in your file and a maintained reference library, and it tells you how sure it is.
Blue screen questions
The things people ask us after a blue screen
Six of the questions that bring people to this page, answered the way the report answers them.
My PC keeps crashing
Collect the dumps before you start changing hardware. Grab everything in the minidump folder, note the time of each crash, and read them together rather than reacting to the newest one.
ntoskrnl.exe is not the culprit
The Windows kernel is usually the victim. It is the code that noticed the damage and stopped the machine. The interesting name is the third party driver that was on the stack or had touched the memory first.
Graphics driver crashes and TDR
Display timeouts often surface a graphics module such as nvlddmkm in the dump. Seeing that name is a lead, not a sentence. We show what the file says and let you test it.
Stop codes explained
Each bugcheck gets its own explainer in the library, including IRQL_NOT_LESS_OR_EQUAL, with what the parameters mean and which checks are worth doing first.
Driver pages, vendor links only
The driver library is a maintained knowledge base with download URLs that point at the vendor. It is not live malware or antivirus scanning, and we never send you to a third party driver pack site.
What the report gives you
Verdict with confidence and reason, what to do, how we know, details, take it away, and a technical appendix. We describe the shape here and print your own results in the tool, never a made up sample.
05 — Common questions
What people check before they drop a dump file
Frequently Asked Questions
- Do you upload my dump file?
- No. The file is read on your machine by code running in your browser tab. There is no upload step, no copy kept on a server, and nothing about the dump is stored when you close the tab. That is the whole reason the tool works this way.
- Is there a size limit on MEMORY.DMP?
- No. Reads are byte-range, so the parser only pulls the parts of the file it needs rather than loading the whole thing into memory. A full memory dump sized to a large amount of RAM goes through the same path as a small minidump.
- The report keeps mentioning ntoskrnl.exe. Is that the cause?
- Usually not. The kernel is the component that detected the fault and halted the machine, so its name appears in most dumps. We say so plainly in the report and point at the third party module the evidence actually implicates, with the reason it was picked.
- Can you tell me exactly which driver broke my PC?
- We will not state a verdict for a machine we have not read. When you drop your own dump, the report names the module the evidence points at, gives a confidence level, and lists the observations behind it so you can judge the call yourself.
- Where do I find the minidump folder?
- Open C:\Windows\Minidump in File Explorer. Each blue screen adds a file stamped with the date and time. If that folder is empty, check for C:\Windows\MEMORY.DMP, which is the full dump Windows writes when it is configured to do so.
- Does an AI write the answer?
- No. The stop code, the module list and the fix plan come from the parser and the reference library. There is an optional second opinion that sees a short text summary of the finished report, never the file itself, and the report stands on its own without it.
Open the analyser and read your own dump
Take the file out of the minidump folder, drop it on the analyser, and read the stop code, the blamed module and the evidence on your own PC. It is free, and the file stays where it is.