Dpc_watchdog_violation

bradh · 10-02-2014, 09:42 PM

Hi,
We have numerous Surface Pro tablets using dock's that have serious stability issues. I first thought this was to do with faulty Tablets and have had several replacements sent out by Microsoft, and have installed all the latest drivers and firmware for them. But the problem persists and is possibly being caused by the DisplayLink drivers.
Here is our current setup:
- Surface Pro 2 128GB Tablets
- Toshiba Dynadock U3.0 (PA3927A-1PRP) Docks
- Windows 8.1 Enterprise OS (64-bit)
- DisplayLink drivers installed: "DisplayLink_7.6M2.exe"

They will randomely crash 1-2 times a day with the DPC_WATCHDOG_VIOLATION blue screens.
Bugcheck is detailed below. And I'm also attaching the ZIP file from running the DisplayLink Support Tool" Is someone able to analyse this for me to try and narrow down what is happening? Thanks.

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

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

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x133

PROCESS_NAME: System

CURRENT_IRQL: d

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

LAST_CONTROL_TRANSFER: from fffff802cd7aaad6 to fffff802cd76afa0

STACK_TEXT:
ffffd001`18030c98 fffff802`cd7aaad6 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd001`18030ca0 fffff802`cd6caf85 : 00000000`00000001 00000000`00000000 00000000`7fffffff fffff801`b087cf99 : nt! ?? ::FNODOBFM::`string'+0x2f626
ffffd001`18030d30 fffff802`cdda87b5 : 00000000`00400a02 fffff802`cd701426 fffff801`b0217ab0 00000000`0000b101 : nt!KeClockInterruptNotify+0x95
ffffd001`18030f40 fffff802`cd6e6363 : ffffd001`18030f60 00000000`00000008 ffff26f6`130b00ed 00000000`00000010 : hal!HalpTimerClockIpiRoutine+0x15
ffffd001`18030f70 fffff802`cd76c42a : fffff802`cddf4d00 ffffd001`141fc960 00000000`00000000 ffffe000`99c0d000 : nt!KiCallInterruptServiceRoutine+0xa3
ffffd001`18030fb0 fffff802`cd76c80f : 00000001`11f80000 00000000`00000100 00000000`00000000 00000000`00000004 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffd001`141fc750 fffff802`cd6bcc24 : ffffe000`99c0d000 fffff801`b06c0462 ffffd001`141fc998 00000000`00000000 : nt!KiInterruptDispatchLBControl+0x11f
ffffd001`141fc8e0 fffff801`b06d896f : ffffe000`99c0d000 00000000`00000100 00000400`00000000 00000000`00000000 : nt!KxWaitForLockOwnerShip+0x34
ffffd001`141fc910 fffff801`b07750f4 : 00000000`00000001 ffffe000`9840a6d0 ffffe000`9ac1a4e0 fffff801`00000000 : igdkmd64+0x6096f
ffffd001`141fc9c0 fffff801`b06bf763 : ffffd001`141fcb49 ffffe000`99c13488 ffffe000`9ac00000 ffffe000`9840a6d0 : igdkmd64+0xfd0f4
ffffd001`141fca20 fffff801`b06c96d9 : 00000000`00000000 ffffe000`99c0d000 00000000`00000002 00000000`00000000 : igdkmd64+0x47763
ffffd001`141fca60 fffff801`b07054de : ffffe000`99c0d000 ffffe000`9840a6d0 ffffe000`00000000 fffff801`b06867bf : igdkmd64+0x516d9
ffffd001`141fcb90 fffff801`b068f9b0 : ffffe000`99c0d000 ffffd001`141fcd10 fffff801`b079ae90 00000000`124c0000 : igdkmd64+0x8d4de
ffffd001`141fcc10 fffff801`b0062dd4 : fffff801`ffffffff ffffe000`9a4ee4f0 00000000`ffffffff ffffe000`9c161ab0 : igdkmd64+0x179b0
ffffd001`141fcde0 fffff801`b0217b97 : 00000000`0000000b ffffd001`141fd278 ffffe000`9a1952f0 ffffe000`98c3b000 : dlkmd+0x15dd4
ffffd001`141fd070 fffff801`b00ea44b : ffffd001`141fd270 fffff801`b00ea41c ffffe000`98c3b040 ffffd001`141fd278 : dxgkrnl!ADAPTER_DISPLAY_DdiSetVidPnSourceAddress+0 x67
ffffd001`141fd0a0 fffff802`cd76bc32 : ffffe000`99a45190 00000000`00000000 ffffe000`988a9801 fffff802`cdda658f : dxgmms1!VidSchiExecuteMmIoFlipAtISR+0x2f
ffffd001`141fd0d0 fffff801`b021773f : ffffe000`9803f688 fffff801`b00ea41c ffffd001`141fd270 00000001`ffffffff : nt!KeSynchronizeExecution+0x42
ffffd001`141fd110 fffff801`b00dfaf1 : ffffe000`9beaddc8 ffffd001`141fd2a0 00000000`00000000 ffffe000`9a8a1000 : dxgkrnl!DpSynchronizeExecution+0xaf
ffffd001`141fd160 fffff801`b00e08f1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`0000000a : dxgmms1!VidSchiExecuteMmIoFlip+0x241
ffffd001`141fd510 fffff801`b00e34cb : 00000000`00000000 ffffe000`9b4c4410 ffffe000`9a8a1000 00000000`ffffffff : dxgmms1!VidSchUnwaitFlipQueue+0x251
ffffd001`141fd570 fffff801`b00e20b3 : ffffe000`99a45100 fffff801`00000000 ffffe000`00000000 00000000`0000000f : dxgmms1!VidSchiProcessDpcCompletedPacket+0x63b
ffffd001`141fd680 fffff801`b00e1f84 : 00000000`00000000 ffffe000`9803fbb0 ffffe000`9a8a1000 fffff801`b0217a1a : dxgmms1!VidSchiProcessDpcDmaPacket+0xb3
ffffd001`141fd6d0 fffff801`b021798a : ffffe000`99a45040 00000000`00000004 00000000`00000000 00000000`00000020 : dxgmms1!VidSchDdiNotifyDpc+0xf4
ffffd001`141fd720 fffff801`b0766865 : ffffe000`99c0d000 00000000`00000004 00000000`00000000 fffff801`b0249d08 : dxgkrnl!DxgNotifyDpcCB+0x5a
ffffd001`141fd750 fffff801`b072b857 : 00000000`00000001 ffffd001`141fd960 ffffe000`999b2020 ffffe000`99c0d000 : igdkmd64+0xee865
ffffd001`141fd780 fffff801`b06a5b70 : ffff7a5c`00000010 ffffe000`00000000 ffffe000`99c0d000 00006130`b77ed238 : igdkmd64+0xb3857
ffffd001`141fd7e0 fffff801`b0217e3f : ffffe000`982c7000 ffffe000`980fc060 fffff801`00000610 fffff801`aef8fc81 : igdkmd64+0x2db70
ffffd001`141fd810 fffff802`cd6711e0 : ffffd001`18002f00 fffff802`cd617000 fffff802`cd8c2580 fffff802`cd6ce950 : dxgkrnl!DpiFdoDpcForIsr+0x3b
ffffd001`141fd860 fffff802`cd6703fb : ffffd001`18000180 ffffe000`9c28d000 ffffe000`9805c900 00000000`005b698f : nt!KiExecuteAllDpcs+0x1b0
ffffd001`141fd9b0 fffff802`cd76eaea : ffffd001`18000180 ffffd001`18000180 ffffd001`1800c2c0 ffffe000`9c4ae880 : nt!KiRetireDpcList+0xdb
ffffd001`141fdc60 00000000`00000000 : ffffd001`141fe000 ffffd001`141f8000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_IP:
igdkmd64+6096f
fffff801`b06d896f eb1c jmp igdkmd64+0x6098d (fffff801`b06d898d)

