DPC_Watchdog_Violation, but probably not caused by SSD

ms4sman · Oct 5, 2014

A couple of days ago I suddenly started having my computer crash several times a day due to the DPC_Watchdog_Violation error. I did some research on the error and found that it is most commonly caused by outdated firmware for an SSD. Since I have an SSD in my computer, I figured that must be the cause, but when I went to update the firmware, the Samsung Magician software says that the firmware is already up to date. I saw several other causes of the error, but none of them jumped out as being terribly likely. Does anyone here have any clues for me as to what is causing it?

I can usually tell it is coming because if there is any audio being played, it will suddenly slow way down and get very choppy, and the mouse freezes up. Then a few seconds later, it will crash.

If it helps, I am using an Asus N56-VJ laptop, with an external monitor, mouse, and optical drive plugged in. Let me know if there is any other information needed

blueelvis · Oct 8, 2014

Hi ms4sman ^_^,

I have analysed your dump files and below has been provided an analysis of the dump files for informative purposes :-

Code:

**************************Sat Oct  4 22:01:34.851 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\100414-5656-01.dmp]
 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 17:00:31.641
 
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
 
BugCheck 133, {0,[COLOR=#FF0000][B][U] 501[/U][/B][/COLOR],[COLOR=#0000FF][B][U] 500[/U][/B][/COLOR], 0}
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: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  firefox.exe
 
FAILURE_BUCKET_ID:  ZEROED_STACK
 
CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
 
MaxSpeed:     2400
 
CurrentSpeed: 2395
 
  BIOS Version                  N56VJ.203
 
  BIOS Release Date             08/29/2012
 
  Manufacturer                  ASUSTeK COMPUTER INC.
 
  Product Name                  N56VJ
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct  4 05:00:45.381 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\100314-5609-01.dmp]
 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 3:26:15.172
 
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
 
BugCheck 133, {0, 501, 500, 0}
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: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  ZEROED_STACK
 
CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
 
MaxSpeed:     2400
 
CurrentSpeed: 2395
 
  BIOS Version                  N56VJ.203
 
  BIOS Release Date             08/29/2012
 
  Manufacturer                  ASUSTeK COMPUTER INC.
 
  Product Name                  N56VJ
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct  4 00:44:17.413 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\100314-9203-01.dmp]
 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 2:28:47.203
 
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
 
BugCheck 133, {0, 501, 500, 0}
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: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  ZEROED_STACK
 
CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
 
MaxSpeed:     2400
 
CurrentSpeed: 2395
 
  BIOS Version                  N56VJ.203
 
  BIOS Release Date             08/29/2012
 
  Manufacturer                  ASUSTeK COMPUTER INC.
 
  Product Name                  N56VJ
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Oct  3 22:15:09.772 2014 (UTC + 5:30)**************************
Loading Dump File [C:\SysnativeBSODApps\100314-7093-01.dmp]
 
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
 
Built by: 9600.17238.amd64fre.winblue_gdr.140723-2018
 
System Uptime: 0 days 19:42:53.578
 
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )
 
BugCheck 133, {0, 501, 500, 0}
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: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: 0000000000000000
BUGCHECK_STR:  0x133
 
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
 
PROCESS_NAME:  System
 
FAILURE_BUCKET_ID:  ZEROED_STACK
 
CPUID:        "Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz"
 
MaxSpeed:     2400
 
CurrentSpeed: 2395
 
  BIOS Version                  N56VJ.203
 
  BIOS Release Date             08/29/2012
 
  Manufacturer                  ASUSTeK COMPUTER INC.
 
  Product Name                  N56VJ
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Information is not saved into the dump files but generally, I have seen the 500 & 501 tick DPC_WATCHDOG_VIOLATION which is generally caused by NVIDIA Drivers which are updated. The only thing is that the Laptops are suggested strongly to have drivers only from the manufacturer.
Below is a list of 3rd party drivers present on the system :-

Code:

