- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add microsoft/win-dev-skills --skill windbg-kernel-irp-lifecycle-triage -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add microsoft/win-dev-skills --skill windbg-kernel-irp-lifecycle-triage -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add microsoft/win-dev-skills --skill windbg-kernel-irp-lifecycle-triage -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add microsoft/win-dev-skills --skill windbg-kernel-irp-lifecycle-triage -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/microsoft/win-dev-skills/tree/HEAD/plugins/windbg/skills/windbg-kernel-irp-lifecycle-triageDe l'éditeur
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.
Investigate I/O Request Packets in a kernel dump or authorized live kernel
session. Examples include 0x9F power failures and hangs where progress
depends on a driver request. Apply the parameter table for the specific
bugcheck subtype rather than assuming every 0x9F identifies the same object.
For 0x9F with P1 equal to 3, P4 is the blocked IRP. Inspect that directly
before running a system-wide search.
!analyze -v
!irp <irp-address>
When no request address is known and the dump has the required pool data:
!irpfind
!irpfind can be expensive in a live session and incomplete in a limited dump.
Use supported filters where appropriate. No result does not prove there are
no outstanding requests.
Record the major/minor operation, current stack location, device/driver stack, completion routine, pending flags, cancellation state, and any relevant thread. Use the available device stack and driver source to establish which component is expected to advance or complete the request.
Do not identify an offending driver solely by the last name printed in the IRP stack. A completion routine, downstream dependency, or framework-owned request may change the responsible path.
Preserve evidence between skills; avoid repeatedly handing the same unchanged IRP back and forth.
WDM and WDF have different ownership APIs. Do not transplant a raw WDM completion/cancel pattern into a framework-owned request without checking its contract. This skill establishes evidence; it is not a complete I/O protocol reference or a decoder for every power subtype.
Name the operation, current owner/dependency, and supported protocol violation or stalled path. Test normal completion, concurrent cancellation, removal, power transitions, and shutdown where relevant. If history is missing, propose an approved instrumented test using the verifier skill rather than inventing which driver lost the completion.
Follow FEEDBACK.md and report only reviewed, sanitized feedback to
WinDbg-Feedback.
Include windbg-kernel-irp-lifecycle-triage and the package version from plugin.json; no
automatic kernel dump or request-content upload.
Use when kernel evidence shows stalled I/O, a power IRP, or completion/cancellation misuse; inspect request state and driver ownership. Not for interpreting an empty IRP search in a limited dump as pr
---name: windbg-kernel-irp-lifecycle-triagedescription: Use when kernel evidence shows stalled I/O, a power IRP, or completion/cancellation misuse; inspect request…---# plugins/windbg/skills/windbg-kernel-irp-lifecycle-triage/SKILL.mdVue d'ensemble
Use when kernel evidence shows stalled I/O, a power IRP, or completion/cancellation misuse; inspect request state and driver ownership. Not for interpreting an empty IRP search in a limited dump as proof of healthy I/O.
FAQ
Téléchargez plugins/windbg/skills/windbg-kernel-irp-lifecycle-triage/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/microsoft/win-dev-skills.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.