The !pcr extension displays the current status of the Processor Control Region (PCR) on a specific processor.
You may want to use the u, ub, uu (Unassemble) command to look deeper into the specifics of a the code that was running. K (Display Stack Backtrace) to look at what code was running when the stop code occurred. Use the following debugger commands to gather more information for failures with a parameter of 0: The offendingĬomponent can usually be identified with a stack trace.Īrg2: 0000000000000501, The DPC time count (in ticks).Īrg3: 0000000000000500, The DPC time allotment (in ticks). The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVELĪrg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The image name indicates that this code was executing when the bug check occurred. In this example, the tick count of 501 exceeds the DPC time allotment of 500. The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause. The offending component can usually be identified with a stack trace. The system cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above.
Parameter 1Ī single DPC or ISR exceeded its time allotment.
The meaning of the other parameters depends on the value of Parameter 1. Parameter 1 indicates the type of violation. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.