Windows 10: DCP_WATCHDOG_VIOLATION happening everyday

I'm constantly getting DCP_WATCHDOG_VIOLATION everyday. The crash dump says it's probably caused by nvlddmkm. I've removed my Nvidia driver with DDU and did a clean install but it's still happening.


Here is the dump from the most recent crash.

https://1drv.ms/u/s!Apo0P17F-1RFgdlEu0wbYdeLChVgQA

The dump content when opened in WinDbg:

==============================================

Microsoft (R) Windows Debugger Version 10.0.17763.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\110718-6796-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 17134 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17134.1.amd64fre.rs4_release.180410-1804
Machine Name:
Kernel base = 0xfffff803`ab68f000 PsLoadedModuleList = 0xfffff803`aba3d290
Debug session time: Wed Nov 7 10:11:19.910 2018 (UTC - 8:00)
System Uptime: 0 days 10:20:20.609
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..........................................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 133, {1, 1e00, fffff803abadc378, 0}

*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.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
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KeAccumulateTicks+1187d5 )

Followup: MachineOwner
---------

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: fffff803abadc378, 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


STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 17134.1.amd64fre.rs4_release.180410-1804

SYSTEM_MANUFACTURER: Gigabyte Technology Co., Ltd.

SYSTEM_PRODUCT_NAME: Z170XP-SLI

SYSTEM_SKU: Default string

SYSTEM_VERSION: Default string

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: F22f

BIOS_DATE: 03/09/2018

BASEBOARD_MANUFACTURER: Gigabyte Technology Co., Ltd.

BASEBOARD_PRODUCT: Z170XP-SLI-CF

BASEBOARD_VERSION: x.x

DUMP_TYPE: 2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff803abadc378

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 8

CPU_MHZ: d50

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 5e

CPU_STEPPING: 3

CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C2'00000000 (cache) C2'00000000 (init)

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: RZ-DESKTOP

ANALYSIS_SESSION_TIME: 11-07-2018 10:15:47.0947

ANALYSIS_VERSION: 10.0.17763.1 amd64fre

LAST_CONTROL_TRANSFER: from fffff803ab88a495 to fffff803ab838490

STACK_TEXT:
fffff803`ab3f0b78 fffff803`ab88a495 : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`abadc378 : nt!KeBugCheckEx
fffff803`ab3f0b80 fffff803`ab76e1ad : 00004adb`e61396be fffff803`aacc8180 00000000`00000246 00000000`00245927 : nt!KeAccumulateTicks+0x1187d5
fffff803`ab3f0be0 fffff803`ab76f293 : fffff780`00000340 00000000`00000000 00000000`00245927 00000000`00000000 : nt!KiUpdateRunTime+0x5d
fffff803`ab3f0c30 fffff803`ab604883 : 00004adb`e6134234 00000000`0010a1c4 00000000`00000000 fffff902`1a4765a0 : nt!KeClockInterruptNotify+0x8f3
fffff803`ab3f0f40 fffff803`ab7bbd75 : fffff803`ab665cb0 ffff8c80`0f3bb280 ffff8c80`0f3bb280 00000000`00000000 : hal!HalpTimerClockInterrupt+0x63
fffff803`ab3f0f70 fffff803`ab839d4a : fffff902`1a476620 fffff803`ab665cb0 ffffd68d`23021f90 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff803`ab3f0fb0 fffff803`ab83a237 : fffff803`aacc8180 ffff8c80`0f3bb280 00000000`00000000 ffffd68d`1fe5e000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff902`1a4765a0 fffff803`ab83f1e8 : ffff8c80`0f3bb280 fffff803`ab6064e6 fffff902`1a476950 ffffd68d`23021000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff902`1a476730 fffff803`ab83eb15 : ffffd68d`23021000 fffff803`ab839671 00000000`00000000 ffff8c80`0f3bb280 : nt!KiDispatchInterruptContinue+0x8
fffff902`1a476760 fffff803`ab839671 : 00000000`00000000 ffff8c80`0f3bb280 fffff803`ab665bb0 fffff803`ab6064e6 : nt!KiDpcInterruptBypass+0x25
fffff902`1a476770 fffff803`af5e6aa6 : fffff803`af60cbf6 00000000`00000000 00000000`00000000 00000000`0010a1c4 : nt!KiChainedDispatch+0xb1
fffff902`1a476908 fffff803`af60cbf6 : 00000000`00000000 00000000`00000000 00000000`0010a1c4 00000000`00000000 : nvlddmkm+0x1e6aa6
fffff902`1a476910 00000000`00000000 : 00000000`00000000 00000000`0010a1c4 00000000`00000000 ffffd68d`00000000 : nvlddmkm+0x20cbf6


