DPC_WATCHDOG_VIOLATION

p1xel8ted · Mar 20, 2013

Hello all, first time here and appreciate any help at all. Not an urgent matter, seems to only do it when I alt tab out of Tomb Raider too often. From what I can gather its being caused by Windows itself, but Ill leave that to the experts to decide.

View attachment Windows7_Vista_jcgriff2.zip

Windows 8 x64 Pro with Media Center (legit)
Asus Sabertooth x79 Mobo
2gb EVGA GTX 680
16gb Corsair DominatorGT 2133Mhz Ram
Enermax 1000w PSU
Fully Watercooled.
Intel SSD with System, games, apps on it.
2x WD Green Drives (1 new version, 1 old version) for storage.

Have run SFC to check, came back clean. Not overclocking at all. Running RAM according to XMP.

p1xel8ted · Mar 20, 2013

Code:

*******************************************************************************
*                                                                             *
*                        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: 0000000000000281, The DPC time count (in ticks).
Arg3: 0000000000000280, The DPC time allotment (in ticks).
Arg4: 0000000000000000


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




CUSTOMER_CRASH_COUNT:  1


DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT


BUGCHECK_STR:  0x133


PROCESS_NAME:  System


CURRENT_IRQL:  d


LAST_CONTROL_TRANSFER:  from fffff8026b5ed6ef to fffff8026b494040


