Y
YanZhang_390
Guest
[COLOR=rgba(30, 30, 30, 1)]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8034b6fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3436
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4794
Key : Analysis.Init.CPU.mSec
Value: 656
Key : Analysis.Init.Elapsed.mSec
Value: 35061
Key : Analysis.Memory.CommitPeak.Mb
Value: 86
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8034b6fb320
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
TRAP_FRAME: ffffed89c08bf540 -- [/COLOR][COLOR=rgba(0, 0, 255, 1)](.trap 0xffffed89c08bf540)
[/COLOR][COLOR=rgba(30, 30, 30, 1)]NOTE: The trap frame does not contain all registers.
[/COLOR][COLOR=rgba(0, 0, 255, 1)]Some register values may be zeroed or incorrect.
[/COLOR][COLOR=rgba(30, 30, 30, 1)]rax=000000001ceb36f3 rbx=0000000000000000 rcx=ffffed89c08bf778
rdx=ffffed89c97b7450 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8034ac44567 rsp=ffffed89c08bf6d0 rbp=ffffed89c97b7260
r8=ffffed89c97b7260 r9=ffffed89c97b7270 r10=fffff8034af0c620
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KeYieldProcessorEx+0x17:
fffff803`4ac44567 4883c420 add rsp,20h
Resetting default scope
BLACKBOXBSD: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxbsd[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXNTFS: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxntfs[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXPNP: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxpnp[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9880`3231fc88 fffff803`4ae3adce : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9880`3231fc90 fffff803`4ac7541d : 0000174f`7a36ab33 ffff9880`32306180 00000000`00000246 00000000`0041149a : nt!KeAccumulateTicks+0x1c8bce
ffff9880`3231fcf0 fffff803`4ac759c1 : 00000000`00410f00 00000000`0026ca7e ffff9880`32306180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffff9880`3231fd40 fffff803`4ac6f833 : ffff9880`32306180 00000000`00000000 fffff803`4b631a80 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffff9880`3231fe80 fffff803`4ac781f2 : ffffed89`c08bf540 ffffed89`c08bf5c0 ffffed89`c08bf500 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffff9880`3231ff30 fffff803`4ad27f55 : 0000009b`2ad20145 ffffa985`708ea500 ffffa985`708ea5b0 ffff1d1a`e1ff0733 : nt!HalpTimerClockInterrupt+0xe2
ffff9880`3231ff60 fffff803`4adf785a : ffffed89`c08bf5c0 ffffa985`708ea500 00000000`80000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9880`3231ffb0 fffff803`4adf7dc7 : 00000000`00000000 ffff9880`3230e1c8 ffffed89`c97b7450 fffff803`4adf7dd4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffed89`c08bf540 fffff803`4ac44567 : ffffffff`ffffffd1 fffff803`4af0c6e9 00000000`00000010 00000000`00000286 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffed89`c08bf6d0 fffff803`4af0c6fc : 00000000`00000001 ffffed89`c08bf710 00000000`00010001 00000000`00000000 : nt!KeYieldProcessorEx+0x17
ffffed89`c08bf700 fffff803`4ac0781e : ffff9880`32309240 ffffed89`c08bf860 00000000`00000000 ffffa985`1ceb36f3 : nt!KiConfigureHeteroProcessorsTarget+0xdc
ffffed89`c08bf760 fffff803`4ac06b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffffed89`c08bf8d0 fffff803`4adf991e : ffffffff`00000000 ffff9880`32306180 ffff9880`32311440 ffffa985`a4d66080 : nt!KiRetireDpcList+0x1f4
ffffed89`c08bfb60 00000000`00000000 : ffffed89`c08c0000 ffffed89`c08b9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: nt!KeAccumulateTicks+1c8bce
MODULE_NAME: [/COLOR][COLOR=rgba(0, 0, 255, 1)]nt
[/COLOR][COLOR=rgba(30, 30, 30, 1)]IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1c8bce
FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}
Followup: MachineOwner[/COLOR]
[COLOR=rgba(30, 30, 30, 1)]I have the Minidump file and system info here at this link as well if someone is able to help[/COLOR]
Crash Laptop
Continue reading...
* *
* Bugcheck Analysis *
* *
*******************************************************************************
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8034b6fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: TickPeriods ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 3436
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4794
Key : Analysis.Init.CPU.mSec
Value: 656
Key : Analysis.Init.Elapsed.mSec
Value: 35061
Key : Analysis.Memory.CommitPeak.Mb
Value: 86
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff8034b6fb320
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
TRAP_FRAME: ffffed89c08bf540 -- [/COLOR][COLOR=rgba(0, 0, 255, 1)](.trap 0xffffed89c08bf540)
[/COLOR][COLOR=rgba(30, 30, 30, 1)]NOTE: The trap frame does not contain all registers.
[/COLOR][COLOR=rgba(0, 0, 255, 1)]Some register values may be zeroed or incorrect.
[/COLOR][COLOR=rgba(30, 30, 30, 1)]rax=000000001ceb36f3 rbx=0000000000000000 rcx=ffffed89c08bf778
rdx=ffffed89c97b7450 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8034ac44567 rsp=ffffed89c08bf6d0 rbp=ffffed89c97b7260
r8=ffffed89c97b7260 r9=ffffed89c97b7270 r10=fffff8034af0c620
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KeYieldProcessorEx+0x17:
fffff803`4ac44567 4883c420 add rsp,20h
Resetting default scope
BLACKBOXBSD: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxbsd[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXNTFS: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxntfs[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXPNP: 1 ([/COLOR][COLOR=rgba(0, 0, 255, 1)]!blackboxpnp[/COLOR][COLOR=rgba(30, 30, 30, 1)])
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9880`3231fc88 fffff803`4ae3adce : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9880`3231fc90 fffff803`4ac7541d : 0000174f`7a36ab33 ffff9880`32306180 00000000`00000246 00000000`0041149a : nt!KeAccumulateTicks+0x1c8bce
ffff9880`3231fcf0 fffff803`4ac759c1 : 00000000`00410f00 00000000`0026ca7e ffff9880`32306180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
ffff9880`3231fd40 fffff803`4ac6f833 : ffff9880`32306180 00000000`00000000 fffff803`4b631a80 00000000`00000000 : nt!KiUpdateTime+0x4a1
ffff9880`3231fe80 fffff803`4ac781f2 : ffffed89`c08bf540 ffffed89`c08bf5c0 ffffed89`c08bf500 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
ffff9880`3231ff30 fffff803`4ad27f55 : 0000009b`2ad20145 ffffa985`708ea500 ffffa985`708ea5b0 ffff1d1a`e1ff0733 : nt!HalpTimerClockInterrupt+0xe2
ffff9880`3231ff60 fffff803`4adf785a : ffffed89`c08bf5c0 ffffa985`708ea500 00000000`80000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9880`3231ffb0 fffff803`4adf7dc7 : 00000000`00000000 ffff9880`3230e1c8 ffffed89`c97b7450 fffff803`4adf7dd4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffed89`c08bf540 fffff803`4ac44567 : ffffffff`ffffffd1 fffff803`4af0c6e9 00000000`00000010 00000000`00000286 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffed89`c08bf6d0 fffff803`4af0c6fc : 00000000`00000001 ffffed89`c08bf710 00000000`00010001 00000000`00000000 : nt!KeYieldProcessorEx+0x17
ffffed89`c08bf700 fffff803`4ac0781e : ffff9880`32309240 ffffed89`c08bf860 00000000`00000000 ffffa985`1ceb36f3 : nt!KiConfigureHeteroProcessorsTarget+0xdc
ffffed89`c08bf760 fffff803`4ac06b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffffed89`c08bf8d0 fffff803`4adf991e : ffffffff`00000000 ffff9880`32306180 ffff9880`32311440 ffffa985`a4d66080 : nt!KiRetireDpcList+0x1f4
ffffed89`c08bfb60 00000000`00000000 : ffffed89`c08c0000 ffffed89`c08b9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
SYMBOL_NAME: nt!KeAccumulateTicks+1c8bce
MODULE_NAME: [/COLOR][COLOR=rgba(0, 0, 255, 1)]nt
[/COLOR][COLOR=rgba(30, 30, 30, 1)]IMAGE_NAME: ntkrnlmp.exe
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 1c8bce
FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}
Followup: MachineOwner[/COLOR]
[COLOR=rgba(30, 30, 30, 1)]I have the Minidump file and system info here at this link as well if someone is able to help[/COLOR]
Crash Laptop
Continue reading...