DPC_WATCHDOG_VIOLATION (133) bug check HELP!!!!!

Question

This is the whole text which came out after debugging from windebug please anyone analise it and help me.
from 2 days when i'm opening my laptop then the loading logo stucks in middle and do 2 time restart and blue screen.

************* Preparing the environment for Debugger Extensions Gallery repositories **************

ExtensionRepository : Implicit

UseExperimentalFeatureForNugetShare : true

AllowNugetExeUpdate : true

NonInteractiveNuget : true

AllowNugetMSCredentialProviderInstall : true

AllowParallelInitializationOfLocalRepositories : true

EnableRedirectToChakraJsProvider : false

-- Configuring repositories

  ----> Repository : LocalInstalled, Enabled: true 

  ----> Repository : UserExtensions, Enabled: true 

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.515 seconds

----> Repository : UserExtensions, Enabled: true, Packages count: 0

----> Repository : LocalInstalled, Enabled: true, Packages count: 43

Microsoft (R) Windows Debugger Version 10.0.27793.1000 AMD64

Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\sumit\OneDrive\Desktop\031025-14906-01.dmp]

Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************

Response Time (ms) Location

Deferred srv*

Symbol search path is: srv*

Executable search path is:

Windows 10 Kernel Version 26100 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS Personal

Kernel base = 0xfffff8017de00000 PsLoadedModuleList = 0xfffff8017ecf47c0

Debug session time: Mon Mar 10 00:39:11.016 2025 (UTC + 5:30)

System Uptime: 0 days 0:02:09.157

Loading Kernel Symbols

...............................................................

................................................................

..............................

Loading User Symbols

Loading unloaded module list

...

For analysis of this file, run !analyze -v

nt!KeBugCheckEx:

fffff8017e2b7ce0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff801106e6930=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: fffff8017edc33a0, 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: 2406 

Key  : Analysis.Elapsed.mSec 

Value: 2439 

Key  : Analysis.IO.Other.Mb 

Value: 5 

Key  : Analysis.IO.Read.Mb 

Value: 1 

Key  : Analysis.IO.Write.Mb 

Value: 23 

Key  : Analysis.Init.CPU.mSec 

Value: 890 

Key  : Analysis.Init.Elapsed.mSec 

Value: 97374 

Key  : Analysis.Memory.CommitPeak.Mb 

Value: 88 

Key  : Analysis.Version.DbgEng 

Value: 10.0.27793.1000 

Key  : Analysis.Version.Description 

Value: 10.2410.02.02 amd64fre 

Key  : Analysis.Version.Ext 

Value: 1.2410.2.2 

Key  : Bugcheck.Code.LegacyAPI 

Value: 0x133 

Key  : Bugcheck.Code.TargetModel 

Value: 0x133 

Key  : Dump.Attributes.AsUlong 

Value: 0x21808 

Key  : Dump.Attributes.DiagDataWrittenToHeader 

Value: 1 

Key  : Dump.Attributes.ErrorCode 

Value: 0x0 

Key  : Dump.Attributes.KernelGeneratedTriageDump 

Value: 1 

Key  : Dump.Attributes.LastLine 

Value: Dump completed successfully. 

Key  : Dump.Attributes.ProgressPercentage 

Value: 0 

Key  : Failure.Bucket 

Value: 0x133\_ISR\_nt!KeAccumulateTicks 

Key  : Failure.Hash 

Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} 

Key  : Hypervisor.Enlightenments.ValueHex 

Value: 0x7497cf94 

Key  : Hypervisor.Flags.AnyHypervisorPresent 

Value: 1 

Key  : Hypervisor.Flags.ApicEnlightened 

Value: 1 

Key  : Hypervisor.Flags.ApicVirtualizationAvailable 

Value: 0 

Key  : Hypervisor.Flags.AsyncMemoryHint 

Value: 0 

Key  : Hypervisor.Flags.CoreSchedulerRequested 

Value: 0 

Key  : Hypervisor.Flags.CpuManager 

Value: 1 

Key  : Hypervisor.Flags.DeprecateAutoEoi 

Value: 0 

Key  : Hypervisor.Flags.DynamicCpuDisabled 

Value: 1 

Key  : Hypervisor.Flags.Epf 

Value: 0 

Key  : Hypervisor.Flags.ExtendedProcessorMasks 

Value: 1 

Key  : Hypervisor.Flags.HardwareMbecAvailable 

Value: 1 

