Skip to content

Free browser-based Windows diagnostics

A BSOD analyzer with no upload, plus readers for WER reports, certificates, .reg files and unknown files. Crash dumps decoded on the spot, your files never leave your computer, and no AI is involved in the answer.

Open the BSOD analyzer

See how it works

Three steps

From dump file to fix plan in three steps

Same routine whether you have a 300 KB minidump, a 16 GB MEMORY.DMP, a .wer report or a certificate you cannot read.

  1. Drop the file. It stays on the

    Parsing happens on a background thread in your browser using byte-range reads, so only the parts of the file we need are touched. A 16 GB MEMORY.DMP is handled the same way as a 300 KB minidump, and there is no size limit because nothing is being sent anywhere.

  2. Read the verdict and the evidence

    You get one plain sentence saying what went wrong, then a fix plan in order, then every observation with the source field it came from. When the evidence is thin the confidence drops and the report tells you which part is a guess. That is why ntoskrnl.exe gets explained as

  3. Take the report with you

    Copy it, download it, or print it as Markdown or plain text, then paste it into a forum thread or a support ticket. You are handing over a readable report instead of a dump file full of your own memory contents.

Read the full method

03

How we work

A clear path from first conversation to finished work.

  1. 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.

  2. 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.

  3. 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.

  4. .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.

Two things we refuse to do: ask you to upload a dump to a stranger, and skim a file so a language model can print a confident guess. The verdict comes from the parser and the reference library. Optional AI only ever sees the text of a report you already have.

Why Crashed, How the tools are built

Why this site exists

Read the privacy promise

Five tools

Pick the reader that matches your file

Each tool reads the bytes in your browser and checks them against a maintained library of 69 stop codes, 82 driver pages, 29 exception codes and 50 file types, with six walkthrough guides behind them.

05 — Common questions

Questions about the no-upload BSOD analyzer

The short versions are here. The full list, including how the optional AI second opinion works, is on the FAQ page.

Frequently Asked Questions

Do you upload my dump file anywhere?
No. Your browser opens the file from disk and the parser reads byte ranges out of it on a background thread. Nothing is sent to us, nothing is stored, and closing the tab is the end of it. That is the whole reason the site exists.
Is there a size limit on a MEMORY.DMP?
No. Because we never transfer the file, there is no upload cap to hit. We seek to the parts of the dump we need, so a 16 GB MEMORY.DMP is read in the same way as a small minidump.
Is ntoskrnl.exe the cause of my crash?
Usually not. The Windows kernel is often the module that notices the damage and calls the bug check, so it ends up named in the dump while a driver further down the stack is the real problem. The report explains which role each module is playing.
Can you tell me if a certificate has been revoked?
No. The certificate decoder runs offline in your browser, so there is no revocation lookup, and the issuer signature is not proven against a trusted root store. You get subject, issuer, expiry, SANs and fingerprints, which is enough to answer most questions.
Does viewing a .reg file mean it is safe to merge?
No, and the viewer never says that. It shows you the keys, value types and locations in plain language so you can decide. Merging is your call, and a merge cannot be undone.

Read the full FAQ

Drop the dump and read it yourself

Free, no account, nothing to install. Start with the blue screen tools, or come at it from the app crash side if it is a program that died rather than the whole machine.

Open the BSOD analyzer