Windows crash dump triage, without the debugger console.
Upload a Windows crash dump and get a root-cause report back — faulting module, bugcheck code, stack, and a plain-language summary. We read the header, run the right command set, and have AI read the output. Cases the automated passes can't settle go to an engineer, and so far in the pilot that's been most of them; we'll publish the automated share once we've measured it.
How it works
Tier 1 — automated read
A fixed set of WinDbg/CDB/KD commands runs against your dump and a model reads the output. Only a case the rules say is clear-cut is sent back without a human.
Tier 2 — deeper pass
Ambiguous cases run a wider command set and a stronger model, checking for agreement with the first pass.
Tier 3 — engineer review
Cases neither pass can settle go to an engineer, and heap corruption, memory-corruption exceptions or a crashing driver we can't identify always do. No false confidence.
Built for how ISVs actually ship
- Both dump formats. User-mode minidumps and full kernel-mode dumps go through the same pipeline — we detect which from the file header, you don't have to know.
- Redaction before any AI sees it. Debugger output is scrubbed for secrets before it reaches a model. See who processes what, and where.
- An audit trail, not a black box. Every command run against your dump is logged — never the output, only what was asked.
- Webhooks for your pipeline. Get notified the moment a report is ready instead of polling.
Currently onboarding pilot customers
Free while we build out the automation-rate baseline. Create an account to get an API key, or talk to us first if you need higher limits or an agreement in place.
Create an account