CrashAtlas

Never claim untested things work.

CrashAtlas is a two-part diagnostic suite for Windows PCs that crash, run slow, or misbehave — built for non-technical users first, with a details mode and a WinDbg-style Debug Console for power users. When something can't be run in a given environment, that's said explicitly, rather than guessed at.

Design principles actually followed.

No unattended system changes

Every feature that modifies the system is one explicit user click away, shows its own UAC prompt, and never runs as a background auto-fix.

No custom kernel-mode driver

Sensor access rides on already-signed, already-trusted third-party drivers rather than a new EV code-signing + WHCP dependency.

Offline-first

Self-hosted fonts, inlined icons, no CDN scripts, no network calls the app doesn't strictly need.

Bilingual by design

Every user-facing string, dataset, and Wiki entry ships in English and Spanish from the same schema, not bolted on later.

Approximate is labeled as approximate

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.

Never claim untested things work

Every verification claim distinguishes unit-tested, typechecked, and confirmed-on-real-hardware as different tiers of confidence.

Where each component actually stands.

ComponentWhat's testedHow
tools/minidump-cliByte-level parsing correctnessHand-built synthetic .dmp fixtures matching the documented format, asserting correct extraction of bugcheck code, faulting module, system info.
Desktop app — servicesEvery core service, the report model, exporters, IPC-argument handlingnode:test + ts-node, 805+ tests, no Electron binary needed.
Desktop app — rendererType correctness of every route and the typed API layertsc --noEmit on a separate renderer tsconfig — the root typecheck alone can't see it.
Desktop app — UI renderingEvery screen actually renders, Tailwind/font/i18n wiring worksHeadless Chromium via Playwright, screenshotted across resolutions and both languages.
Desktop app — real hardwareActual Electron launch, real PowerShell output, real sensor valuesManual verification passes on a real Windows machine — this is where the elevation bug was found.
boot-image / diagtoolEvery test module's algorithm logic, the config and report modelsmake test (native host-gcc, assert-based) and make asan (AddressSanitizer/UBSan).
diagtool interactive UIThe ncurses menu, live progress bars, ASCII-art result bannersDriven programmatically over a real pty, asserting on actual terminal escape sequences.
boot-image boot pipelinegenimage.cfg / grub.cfg / post-build.sh / inittab actually produce a bootable imageQEMU + OVMF, using a host-package substitute for Buildroot's cross-compiled output.
boot-image on real hardwareNothing yetNeeds a completed Buildroot cross-build and a physical machine.
See the engineering decisions behind these tradeoffs

A large project, built in small, honest increments.

250+ numbered increments in the roadmap, every one with real, committed code behind it.

40
Bugcheck codes (EN/ES)
805+
Unit tests
30+
Debug Console commands
5
RAM test algorithms
3
CPU stress algorithms
2
Languages, same schema
250+
Roadmap increments shipped
3
Verification tiers, never blurred

News & roadmap

Every phase shipped, in order, with an honest account of what's verified.

See the roadmap