Forum Home
Press F1
 
Thread ID: 143981 2017-05-29 21:01:00 DPC_WATCHDOG_VIOLATION BSOD error DeSade (984) Press F1
Post ID Timestamp Content User
1435867 2017-05-30 05:49:00 Heres eh complete result:

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

Debugging Details:

DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 15063.0.amd64fre.rs2_release.170317-1834

SYSTEM_MANUFACTURER: ASUS

SYSTEM_PRODUCT_NAME: All Series

SYSTEM_SKU: All

SYSTEM_VERSION: System Version

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 2009

BIOS_DATE: 01/18/2016

BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.

BASEBOARD_PRODUCT: X99-E WS

BASEBOARD_VERSION: Rev 1.xx

DUMP_TYPE: 2

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff802121ed348

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CPU_COUNT: 10

CPU_MHZ: bbd

CPU_VENDOR: GenuineIntel

CPU_FAMILY: 6

CPU_MODEL: 3f

CPU_STEPPING: 2

CPU_MICROCODE: 6,3f,2,0 (F,M,S,R) SIG: 36'00000000 (cache) 36'00000000 (init)

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: Diligent.Board

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: LOUNGE

ANALYSIS_SESSION_TIME: 05-30-2017 16:43:53.0433

ANALYSIS_VERSION: 10.0.10586.567 amd64fre

LAST_CONTROL_TRANSFER: from fffff80211fa16af to fffff80211f78310

STACK_TEXT:
fffff802`13c463f8 fffff802`11fa16af : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`121ed348 : nt!KeBugCheckEx
fffff802`13c46400 fffff802`11e62db9 : 0001538f`2b61fb9c fffff802`10a3b180 00000000`00795f3e 00000000`00000007 : nt!KeAccumulateTicks+0x13cc5f
fffff802`13c46460 fffff802`12698676 : 0001538f`2b61e885 ffffce8a`ac07c000 fffff802`13c46830 fffff802`126e8460 : nt!KeClockInterruptNotify+0x599
fffff802`13c46770 fffff802`11ea9255 : fffff802`126e83b0 fffff802`12698676 0001538f`2b1cfd52 ffffce8a`ac07c000 : hal!HalpTimerClockInterrupt+0x56
fffff802`13c467a0 fffff802`11f799aa : fffff802`13c468b0 fffff802`126e83b0 fffff802`13c46ca0 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff802`13c467e0 fffff802`11f79df7 : fffff802`13c46ca0 00000000`00000000 0001538f`2b060588 fffff802`11f79df7 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
fffff802`13c46830 fffff80f`607fa7f9 : fffff80f`60839563 ffffce8a`b13a6000 ffffce8a`b13a6000 ffffce8a`b16a8930 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff802`13c469c8 fffff80f`60839563 : ffffce8a`b13a6000 ffffce8a`b13a6000 ffffce8a`b16a8930 00000000`00000000 : nvlddmkm+0x1aa7f9
fffff802`13c469d0 ffffce8a`b13a6000 : ffffce8a`b13a6000 ffffce8a`b16a8930 00000000`00000000 ffffce8a`00000020 : nvlddmkm+0x1e9563
fffff802`13c469d8 ffffce8a`b13a6000 : ffffce8a`b16a8930 00000000`00000000 ffffce8a`00000020 fffff802`13c46a10 : 0xffffce8a`b13a6000
fffff802`13c469e0 ffffce8a`b16a8930 : 00000000`00000000 ffffce8a`00000020 fffff802`13c46a10 fffff802`13c46ca0 : 0xffffce8a`b13a6000
fffff802`13c469e8 00000000`00000000 : ffffce8a`00000020 fffff802`13c46a10 fffff802`13c46ca0 fffff80f`60836ab4 : 0xffffce8a`b16a8930


STACK_COMMAND: kb

THREAD_SHA1_HASH_MOD_FUNC: 73862278aea89c6e9afe926a97214e8bed469217

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 62aade81148608c7489cba9cecbfc898d25e01c4

THREAD_SHA1_HASH_MOD: b65638c546229c8b9c3693c2a82ed471ad9bee32

FOLLOWUP_IP:
nvlddmkm+1aa7f9
fffff80f`607fa7f9 c3 ret

FAULT_INSTR_CODE: 8accccc3

SYMBOL_STACK_INDEX: 7

SYMBOL_NAME: nvlddmkm+1aa7f9

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 591d2b35

BUCKET_ID_FUNC_OFFSET: 1aa7f9

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-05-29T08:08:46.000Z

OSBUILD: 15063

OSSERVICEPACK: 0

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: 2017-04-28 11:52:30

BUILDDATESTAMP_STR: 170317-1834

BUILDLAB_STR: rs2_release

BUILDOSVER_STR: 10.0.15063.0.amd64fre.rs2_release.170317-1834

ANALYSIS_SESSION_ELAPSED_TIME: 981f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_isr_nvlddmkm!unknown_function

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

Followup: MachineOwner
--------- 		wainuitech (129)
1435868 2017-05-30 06:08:00 The above log, missed one line at the beginning that says

"This was likely caused by the following module: nvlddmkm.sys" 		wainuitech (129)
1435869 2017-06-03 05:21:00 So I have reinstalled all nVidia drivers from the source after doing a complete driver removal.
The BSOD is still occurring.

What am I missing? 		DeSade (984)
1435870 2017-06-04 04:05:00 Have a read of this (www.tomshardware.com)

I would either install an old version of the drivers, (if the card is a brand, get the drivers off that site, even if theyre old). They'll probably be more stable

Or disable the audio drivers (the drivers that install with the videocard drivers) 		Speedy Gonzales (78)
1435871 2017-06-04 04:47:00 I did disable the audio drivers but when I went to check that just now they were enabled again.
Any idea how to disable them for good? 		DeSade (984)
1435872 2017-06-12 21:30:00 I have created a thread here with dumps and mini dumps but I need more exposure to it.
I am seriously worried about damage to my machine with all these crashes.

answers.microsoft.com 		DeSade (984)
1435873 2017-06-12 23:17:00 Well if VPN software is causing it as well. Not much you can do about it, if you wont uninstall it to fix it Speedy Gonzales (78)
1435874 2017-06-12 23:55:00 I'm no expert in this but I hardly ever use the VPN.
I never used it yesterday for instance and crashed 4 times. 		DeSade (984)
1435875 2017-06-12 23:58:00 So did you try the older driver version 340.52. as suggested in the Tom's Hardware thread that Speedy linked? KarameaDave (15222)
1435876 2017-06-13 00:07:00 So did you try the older driver version 340.52. as suggested in the Tom's Hardware thread that Speedy linked?

Yes I did

I have gone through 4 nVidia drivers through this issue.

382.33 to >
340.52 to > back to 382.33 after crashing

382.33 to >
382.53 > then straight to
381.78 which is current 		DeSade (984)
1 2 3 4