← ClaudeAtlas

bsod-analyzerlisted

Windows BSOD diagnosis. Prioritizes driver-caused crashes while checking hardware, storage, and firmware signals. Dump analysis -> audit -> cleanup plan -> prevention. Zero-dependency fallback.
sitabanubanu/bsod-analyzer · ★ 1 · AI & Automation · score 64
Install: claude install-skill sitabanubanu/bsod-analyzer
# BSOD Analyzer ## What This Skill Covers This skill is specifically for Windows blue screen / system crash diagnosis. It is NOT a general-purpose software debug skill. **Before starting, load these files from the same directory as this skill:** - `BugcheckKB.json` -- BugCheck code meanings, common causes, what to check - `KnownBadDrivers.json` -- Driver version ranges with known issues These are NOT optional. In the final report, state which BugCheckKB entries matched and which KnownBadDrivers entries were checked and found not to match. **Key differences from software bug diagnosis:** 1. **Crash artifacts ARE reproduction.** BSODs cannot and should not be intentionally triggered. Accept the following as proof a crash occurred: BugCheck event (ID 1001), minidump/MEMORY.DMP, Kernel-Power event (ID 41), abnormal shutdown event (ID 6008), Reliability Monitor entries. 2. **"Regression test" = observation window.** There is no test suite for kernel drivers. After a fix, the verification is time-based: observe 24-72 hours without recurrence. For stress verification: memory diagnostic (mdsched), disk stress, GPU stress. 3. **"Reproduce before fixing" does not apply.** Never try to trigger a BSOD on purpose. The dump file IS the reproduction. Analyze it, form a hypothesis, make one change, observe. 4. **Permission failures are expected.** Minidump files require admin to read. When blocked, CONTINUE with what you can access (event logs, Reliability Monitor,