Free full-debugger analysis with an AI explanation. No signup. Microsoft's own debugger (WinDbg) reads your crash dump, names the driver that caused it, and tells you how to fix it — usually in under a minute.
Your PC saves a crash report — a small file called a minidump — every time it blue-screens. When the PC is back up, open this site on the PC and upload that file for the exact cause and the fix.
Text or email yourself the link so it's one tap away later:
Where the file lives: on the PC, open File Explorer →
C:\Windows\Minidump → grab the newest .dmp file.
Drop your crash dump here, or click to choose a file
.dmp files up to 100 MB
Minidumps live in C:\Windows\Minidump\ — grab the newest one.
By uploading you agree to our Privacy Policy. Your dump is analyzed and deleted after processing.
Uploading…
Windows saves a crash dump every time it blue-screens. Drop the newest one from C:\Windows\Minidump\ above.
Our servers run your dump through Microsoft's WinDbg debugger with full debug symbols — the same tool support engineers use.
You get the stop code, the driver that caused it, the exact failing function, and an AI explanation of what to actually do about it.
Open File Explorer and go to C:\Windows\Minidump\. Each blue screen leaves a small .dmp file named by date (like 070426-12345-01.dmp). Grab the newest one. If the folder is empty, Windows may be set to a different dump type — search Start for "view advanced system settings" → Startup and Recovery → set "Write debugging information" to "Small memory dump".
No catch. Your dump is analyzed and then deleted after processing. What we keep is a de-identified technical summary of each analysis (stop code, faulting driver, stack symbols — no memory contents, no identifiers), and that summary is how the diagnosis engine gets smarter for everyone. If you want to help more, there's an optional checkbox to let us keep the dump file itself (auto-deleted after 90 days, deletable by you anytime). No ads, no accounts, no selling your data.
A minidump holds technical crash data: the stop code, the list of loaded drivers, kernel call stacks, and basic system info. It generally does not contain your documents, browsing history, or passwords, but it can include small fragments of system memory from the moment of the crash. Your uploaded dump is deleted from our servers right after processing — we retain only a de-identified technical summary of the analysis. Our privacy page explains exactly what we keep and who processes it. If you'd rather your dump never left your machine at all: the instant in-browser preview at whycrash.com, from the same team, runs entirely on your PC.
Five per day per network connection. That covers a normal debugging session with room to spare; it mostly exists to keep bots out.
No — if your Windows build is one we haven't seen before, the debugger has to download its debug symbols from Microsoft first, which can take a few minutes the first time. Try again shortly and it'll be fast. Every analysis after that for the same build is quick.
Up to 100 MB per file right now. The small minidumps in C:\Windows\Minidump\ are almost always enough to identify the cause, and they're usually under 2 MB.
The team behind WhyCrash. FixMyBSOD is our free lab: it helps people fix blue screens today, and the de-identified crash data it gathers makes crash diagnosis better for everyone.