Blue Screen DPC_WATCHDOG_VIOLATION (133)

[hotaren]

So I had this problem a few months ago after I uninstalled my notebook's factory software (ASUS Splendid).
It happens every few times after I booted my notebook and the blue screens shows error code such as dpc_watchdog_violation, video_scheduler_internal_error, or video_tdr_failure.
I tried re-istalling NVidia driver as I suspect is the cause, but the problem persists.

If it helps, I'm running on Windows 10 64-bit and my notebook uses Intel HD Graphics for desktop and NVidia GTX for any other application performances.

Here's the latest the minidump:

Spoiler

*******************************************************************************
* *
* 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: 0000000000000000
Arg4: 0000000000000000

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


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 10.0.14393.693 (rs1_release.161220-1747)

SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.

SYSTEM_PRODUCT_NAME: GL552JX

SYSTEM_SKU: ASUS-NotebookSKU

SYSTEM_VERSION: 1.0

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: GL552JX.207

BIOS_DATE: 08/11/2015

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: GL552JX

BASEBOARD_VERSION: 1.0

DUMP_TYPE: 2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: 0

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 8

CPU_MHZ: a22

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3c

CPU_STEPPING: 3

CPU_MICROCODE: 6,3c,3,0 (F,M,S,R) SIG: 1E'00000000 (cache) 1E'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: REN

ANALYSIS_SESSION_TIME: 02-16-2017 13:53:12.0436

ANALYSIS_VERSION: 10.0.14321.1024 amd64fre

LAST_CONTROL_TRANSFER: from fffff80168c1a000 to fffff80168bc46f0

STACK_TEXT:
fffff801`6b199d88 fffff801`68c1a000 : 00000000`00000133 00000000`00000001 00000000`00001e00 00000000`00000000 : nt!KeBugCheckEx
fffff801`6b199d90 fffff801`68b45b99 : 000002ea`64c49978 000002ea`64c4974c fffff780`00000320 fffff801`68a53490 : nt! ?? ::FNODOBFM::`string'+0x46470
fffff801`6b199df0 fffff801`68a08366 : fffff801`6b18ab50 fffff801`68a533e0 00000000`00000002 000002ea`64c4974c : nt!KeClockInterruptNotify+0x469
fffff801`6b199f40 fffff801`68ad15d6 : fffff801`68a533e0 00000000`00000008 fffff801`6b199f50 00000000`00000010 : hal!HalpTimerClockInterrupt+0x56
fffff801`6b199f70 fffff801`68bc5d6a : fffff801`6b18abd0 fffff802`2e628b14 fffff801`6b18b888 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x106
fffff801`6b199fb0 fffff801`68bc61b7 : 0004f530`00820000 00000000`00000000 00000013`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff801`6b18ab50 fffff801`68b0edc5 : ffffcd80`001a3637 fffff801`6b18ae78 00000000`0000000e fffff801`6b18b628 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff801`6b18ace0 fffff801`68b0e673 : 00000000`00000100 ffffe384`81904000 ffffe384`00000000 fffff802`2e0d220a : nt!RtlpWalkFrameChain+0x565
fffff801`6b18b400 fffff801`68b0bccc : 00000000`0000000d fffff801`6b18b4b8 ffffe384`802f4940 fffff801`6b186000 : nt!RtlWalkFrameChain+0x93
fffff801`6b18b450 fffff802`2e0cb882 : ffffe384`802f3750 fffff801`6b18b5b0 00000000`00000000 00000000`00000000 : nt!RtlCaptureStackBackTrace+0x44
fffff801`6b18b480 ffffe384`802f3750 : fffff801`6b18b5b0 00000000`00000000 00000000`00000000 00000000`00000001 : nvlddmkm+0x1bb882
fffff801`6b18b488 fffff801`6b18b5b0 : 00000000`00000000 00000000`00000000 00000000`00000001 fffff802`2e0a1396 : 0xffffe384`802f3750
fffff801`6b18b490 00000000`00000000 : 00000000`00000000 00000000`00000001 fffff802`2e0a1396 fffff801`68e37940 : 0xfffff801`6b18b5b0


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 48cd0fe845a86098f636240581c27f06d9927c22

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 371ebcf454ace855dd075617c30ef0df9e9758ad

THREAD_SHA1_HASH_MOD: 2131cf11cab813b532d1229bd4dd270e2dbd5e0c

FOLLOWUP_IP:
nvlddmkm+1bb882
fffff802`2e0cb882 488b442438 mov rax,qword ptr [rsp+38h]

FAULT_INSTR_CODE: 24448b48

SYMBOL_STACK_INDEX: a

SYMBOL_NAME: nvlddmkm+1bb882

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 588210d7

BUCKET_ID_FUNC_OFFSET: 1bb882

FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function

PRIMARY_PROBLEM_CLASS: 0x133_ISR_nvlddmkm!unknown_function

TARGET_TIME: 2017-02-16T04:45:16.000Z

OSBUILD: 14393

OSSERVICEPACK: 693

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 784

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2016-12-21 13:50:57

BUILDDATESTAMP_STR: 161220-1747

BUILDLAB_STR: rs1_release

BUILDOSVER_STR: 10.0.14393.693

ANALYSIS_SESSION_ELAPSED_TIME: 113f1

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm!unknown_function

FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86}

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

I'd be glad if someone could point out my problem. Here's the Minidump files of the time when blue screen starts to appear and the latest one.

 

[The_Staplergun]

Are you using Windows 8? This is something I saw if so:
http://www.reviversoft.com/blog/2012/11/a-guide-to-blue-screens-of-death-dpc-watchdog-violation/

 

[hotaren]

Are you using Windows 8? This is something I saw if so:
http://www.reviversoft.com/blog/2012/11/a-guide-to-blue-screens-of-death-dpc-watchdog-violation/

How can I even forget to state my OS.
I've been using Windows 10 ever since I use my notebook, but I'll check the link, thanks for the reply.

 

[troy1960]

I've had this too after instability with overclocking. Called Microsoft and they managed to fix it all up.

 

[Maarsch]

I had only the watchdog
This has a list of all the things I've tried: my thread
All the things mentioned under "things I've tried" are suggestions from different part of the internet

Only solution that ended up working for me was a complete re-install.

Considering you have a bunch of different BSODs your issue will probably be something different.
But running through the solutions mentioned may still help (googling DPC WATCHDOG and my keyword should probably get you the detailed solution)