Key  : Hypervisor.Flags.MaxBankNumber 

Value: 0 

Key  : Hypervisor.Flags.MemoryZeroingControl 

Value: 0 

Key  : Hypervisor.Flags.NoExtendedRangeFlush 

Value: 0 

Key  : Hypervisor.Flags.NoNonArchCoreSharing 

Value: 1 

Key  : Hypervisor.Flags.Phase0InitDone 

Value: 1 

Key  : Hypervisor.Flags.PowerSchedulerQos 

Value: 0 

Key  : Hypervisor.Flags.RootScheduler 

Value: 0 

Key  : Hypervisor.Flags.SynicAvailable 

Value: 1 

Key  : Hypervisor.Flags.UseQpcBias 

Value: 0 

Key  : Hypervisor.Flags.Value 

Value: 38408431 

Key  : Hypervisor.Flags.ValueHex 

Value: 0x24a10ef 

Key  : Hypervisor.Flags.VpAssistPage 

Value: 1 

Key  : Hypervisor.Flags.VsmAvailable 

Value: 1 

Key  : Hypervisor.RootFlags.AccessStats 

Value: 1 

Key  : Hypervisor.RootFlags.CrashdumpEnlightened 

Value: 1 

Key  : Hypervisor.RootFlags.CreateVirtualProcessor 

Value: 1 

Key  : Hypervisor.RootFlags.DisableHyperthreading 

Value: 0 

Key  : Hypervisor.RootFlags.HostTimelineSync 

Value: 1 

Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled 

Value: 0 

Key  : Hypervisor.RootFlags.IsHyperV 

Value: 1 

Key  : Hypervisor.RootFlags.LivedumpEnlightened 

Value: 1 

Key  : Hypervisor.RootFlags.MapDeviceInterrupt 

Value: 1 

Key  : Hypervisor.RootFlags.MceEnlightened 

Value: 1 

Key  : Hypervisor.RootFlags.Nested 

Value: 0 

Key  : Hypervisor.RootFlags.StartLogicalProcessor 

Value: 1 

Key  : Hypervisor.RootFlags.Value 

Value: 1015 

Key  : Hypervisor.RootFlags.ValueHex 

Value: 0x3f7 

Key  : Stack.Pointer 

Value: ISR 

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8017edc33a0

BUGCHECK_P4: 0

FILE_IN_CAB: 031025-14906-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x21808

Kernel Generated Triage Dump

FAULTING_THREAD: ffff8505d4541400

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff90b38e9bd10 -- (.trap 0xfffff90b38e9bd10)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=fffff801410f8680 rbx=0000000000000000 rcx=ffff8505e1db3040

rdx=ffff8505d9c49d30 rsi=0000000000000000 rdi=0000000000000000

rip=fffff801410f8680 rsp=fffff90b38e9bea8 rbp=fffff90b38e9c190

r8=0000000000000000 r9=ffff8505e1db3040 r10=0000fffff801410f

r11=ffffd77f05a00000 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei pl nz ac po cy

CmBatt!CmBattOpenClose:

fffff801410f8680 488bc4 mov rax,rsp

Resetting default scope

STACK_TEXT:

fffff801106e6928 fffff8017e11c699 : 0000000000000133 0000000000000001 0000000000001e00 fffff8017edc33a0 : nt!KeBugCheckEx

fffff801106e6930 fffff8017e1270e1 : 0000000000000000 000000000000000a 0000000000000000 0000000000002049 : nt!KeAccumulateTicks+0x589

fffff801106e69a0 fffff8017e126ca5 : 000000000000133e 0000000000000000 000000004cfbd0c7 000000000000000d : nt!KiUpdateRunTime+0xc9

fffff801106e6a20 fffff8017e082f4e : 000000000000000d 0000000000000000 fffff8010c3ee928 fffff8017ed20530 : nt!KiUpdateTime+0x2b5

fffff801106e6bb0 fffff8017e0848fd : fffff8017ec10920 0000000000000000 fffff8017ec109d0 fffff8017ed8df68 : nt!KeClockInterruptNotify+0x66e

fffff801106e6d30 fffff8017e47b06e : ffffe78067a68a0a fffff8017ec10920 fffff801106e6de0 000000004cfedef6 : nt!KiCallInterruptServiceRoutine+0x2ed

fffff801106e6d90 fffff8017e47b87c : 0000000000000000 fffff801106e6e99 ffff850500500a02 0000000000000004 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e

