<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Socrates liang</title>
    <description>The latest articles on DEV Community by Socrates liang (@sitabanubanu).</description>
    <link>https://dev.to/sitabanubanu</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3966528%2Fe0fd187a-94f2-48b4-8cf3-2623c75a0c33.png</url>
      <title>DEV Community: Socrates liang</title>
      <link>https://dev.to/sitabanubanu</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/sitabanubanu"/>
    <language>en</language>
    <item>
      <title>I Built a Claude Code Skill That Diagnoses Windows BSODs Better Than I Can</title>
      <dc:creator>Socrates liang</dc:creator>
      <pubDate>Wed, 03 Jun 2026 12:18:05 +0000</pubDate>
      <link>https://dev.to/sitabanubanu/i-built-a-claude-code-skill-that-diagnoses-windows-bsods-better-than-i-can-3627</link>
      <guid>https://dev.to/sitabanubanu/i-built-a-claude-code-skill-that-diagnoses-windows-bsods-better-than-i-can-3627</guid>
      <description>&lt;h2&gt;
  
  
  The Problem
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I Built
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  How It's Different From Existing Tools
&lt;/h2&gt;

&lt;p&gt;Every existing BSOD tool stops at "here's the driver in the crash bucket." None of them:&lt;/p&gt;

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

&lt;h2&gt;
  
  
  What It Found On My Machine
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try It
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://github.com/sitabanubanu/bsod-analyzer" rel="noopener noreferrer"&gt;https://github.com/sitabanubanu/bsod-analyzer&lt;/a&gt;&lt;br&gt;
MIT license. 26KB. Drop it in ~/.claude/skills/ and say "diagnose my BSOD."&lt;/p&gt;

</description>
      <category>automation</category>
      <category>claude</category>
      <category>microsoft</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