THREAD_SHA1_HASH_MOD_FUNC: 2f7df49311e2707781eacfb5bd7ac6e2f9025231

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 88d081cb8373d7e2f78414907a6d5c538051ee5a

THREAD_SHA1_HASH_MOD: 548a9ef27e2c9a6a0c91ea974b9eba29a6868379

FOLLOWUP_IP:
nt!KeAccumulateTicks+1187d5
fffff803`ab88a495 cc int 3

FAULT_INSTR_CODE: ab3944cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KeAccumulateTicks+1187d5

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 5ba316ae

IMAGE_VERSION: 10.0.17134.345

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1187d5

FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

PRIMARY_PROBLEM_CLASS: 0x133_ISR_nt!KeAccumulateTicks

TARGET_TIME: 2018-11-07T18:11:19.000Z

OSBUILD: 17134

OSSERVICEPACK: 345

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: 2018-09-19 20:40:30

BUILDDATESTAMP_STR: 180410-1804

BUILDLAB_STR: rs4_release

BUILDOSVER_STR: 10.0.17134.1.amd64fre.rs4_release.180410-1804

ANALYSIS_SESSION_ELAPSED_TIME: 7181

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_isr_nt!keaccumulateticks

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

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.

 

Edge Search Does Not Permit Change of Region


I got these suggestions from the Microsoft Community forum.No. 1 worked for me:

Thank you for posting the query on Microsoft Community. I am glad to assist you on this.
We have reproduce the issue here and we are able to access non-regional search for google using Microsoft Edge.
I would suggest you to try the below steps and check if it helps.
Step 1:
Clear browsing data option of Microsoft Edge and check if you face the issue. To do so perform the steps below.

1. Click on the More actions icon next to the feedback icon present on top right corner of the Project Spartan homepage.
2. Select Settings and click on Choose what to clear.
3. Check the boxes Browsing history, Cookies and saved website data and Cached data and files and click on Clear.

Step 2:
I suggest you to create a new user account and check if the issue occurs.

1. Go to Settings.
2. Choose Accounts and then select Family and other users.
3. Select add someone else on this PC.
4. Enter a user name and hit next.
5. Click on Finish.
6. Sign out from the current Account and Log into the new account.

Step 3:
It could also happen because of network issue. I suggest you to try with different network connection and check if it helps.

 

Hi (Rongduan Zhu),


I'm also having this DPC_WATCHDOG_VIOLATION almost everyday.
I compared my dump with yours. And it is almost the same.

As for the hardware: You have a Z170, I have a H170.
Intel Core i5-6600 6the Gen. CPU is the same (CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: C2'00000000 (cache) C2'00000000 (init))

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: fffff802a245d378, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Same FAULT_INSTR_CODE: ab3944cc


For your information. I had this BSOD on my nVidia MSI 970.
Last week replaced this videocard with the new MSI 1070 Ti and still having BSOD DPC!
So, it is not the videocard hardware that was the issue. Powersupply is 650W.
I'm running Windows 10 1803 (17134.345) on Samsung EVO 850 SSD.

but ... after everything still no solution....

 

a solution was found with the tool: MSI_util_v2.exe
CHEF-KOCH/MSI-utility

1. Download the MSI Utility v2.0 zip file
2. Open the zip file and then extract "MSI_util_v2.exe" to your local system.
3. Right-click the "MSI_util_v2.exe" and Run as administrator.
4. Enable MSI for each GPU listed.
5. Restart the system.

No more BSOD