STACK_TEXT:  
fffff880`01c83f48 fffff802`6b5ed6ef : 00000000`00000133 00000000`00000000 00000000`00000281 00000000`00000280 : nt!KeBugCheckEx
fffff880`01c83f50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x13c80




STACK_COMMAND:  kb


FOLLOWUP_IP: 
nt! ?? ::FNODOBFM::`string'+13c80
fffff802`6b5ed6ef cc              int     3


SYMBOL_STACK_INDEX:  1


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+13c80


FOLLOWUP_NAME:  MachineOwner


MODULE_NAME: nt


IMAGE_NAME:  ntkrnlmp.exe


DEBUG_FLR_IMAGE_TIMESTAMP:  50ecec77


FAILURE_BUCKET_ID:  X64_0x133_nt!_??_::FNODOBFM::_string_+13c80


BUCKET_ID:  X64_0x133_nt!_??_::FNODOBFM::_string_+13c80


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

usasma · Mar 20, 2013

You have a NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter:

I do not recommend using wireless USB network devices. Especially in Win7/Win8 systems.
These wireless USB devices have many issues with Win7(and I suspect with Win8) - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win7/Win8 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

C: drive only has about 2% free space. Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance. Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty)

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website). Be sure to update ALL controllers on the motherboard! I STRONGLY suggest not using controller drivers older than mid-2012 with SSD's.
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.
- Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
05 Jan 2013 - very interesting post about difficulties with the Marvell controllers even when not connected to the SSD drives: https://www.eightforums.com/bsod-cr...-pc-reboots-when-waking-sleep.html#post169956
27 Feb 2013 - I'm starting to see much better reliability with SSD's using current (mid-2012 and later) storage drivers. I have withdrawn my objections to using these devices in everyday systems.

These devices have issues:

Microsoft Kernel Debug Network Adapter ROOT\KDNIC\0000 This device is disabled.

Multiple Card Reader USB Device USBSTOR\DISK&VEN_MULTIPLE&PROD_CARD__READER&REV_1.00\058F63666438&0 This device is disabled.

eHome Infrared Receiver (USBCIR) USB\VID_0609&PID_0334\6&DBCE08D&0&1 This device cannot start.

The Network Adapter and Card Reader are disabled. Is this deliberate? If so, why?
Please remove the software for the Infrared Receiver and then download and install the latest, Win8 compatible version of the software from the manufacturer's website.

The memory dumps point to your video drivers. Please follow the troubleshooting steps from here: https://www.sysnative.com/forums/bs...-video-tdr-timeout-0x116-0x117.html#post29532

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

lirsgt.sys Sun May 17 09:06:57 2009 (4A100BF1)
part of a Copy Protection platform developed by Tages SA
http://www.carrona.org/drivers/driver.php?id=lirsgt.sys

atksgt.sys Sun May 17 09:36:34 2009 (4A1012E2)
part of a Copy Protection platform developed by Tages SA
http://www.carrona.org/drivers/driver.php?id=atksgt.sys

AsIO.sys Mon Aug 23 21:53:02 2010 (4C7325FE)
Asus PCProbe Utility
http://www.carrona.org/drivers/driver.php?id=AsIO.sys

VClone.sys Sat Jan 15 11:21:04 2011 (4D31C970)
VirtualCloneCD Driver by Elaborate Bytes AG
http://www.carrona.org/drivers/driver.php?id=VClone.sys

bcmwlhigh664.sys Tue Apr 19 03:13:08 2011 (4DAD3604)
Broadcom 802.11 USB Network Adapter Driver
http://www.carrona.org/drivers/driver.php?id=bcmwlhigh664.sys

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Wed Mar 20 02:11:54.480 2013 (UTC - 4:00)**************************
Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032013-20906-01.dmp]
Windows 8 Kernel Version 9200 MP (12 procs) Free x64
Built by: [B]9200[/B].16496.amd64fre.win8_gdr.130108-1504
System Uptime:[B]0 days 1:02:18.141[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+202c04 )[/B]
BugCheck [B]133, {0, 281, 280, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000133]DPC_WATCHDOG_VIOLATION (133)[/url]
Arguments: 
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
	component can usually be identified with a stack trace.
Arg2: 0000000000000281, The DPC time count (in ticks).
Arg3: 0000000000000280, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x133_DPC_nvlddmkm+202c04[/B]
CPUID:        "Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz"
MaxSpeed:     3200
CurrentSpeed: [B]3200[/B]
  BIOS Version                  3305
  BIOS Release Date             12/25/2012
  Manufacturer                  System manufacturer
  Product Name                  System Product Name
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Wed Mar 20 02:11:54.480 2013 (UTC - 4:00)**************************
[COLOR=RED][B]lirsgt.sys                  Sun May 17 09:06:57 2009 (4A100BF1)[/B][/COLOR]
[COLOR=RED][B]atksgt.sys                  Sun May 17 09:36:34 2009 (4A1012E2)[/B][/COLOR]
[COLOR=RED][B]AsIO.sys                    Mon Aug 23 21:53:02 2010 (4C7325FE)[/B][/COLOR]
[COLOR=RED][B]VClone.sys                  Sat Jan 15 11:21:04 2011 (4D31C970)[/B][/COLOR]
[COLOR=RED][B]bcmwlhigh664.sys            Tue Apr 19 03:13:08 2011 (4DAD3604)[/B][/COLOR]
asahci64.sys                Thu Jan  5 00:08:19 2012 (4F053043)
mv91cons.sys                Wed Jun  6 06:26:38 2012 (4FCF305E)
mvxxmm.sys                  Wed Jun  6 23:09:05 2012 (4FD01B51)
mvs91xx.sys                 Wed Jun  6 23:09:20 2012 (4FD01B60)
RTKVHD64.sys                Tue Jun 12 06:02:32 2012 (4FD713B8)
HECIx64.sys                 Thu Jul 12 22:18:26 2012 (4FFF8572)
intelppm.sys                Mon Nov  5 22:55:02 2012 (50988A16)
dump_iaStorA.sys            Mon Nov 19 15:09:40 2012 (50AA9204)
iaStorA.sys                 Mon Nov 19 15:09:40 2012 (50AA9204)
idmwfp.sys                  Wed Nov 21 09:42:58 2012 (50ACE872)
nvhda64v.sys                Wed Dec 19 00:41:41 2012 (50D15395)
ElbyCDIO.sys                Mon Mar  4 04:21:51 2013 (513467AF)
AnyDVD.sys                  Mon Mar  4 09:01:41 2013 (5134A945)
nvlddmkm.sys                Thu Mar 14 03:29:32 2013 (51417C5C)
[/font]

p1xel8ted · Mar 20, 2013

Thanks for the info, how come your analysis results differ from mine, yours says its the video drivers, mine just says system.

writhziden · Mar 20, 2013

It depends on what version of the debugging tools or Windows kits you use. What version of WinDbg do you have on your system?

DPC_WATCHDOG_VIOLATION

p1xel8ted

New member

p1xel8ted

New member

usasma

Retired Admin

p1xel8ted

New member

writhziden

Administrator, .NET/UWP Developer