Irp is active with 7 stacks 6 is current (= 0xfffffa800ab61e08)
You can use various debugger commands to follow the LIST_ENTRY fields to examine the list of outstanding IRPs and the power IRP worker threads. The dt (Display Type) command displays the structure. +0x018 DelayedWorkQueue : 0xfffff800`01c6d2d8 _TRIAGE_EX_WORK_QUEUE Use the dt (Display Type) command and specify the nt!TRIAGE_9F_POWER structure using the address from Arg3.Ġ: kd> dt nt!TRIAGE_9F_POWER fffff8000386c3d8.The structure can provide a list of all outstanding power IRPs, a list of all power IRP worker threads, and a pointer to the delayed system worker queue.
The nt!TRIAGE_9F_POWER structure provides additional bug check information that might help you determine the cause of this bug check. You can use dx (display debugger object model expression), a debugger command, to display this: dx KiBugCheckDriver.
If a driver that is responsible for the error can be identified, its name is printed on the blue screen and stored in memory at the location (PUNICODE_STRING) KiBugCheckDriver. The verbose analysis displays the address of the nt!TRIAGE_9F_POWER structure, which is in Arg3.
To determine the specific cause and to create a code fix, programming experience and access to the source code of the faulting module is required.ĭebugging bug check 0x9F when Parameter 1 equals 0x3