fffff801106e6de0 fffff8017e47adf1 : 0000000000000400 ffffe78067a68a00 ffffe78067a68a00 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c

fffff801106e6f70 fffff8017e47aa0c : 000000004cfeddf9 fffff90b38e9b320 000000004cfede92 000000571238b21b : nt!KiScanInterruptObjectList+0x41

fffff90b38e9b2a0 fffff8010c62001c : fffff8017e4744fb 0000000000000000 fffff90b38e9b660 0000000000000000 : nt!KiChainedDispatch+0x3c

fffff90b38e9b438 fffff8017e4744fb : 0000000000000000 fffff90b38e9b660 0000000000000000 fffff90b38e9b4c8 : 0xfffff8010c62001c

fffff90b38e9b440 fffff8017e062fe8 : b4676400003c6776 00000000003c6769 00000000003c6776 ffffa0800b5363b0 : nt!HvlSwitchToVsmVtl1+0xab

fffff90b38e9b580 fffff8017e375a20 : 007b002300310023 00001f8000320237 fffff90b38e9b6a9 fffff8017ec2d29c : nt!VslpEnterIumSecureMode+0x2b8

fffff90b38e9b640 fffff8017e4ae10b : 0000000000000001 ffff9feb05460001 fffff90b38e9b7a1 8000000000000000 : nt!KeSetPagePrivilege+0xac

fffff90b38e9b710 fffff8017e03b719 : fffff8017ec377c0 ffff9ffc00a087c0 ffffa0800b5362c0 0000000000000000 : nt!MiAllocateWsle+0x37fabb

fffff90b38e9b7f0 fffff8017e03bfc5 : fffff90b38e9bab0 0000000000000000 0000000000000000 ffffa08000000000 : nt!MiCompleteProtoPteFault+0x385

fffff90b38e9b8e0 fffff8017e0c4777 : 0000000300000000 00000003c6764860 0a000003c6764121 0000000000000000 : nt!MiResolveTransitionFault+0x425

fffff90b38e9b9b0 fffff8017e0c3a32 : fffff801410f8680 0000000000000000 fffff90b38e9ba88 ffffd70321364f80 : nt!MiResolveProtoPteFault+0x237

fffff90b38e9ba50 fffff8017e08ea63 : fffff801410f8680 0000000000001000 0000000000001000 fffff8017de00000 : nt!MiDispatchFault+0x226

fffff90b38e9bba0 fffff8017e4880cb : 000000000b2974bf fffff8017e1deb2a ffff8505e1dbb450 ffff8505e1328a20 : nt!MmAccessFault+0x183

fffff90b38e9bd10 fffff801410f8680 : fffff8017e14e4ae ffffffffffffffa0 fffff8017e7867a3 0000000001000010 : nt!KiPageFault+0x38b

fffff90b38e9bea8 fffff8017e14e4ae : ffffffffffffffa0 fffff8017e7867a3 0000000001000010 0000000000040246 : CmBatt!CmBattOpenClose

fffff90b38e9beb0 fffff8017e7c916a : fffff8017e7c7f04 fffff90b38e9c190 0000000000000000 0000000639f9a752 : nt!IofCallDriver+0xbe

fffff90b38e9bef0 fffff8017e65696d : fffff8017e7c7f00 fffff8017e7c7f00 0000000000000001 fffff90b38e9c2d8 : nt!IopParseDevice+0x126a

fffff90b38e9c090 fffff8017e6547c1 : ffff8505e1329a01 fffff90b38e9c2d8 ffff850500000240 ffff8505d45b6c80 : nt!ObpLookupObjectName+0xe8d

fffff90b38e9c250 fffff8017e75e282 : 0000000000000000 ffff8505d45b6c80 0000000000000001 fffff8017e1deb2a : nt!ObOpenObjectByNameEx+0x201

fffff90b38e9c3a0 fffff8017e75def9 : fffff90b38e9c7e0 00340035001f01ff fffff90b38e9c790 fffff90b38e9c780 : nt!IopCreateFile+0x37a

fffff90b38e9c480 fffff8017e48c558 : 0000000000000160 0000000000000002 ffff8505d4100380 0000000000000000 : nt!NtCreateFile+0x79

fffff90b38e9c510 fffff8017e47a9b0 : fffff8017e533d76 0000000074746142 fffff8017e934189 0000000000000040 : nt!KiSystemServiceCopyEnd+0x28

