WinDbg Diagnostic Method
Apply this method alongside the bug-family-specific skill selected for an
investigation. Pattern matches route the investigation; they do not prove the
root cause.
Evidence ladder
Prefer direct evidence in this order:
- Faulting instruction/context, bugcheck or exception parameters, and resource
owners/waiters from the actual dump or trace.
- Matching symbols and the user's authorized source for the involved build.
- Allocation/free, Verifier, IRP, lock, ETW, WCT, or TTD history captured for
the same failure.
- Controlled reproduction and instrumentation.
- Pattern guidance as a hypothesis only.
Never claim commands, source access, or artifacts that are unavailable in the
session.
First-pass normalization
- Confirm process dump versus kernel dump and target architecture/build.
- Load public Windows symbols and matching symbols for user/vendor modules.
- Record missing pages, symbols, related-process dumps, trace scope, and tool
availability.
- User-mode exception:
.exr -1, .ecxr, stack, and registers.
- Kernel bugcheck:
.bugcheck, !analyze -v, then documented context/trap
recovery for that code.
- Hang: identify the affected operation, wait type, owner/server, and deepest
supported blocker.
- Memory: distinguish corruption, address-space pressure, and commit/limit
failures before choosing a fix.
Five-phase investigation
- OBSERVE: establish dump/trace type, architecture, symbols, code, stack,
registers, thread/resource state, and missing evidence.
- HYPOTHESIZE: form a specific primary mechanism and at least two plausible
alternatives when the evidence permits.
- TEST: identify direct debugger, source, trace, or reproduction evidence
that distinguishes the hypotheses. Absence of evidence is not evidence of
absence.
- EVALUATE: record supporting, contradictory, and missing evidence.
- CONCLUDE or PIVOT: name the violated invariant and verification plan, or
remain
candidate-pending-verification.
Routing index
| Evidence |
Skill |
| Native user-mode exception in an app, service, or UMDF/user-mode driver host |
windbg-user-exception-triage |
| User-mode heap corruption or allocation/free history |
windbg-user-heap-corruption-investigation |
| Cross-thread/process, COM/RPC, or service wait |
windbg-user-wait-chain-analysis |
| User-mode TTD history question |
windbg-user-ttd-reverse-debugging-triage |
| User-mode VA fragmentation, allocation failure, or commit pressure |
windbg-user-virtual-memory-exhaustion |
| Thread-affine lock across coroutine suspension |
windbg-user-mutex-held-across-co-await |
| Kernel bugcheck, trap frame, or saved context |
windbg-kernel-bugcheck-triage |
| Driver Verifier violation |
windbg-kernel-verifier-triage |
| Outstanding/power IRP, completion, or cancellation |
windbg-kernel-irp-lifecycle-triage |
| Kernel lock owner/waiter chain |
windbg-kernel-lock-deadlock-triage |
These are the complete bug-family routes. Continue evidence-led reasoning for
unsupported families; never dispatch to an absent skill.
Routing depth
- Fast (indicative diagnosis confidence >=0.80): validate the apparent
pattern, its required evidence, and plausible alternatives.
- Validate (0.40-0.79): test the leading pattern and at least one plausible
alternative through the full cycle.
- Full reasoning (<0.40 or no match): reason from observations and preserve
explicit uncertainty.
Confidence is explanatory judgment, not measured probability.
Trigger and fix gates
- Verify the trigger in the dump, disassembly, source, trace, or controlled
reproduction before declaring a final fix.
- Name the violated invariant and the parties or path that violate it.
- Separate the detector or victim from the original writer, freeing actor, or
resource holder.
- A fix must restore the violated invariant, not merely suppress the reproducer.
- If the trigger is unverified, use
candidate-pending-verification, set the
fix to null or a verification plan, and name the evidence/fix matrix needed.
- Do not blame a module solely from a bucket or
MODULE_NAME.
Fix-confidence calibration
Diagnosis confidence and fix confidence are separate. Every proposed fix must
declare fix_confidence and one fix_code_path_coverage value:
| Fix confidence |
Required coverage |
>=0.90 |
read-this-session: the actual fix path was read in this investigation. |
0.70-0.89 |
read-prior-session or symbol-or-disassembly: direct coverage exists, but the complete source path was not read in this investigation. |
0.50-0.69 |
pattern-only, or incomplete symbol/disassembly evidence. Treat the fix as a candidate. |
<0.50 |
not-read: no direct fix-path coverage. Keep the diagnosis candidate-pending-verification and set the fix to null or a verification plan. |
Lower confidence is always allowed when evidence quality, path coverage, or
alternatives warrant it. Never raise confidence to fit the table.
Independent review
Before finalizing a full diagnosis:
- When the host supports the bundled Copilot agents, invoke the
contrarian
agent once with the complete proposed diagnosis.
- When the host cannot run that agent, state that the independent review did
not run; do not silently substitute inline self-review.
- If the verdict is
CHALLENGED, test the counter-hypothesis with direct
evidence, then downgrade confidence or remain pending verification.
- Stop after one loopback. A second challenge remains pending verification.
Record contrarian_loopback as the Boolean true or false.
Report contract
A full report contains these H2 sections in order:
- Analysis
- Root Cause
- Fix
- Reasoning Chain
- Alternatives Considered
- Trigger Verification
- Mermaid
- Contrarian Verdict
- JSON Output Contract Summary
The Trigger Verification section must distinguish observed, contradictory, and
missing evidence plus fix validation. Mermaid must reflect verified evidence.
The JSON summary must include:
diagnosis_status
routing_path
root_cause
confidence
fix_confidence
fix_code_path_coverage
contrarian_review
contrarian_loopback
Deterministic report validation
After writing the report, run the bundled validator with PowerShell 7:
pwsh -NoProfile -File <skill-directory>\scripts\validate-diagnosis-output.ps1 `
-Path <diagnosis-markdown-path>
Use the installed windbg-diagnostic-method directory for
<skill-directory>. The script checks each section body independently,
requires at least two alternatives, accepts explicit or implicit Mermaid
participants, parses the JSON summary, and exits nonzero on failure.
Correct failed checks and rerun the script before presenting the report as
structurally complete. Structural validation does not replace technical review.
Safety and privacy
Dumps, traces, ETLs, CABs, source, paths, tokens, and memory contents can be
sensitive. Obtain authorization before capture, configuration changes, or
sharing. Verifier and Page Heap can disrupt workloads and require a recoverable
test plan plus restoration steps. Public feedback follows FEEDBACK.md and
defaults to a minimal reviewed summary with no automatic attachments.
Feedback
For feedback about this method or validator, follow the package FEEDBACK.md.
Do not attach private diagnosis files automatically.
1---2name: windbg-diagnostic-method3description: Use with every WinDbg plugin investigation to apply evidence-first reasoning, confidence calibration, contrarian review, structured reporting, and deterministic validation. Not a bug-family-specific triage skill.4user-invocable: false5metadata:6 source: https://skillmd.com/skills/microsoft/windbg-diagnostic-method7---89# WinDbg Diagnostic Method1011Apply this method alongside the bug-family-specific skill selected for an12investigation. Pattern matches route the investigation; they do not prove the13root cause.1415## Evidence ladder1617Prefer direct evidence in this order:18191. Faulting instruction/context, bugcheck or exception parameters, and resource20 owners/waiters from the actual dump or trace.212. Matching symbols and the user's authorized source for the involved build.223. Allocation/free, Verifier, IRP, lock, ETW, WCT, or TTD history captured for23 the same failure.244. Controlled reproduction and instrumentation.255. Pattern guidance as a hypothesis only.2627Never claim commands, source access, or artifacts that are unavailable in the28session.2930## First-pass normalization3132- Confirm process dump versus kernel dump and target architecture/build.33- Load public Windows symbols and matching symbols for user/vendor modules.34- Record missing pages, symbols, related-process dumps, trace scope, and tool35 availability.36- User-mode exception: `.exr -1`, `.ecxr`, stack, and registers.37- Kernel bugcheck: `.bugcheck`, `!analyze -v`, then documented context/trap38 recovery for that code.39- Hang: identify the affected operation, wait type, owner/server, and deepest40 supported blocker.41- Memory: distinguish corruption, address-space pressure, and commit/limit42 failures before choosing a fix.4344## Five-phase investigation45461. **OBSERVE**: establish dump/trace type, architecture, symbols, code, stack,47 registers, thread/resource state, and missing evidence.482. **HYPOTHESIZE**: form a specific primary mechanism and at least two plausible49 alternatives when the evidence permits.503. **TEST**: identify direct debugger, source, trace, or reproduction evidence51 that distinguishes the hypotheses. Absence of evidence is not evidence of52 absence.534. **EVALUATE**: record supporting, contradictory, and missing evidence.545. **CONCLUDE or PIVOT**: name the violated invariant and verification plan, or55 remain `candidate-pending-verification`.5657## Routing index5859| Evidence | Skill |60|---|---|61| Native user-mode exception in an app, service, or UMDF/user-mode driver host | `windbg-user-exception-triage` |62| User-mode heap corruption or allocation/free history | `windbg-user-heap-corruption-investigation` |63| Cross-thread/process, COM/RPC, or service wait | `windbg-user-wait-chain-analysis` |64| User-mode TTD history question | `windbg-user-ttd-reverse-debugging-triage` |65| User-mode VA fragmentation, allocation failure, or commit pressure | `windbg-user-virtual-memory-exhaustion` |66| Thread-affine lock across coroutine suspension | `windbg-user-mutex-held-across-co-await` |67| Kernel bugcheck, trap frame, or saved context | `windbg-kernel-bugcheck-triage` |68| Driver Verifier violation | `windbg-kernel-verifier-triage` |69| Outstanding/power IRP, completion, or cancellation | `windbg-kernel-irp-lifecycle-triage` |70| Kernel lock owner/waiter chain | `windbg-kernel-lock-deadlock-triage` |7172These are the complete bug-family routes. Continue evidence-led reasoning for73unsupported families; never dispatch to an absent skill.7475## Routing depth7677- **Fast (indicative diagnosis confidence >=0.80)**: validate the apparent78 pattern, its required evidence, and plausible alternatives.79- **Validate (0.40-0.79)**: test the leading pattern and at least one plausible80 alternative through the full cycle.81- **Full reasoning (<0.40 or no match)**: reason from observations and preserve82 explicit uncertainty.8384Confidence is explanatory judgment, not measured probability.8586## Trigger and fix gates8788- Verify the trigger in the dump, disassembly, source, trace, or controlled89 reproduction before declaring a final fix.90- Name the violated invariant and the parties or path that violate it.91- Separate the detector or victim from the original writer, freeing actor, or92 resource holder.93- A fix must restore the violated invariant, not merely suppress the reproducer.94- If the trigger is unverified, use `candidate-pending-verification`, set the95 fix to null or a verification plan, and name the evidence/fix matrix needed.96- Do not blame a module solely from a bucket or `MODULE_NAME`.9798## Fix-confidence calibration99100Diagnosis confidence and fix confidence are separate. Every proposed fix must101declare `fix_confidence` and one `fix_code_path_coverage` value:102103| Fix confidence | Required coverage |104|---|---|105| `>=0.90` | `read-this-session`: the actual fix path was read in this investigation. |106| `0.70-0.89` | `read-prior-session` or `symbol-or-disassembly`: direct coverage exists, but the complete source path was not read in this investigation. |107| `0.50-0.69` | `pattern-only`, or incomplete symbol/disassembly evidence. Treat the fix as a candidate. |108| `<0.50` | `not-read`: no direct fix-path coverage. Keep the diagnosis candidate-pending-verification and set the fix to null or a verification plan. |109110Lower confidence is always allowed when evidence quality, path coverage, or111alternatives warrant it. Never raise confidence to fit the table.112113## Independent review114115Before finalizing a full diagnosis:1161171. When the host supports the bundled Copilot agents, invoke the `contrarian`118 agent once with the complete proposed diagnosis.1192. When the host cannot run that agent, state that the independent review did120 not run; do not silently substitute inline self-review.1213. If the verdict is `CHALLENGED`, test the counter-hypothesis with direct122 evidence, then downgrade confidence or remain pending verification.1234. Stop after one loopback. A second challenge remains pending verification.124125Record `contrarian_loopback` as the Boolean `true` or `false`.126127## Report contract128129A full report contains these H2 sections in order:1301311. Analysis1322. Root Cause1333. Fix1344. Reasoning Chain1355. Alternatives Considered1366. Trigger Verification1377. Mermaid1388. Contrarian Verdict1399. JSON Output Contract Summary140141The Trigger Verification section must distinguish observed, contradictory, and142missing evidence plus fix validation. Mermaid must reflect verified evidence.143The JSON summary must include:144145- `diagnosis_status`146- `routing_path`147- `root_cause`148- `confidence`149- `fix_confidence`150- `fix_code_path_coverage`151- `contrarian_review`152- `contrarian_loopback`153154## Deterministic report validation155156After writing the report, run the bundled validator with PowerShell 7:157158```powershell159pwsh -NoProfile -File <skill-directory>\scripts\validate-diagnosis-output.ps1 `160 -Path <diagnosis-markdown-path>161```162163Use the installed `windbg-diagnostic-method` directory for164`<skill-directory>`. The script checks each section body independently,165requires at least two alternatives, accepts explicit or implicit Mermaid166participants, parses the JSON summary, and exits nonzero on failure.167168Correct failed checks and rerun the script before presenting the report as169structurally complete. Structural validation does not replace technical review.170171## Safety and privacy172173Dumps, traces, ETLs, CABs, source, paths, tokens, and memory contents can be174sensitive. Obtain authorization before capture, configuration changes, or175sharing. Verifier and Page Heap can disrupt workloads and require a recoverable176test plan plus restoration steps. Public feedback follows `FEEDBACK.md` and177defaults to a minimal reviewed summary with no automatic attachments.178179## Feedback180181For feedback about this method or validator, follow the package `FEEDBACK.md`.182Do not attach private diagnosis files automatically.