WhyCrashed privacy and terms of use

1. You choose the file

   You drop a dump, error report, certificate, key, PFX, .reg file or unknown file onto the page. The browser hands our code a reference to the file on your disk. No network request carries those bytes.

2. The parser reads bytes locally

   Reading happens on a background thread using byte-range reads, so a 16 GB MEMORY.DMP is handled the same way as a 300 KB minidump. There is no upload and no size limit, and nothing read from the file is stored by WhyCrashed.

3. The report comes from the parser and

   The verdict, the evidence list and the confidence level are computed from the file bytes and our maintained stop code, driver, exception code and file type references. No language model writes that answer.

4. Optional AI second opinion, text only

   If you switch on the second opinion, only the short deterministic report text is sent. It is clipped in length and rate limited. Dump bytes, certificate files, private keys and .reg contents are never sent. Leave the step off, or let it error, and the full report still stands on

5. You take the report away

   Copy, download or print the report as Markdown or plain text for a forum post or a support ticket. Close the tab and there is nothing of your file left with us to keep.

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.

Frequently Asked Questions

Do you upload my crash dump?

No. The dump is opened by your browser from your own disk and parsed there. No part of the file is sent to us, and nothing read out of it is stored by WhyCrashed. That applies equally to a minidump, a full MEMORY.DMP, a .wer report, a certificate, a private key, a PFX file, a .reg file or a file you cannot identify.

Is there a file size limit?

No. The parser uses byte-range reads on a background thread, so it pulls only the regions it needs. A 16 GB MEMORY.DMP is handled the same way as a 300 KB minidump, and neither one has to travel across a network first.

What exactly does the optional AI step send?

Only the short deterministic report text that you can already read on screen. It is clipped in length and rate limited. Dump bytes, certificate files, private keys and .reg contents are never sent. If you leave the step switched off, or if it errors, the full report stands on its own without it.

What cookies or local storage does the site use?

Only the strictly necessary cookies or local storage the site itself needs to function. We do not build an advertising profile of you, and we do not sell or trade data about your visit.

Does a clean read mean my file is safe to open?

No. Viewing a .reg file or identifying an unknown file tells you what it is and what it would change. It is not a malware scan and it is not a safety certificate. We never stamp a file safe, and a registry merge cannot be undone once it runs.

Can you tell me if a certificate has been revoked?

No. The certificate decoder works offline, so it can show subject, issuer, expiry, SANs and fingerprints, but it cannot perform a revocation check and it cannot prove the issuer signature against a trusted root store. Check revocation with an online tool or the issuing authority.

Who do I contact about this page?

Send your question through the contact form and say which tool and which clause you are asking about. If it is a how question rather than a privacy one, the how it works page covers the client side parse, the evidence ledger and the confidence rules in more depth.