A program keeps crashing? Read its crash report.
Windows writes a .wer report for every application crash. Drop it here (or an app-crash .dmp) and see which program died, which module took it down, and what the exception code means — parsed in your browser, never uploaded. You get a tickable fix plan, deep links into the exception library, and an optional AI second opinion on the text summary only.
Drop a .wer report or app-crash .dmp here
Drop Report.wer or .dmp files, or click Choose file(s). Nothing is uploaded.
Choose file(s)How it works
1
Find the report
ReportArchive / ReportQueue hold Report.wer files; CrashDumps holds app .dmp files. On a phone? Open this page on the PC and follow the on-screen paths.
2
Read locally
We decode AppName, FaultModule, ExceptionCode and signatures in your browser — the same evidence support desks ask for.
3
Fix with a plan
Tickable steps prioritize the faulting module, then the exception guidance, then hardware baselines when many apps fail.
Blue screen instead of an app crash?
If your whole PC crashed to a blue screen, that's a kernel dump — use our BSOD analyzer instead. This page is for single-program crashes.
Curious what the crash codes mean? Browse the exception-code reference, or the guides: find WER reports · PC keeps crashing.
Related tools
BSOD Analyzer
Read your blue-screen crash dump and get the guilty driver plus a fix plan.
Certificate Decoder
Inspect certificates, chains, CSRs, keys and .pfx bundles — locally.
.reg File Viewer
See what a .reg file actually does — and whether it looks safe to run.
File Identifier
Don't know what a file is? Drop it — we identify it by its bytes.