Windows 10: BlueScreen DCP_WATCHDOG_VIOLATION

Hi, I've been getting a BlueScreen every time when I try to play Anthem. After few minutes the game freezes and I get a BlueScreen with DCP_WATCHDOG_VIOLATION. If anyone knows the solution for this, it would be greatly appreciated.


The dump File can be seen below:


Loading Dump File [C:\Windows\Minidump\042419-11671-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 17763 MP (16 procs) Free x64

Product: WinNt, suite: TerminalServer SingleUserTS

Built by: 17763.1.amd64fre.rs5_release.180914-1434

Machine Name:

Kernel base = 0xfffff805`4f2b3000 PsLoadedModuleList = 0xfffff805`4f6ce790

Debug session time: Wed Apr 24 23:15:10.044 2019 (UTC + 2:00)

System Uptime: 0 days 0:03:37.859

Loading Kernel Symbols

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

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

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



Loading User Symbols

Loading unloaded module list

..........

For analysis of this file, run !analyze -v

1: 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: 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: fffff8054f7f5380, 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 ***

*** ***

*************************************************************************

*** WARNING: Unable to verify timestamp for win32k.sys



KEY_VALUES_STRING: 1





PROCESSES_ANALYSIS: 1



SERVICE_ANALYSIS: 1



STACKHASH_ANALYSIS: 1



TIMELINE_ANALYSIS: 1





DUMP_CLASS: 1



DUMP_QUALIFIER: 400



BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434



SYSTEM_MANUFACTURER: System manufacturer



SYSTEM_PRODUCT_NAME: System Product Name



SYSTEM_SKU: ASUS_MB_CNL



SYSTEM_VERSION: System Version



BIOS_VENDOR: American Megatrends Inc.



BIOS_VERSION: 0702



BIOS_DATE: 12/21/2018



BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.



BASEBOARD_PRODUCT: ROG MAXIMUS XI HERO



BASEBOARD_VERSION: Rev 1.xx



DUMP_TYPE: 2



BUGCHECK_P1: 0



BUGCHECK_P2: 501



BUGCHECK_P3: 500



BUGCHECK_P4: fffff8054f7f5380



DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED



CPU_COUNT: 10



CPU_MHZ: e10



CPU_VENDOR: GenuineIntel



CPU_FAMILY: 6



CPU_MODEL: 9e



CPU_STEPPING: c



CPU_MICROCODE: 6,9e,c,0 (F,M,S,R) SIG: A0'00000000 (cache) A0'00000000 (init)



BLACKBOXBSD: 1 (!blackboxbsd)





BLACKBOXPNP: 1 (!blackboxpnp)





CUSTOMER_CRASH_COUNT: 1



DEFAULT_BUCKET_ID: VERIFIER_ENABLED_VISTA_MINIDUMP



BUGCHECK_STR: 0x133



PROCESS_NAME: System



CURRENT_IRQL: d



ANALYSIS_SESSION_HOST: PHILIP-PC



ANALYSIS_SESSION_TIME: 04-25-2019 18:36:50.0482



ANALYSIS_VERSION: 10.0.18362.1 x86fre



LAST_CONTROL_TRANSFER: from fffff8054f4dfb33 to fffff8054f466730



STACK_TEXT:

ffffc101`10940ba8 fffff805`4f4dfb33 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx

ffffc101`10940bb0 fffff805`4f3978bf : 000000c8`3dddc78d ffffc101`107c0180 00000000`00000286 00000000`00003677 : nt!KeAccumulateTicks+0x144c03

ffffc101`10940c10 fffff805`4f21e47c : 00000000`00000000 ffffd38b`2c0ae200 ffffd206`d9e2f430 ffffd38b`2c0ae2b0 : nt!KeClockInterruptNotify+0xcf

ffffc101`10940f30 fffff805`4f3e6195 : ffffd38b`2c0ae200 00000000`00000010 ffffb4d0`7541c204 ffffb4d0`7541c3f4 : hal!HalpTimerClockIpiRoutine+0x1c

ffffc101`10940f60 fffff805`4f46812a : ffffd206`d9e2f430 ffffd38b`2c0ae200 00000000`000004c0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5

ffffc101`10940fb0 fffff805`4f468677 : ffffd38b`34d65170 00000000`000003e8 ffffd38b`2ed74c00 fffff805`54072053 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa

ffffd206`d9e2f3b0 fffff805`4f3cdde0 : 00000000`00000000 ffffd38b`35622b00 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37

ffffd206`d9e2f540 fffff805`4f3cdda7 : ffffd38b`355f28c0 ffffc101`107c0180 00000000`00000000 00000000`00000000 : nt!KxWaitForSpinLockAndAcquire+0x30

ffffd206`d9e2f570 fffff805`53f7252c : ffffd38b`3560f960 ffffd38b`355f2850 00000000`00000004 00000000`00000004 : nt!KeAcquireSpinLockRaiseToDpc+0x87

ffffd206`d9e2f5a0 fffff805`574f1794 : ffffd38b`355f2900 ffffd38b`355f2850 ffffd206`d9e2f670 ffffd38b`35622bd0 : Wdf01000!imp_WdfSpinLockAcquire+0x6c [minkernel\wdf\framework\shared\support\fxspinlockapi.cpp @ 141]

ffffd206`d9e2f5e0 fffff805`574b7c8b : 00000000`00000004 ffffd206`d9e2f6d0 00000000`00000004 ffffd206`d9e2f6d8 : USBXHCI!DynamicLock_Acquire+0x74

ffffd206`d9e2f610 fffff805`574cb7fc : ffffd38b`35622b00 ffffd38b`35622bd0 ffffc101`13da2400 ffffd38b`2efc0120 : USBXHCI!Command_HandleCommandCompletionEvent+0x67

ffffd206`d9e2f6a0 fffff805`574cbffc : 00000000`00000001 ffffd206`d9e2f7b0 00000000`00010001 ffffd38b`35622900 : USBXHCI!Interrupter_DeferredWorkProcessor+0x74c

ffffd206`d9e2f7a0 fffff805`53f7381d : ffffc101`107c0180 fffff805`4f21d7a9 00000000`00000000 00000000`00000004 : USBXHCI!Interrupter_WdfEvtInterruptDpc+0xc

ffffd206`d9e2f7d0 fffff805`4f32c577 : ffffffff`ffffffff ffffd206`d9e2f910 00000000`0004c4b4 00000000`00000000 : Wdf01000!FxInterrupt::_InterruptDpcThunk+0x9d [minkernel\wdf\framework\shared\irphandlers\pnp\km\interruptobjectkm.cpp @ 410]

ffffd206`d9e2f810 fffff805`4f32bbbe : 00000000`00000000 00000000`00000048 00000000`00000000 ffffc101`107c0180 : nt!KiExecuteAllDpcs+0x2e7

ffffd206`d9e2f950 fffff805`4f46a14a : ffffffff`00000000 ffffc101`107c0180 00000000`00000000 ffffc101`107d0400 : nt!KiRetireDpcList+0x1ae

ffffd206`d9e2fb60 00000000`00000000 : ffffd206`d9e30000 ffffd206`d9e29000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a





THREAD_SHA1_HASH_MOD_FUNC: 2070539a446c869398e2553442605eb5448eeef5



THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 644f1fd5771b10b5079c17ab5d216960effb2ca1



THREAD_SHA1_HASH_MOD: 02ff5aba7d382c4e7f478d955433aed2f09c5c8f



FOLLOWUP_IP:

USBXHCI!DynamicLock_Acquire+74

fffff805`574f1794 4883c420 add rsp,20h



FAULT_INSTR_CODE: 20c48348



SYMBOL_STACK_INDEX: a



SYMBOL_NAME: USBXHCI!DynamicLock_Acquire+74



FOLLOWUP_NAME: MachineOwner



MODULE_NAME: USBXHCI



IMAGE_NAME: USBXHCI.SYS



DEBUG_FLR_IMAGE_TIMESTAMP: 0



IMAGE_VERSION: 10.0.17763.379



STACK_COMMAND: .thread ; .cxr ; kb



BUCKET_ID_FUNC_OFFSET: 74



FAILURE_BUCKET_ID: 0x133_VRF_DPC_USBXHCI!DynamicLock_Acquire



BUCKET_ID: 0x133_VRF_DPC_USBXHCI!DynamicLock_Acquire



PRIMARY_PROBLEM_CLASS: 0x133_VRF_DPC_USBXHCI!DynamicLock_Acquire



TARGET_TIME: 2019-04-24T21:15:10.000Z



OSBUILD: 17763



OSSERVICEPACK: 437



SERVICEPACK_NUMBER: 0



OS_REVISION: 0



SUITE_MASK: 272



PRODUCT_TYPE: 1



OSPLATFORM_TYPE: x64



OSNAME: Windows 10



OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS



OS_LOCALE:



USER_LCID: 0



OSBUILD_TIMESTAMP: 2005-12-02 08:58:59



BUILDDATESTAMP_STR: 180914-1434



BUILDLAB_STR: rs5_release



BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434



ANALYSIS_SESSION_ELAPSED_TIME: 8445



ANALYSIS_SOURCE: KM



FAILURE_ID_HASH_STRING: km:0x133_vrf_dpc_usbxhci!dynamiclock_acquire



FAILURE_ID_HASH: {eea3f8ff-b4cc-70e1-782a-8179c8a75205}



Followup: MachineOwner

---------

:)

 