fffff90b38e9c718 fffff8017e533d76 : 0000000074746142 fffff8017e934189 0000000000000040 0000000000000002 : nt!KiServiceLinkage

fffff90b38e9c720 fffff8017e533c0c : 0000000000000000 fffff8017ed0a5e0 0000000000000000 fffff8017ec01b00 : nt!PopGetPolicyDeviceObject+0x8a

fffff90b38e9c7e0 fffff8017e533eb1 : fffff90b38e9c948 ffffd70320646530 0000000000000000 0000000000000018 : nt!PopConnectToPolicyDevice+0xb8

fffff90b38e9c840 fffff8017e71c578 : 01db912675ec4863 0000000000000000 0000000000000000 0000000000000000 : nt!PopNotifyPolicyDevice+0x91

fffff90b38e9c870 fffff8017e71bfa8 : fffff90b38e9cb00 fffff90b38e9c948 00000000ffffffff 0000000000000001 : nt!PnpNotifyDriverCallback+0x54

fffff90b38e9c920 fffff8017e71a92f : 0000000000000000 fffff90b38e9cb00 ffffd7032585d790 fffff8017e71a600 : nt!PnpNotifyDeviceClassChange+0xac

fffff90b38e9c9c0 fffff8017e117b02 : ffff8505d4541400 ffff8505d4541400 fffff90b38e9cb40 ffff8505d4677c20 : nt!PnpDeviceEventWorker+0x2bf

fffff90b38e9ca40 fffff8017e24fd8a : ffff8505d4541400 ffff8505d4541400 fffff8017e117950 ffff8505d4677c20 : nt!ExpWorkerThread+0x1b2

fffff90b38e9cbf0 fffff8017e47a024 : ffffe780341c0180 ffff8505d4541400 fffff8017e24fd30 2b00000061007400 : nt!PspSystemThreadStartup+0x5a

fffff90b38e9cc40 0000000000000000 : fffff90b38e9d000 fffff90b38e97000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x34

SYMBOL_NAME: nt!KeAccumulateTicks+589

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.26100.3323

STACK_COMMAND: .process /r /p 0xffff8505d451a040; .thread 0xffff8505d4541400 ; kb

BUCKET_ID_FUNC_OFFSET: 589

FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup: MachineOwner

Answer 1

Hello，sumit rathod

Welcome to posting in the Microsoft Community.

Thank you for providing such a detailed debug report! I do understand the distress caused by encountering such frequent blue screen problems, please don't worry, we will check and solve this problem together step by step.

From your description and debugging results, the problem DPC_WATCHDOG_VIOLATION (133) is usually caused by incompatible underlying system drivers or long delays. And according to the situation you mentioned, these problems may be caused by the blue screen phenomenon when the system is booting up or loading the device driver.

In order to better help you solve the problem, I need to confirm the following:

1. Were there any updates performed before the problem occurred?

For example, a Windows system update, a driver update, or some new third-party software was installed. Some updates (especially driver updates or Windows cumulative updates) may cause compatibility issues.

Please recall what you did before the problem occurred, as this can help us quickly pinpoint the cause of the problem.

2. Is the system currently accessible?

If you can't get into the system, can you get into “Safe Mode”? Safe Mode allows us to temporarily disable non-essential drivers and to try to further investigate the problem, by entering Safe Mode as follows:

1. Press and hold the power button for 10 seconds to turn off your device.
2. Press the power button again to turn on your device.
3. Immediately after Windows starts (e.g., on some devices, the manufacturer's logo is on restart), press and hold the power button for 10 seconds to turn off the device.
4. Press the power button again to turn on your device.
5. Press and hold the power button for 10 seconds to turn off your device while Windows restarts.
6. Press the power button again to turn on your device.
7. Allow the device to restart to perform the automatic repair, and then select "Advanced Options" to enter winRE.
8. In winRE, on the "Select Options" screen, select "Troubleshoot > Advanced Options" > "Startup Settings > Restart". After the device restarts, you will see a list of options. Select "5" from the list or press F5 to enter the "Safe Mode with Networking", this way you can switch to the system's Safe Mode for further actions.

Let's start with these steps to troubleshoot. If you can't access your system or can't get into safe mode, let me know and I'll provide further analysis and guidance to help you resolve the issue. Let me know if you have any new information and we'll move forward step by step to resolve the issue! Don't worry, I'll be there to assist you until the issue is properly resolved!

Best Regards，

Rota|Microsoft Community Support Specialist