Windows 8 and 8.1 Forums


0x133 - DPC_WATCHDOG_VIOLATION (Random occurrences)

  1. #1


    Posts : 4
    Windows 8.1 64-bit

    0x133 - DPC_WATCHDOG_VIOLATION (Random occurrences)


    This is a relatively new install of Windows 8.1 64-bit.

    My system repeatedly hangs, sometimes without a dump, sometimes with. I have three dump files relating to the issue.

    The first dump has the driver verifier disabled, and is a 0x133.
    The second dump has the driver verifier enabled, using this tutorial:
    Driver Verifier-- tracking down a mis-behaving driver. - Microsoft Community
    The third dump (I think) happened on boot and was related to Driver Verifier.

    Not being an expert on dump analysis, I would be extremely grateful if I could find a fix for this irritating issue!
    Last edited by Zudo; 31 May 2015 at 07:41. Reason: added dm log collector

      My System SpecsSystem Spec

  2. #2


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


    Hi Zudo & Welcome to the forums ^_^,

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

    DRIVER_VERIFIER_IOMANAGER_VIOLATION (c9)
    The IO manager has caught a misbehaving driver.
    Code:
    Arguments:
    Arg1: 0000000000000006, IRP passed to IoCompleteRequest contains invalid status
    Arg2: 0000000000000103, the status
    Arg3: ffffcf8110c8edc0, the IRP
    Arg4: 0000000000000000
    So, the IO Manager has caught the bad driver which is causing the problems. Let's check the IRP and see if we can find the culprit -
    Code:
    1: kd> !irp ffffcf8110c8edc0
    Irp is active with 4 stacks 3 is current (= 0xffffcf8110c8ef20)
     No Mdl: No System Buffer: Thread ffffe00020cc75c0:  Irp stack trace.  Pending has been returned
         cmd  flg cl Device   File     Completion-Context
     [ 1b, 0]   0 10 ffffe00020d8c060 00000000 fffff800ac8fe31c-ffffd000323372c0    
           ffffe00020d8c060: Could not read device object or _DEVICE_OBJECT not found
     nt!ViFilterStartCompletionRoutine
       Args: 00000000 00000000 00000000 00000000
     [ 1b, 0]   0 10 ffffe00024106de0 00000000 fffff80050e01050-ffffd00032337390    
           Cannot read _DRIVER_OBJECT at ffffe00024427b20
     nvoclk64
       Args: 00000000 00000000 00000000 00000000
    >[ 1b, 0]   0 e0 ffffe00024106ac0 00000000 fffff800ac8fe31c-ffffd000323374e0 Success Error Cancel 
           Cannot read _DRIVER_OBJECT at ffffe00024105680
     nt!ViFilterStartCompletionRoutine
       Args: 00000000 00000000 00000000 00000000
     [ 1b, 0]   0 e0 ffffe00024106840 00000000 fffff800ac2c3180-ffffe00024292f00 Success Error Cancel 
           Cannot read _DRIVER_OBJECT at ffffe00024427b20
     nt!PnpDeviceCompletionRoutine
       Args: 00000000 00000000 00000000 00000000
    Seems like we have found it. We see that the data is missing in most of the cases but this driver highlighted in RED caused the IO Manager to flag it as culprit.


    Below is a list of 3rd party drivers present on your system -
    Code:
    **************************Sun May 31 17:51:39.185 2015 (UTC + 5:30)**************************
    nvoclk64.sys                Wed Sep 16 03:29:25 2009 (4AB00E3D)
    ASACPI.sys                  Fri Nov  2 07:24:34 2012 (509327DA)
    Rt630x64.sys                Fri Jul 26 12:31:35 2013 (51F21ECF)
    nvvad64v.sys                Thu Nov 20 21:03:54 2014 (546E09E2)
    avgdiska.sys                Wed Mar 11 15:46:03 2015 (550015E3)
    avgrkx64.sys                Fri Mar 20 15:48:15 2015 (550BF3E7)
    avgldx64.sys                Wed Apr 15 16:35:57 2015 (552E4615)
    avgidsdrivera.sys           Mon Apr 27 16:49:06 2015 (553E1B2A)
    avgwfpa.sys                 Mon May  4 17:44:25 2015 (554762A1)
    avgmfx64.sys                Thu May  7 17:19:17 2015 (554B513D)
    avgidsha.sys                Thu May  7 17:19:18 2015 (554B513E)
    avgloga.sys                 Thu May  7 17:20:17 2015 (554B5179)
    nvlddmkm.sys                Tue May 12 07:29:00 2015 (55515E64)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sun May 31 16:16:44.220 2015 (UTC + 5:30)**************************
    RTKVHD64.sys                Fri Sep 13 16:16:51 2013 (5232ED1B)
    mbam.sys                    Wed Sep  3 23:20:25 2014 (540754E1)
    NvStreamKms.sys             Tue Mar 17 11:49:52 2015 (5507C788)
    nvhda64v.sys                Fri Apr 17 00:33:16 2015 (55300774)
    nvvadarm.sys                Tue May 12 07:58:45 2015 (5551655D)
    http://www.carrona.org/drivers/driver.php?id=nvoclk64.sys
    http://www.carrona.org/drivers/driver.php?id=ASACPI.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=avgdiska.sys
    http://www.carrona.org/drivers/driver.php?id=avgrkx64.sys
    http://www.carrona.org/drivers/driver.php?id=avgldx64.sys
    http://www.carrona.org/drivers/driver.php?id=avgidsdrivera.sys
    http://www.carrona.org/drivers/driver.php?id=avgwfpa.sys
    http://www.carrona.org/drivers/driver.php?id=avgmfx64.sys
    http://www.carrona.org/drivers/driver.php?id=avgidsha.sys
    http://www.carrona.org/drivers/driver.php?id=avgloga.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=mbam.sys
    http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    http://www.carrona.org/drivers/driver.php?id=nvvadarm.sys


    Well, the driver highlighted in RED is the NVIDIA System Utility Driver. The driver is extremely old and is most likely not compatible with Windows 8.1. Kindly remove the NVIDIA System Utility and see if the system stabilises or not.


    Let me know how it goes ^_^

    -Pranav
      My System SpecsSystem Spec

  3. #3


    Posts : 4
    Windows 8.1 64-bit


    Quote Originally Posted by blueelvis View Post
    -- snip --
    Strangely enough, my computer just decided to hang and reboot without leaving a dump! I've removed the driver, but I don't know what I should do now.
      My System SpecsSystem Spec

  4. #4


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


    Quote Originally Posted by Zudo View Post
    Quote Originally Posted by blueelvis View Post
    -- snip --
    Strangely enough, my computer just decided to hang and reboot without leaving a dump! I've removed the driver, but I don't know what I should do now.
    Well that is strange. Is it happening repeatedly? If you are still facing problems, kindly explain me in some more detail and I would like to see a freshly generated copy of the Diagnostic Utility with your next post.


    Let me know how it goes ^_^.


    -Pranav
      My System SpecsSystem Spec

  5. #5


    Posts : 4
    Windows 8.1 64-bit


    Quote Originally Posted by blueelvis View Post
    Quote Originally Posted by Zudo View Post
    Quote Originally Posted by blueelvis View Post
    -- snip --
    Strangely enough, my computer just decided to hang and reboot without leaving a dump! I've removed the driver, but I don't know what I should do now.
    Well that is strange. Is it happening repeatedly? If you are still facing problems, kindly explain me in some more detail and I would like to see a freshly generated copy of the Diagnostic Utility with your next post.


    Let me know how it goes ^_^.


    -Pranav
    I've just attached a new copy. I'm running using the "Microsoft Basic Display Driver", as far as I can see.
      My System SpecsSystem Spec

  6. #6


    Posts : 4
    Windows 8.1 64-bit


    Interestingly enough, looking at the latest dump myself let me to an interesting conclusion:

    Code:
    3: 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: 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: 0000000000000000
    Arg4: 0000000000000000
    
    
    Debugging Details:
    ------------------
    
    
    
    
    DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    
    
    BUGCHECK_STR:  0x133
    
    
    PROCESS_NAME:  pyrun.exe
    
    It seems I had something left over from installing Ubuntu, which I have now deleted. Strange, right?
      My System SpecsSystem Spec

  7. #7


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


    Hi Zudo ^_^,

    So, are you still experiencing the crashes?

    The process name doesn't necessarily gives the clue as to what is causing the problem.

    -Pranav
      My System SpecsSystem Spec

