Dear All,
I have this DPC_WATCHDOG_VIOLATION Blue Screen. Sometimes the Computer runs fine for 15 days and sometimes it crashs three times a day... It just happens very randomly. Last time it crashed when I was writing a Mail. Then it crashed when surfing. Then it crashed when using my CAD program....
I'm so close to think it's a hardware issue, since I've tried so many things:
- Run Antivirus check and now only using defender from microsoft
- Run instant Upgrade from Windows 10
- Update all the driver, Bios and so on.
- Run Chkdsk, sfc scannow
Computer Specs:
Lenovo Legion T5 28IMB05
Intel Core i7-10700, 16 GB, 512 GB SSD, 1 TB HDD,
nVidia GeForce RTX 2070 Super
Download Memory Dump from
https://www.buchli-it.ch/memory.dmp
!analyze -v from memory.dmp
DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff8032a0fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000
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: 2452
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 2523
Key : Analysis.Init.CPU.mSec
Value: 1186
Key : Analysis.Init.Elapsed.mSec
Value: 16134
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: 1
BUGCHECK_P2: 1e00
BUGCHECK_P3: fffff8032a0fb320
BUGCHECK_P4: 0
DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
TRAP_FRAME: ffff8f8fe61e26c0 -- (.trap 0xffff8f8fe61e26c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=fffff8032cbf1f98
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803296d79cc rsp=ffff8f8fe61e2850 rbp=ffff8f8fe61e29a9
r8=0000000000000000 r9=0000000000040408 r10=fffff803296d7910
r11=ffffd28f1df19ef8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
nt!KxWaitForSpinLockAndAcquire+0x2c:
fffff803`296d79cc 488b07 mov rax,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9a01`fbeaee18 fffff803`2981f57e : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`2a0fb320 : nt!KeBugCheckEx
ffff9a01`fbeaee20 fffff803`29616953 : 000000b7`7e8e811f ffff9a01`fbe5c180 00000000`00000000 ffff9a01`fbe5c180 : nt!KeAccumulateTicks+0x2063ce
ffff9a01`fbeaee80 fffff803`2961643a : ffffd28f`178ec040 ffff8f8f`e61e2740 00000000`00000000 ffffd28f`178c74c0 : nt!KeClockInterruptNotify+0x453
ffff9a01`fbeaef30 fffff803`296de055 : ffffd28f`178ec040 fffff803`29752447 00000000`00000000 00000000`00000000 : nt!HalpTimerClockIpiRoutine+0x1a
ffff9a01`fbeaef60 fffff803`297f8c5a : ffff8f8f`e61e2740 ffffd28f`178ec040 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9a01`fbeaefb0 fffff803`297f91c7 : 00000000`d7e68fd6 fffff803`2cb92490 ffffd28f`23845010 ffffd28f`23845010 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8f8f`e61e26c0 fffff803`296d79cc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8f8f`e61e2850 fffff803`296d7998 : fffff803`2cbf1f98 ffff9a01`fbe5c180 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x2c
ffff8f8f`e61e2880 fffff803`2cba0bab : ffffd28f`23845198 00000000`00040408 00000000`00000000 ffffd28f`23845198 : nt!KeAcquireSpinLockRaiseToDpc+0x88
ffff8f8f`e61e28b0 fffff803`2cb75243 : ffffd28f`23845010 ffffd28f`00040408 ffffd28f`23845198 00000000`00000100 : ACPI!ACPIInterruptEventCompletion+0x2b
ffff8f8f`e61e28e0 fffff803`2cb74685 : ffffd28f`17dc8000 ffffd28f`23845010 00000000`00000000 00000000`00000032 : ACPI!RunContext+0x833
ffff8f8f`e61e2a10 fffff803`2cb9a325 : ffffd28f`23845010 00000000`00000080 ffffd28f`23845010 00000000`000001d2 : ACPI!InsertReadyQueue+0x2a5
ffff8f8f`e61e2a70 fffff803`2cb98c97 : fffff803`2cbf2790 00000000`00000000 00000000`00000000 ffff8f8f`e63a7c00 : ACPI!RestartCtxtPassive+0x35
ffff8f8f`e61e2aa0 fffff803`29755855 : ffffd28f`178c74c0 fffff803`2cb98b90 00000000`00000000 ffffd28f`178b3140 : ACPI!ACPIWorkerThread+0x107
ffff8f8f`e61e2b10 fffff803`297fe808 : ffff9a01`fbe5c180 ffffd28f`178c74c0 fffff803`29755800 05ebd88b`af758b4c : nt!PspSystemThreadStartup+0x55
ffff8f8f`e61e2b60 00000000`00000000 : ffff8f8f`e61e3000 ffff8f8f`e61dc000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: ACPI!ACPIInterruptEventCompletion+2b
MODULE_NAME: ACPI
IMAGE_NAME: ACPI.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 2b
FAILURE_BUCKET_ID: 0x133_ISR_ACPI!ACPIInterruptEventCompletion
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {66ccecbc-0d7a-4186-e177-11481af8fb9f}
Followup: MachineOwner
---------
11: kd> !dpcwatchdog
All durations are in seconds (1 System tick = 15.625000 milliseconds)
Circular Kernel Context Logger history: !logdump 0x2
DPC and ISR stats (total since boot): !intstats /d
DPC and ISR stats (during DPC watchdog period): !intstats /w
--------------------------------------------------
CPU#0
--------------------------------------------------
Current DPC: ACPI!ACPIInterruptDispatchEventDpc (Normal DPC)
Debugger Saved IRQL: 15
Cumulative DPC Time Limit: 120.000 seconds
Current Cumulative DPC Time: 120.000 seconds
Single DPC Time Limit: 20.000 seconds
Current Single DPC Time: 0.500 seconds
dt nt!_ISRDPCSTATS fffff8032a0f3a10
IsrActive: TRUE
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nvlei.inf_amd64_31ecf038806d15fe\nvlddmkm.sys, Win32 error 0n2
Page 44c6f6 not present in the dump file. Type ".hh dbgerr004" for details
Page 44c6f6 not present in the dump file. Type ".hh dbgerr004" for details
0: Normal : 0xffffd28f23d440e0 0xfffff80346220d1c nvlddmkm
0: Normal : 0xffffd28f2357acb0 0xfffff80345a998b4 nvlddmkm
0: Normal : 0xfffff8032a020e00 0xfffff8032961fef0 nt!PpmCheckPeriodicStart
0: Normal : 0xfffff8032a031f20 0xfffff80329728ed0 nt!KiBalanceSetManagerDeferredRoutine
0: Normal : 0xffffd28f178cad30 0xfffff80329728c90 nt!ExpCenturyDpcRoutine
DPC Watchdog Captures Analysis for CPU #0.
DPC Watchdog capture size: 641 stacks.
Number of unique stacks: 298.
Most common function: fffff803297f8d21 nt!KiInterruptDispatch+0xB1
List of functions that exist often in the Watchdog record:
Module Name Function Name #Stack #Of Occurrences
nt KiInterruptSubDispatch 018 74 (of 151)
ACPI READ_PM1_STATUS 004 34 (of 68)
List of functions that are called often in the Watchdog record:
Module Name Function Name #Stack #Of Occurrences
ACPI ACPIInterruptServiceRoutine 003 223 (of 223)
HDAudBus HdaController::Isr 019 68 (of 68)
nt KiDpcInterruptBypass 070 3 (of 3)
dxgkrnl DpiFdoLineInterruptRoutine 270 2 (of 2)
--------------------------------------------------
CPU#1
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#2
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#3
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#4
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#5
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#6
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#7
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#8
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#9
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#10
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#11
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
11: Normal : 0xffff9a01fbe64868 0xfffff803297515c0 nt!KiEntropyDpcRoutine
DPC Watchdog Captures Analysis for CPU #11.
DPC Watchdog capture size: 641 stacks.
Number of unique stacks: 1.
No common functions detected!
The captured stacks seem to indicate that only a single DPC or generic function is the culprit.
Try to analyse what other processors were doing at the time of the following reference capture:
CPU #11 DPC Watchdog Reference Stack (#0 of 641) - Profiling started at time since boot: 4 Min 15 Sec 593.75 mSec
# RetAddr Call Site
00 fffff8032961643a nt!KeClockInterruptNotify+0x453
01 fffff803296de055 nt!HalpTimerClockIpiRoutine+0x1A
02 fffff803297f8c5a nt!KiCallInterruptServiceRoutine+0xA5
03 fffff803297f91c7 nt!KiInterruptSubDispatchNoLockNoEtw+0xFA
04 fffff803296d79cc nt!KiInterruptDispatchNoLockNoEtw+0x37
05 fffff803296d7998 nt!KxWaitForSpinLockAndAcquire+0x2C
06 fffff8032cba0bab nt!KeAcquireSpinLockRaiseToDpc+0x88
07 fffff8032cb75243 ACPI!ACPIInterruptEventCompletion+0x2B
08 fffff8032cb74685 ACPI!RunContext+0x833
09 fffff8032cb9a325 ACPI!InsertReadyQueue+0x2A5
0a fffff8032cb98c97 ACPI!RestartCtxtPassive+0x35
0b fffff80329755855 ACPI!ACPIWorkerThread+0x107
0c fffff803297fe808 nt!PspSystemThreadStartup+0x55
0d ---------------- nt!KiStartSystemThread+0x28
--------------------------------------------------
CPU#12
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#13
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#14
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
--------------------------------------------------
CPU#15
--------------------------------------------------
Current DPC: No Active DPC
Pending DPCs:
----------------------------------------
CPU Type KDPC Function
dpcs: no pending DPCs found
