Windows 10: DPC_WATCHDOG_VIOLATION 133 bluescreen problem

Microsoft R Windows Debugger Version 10.0.19041.685 X86
Copyright c Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\040721-24062-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 19041 MP 12 procs Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff804`23a00000 PsLoadedModuleList = 0xfffff804`2462a490
Debug session time: Wed Apr 7 05:14:00.804 2021 UTC + 9:00
System Uptime: 0 days 19:59:52.485
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...................
For analysis of this file, run !analyze -v
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. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff804246fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for ksaud.sys
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 3

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on KGH

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.Sec
Value: 8

Key : Analysis.Memory.CommitPeak.Mb
Value: 86

Key : Analysis.System
Value: CreateObject


BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff804246fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 !blackboxbsd


BLACKBOXNTFS: 1 !blackboxntfs


BLACKBOXPNP: 1 !blackboxpnp


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff804`2ac33c88 fffff804`23e3ac52 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`246fb320 : nt!KeBugCheckEx
fffff804`2ac33c90 fffff804`23c7541d : 0000f258`0df885f6 fffff804`221e6180 00000000`00000246 00000000`00464e1f : nt!KeAccumulateTicks+0x1c8a52
fffff804`2ac33cf0 fffff804`23c759c1 : fffff804`2ac33e90 00000000`0029e7b7 fffff804`221e6180 00000000`00000001 : nt!KiUpdateRunTime+0x5d
fffff804`2ac33d40 fffff804`23c6f833 : ffffef8a`8b02f840 00000000`00000000 fffff804`24631ad0 00000000`00000000 : nt!KiUpdateTime+0x4a1
fffff804`2ac33e80 fffff804`23c781f2 : ffffef8a`8b02f840 ffffef8a`8b02f8c0 ffffef8a`8b02f800 00000000`00000002 : nt!KeClockInterruptNotify+0x2e3
fffff804`2ac33f30 fffff804`23d27f55 : 000000a7`9f00bf65 fffff804`246f3ba0 fffff804`246f3c50 ffffd7bc`acdfdc47 : nt!HalpTimerClockInterrupt+0xe2
fffff804`2ac33f60 fffff804`23df76fa : ffffef8a`8b02f8c0 fffff804`246f3ba0 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff804`2ac33fb0 fffff804`23df7c67 : ffff8006`2ef718b0 fffff804`23df7795 fffff804`23df1d40 fffff804`23cec5ca : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffef8a`8b02f840 fffff804`3cf64025 : fffff804`3cf63bc6 ffff8006`2ef718b0 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffef8a`8b02f9d8 fffff804`3cf63bc6 : ffff8006`2ef718b0 00000000`00000000 00000000`00000000 fffff804`3cf63b10 : ks!CKsQueue::UpdateByteAvailability+0x5
ffffef8a`8b02f9e0 fffff804`3a441dac : 00000000`00000500 fffff804`24725440 ffff8006`2bd6fa00 ffff8006`2ef718b0 : ks!KsStreamPointerAdvanceOffsets+0xb6
ffffef8a`8b02fa30 00000000`00000500 : fffff804`24725440 ffff8006`2bd6fa00 ffff8006`2ef718b0 ffff8006`2be03348 : ksaud+0xb1dac
ffffef8a`8b02fa38 fffff804`24725440 : ffff8006`2bd6fa00 ffff8006`2ef718b0 ffff8006`2be03348 00000000`00000000 : 0x500
ffffef8a`8b02fa40 ffff8006`2bd6fa00 : ffff8006`2ef718b0 ffff8006`2be03348 00000000`00000000 00000000`00000500 : nt!ExNode0
ffffef8a`8b02fa48 ffff8006`2ef718b0 : ffff8006`2be03348 00000000`00000000 00000000`00000500 ffff8006`2bd6fa28 : 0xffff8006`2bd6fa00
ffffef8a`8b02fa50 ffff8006`2be03348 : 00000000`00000000 00000000`00000500 ffff8006`2bd6fa28 00000000`00000000 : 0xffff8006`2ef718b0
ffffef8a`8b02fa58 00000000`00000000 : 00000000`00000500 ffff8006`2bd6fa28 00000000`00000000 fffff804`3cf6417b : 0xffff8006`2be03348


SYMBOL_NAME: ks!CKsQueue::UpdateByteAvailability+5

MODULE_NAME: ks

IMAGE_NAME: ks.sys

IMAGE_VERSION: 10.0.19041.870

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 5

FAILURE_BUCKET_ID: 0x133_ISR_ks!CKsQueue::UpdateByteAvailability

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c75359d3-05e6-e5c7-7d47-11c0a24b1753}


Followup: MachineOwner


------------------------------------------------------------------------------------------------------------------------

this is 040721....dmp the last bluescreen


minidump.zip file onedrive here => https://1drv.ms/u/s!ApyqE8AC8r3Bnh27uDEmZUYyq_Q_?e=9ZLfrG


there is bluescreen DPC_WATCHDOG_VIOLATION 133 for several times this week.

so this is what i did :

1. reset ram overclock to factory overclocked half years but fine

2. reinstall [COLOR=rgba32, 33, 36, 1]graphic [/COLOR]driverdelete and install option

3. reinstall internet driver

but still bluescreen appears


no hardware newly installed.


if internet stop for minute and back might cause this problem, I think this last bluescreen could be caused by router.


these is five dmp files. four of them are happened when monitor off energy save.

and when i wake this up no respond and even monitor did not turn on.

so i turn off and reinstall [COLOR=rgba32, 33, 36, 1]graphic [/COLOR]driver but nothing changed


please help

thank you

:)

 

DPC_WATCHDOG_VIOLATION BLUESCREEN WINDOWS 10

Because I reinstalled Windows 10.

Last Windows 10 I got a lot of this bluescreen (DPC_WATCHDOG_VIOLATION).

bluescreens occur when playing
games and the battery charger is connected.

 

DPC_Watchdog_Violation

Hi,

I understand the inconvenience caused, I will be glad to assist you with this.

This could be due to hardware failure, faulty RAM or corrupted or outdated drivers.

I suggest you to try the steps provided by Anannya Podder in the link below and check if it helps.

Bluescreen Error: DPC_WATCHDOG_VIOLATION


Let us know the result, we will be glad to help if you need further assistance.

 

dpc_watchdog_violation Bluescreen

Hi Duncan,

Conflicts with a third-party program is one of the possible reasons why you are having a blue screen that has the error code, DPC_WATCHDOG_VIOLATION. For us to assist you better, kindly answer the questions below:

• Have you made any changes to your computer prior to this issue?
• Which version and OS build number of Windows 10 is currently installed? To check, press the Windows key, type winver, and press the Enter key.
• Do you have a third-party security software installed?
• Have you tried the steps in this
  link to troubleshoot blue screen issues?

Meanwhile, I would suggest that you try running your computer in clean boot and check if it helps. This helps eliminate software conflicts that occur when you install a program or an update or when you run a program in Windows 10. You can follow the steps
in this
link.

Note: Please go through the section: How to reset the computer to start normally after clean boot troubleshooting of the Kb article to boot the computer in normal startup after fixing the issue.

We'll be looking forward to your reply.