SYMBOL_STACK_INDEX: 8

SYMBOL_NAME: igdkmd64+6096f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: igdkmd64

IMAGE_NAME: igdkmd64.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 5319ef18

FAILURE_BUCKET_ID: 0x133_DPC_igdkmd64+6096f

BUCKET_ID: 0x133_DPC_igdkmd64+6096f

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:0x133_dpc_igdkmd64+6096f

FAILURE_ID_HASH: {6ceaa5be-d197-0c38-e48e-58d23e731d2b}

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

"

JamesH · 10-06-2014, 02:56 PM

Hi,

Can you try the latest Intel graphics drivers (in ZIP format) from here?
https://downloadcenter.intel.com/Det...ng&ProdId=3719

It's likely that you'll need to install the drivers using this method:
http://www.intel.com/support/graphics/sb/CS-033915.htm

It's also worth installing the latest Surface Pro firmware and driver pack from here: http://www.microsoft.com/en-gb/downl....aspx?id=38826

Thanks,
James

bradh · 10-06-2014, 04:46 PM

Hi James,
Thanks for the suggestions. I'm away on a training course for the week, so won't be able to try this till next week.

I'll try the driver update...although last time I attempted something similar on the Surface Pro's it wouldn't let me install a graphics driver for the device that didn't come from the Microsoft update site.

