Windows 8 and 8.1 Forums


DPC_Watchdog_Violation BSODs

  1. #1

    DPC_Watchdog_Violation BSODs


    Hello, for a while now I have been suffering random BSODs on my copy of Windows 8.1 Pro. I have been suffering these ever since I had upgraded from Vista to Windows 8 Pro. At first I had been getting Memory Management BSODs, however I fixed that by replacing the RAM. I have been getting these for about a year or so but I have been suffering these DPC Watchdog Violation errors on a random basis. There is no specific thing that 'triggers' them to happen more often, they tend to only happen once in a day and then they don't happen for a while if I am lucky.
    I have attached the required zip folder.
    Last edited by IllusionaryInno; 04 Sep 2014 at 01:48.

      My System SpecsSystem Spec

  2. #2


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi Illusionaryinno ^_^,

    I have analyzed your dump files and below has been provided an analysis of the same for informative purposes :-
    Code:
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    DPC_WATCHDOG_VIOLATION (133)
    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
    or above.
    Arguments:
    Arg1: 00000000, A single DPC or ISR exceeded its time allotment. The offending
    	component can usually be identified with a stack trace.
    Arg2: 00000501, The DPC time count (in ticks).
    Arg3: 00000500, The DPC time allotment (in ticks).
    Arg4: 00000000
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x133
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  1c
    
    
    ANALYSIS_VERSION: 6.3.9600.17237 (debuggers(dbg).140716-0327) amd64fre
    
    
    DPC_STACK_BASE:  FFFFFFFF801E2000
    
    
    LAST_CONTROL_TRANSFER:  from 813add5e to 813641a4
    
    
    STACK_TEXT:  
    801e1ab0 813add5e 00000133 00000000 00000501 nt!KeBugCheckEx
    801e1b1c 81317c7d 00147ff6 00000002 00000000 nt! ?? ::FNODOBFM::`string'+0x301dc
    801e1bcc 8120c2be 8121bdef 81209c02 000000d2 nt!KeClockInterruptNotify+0x7d
    801e1bd0 8121bdef 81209c02 000000d2 8382eb9c hal!HalpTimerClockIpiRoutineCommon+0x6
    801e1bd0 812ffa9d 81209c02 000000d2 8382eb9c hal!HalpTimerClockIpiRoutine+0x1cb
    801e1d24 81296eab 8a8c01d8 0000000c 8a8c02b4 nt!KiInsertTimerTable+0x29d
    801e1d48 81a4570d 008c01b0 ffffffff ffffffff nt!KeSetTimer+0x5b
    801e1d60 81a45a18 8b7000e8 8f9ce858 00000000 ndis!ndisQueuePeriodicReceivesTimer+0x51
    801e1d9c 81a3d3c2 00000000 00000000 00000001 ndis!ndisQueueDpcWorkItem+0x146
    801e1e18 812afa96 8f9ce9d4 8f9ce858 00000000 ndis!ndisInterruptDpc+0x240
    801e1ed0 812af693 801e1f18 00000000 8a8c02bc nt!KiExecuteAllDpcs+0x216
    801e1ff4 813794ae 8a1c7d08 00000000 00000000 nt!KiRetireDpcList+0xf3
    801e1ff8 8a1c7d08 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x2e
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    813794ae 00000000 00000023 011b850f bb830000 0x8a1c7d08
    
    
    
    
    STACK_COMMAND:  kb
    
    
    FOLLOWUP_IP: 
    ndis!ndisQueuePeriodicReceivesTimer+51
    81a4570d 5e              pop     esi
    
    
    SYMBOL_STACK_INDEX:  7
    
    
    SYMBOL_NAME:  ndis!ndisQueuePeriodicReceivesTimer+51
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: ndis
    
    
    IMAGE_NAME:  ndis.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  53904c46
    
    
    IMAGE_VERSION:  6.3.9600.17199
    
    
    BUCKET_ID_FUNC_OFFSET:  51
    
    
    FAILURE_BUCKET_ID:  0x133_DPC_ndis!ndisQueuePeriodicReceivesTimer
    
    
    BUCKET_ID:  0x133_DPC_ndis!ndisQueuePeriodicReceivesTimer
    
    
    ANALYSIS_SOURCE:  KM
    
    
    FAILURE_ID_HASH_STRING:  km:0x133_dpc_ndis!ndisqueueperiodicreceivestimer
    
    
    FAILURE_ID_HASH:  {ecb20391-c476-9ab0-cad9-35a4b4cb253c}
    
    
    Followup: MachineOwner
    ---------
    
    
    1: kd> !dpcs
    CPU Type      KDPC       Function
    Failed to read DPC at 0x8a9dfdf4
    1: kd> !timer
    ffdf0000: Unable to get shared data
    1: kd> !analyze -hang
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 133, {0, 501, 500, 0}
    
    
    Scanning for threads blocked on locks ...
    8144f138: Unable to get value of ExpSystemResourcesList
    Probably caused by : ndis.sys ( ndis!ndisQueuePeriodicReceivesTimer+51 )
    
    
    Followup: MachineOwner
    ---------
    Below is a list of 3rd party drivers present on the system :-
    Code:
    **************************Thu Sep  4 08:55:58.122 2014 (UTC + 5:30)**************************
    ASACPI.sys                  Thu Nov  1 07:17:02 2012 (5091D496)
    klwfp.sys                   Wed Feb 27 14:18:23 2013 (512DC857)
    kneps.sys                   Tue Mar  5 14:38:52 2013 (5135B624)
    Rt630x86.sys                Fri May 10 15:29:39 2013 (518CC50B)
    klim6.sys                   Thu Jul 11 13:23:48 2013 (51DE648C)
    netr28.sys                  Thu Jul 11 15:01:48 2013 (51DE7B84)
    klkbdflt.sys                Thu Aug  8 18:38:25 2013 (52039849)
    klmouflt.sys                Thu Aug  8 18:38:37 2013 (52039855)
    intelppm.sys                Thu Aug 22 07:28:53 2013 (5215705D)
    CSCrySec.sys                Wed Sep 18 12:04:57 2013 (52394991)
    CSVirtualDiskDrv.sys        Wed Sep 18 12:06:47 2013 (523949FF)
    kl1.sys                     Fri Oct 18 14:48:39 2013 (5260FCEF)
    klflt.sys                   Tue Nov 26 18:07:31 2013 (5294960B)
    nvhda32v.sys                Thu Nov 28 19:07:50 2013 (5297472E)
    nvlddmkm.sys                Tue Mar  4 16:33:29 2014 (5315B301)
    klif.sys                    Fri May 16 21:59:52 2014 (53763D00)
    http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
    http://www.carrona.org/drivers/driver.php?id=klwfp.sys
    http://www.carrona.org/drivers/driver.php?id=kneps.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x86.sys
    http://www.carrona.org/drivers/driver.php?id=klim6.sys
    http://www.carrona.org/drivers/driver.php?id=netr28.sys
    http://www.carrona.org/drivers/driver.php?id=klkbdflt.sys
    http://www.carrona.org/drivers/driver.php?id=klmouflt.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=CSCrySec.sys
    http://www.carrona.org/drivers/driver.php?id=CSVirtualDiskDrv.sys
    http://www.carrona.org/drivers/driver.php?id=kl1.sys
    http://www.carrona.org/drivers/driver.php?id=klflt.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda32v.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=klif.sys



    According to the analysis, the "NDIS.sys" has been blamed and something utilizing it hung it up for more than the number of clock ticks (Unit for measuring CPU Time) which was set at 500, but the driver took 501 clock ticks which caused the System To Bugcheck. Now, since "NDIS.SYS" is the Networking Driver which is used by many other components of the component, if the component makes the fault while using NDIS.SYS, the bugchecks say that NDIS.SYS is the cause.

    This is generally caused by AntiVirus or an outdated Network Card Driver. I would advise you to remove Kaspersky using this **TOOL** and if the BSOD's still persist then please update the drivers for "RT630x86.sys".

    Let me know how it goes ^_^.
      My System SpecsSystem Spec

  3. #3


    Lovely. Whelp, I can't remove Kaspersky cause that's my Anti-Virus suite. Which doesn't help since I don't trust a Free Anti-Virus to be as good as the paid AV that Kaspersky is. The BSOD happens randomly so its gonna be difficult to tell if I don't have it anymore. I wouldn't be surprised if it was caused by the Network Card Driver, after all I'm using a D-Link PCI-E card.

    ...Question since I'm trying to hold out with this computer until I save up for a new PC, would building a new PC and using the drivers on the disk typically have more up to date versions?

    Also its as simple for updating drivers as going to the website, clicking through to the driver source and downloading an executable I take it?

    EDIT: So after looking up the "RT630x86.sys" driver in Device Manager? Turns out its the driver for my Ethernet ports. They are never in use. As in I use a wireless connection. Would it make sense to disable the Ethernet ports? The BSOD does happen randomly, like looking in the action center's reliability center I hadn't have a BSOD for 2 weeks but before THAT point it was 4 days. Its really inconsistant so idk.
    EDIT 2: Might possibly be the Ethernet ports? Cause I'm using the latest drivers for the Wireless card which despite being made by D-Link has 'Ralink' drivers apparently. So idk
    EDIT: Will disabling the Ethernet LAN connectors cause it not to use the Realtek drivers? Or is it still a good idea to try and update them?
    Last edited by IllusionaryInno; 06 Sep 2014 at 02:52. Reason: Updating with new information
      My System SpecsSystem Spec

  4. #4


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Hi ^_^,

    The anti-virus are generally the causes of such Network Related problems. That is why, I have asked you to remove the Kaspersky Suite. I myself am using Windows Defender along with Windows Firewall and I am pretty good with it. I have asked you to remove the Kaspersky just to make sure that it is not causing the problems.

    I doubt that the D-Link PCI Card would be at fault as the PCI devices related to Network are pretty robust although could you please tell me the model and make of it? The problems are generally caused when you use those Mobile Broadband Plug "N" Play devices.

    Nope, the drivers on the disk are generally not the latest but they have been tested rigorously by the manufacturer.

    Yes, the installation of drivers is just like that, given that you install the drivers related to you. Although it is rare these days that the installer won't check your system but it is better to know which one to download ^_^

    Yes, disabling the Ethernet Adapters would stop the driver loads. But, I wonder if those are at fault since you are using the Wireless Connection.
      My System SpecsSystem Spec

  5. #5


    It'd make some sense for the Ethernet Ports to be at fault since you were the one who mentioned the 'rt630x86.sys'. Given how they're the only out of date drivers and you mentioned NDIS.sys as being blamed by the BlueScreen.

    They might be at fault, cause... they're probably running by sheer virtue of the ports being enabled. I only ever get the BSOD when I'm doing something on the internet, say watching Twitch or something like that.
    EDIT: I just hope when I build my next computer I don't have these issues.
    Last edited by IllusionaryInno; 07 Sep 2014 at 17:37.
      My System SpecsSystem Spec

  6. #6


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by IllusionaryInno View Post
    It'd make some sense for the Ethernet Ports to be at fault since you were the one who mentioned the 'rt630x86.sys'. Given how they're the only out of date drivers and you mentioned NDIS.sys as being blamed by the BlueScreen.

    They might be at fault, cause... they're probably running by sheer virtue of the ports being enabled. I only ever get the BSOD when I'm doing something on the internet, say watching Twitch or something like that.
    EDIT: I just hope when I build my next computer I don't have these issues.
    So, has the issue been resolved? If yes, then please Mark this Thread as SOLVED. If not then please post back with your latest SF Diagnostic ZIP File.
      My System SpecsSystem Spec

  7. #7


    I guess I'll start a new thread when I get a new BSOD then. xD Alright then.
      My System SpecsSystem Spec

  8. #8


    India
    Posts : 2,097
    Windows 8.1 Industry Pro B-)


    Quote Originally Posted by IllusionaryInno View Post
    I guess I'll start a new thread when I get a new BSOD then. xD Alright then.
    Sure thing, in case of any problem do not hesitate to post back ^_^
      My System SpecsSystem Spec

DPC_Watchdog_Violation BSODs
Related Threads
[Random/Frequent BSODs] DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
I am at a standstill ever since I recieved this BSOD. At first I thought it was just a random crash and that I would've resolved it later, however it became frequent in just a matter of minutes. Playing a game, browsing the internet, listening to music, anything I do will result in another BSOD...
I run Windows 8.1 64-bit Intel Celeron CPU 1037U @ 1.80GHz, 4.0GB RAM, Intel HD Graphics. TOSHIBA Satelite C55-A. A few months ago, I encountered a continous bluescreen titled DPC_WATCHDOG_VIOLATION, and I solved the problem by unchecking fast startup. It was fine for a few months, and then it...
Solved Dpc_watchdog_violation in BSOD Crashes and Debugging
Dear I am a new member and wish to thank you for such a great site! My problem is getting freezes then BSOD with DPC_WATCHDOG_VIOLATION error. I have just bought a ACER Aspire S3 Ultrabook with W8 installed on it. This happens randomly, sometimes once a day or five in an hour. I checked...
Solved Dpc_Watchdog_Violation in BSOD Crashes and Debugging
Hello and Thank you for the attention. I just bought a computer and I got the DPC_watchdog_violation Blue screen. I installed avast free antivirus, but I searched on the forums and I have already uninstalled it. I want to know If I need to uninstall another program. Thank you in advance...
DPC_Watchdog_violation in BSOD Crashes and Debugging
I was doing my web surfing and BSOD DPC_Watchdog_violation attached file required
dpc_Watchdog_Violation in BSOD Crashes and Debugging
I just upgrade my system to Windows8 Pro 3 days ago Then I got the BSOD problem regularly and randomly I am so frustrated! Really need help from someone! The documents needed are attached
Eight Forums Android App Eight Forums IOS App Follow us on Facebook