pdb files (such as the public OS symbols) do not *** pdb files that have full type information.
*** For some commands to work properly, your symbol path *** *** symbol name is typed or the network symbol server is down. *** appear to hang for long periods of time when an incorrect *** *** server shares in the symbol path may cause the debugger to *** *** enabling unqualified symbol resolution with network symbol *** *** of unqualified symbols by typing ".symopt- 100". *** fully qualified symbol module!symbolname, or enable resolution *** *** doesn't have full symbol information. *** Either you specified an unqualified symbol, or your debugger ***
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).Īrg4: fffff8011f3e9348, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which containsĪdditional information regarding this single DPC timeout 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.
0 kommentar(er)
