# Evidence Raw data behind this case study. Times are local (UTC−8) unless a column says UTC. In the published copy, the user profile in paths is shown as ``, and machines go by stand-in names (tools\casestudy.py, PUBLISH.json). ## timeline Compiled from SERVER2's System log (6008, 41, 1001), the Hyper-V Worker log (VM starts and stops), the Application log (Windows Error Reporting) and the iLO's Integrated Management Log (IML), read on 2026-11-18. - `bugchecks.csv`: the 17 bugchecks of 2026-11-18, plus the earlier ones on 11-14 and 10-07. Windows' last-alive time (6008), the IML minute, the debugger's time where a dump exists, the CPU, and Microsoft's WER bucket. - `boot-cycles-2026-11-18.csv`: each boot of the loop. When it started, when its VMs started, how many virtual CPUs were running at the crash, and how long after the last VM start it died. - `vms.csv`: the VMs on SERVER2 and how the Kubernetes VMs were built. ## dumps kd output for the five minidumps that survived (`minidump-HHMM-analyze.txt`, `!analyze -v` and more) and for the full kernel dump of the 11:20:59 crash (`full-dump-1120-*.txt`, five passes). | File | Crash | CPU | |---|---|---| | `minidump-0913-analyze.txt` | 09:13:10 | 1 | | `minidump-0952-analyze.txt` | 09:52:27 | 3 | | `minidump-1011-analyze.txt` | 10:11:45 | 1 | | `minidump-1058-analyze.txt` | 10:58:06 | 1 | | `minidump-1120-analyze.txt` | 11:20:59 | 1 | | `full-dump-1120-*.txt` | 11:20:59 (MEMORY.DMP) | 1 | ## kd The targeted runs that found the storm. Each `kdq-m1-N-commands.txt` is the command file kd read, and `kdq-m1-N-output.txt` is what it printed. | Run | Dump | What it looks at | |---|---|---| | 1 | full | `vertarget`, every CPU's PRCB (interrupt counts and times, DPC data, idle thread, power state), `!cpuinfo` | | 2 | full | the DPC watchdog's profile buffer, every interrupt object on every CPU with its ISR and DPC counts, the TCP timer wheels, the threads waiting on CPU 1 | | 3 | 09:13 and 09:52 minidumps | stacks, PRCB, interrupt objects, pending DPCs (only the first dump loaded; see the log) | | 4 | 10:11 minidump | stack, PRCB, interrupt objects, `!dpcs`, profile buffer | | 5 | 10:58 minidump | the same | | 6 | 09:52 minidump | the same, plus the lock the CPU 3 DPC spins on | | 7 | full | `cpqcidrv`: module dates, its ISR and DPC disassembled, its interrupt object and ISR/DPC statistics, the objects sharing its vector | | 8 | 09:13 minidump | PRCB, the interrupt chain's ISR/DPC statistics, profile buffer | The walk over `PRCB.InterruptObject[]` in runs 2 to 6 uses offsets for this build of Windows Server 2019 (17763). Check them with `dt nt!_KINTERRUPT` before using it on another build. ## health - `hosthealth-2026-11-19-to-20.csv`: SERVER2's 15-minute health record since monitoring started on 11-19. It shows uptime, crashes, bugchecks, ASR and WHEA events, the busiest CPU's interrupts per second and DPC-plus-interrupt time, the VMs running, and the HP driver versions.