0x133 - DPC_WATCHDOG_VIOLATION (Random occurrences)
Related Threads
Random BSOD-DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
Hi Guys, I am getting BSOD crashes randomly while plugging my 3G USB dongle(although not in all occasions). Although sometimes it doesn't get crashed. At first I thought outdated Drivers mighty be the problem, so i updated all my drivers. But still the problem isn't solved. It is to be noted that...
[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...
Random DPC_WATCHDOG_VIOLATION (logs attached) in BSOD Crashes and Debugging
Hi, I've been getting random DPC_WATCHDOG_VIOLATION errors. The first thing that will happen is Chrome will usually stop responding. I can still use the computer for a bit (chrome won't open again though). Then, after a few minutes, everything goes downhill and I get the violation error. ...
Random BSOD DPC_WATCHDOG_VIOLATION on Win 8.1 in BSOD Crashes and Debugging
I've installed Windows 8 last year in January 2013. It was working without any problems until they released the update to Windows 8.1. Ever since I updated my Windows 8 to 8.1. I have been having the same BSOD. I've tried updating my graphics drivers and looked for new driver for my motherboard but...
BSOD at random times - DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
Hi, I've been having random freezes on my pc for the last few weeks. It seems to happen when I'm using multiple applications or a few internet windows. Everything freezes including the mouse and keyboard and I'm stuck staring at whatever it was I was just doing until I manually reboot. I'm not...
Solved Random BSOD's with DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
Hi, My system was running fine with Windows 7, then I did an in-place upgrade to Windows 8, i.e. installed on top of Windows 7. The install went smoothly, but a few days later, it started crashing. I've updated all my drivers, and tested RAM using Memtest, and CPU using Orthos . I would much...
Random Windows 8 BSOD: DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
I have had about 5 or so BSODs since installing windows 8 about a week ago, this being the latest. I turned on my computer a little while ago, and as I began using it I noticed the system was "hiccuping" every few seconds. I would be moving my mouse then it would freeze for ~.5 seconds before...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook