In pursuit of the clearest crash explanation.
The desktop app runs on the machine that's having problems: it finds your .dmp files, explains the bugcheck in plain language, identifies the likely faulting driver, and builds an approximate call chain — Electron and PowerShell on the surface, a native C# helper reading real sensors underneath.
What makes it different
Plain language first
Every bugcheck is explained for a non-technical user by default. Details mode is one click away, never the default view.
No unattended changes
Driver rollback, System Repair, Windows Update uninstall — every system-changing action is one explicit click with its own UAC prompt.
Offline-first
Self-hosted fonts, inlined icons, no CDN scripts, no network calls the app doesn't strictly need.
Bilingual by design
Every string, dataset, and Wiki entry ships in English and Spanish from the same schema — not bolted on later.
Honestly labeled approximations
The call chain isn't a real symbolicated stack trace, and says so. The GPU test isn't a real 3D stress test, and says so too.
How it got here
Every phase below shipped real, committed code — not a placeholder. See the full roadmap for the complete, honest log.
Repo scaffold + minidump parser
The from-scratch .dmp parser, tested against hand-built synthetic fixtures matching the documented format.
Electron shell + first vertical slice
Crash analysis only — the first end-to-end path from a .dmp file to a plain-language explanation.
BSOD Code Wiki
A browsable reference of documented bugcheck codes, in English and Spanish.
Live monitoring
The sensor helper: CPU/GPU/memory/disk temps, clocks, load and voltages.
WinDbg-style Debug Console
A 30+ command text REPL over data the app already computes — no real kernel debugger, no DbgEng dependency.
Bootable USB tool
A Buildroot-based MemTest86-style diagnostic image, boot-tested end-to-end in QEMU.
Every angle on instability
From the crash you already had to the hardware fault you haven't found yet.