And I'm already on the latest firmware as far as I'm aware.

cheers.

bradh · 10-12-2014, 10:08 PM

Hi again,
Unfortunately as I thought, if I try and install this updated video card driver I get an error message on the Surface Pro 2 (running EXE installer) - "The driver being installed is not validated for this computer. Please obtain the appropriate driver from the computer manufacturer".

If I try extracting the ZIP file and updating driver from Device Manager (as per second article linked above), it tells me - "Windows has determined the driver software for your device is up to date").

So it appears the latest video driver I have from Microsoft is the latest one that can be installed on a surface pro 2. This is from the July firmware release which I believe is the latest one available.

Driver Date = 7/03/2014
Driver Version = 10.18.10.3496

Any other suggestions? I don't suppose you are familiar with the diagnosis tool and can analyze the logs I attached to my original email?

Thanks.

bradh · 10-12-2014, 10:39 PM

Actually, just managed to get it installed.
Had to remove the current display adapter and delete the drivers for it. Then scan for new hardware and have it detect as 'microsoft basic display adapter".

I could then run and install the latest intel drivers.

Date = 5/08/2014
Version = 10.18.10.3907

I'll start some testing to see if stability is improved...

bradh · 11-24-2014, 09:06 PM

Quick update on this.
The stability does seem to be improved since the installation of the Intel video drivers. The user who had been reported this issue the most has said him machine isn't crashing anymore.

Will also have to try with the latest 7.7 release of the software to see how we get on.

cheers.

10-06-2014, 02:56 PM	#2
JamesH Senior Member Join Date: Jan 2012 Posts: 1,523	Hi, Can you try the latest Intel graphics drivers (in ZIP format) from here? https://downloadcenter.intel.com/Det...ng&ProdId=3719 It's likely that you'll need to install the drivers using this method: http://www.intel.com/support/graphics/sb/CS-033915.htm It's also worth installing the latest Surface Pro firmware and driver pack from here: http://www.microsoft.com/en-gb/downl....aspx?id=38826 Thanks, James

10-06-2014, 04:46 PM	#3
bradh Junior Member Join Date: Oct 2014 Posts: 5	Hi James, Thanks for the suggestions. I'm away on a training course for the week, so won't be able to try this till next week. I'll try the driver update...although last time I attempted something similar on the Surface Pro's it wouldn't let me install a graphics driver for the device that didn't come from the Microsoft update site. And I'm already on the latest firmware as far as I'm aware. cheers.

10-12-2014, 10:08 PM	#4
bradh Junior Member Join Date: Oct 2014 Posts: 5	Hi again, Unfortunately as I thought, if I try and install this updated video card driver I get an error message on the Surface Pro 2 (running EXE installer) - "The driver being installed is not validated for this computer. Please obtain the appropriate driver from the computer manufacturer". If I try extracting the ZIP file and updating driver from Device Manager (as per second article linked above), it tells me - "Windows has determined the driver software for your device is up to date"). So it appears the latest video driver I have from Microsoft is the latest one that can be installed on a surface pro 2. This is from the July firmware release which I believe is the latest one available. Driver Date = 7/03/2014 Driver Version = 10.18.10.3496 Any other suggestions? I don't suppose you are familiar with the diagnosis tool and can analyze the logs I attached to my original email? Thanks.

10-12-2014, 10:39 PM	#5
bradh Junior Member Join Date: Oct 2014 Posts: 5	Actually, just managed to get it installed. Had to remove the current display adapter and delete the drivers for it. Then scan for new hardware and have it detect as 'microsoft basic display adapter". I could then run and install the latest intel drivers. Date = 5/08/2014 Version = 10.18.10.3907 I'll start some testing to see if stability is improved...

11-24-2014, 09:06 PM	#6
bradh Junior Member Join Date: Oct 2014 Posts: 5	Quick update on this. The stability does seem to be improved since the installation of the Intel video drivers. The user who had been reported this issue the most has said him machine isn't crashing anymore. Will also have to try with the latest 7.7 release of the software to see how we get on. cheers.