May 11 2023 10:55 AM - edited May 12 2023 03:47 AM
I'm getting DCP_WATCHDOG_VIOLATION errors everyday. Can anyone help? Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\FirstName.LastName\Downloads\aguab\051123-18906-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 14393 MP (8 procs) Free x64 Product: Server, suite: TerminalServer SingleUserTS Edition build lab: 14393.5850.amd64fre.rs1_release.230329-2152 Machine Name: Kernel base = 0xfffff801`b241d000 PsLoadedModuleList = 0xfffff801`b2722cd0 Debug session time: Thu May 11 11:15:52.381 2023 (UTC - 1:00) System Uptime: 0 days 0:46:32.453 Loading Kernel Symbols ............................................................... ................................................................ ..................................... Loading User Symbols Loading unloaded module list ........... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff801`b257a1c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801`b447cb90=0000000000000133 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* 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. Arg2: 0000000000001e00, The watchdog period (in ticks). Arg3: fffff801b27c5540, 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: 3296 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 51319 Key : Analysis.IO.Other.Mb Value: 14 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 33 Key : Analysis.Init.CPU.mSec Value: 1874 Key : Analysis.Init.Elapsed.mSec Value: 70116 Key : Analysis.Memory.CommitPeak.Mb Value: 90 Key : Bugcheck.Code.DumpHeader Value: 0x133 Key : Bugcheck.Code.Register Value: 0x133 Key : WER.OS.Branch Value: rs1_release Key : WER.OS.Timestamp Value: 2023-03-29T21:52:00Z Key : WER.OS.Version Value: 10.0.14393.5850 FILE_IN_CAB: 051123-18906-01.dmp BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff801b27c5540 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: fffff801b447ce00 -- (.trap 0xfffff801b447ce00) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000000000a302 rbx=0000000000000000 rcx=00000000ffffffff rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000 rip=fffff801b257bb6d rsp=fffff801b447cf90 rbp=ffff9000d2a515d0 r8=ffffbb89622fc080 r9=0000000000000000 r10=fffff801b2766590 r11=0000000000000370 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl zr na po nc nt!KiScanInterruptObjectList+0xcd: fffff801`b257bb6d 740e je nt!KiScanInterruptObjectList+0xdd (fffff801`b257bb7d) [br=1] Resetting default scope CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: SetupHost.exe STACK_TEXT: fffff801`b447cb88 fffff801`b24a898a : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff801`b27c5540 : nt!KeBugCheckEx fffff801`b447cb90 fffff801`b24a5f89 : 00000987`aaaf3e8b 00000000`00000000 00000000`00000000 fffff780`00000320 : nt!KeAccumulateTicks+0x42a fffff801`b447cbf0 fffff801`b2c3f366 : fffff801`b447ce00 fffff801`b2c8b7b0 00000000`00000009 00000987`aaaeb37b : nt!KeClockInterruptNotify+0x469 fffff801`b447cd40 fffff801`b242d746 : fffff801`b2c8b7b0 00000000`0002ba1c fffff801`b2760180 fffff801`b24a8580 : hal!HalpTimerClockInterrupt+0x56 fffff801`b447cd70 fffff801`b257bfba : fffff801`b447ce80 00000000`00000002 ffffa5bf`ff1c0478 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x106 fffff801`b447cdb0 fffff801`b257c707 : 00000000`00000000 00000000`00000009 fffff801`b447ce00 00000000`00000001 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea fffff801`b447ce00 fffff801`b257bb6d : ffff9000`d2a515d0 00000000`00000000 ffff9000`cedb7500 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff801`b447cf90 fffff801`b257b757 : 00000000`00000001 ffffa5d2`dfff8e00 00000000`00000002 0000028f`a1fb4001 : nt!KiScanInterruptObjectList+0xcd ffff9000`d2a51550 fffff801`b24ddf3b : 00000000`00009b35 00000000`00296d64 00000000`00000000 fffff801`b260e8f9 : nt!KiChainedDispatch+0x37 ffff9000`d2a516e0 fffff801`b24dd499 : ffffa5bf`ff1c3168 ffffa5bf`ff1c0470 ffffbb89`69123220 ffff9000`d2a51829 : nt!MiGetNextPageTable+0x27b ffff9000`d2a517a0 fffff801`b24dd1d9 : 00000000`00000000 fffff80a`f68d3b00 ffffbb89`00000000 0000028f`a1fb40e0 : nt!MiQueryAddressState+0xc9 ffff9000`d2a51830 fffff801`b28ef914 : ffff9000`d2a51980 000000ef`de93eb00 000000ef`00000003 ffff9000`00000001 : nt!MiQueryAddressSpan+0x169 ffff9000`d2a518f0 fffff801`b28eef5d : 0000028f`a25ebdc0 00000000`00000000 ffffbb89`665307d0 ffff9000`d2a51b80 : nt!MmQueryVirtualMemory+0x9a4 ffff9000`d2a51a40 fffff801`b258bd03 : ffff9000`d2a51b10 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtQueryVirtualMemory+0x25 ffff9000`d2a51a90 00007ffe`7d6460f4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13 000000ef`de93ead8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`7d6460f4 SYMBOL_NAME: nt!KeAccumulateTicks+42a MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.14393.5850 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 42a FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks OS_VERSION: 10.0.14393.5850 BUILDLAB_STR: rs1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} Followup: MachineOwner ---------