DCP_Watchdog_Violation

Following install of W10 I'm now in DCP_Watchdog_Violation limbo. I have a 2013 Samsung XE500T and must rely on a usb cd/dvd player. Resetting it does not help.

 

Dcp_watchdog_violation?


hi there to anyone that sees this, I have been having some really annoying and frustrating problems with my PC lately. My PC keeps crashing an coming up with the blue screen of death saying DCP_WATCHDOG_VIOLATION which I did my homework and went and tried most of the logical youtube videos on where they went into device manager, power option and so on but nothing has fixed mine. What is different about my PC crashing is I will be mid way through a game using my 2tb hdd and once my pc crashes it will restart but then my 2tb hdd will be missing and I have no clue on how to fix this. If anyone has any thoughts or suggestions please say otherwise I will have to pay to get fixed.
P.S my system still runs because all my games and junk are stored on the hdd and my OS is on my ssd.

 

bluescreen

Hi,

Thank you for writing to Microsoft Community.

I understand that it can be frustrating for you when the computer shows bluescreen errors. Bluescreen errors are usually caused due to faulty hardware or drivers. We will try to narrow down the cause of the issue by performing a few steps.

1. Do you get bluescreen errors randomly or while performing any specific actions such as playing a game or running any particular application?
   
2. Do you see any error code along with the message “DRIVERS POWER STATE FAILURE”?
   
3. Are there any external devices connected to your computer?
   

The usual causes for bluescreen errors are Graphic card drivers and Network adapter drivers. We can go ahead and try to update the drivers.

Refer the article Update drivers in Windows 10 on how to update Graphic card
and Network drivers.

You may also refer the article Troubleshoot blue screen errors
for additional troubleshooting steps to fix the issue.

You can reply to this post if you need further assistance

Hope it helps.

Muralidhar

Microsoft Community Moderator