- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add microsoft/win-dev-skills --skill windbg-user-exception-triage -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add microsoft/win-dev-skills --skill windbg-user-exception-triage -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add microsoft/win-dev-skills --skill windbg-user-exception-triage -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add microsoft/win-dev-skills --skill windbg-user-exception-triage -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/microsoft/win-dev-skills/tree/HEAD/plugins/windbg/skills/windbg-user-exception-triageDel publicador
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.
Start here for access violations, heap corruption, stack overflow, fail-fast, breakpoints, and other structured exceptions in a native application, service, or user-mode driver host process dump. This includes UMDF driver failures that occur in their user-mode host. Confirm the dump type from WinDbg; the filename extension alone does not distinguish user-mode from kernel-mode dumps.
.exr -1
.ecxr
k
!analyze -v
Record the exception code, address, parameters, access type, registers, module,
and stack. .ecxr selects the saved exception context when available. If no
exception context was captured, report that limitation rather than treating the
currently selected thread as the faulting thread.
Use matching binaries and PDBs for your modules and public Windows symbols. Investigate mismatches or truncated stacks before naming a failing source line.
Do not classify every address in a heap range as a lifetime bug. Check access type, faulting instruction, object layout, and valid allocation boundaries.
0xC0000409 / fail-fast: inspect exception parameters and the documented
fast-fail subcode, then the failing condition and call path. The historical
status name alone does not prove a buffer overrun or rule one out. Not every
fast-fail carries an HRESULT.0xC00000FD / stack overflow: inspect stack bounds and frame sizes; test
recursion, reentrancy, large frames, and inability to commit stack growth.
Use the memory-exhaustion skill when commit evidence supports that branch.0xE06D7363 / MSVC C++ exception: establish whether it was handled,
identify the throw/catch path with available symbols, and inspect the
exception information supported by the runtime/version. A first-chance throw
is not automatically a defect. This package does not decode thrown-object
layouts or fully diagnose noexcept/termination behavior.For this skill, follow the plugin's FEEDBACK.md and report a reviewed, sanitized
issue to WinDbg-Feedback.
Include windbg-user-exception-triage and the package version from plugin.json; do not
upload dumps or private source automatically.
Use when a native C/C++ app, service, or user-mode driver host (including UMDF) crashes with a structured exception in a dump or WinDbg session, including native faults inside managed processes. Not f
---name: windbg-user-exception-triagedescription: Use when a native C/C++ app, service, or user-mode driver host (including UMDF) crashes with a structured…---# plugins/windbg/skills/windbg-user-exception-triage/SKILL.mdResumen general
Use when a native C/C++ app, service, or user-mode driver host (including UMDF) crashes with a structured exception in a dump or WinDbg session, including native faults inside managed processes. Not for managed .NET exceptions, WinUI/XAML app errors, or kernel bugchecks.
Preguntas frecuentes
Descarga plugins/windbg/skills/windbg-user-exception-triage/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/microsoft/win-dev-skills.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.