local-bsod-debugging

Analyze Windows crash dumps locally to extract BugCheck codes and faulting drivers.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/gaos6e/MyOpenclaw --skill local-bsod-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-bsod-debugging
Source: https://github.com/gaos6e/MyOpenclaw/tree/main/workspace/skills/local-bsod-debugging
Command: npx skills add https://github.com/gaos6e/MyOpenclaw --skill local-bsod-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cdb.exe, and includes scripts (resource) components.

What problem does it solve?

Quickly diagnose Windows blue screen (BSOD) crashes by analyzing local dump files (MINIDUMP, MEMORY.DMP) to extract BugCheck codes, faulting modules, and driver information, enabling fast remediation.

Core Features & Use Cases

  • Local crash dump analysis: identify BugCheck codes, faulting drivers, and stack highlights without uploading data.
  • Guidance for remediation: provide actionable steps to update/rollback drivers or apply firmware updates based on findings.
  • Use Case: When a user reports the machine blue-screening after a specific driver update, run this skill to pinpoint the likely driver and recommended fixes.

Quick Start

Provide a Windows crash dump path to start a local analysis and obtain BugCheck details, modules, and remediation steps.

Frequently Asked Questions about local-bsod-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze a Windows minidump to find the driver causing a BSOD?

This Skill analyzes crash dump files locally to identify the faulting driver causing a BSOD. It extracts BugCheck codes and driver information from minidump or MEMORY.DMP files without requiring data upload.

Can I troubleshoot Windows crash dumps locally without uploading sensitive data?

Yes, you can troubleshoot crash dumps locally without uploading data. The Skill runs on-device analysis using cdb.exe and PowerShell scripts to process minidump files and return structured remediation steps.

Does Windows BSOD debugging work with both minidump and full MEMORY.DMP files?

Yes, BSOD debugging works with both minidump and full MEMORY.DMP files. The Skill processes these crash artifacts to extract BugCheck codes, faulting modules, and driver information for remediation.

What is the best way to pinpoint a faulting module after a Windows blue screen?

The best way to pinpoint a faulting module after a blue screen is to analyze the crash dump using cdb or WinDbg. This Skill automates that extraction, returning a structured report with risk factors and actionable remediation steps.

Do I need cdb.exe installed to diagnose Windows blue screen crashes with this tool?

Yes, you need cdb.exe installed because the Skill relies on it to execute local crash dump analysis. The bundled PowerShell scripts use cdb.exe to locate dumps and run the debugging commands for BugCheck extraction.