**************************Sat Oct  4 22:01:34.851 2014 (UTC + 5:30)**************************
[B][U]teamviewervpn.sys      Thu Dec 13 14:52:09 2007 (4760F9C1)
ASMMAP64.sys           Thu Jul  2 14:43:26 2009 (4A4C7A36)
atkwmiacpi64.sys       Wed Sep  7 07:14:52 2011 (4E66CC94)
usbglcs1100301.sys     Fri Mar  9 14:01:24 2012 (4F59BFDC)
HECIx64.sys            Tue Jul  3 03:44:58 2012 (4FF21D62)
iaStorA.sys            Tue Jul 10 02:12:33 2012 (4FFB4239)
dump_iaStorA.sys       Tue Jul 10 02:12:33 2012 (4FFB4239)
L1C63x64.sys           Thu Jul 19 08:24:44 2012 (500776F4)
kbfiltr.sys            Thu Aug  2 08:52:22 2012 (5019F26E)
RTKVHD64.sys           Tue Aug 21 16:02:01 2012 (503363A1)
AsusTP.sys             Mon Oct 29 23:53:54 2012 (508EC9BA)
btath_lwflt.sys        Fri Nov  2 11:05:44 2012 (50935BB0)
btath_hcrp.sys         Tue Dec 18 15:24:54 2012 (50D03D6E)
[/U][/B]btath_bus.sys          Mon Jan 21 14:48:42 2013 (50FD07F2)
netr28ux.sys           Fri Apr 26 08:03:43 2013 (5179E787)
vmci.sys               Sat May 18 06:49:18 2013 (5196D716)
btath_rcp.sys          Fri Jun 21 14:41:54 2013 (51C418DA)
athwbx.sys             Mon Jul 15 12:59:50 2013 (51E3A4EE)
VMNET.SYS              Fri Jul 19 01:12:50 2013 (51E8453A)
vmnetadapter.sys       Fri Jul 19 01:13:00 2013 (51E84544)
vmnetbridge.sys        Fri Jul 19 01:13:47 2013 (51E84573)
iwdbus.sys             Thu Jul 25 06:36:12 2013 (51F07A04)
vsock.sys              Thu Aug  1 08:16:10 2013 (51F9CBF2)
intelppm.sys           Thu Aug 22 14:16:35 2013 (5215CFEB)
btath_flt.sys          Fri Aug 23 09:16:29 2013 (5216DB15)
igdkmd64.sys           Tue Sep 17 05:38:54 2013 (52379D96)
btath_avdt.sys         Wed Sep 18 14:12:14 2013 (52396766)
btath_a2dp.sys         Wed Sep 18 14:15:01 2013 (5239680D)
AsHIDSwitch64.sys      Tue Oct  8 07:15:17 2013 (525363AD)
btfilter.sys           Thu Jan  2 10:54:20 2014 (52C4F804)
dtsoftbus01.sys        Fri Feb 21 15:19:36 2014 (53072130)
hcmon.sys              Fri Feb 28 08:10:28 2014 (530FF71C)
VBoxUSBMon.sys         Fri May 16 17:31:15 2014 (5375FE0B)
VBoxNetFlt.sys         Fri May 16 17:31:15 2014 (5375FE0B)
VBoxNetAdp.sys         Fri May 16 17:31:16 2014 (5375FE0C)
VBoxDrv.sys            Fri May 16 17:34:43 2014 (5375FEDB)
vmnetuserif.sys        Fri Jun 13 05:15:38 2014 (539A3BA2)
vmx86.sys              Fri Jun 13 06:39:56 2014 (539A4F64)
nvvad64v.sys           Thu Sep  4 22:40:48 2014 (54089D18)
NvStreamKms.sys        Sat Sep  6 10:07:11 2014 (540A8F77)
nvkflt.sys             Sun Sep 14 01:22:45 2014 (5414A08D)
nvlddmkm.sys           Sun Sep 14 01:29:50 2014 (5414A236)
nvpciflt.sys           Sun Sep 14 01:32:34 2014 (5414A2DA)

ms4sman · Oct 8, 2014

Thanks for the reply! I have glanced over your suggestion, and I will be following it when I get a chance. However, I have a few things to let you know, and ask you first.

First of all, yesterday this problem got so bad that I could barely get the computer started without it crashing within a few minutes, but I had one idea that I tried, and it seems to have fixed the problem as the computer has not crashed once since. All I did was unplug my USB WiFi adapter from the computer. I am at a college with a very weak wifi network and my laptop's card tended to disconnect a lot which caused lots of issues. So I bought this WiFi card from Amazon and have had no issues with it, until now as it is apparently contributing to this problem. Do you have any clue if this could be the problem, and if it is, how I can fix it so that I can use my USB network adapter again?

On another note, from what I understood after glancing over your suggestions, you think that the problem is caused by a non-manufacturer brand Nvidia driver? Because as far as I know, the only drivers I have ever installed for my Nvidia card came directly from the Nvidia GeForce Experience program which manages the drivers. I don't see how I could have 3rd party drivers.

blueelvis · Oct 9, 2014

Hi Ms4sman ^_^,

That was just my experience. Those are caused by the Networking Drivers as well sometimes. Your USB Wifi adapter's drivers would be the problem if the problem is isolated by the removal of USB Device.

Let me know how It goes ^_^

ms4sman · Oct 9, 2014

I am normally quite good with computers, but I just have trouble solving Blue Screen issues, so I talked to one of my computer friends, and he suggested that perhaps I was overloading the USB ports on my computer (since I use a USB hub). I checked it in Device Manager, and sure enough the port with the hub was completely maxed out, even without the WiFi adapter, so I think that was the problem. Does this sound at least somewhat reasonable to you? Could that error be caused by overloading the USB ports?

blueelvis · Oct 11, 2014

Hi Ms4sman ^_^,

I have no idea if the BSOD could be caused by a USB HUB being overloaded. You could try the suggestion of your friend as well. Did you try my suggestions? What was the result?

DPC_Watchdog_Violation, but probably not caused by SSD

ms4sman

Member

blueelvis

OMG Debugger!

ms4sman

Member

blueelvis

OMG Debugger!

ms4sman

Member

blueelvis

OMG Debugger!

Similar threads