- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add microsoft/win-dev-skills --skill windbg-kernel-bugcheck-triage -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add microsoft/win-dev-skills --skill windbg-kernel-bugcheck-triage -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add microsoft/win-dev-skills --skill windbg-kernel-bugcheck-triage -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add microsoft/win-dev-skills --skill windbg-kernel-bugcheck-triage -a grok -y在 Grok Bot 聊天中发送复制的消息。Bot 会从 GitHub 获取这个 SKILL.md,并添加到你所有 Bot 共享的技能中。
Install this skill: https://github.com/microsoft/win-dev-skills/tree/HEAD/plugins/windbg/skills/windbg-kernel-bugcheck-triage来自发布者
Load windbg-diagnostic-method first if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
Use a kernel crash dump or authorized live kernel session. A process dump captured after a reboot does not contain the earlier kernel fault. Confirm the dump type with the debugger, not a filename or the user's visible symptom. This skill includes exception-context and trap-frame recovery.
.symfix
.sympath+ <your-vendor-symbol-directory>
.reload
!analyze -v
.bugcheck
k
Replace the placeholder with the approved symbol location for your own binaries. Record dump type, target architecture/build, bugcheck code and parameters, faulting instruction, and available memory. Public Windows symbols suffice for many investigations; do not require private Windows source or PDBs.
Do not reuse a parameter layout across different bugchecks.
For 0x7E:
.exr <P3>
.cxr <P4>
kb
r
For 0x3B:
.cxr <P3>
kb
r
For other exception-style bugchecks, locate a valid saved exception/context
using the documented code procedure and available analysis output. Do not
guess .cxr arguments from arbitrary P1..P4 values.
When !analyze -v or verified stack evidence identifies a TRAP_FRAME:
.trap <trap-frame-address>
kb
r
Trap frames can be partial: some registers may be missing or reconstructed incorrectly. Note the debugger's warnings and do not treat unsaved registers as reliable evidence. If a frame is missing, malformed, or absent from the dump, report the limitation rather than scanning arbitrary pointers and claiming a recovered context.
!thread
lmvm <driver-module>
.frame /r <frame-number>
Inspect the recovered instruction, register/object used, IRQL, ownership,
and nearby driver frames. A crash in an operating-system routine may result
from prior driver corruption. Conversely, a third-party name in
MODULE_NAME does not establish that the named driver caused the failure.
Verify vendor build identity against the matching binary/PDB.
For concurrency or blocked requests use windbg-kernel-lock-deadlock-triage or
windbg-kernel-irp-lifecycle-triage. Kernel ~ commands select processors, not the
application thread list; use documented thread/process inspection such as
!thread and !process 0 7.
Record the decoded parameters, recovered context and its limitations, and the
evidence connecting the driver's operation to the violated invariant. Test
competing lifetime, bounds, IRQL, and synchronization explanations. Recommend
an instrumented test/repro only with approval; route Verifier evidence to
windbg-kernel-verifier-triage. Do not call a guessed module assignment a proven cause.
Follow FEEDBACK.md and submit only reviewed, sanitized feedback to
WinDbg-Feedback.
Include windbg-kernel-bugcheck-triage and the package version from plugin.json; no
automatic kernel dump, private-symbol, or source upload.
Use when a kernel dump reports a Windows bugcheck; decode parameters and recover exception or trap context before investigating your driver. Not for user-mode process crashes or blaming a module from
---name: windbg-kernel-bugcheck-triagedescription: Use when a kernel dump reports a Windows bugcheck; decode parameters and recover exception or trap context…---# plugins/windbg/skills/windbg-kernel-bugcheck-triage/SKILL.md概览
Use when a kernel dump reports a Windows bugcheck; decode parameters and recover exception or trap context before investigating your driver. Not for user-mode process crashes or blaming a module from its name alone.
常见问题
从发布者处下载 plugins/windbg/skills/windbg-kernel-bugcheck-triage/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/microsoft/win-dev-skills。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。