DEV Community

Socrates liang
Socrates liang

Posted on

I Built a Claude Code Skill That Diagnoses Windows BSODs Better Than I Can

The Problem

I had 3 BSODs in 8 days on my Windows 11 laptop. Every tool — BlueScreenView, WhoCrashed, even WinDbg — could tell me WHAT crashed, but not WHY, and certainly not HOW to fix it.

What I Built

A Claude Code / Codex skill that runs a complete BSOD diagnosis pipeline in 7 stages. It doesn't just read the dump — it audits the entire system, finds root causes, generates a cleanup plan, and verifies after reboot.

How It's Different From Existing Tools

Every existing BSOD tool stops at "here's the driver in the crash bucket." None of them:

  • Decode pool tags to find third-party memory corruption
  • Detect ghost drivers (loaded in kernel, gone from disk)
  • Scan 18 system locations for remnants in parallel
  • Cross-reference against a knowledge base of 62 BugCheck codes
  • Generate a cleanup plan with rollback instructions
  • Re-verify after reboot

What It Found On My Machine

64+ driver remnants from software I uninstalled months ago. A VPN driver corrupting kernel pool on sleep/wake. And it correctly identified Ntfs.sys as the VICTIM of a third-party pool corruption, not the culprit.

Try It

https://github.com/sitabanubanu/bsod-analyzer
MIT license. 26KB. Drop it in ~/.claude/skills/ and say "diagnose my BSOD."

Top comments (0)