Windows 8 and 8.1 Forums

DPC_Watchdog Violation

  1. #1


    Posts : 5
    Windows 8 RP

    DPC_Watchdog Violation


    Hi, my windows 8 system was running like a dream for about a month, but like a week ago, it started having some strange Bsod with the DPC_Watchdog Violation message. They didnt had any pattern, but when one ocurred, it immediately had another like 5 minutes after the restart.

    Yesterday, my computer couldnt even start windows, cause as soon as I clicked with the mouse, it started to run really slow with a constant stutter and clicks didnt had any effect, like it was hung up. Today I turned it on, and Windows started to do some repair process all of a sudden, and I finally could start the PC. Anywas, as soon as I could I did the dump file process, and I attached it here.

    Any help would be much appreciated!

      My System SpecsSystem Spec

  2. #2


    Posts : 5,139
    Win8.1Pro - Finally!!!


    No Windows Updates present, please visit Windows Update and get all available updates.

    Your hard drive is getting full, please try to maintain a minimum of 15% free space in order to get optimum performance.

    Nearly all of the memory dumps blame your nVidia storage drivers (nvstor.sys).
    Please:
    - download the latest Win8 compatible storage/chipset drivers from World Leader in Visual Computing Technologies | NVIDIA
    - un-install the current nVidia chipset software (NOT the video drivers)
    - install the freshly downloaded chipset drivers
    - monitor for further BSOD's

    AMD OverDrive (AODDriver2.sys) is either a stand-alone application, or a component of the AMD VISION Engine Control Center. This driver is known to cause BSOD's on some Win7 systems (as such, we suspect in Win8 also).
    Please un-install all AMD/ATI video stuff from Control Panel...Programs...Un-install a program
    Then, download (but DO NOT install) a fresh copy of the ATI drivers from Global Provider of Innovative Graphics, Processors and Media Solutions | AMD (in the upper right corner of the page)
    Use this procedure to install the DRIVER ONLY: ATI video cards - DRIVER ONLY installation procedure

    If the device (AODDriver or AODDriver4.01) remains a problem, open Device Manager, select the "View" item.
    Then select "Show hidden devices" and scroll down to the Non-Plug and Play Drivers section.
    Locate the AODDriver entry, right click on it and select "Un-install". Reboot for changes to take affect.
    Sometimes the driver remains and continues to cause BSOD's. If this is the case for you, post back and we'll give further instructions for safely removing it.

    If overclocking, please stop. Remove the overclock and return the system to stock/standard values while we're troubleshooting. Once the system is stable again, feel free to resume the overclocking.

    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! :

    KMWDFILTER.sys Thu Dec 3 20:35:13 2009 (4B186751)
    UASSOFT.com HID (mouse) Driver
    http://www.carrona.org/drivers/driver.php?id=KMWDFILTER.sys

    nvmf6264.sys Wed Apr 20 18:49:36 2011 (4DAF6300)
    nVidia nForce network driver
    http://www.carrona.org/drivers/driver.php?id=nvmf6264.sys

    nvstor.sys Mon Sep 12 19:53:04 2011 (4E6E9B60)
    nVidia Storage Drivers
    http://www.carrona.org/drivers/driver.php?id=nvstor.sys

    hiber_nvstor.sys Mon Sep 12 19:53:04 2011 (4E6E9B60)

    hiber_nvstor.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.

    AODDriver2.sys Thu Apr 5 05:23:37 2012 (4F7D6499)
    AMD Overdrive; also in EasyTune6 for Gigabyte motherboard [br] Known BSOD issues in Win7
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Sat Dec  8 09:49:31.259 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120812-79156-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:03:32.974
    Probably caused by :storport.sys ( storport!RaidpAdapterTimerDpcRoutine+59 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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: 0x133_DPC_storport!RaidpAdapterTimerDpcRoutine
      BIOS Version                  P1.70
      BIOS Release Date             03/03/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Dec  8 01:27:43.193 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120812-136968-01.dmp]
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120812-21906-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 3:20:30.912
    *** WARNING: Unable to verify timestamp for amdppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for amdppm.sys
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13c00 )
    BugCheck 133, {1, 780, 0, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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: 0000000000000780, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
      BIOS Version                  P1.70
      BIOS Release Date             03/03/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec  3 16:47:42.376 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120312-22515-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:10:22.087
    *** WARNING: Unable to verify timestamp for nvstor.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
    Probably caused by :nvstor.sys ( nvstor+74d4 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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: 0x133_DPC_nvstor+74d4
      BIOS Version                  P1.70
      BIOS Release Date             03/03/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec  3 16:34:32.451 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120312-39343-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:00:50.165
    *** WARNING: Unable to verify timestamp for nvstor.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
    Probably caused by :nvstor.sys ( nvstor+74d4 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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: 0x133_DPC_nvstor+74d4
      BIOS Version                  P1.70
      BIOS Release Date             03/03/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec  3 12:52:59.959 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120312-17984-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:55:56.676
    *** WARNING: Unable to verify timestamp for nvstor.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
    Probably caused by :nvstor.sys ( nvstor+74d4 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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: 0x133_DPC_nvstor+74d4
      BIOS Version                  P1.70
      BIOS Release Date             03/03/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec  3 11:56:22.179 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120312-19234-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 0:04:41.891
    *** WARNING: Unable to verify timestamp for nvstor.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
    Probably caused by :nvstor.sys ( nvstor+17f5f )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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: taskhost.exe
    FAILURE_BUCKET_ID: 0x133_DPC_nvstor+17f5f
      BIOS Version                  P1.70
      BIOS Release Date             03/03/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec  3 11:50:58.835 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120312-19359-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:0 days 3:44:00.547
    *** WARNING: Unable to verify timestamp for nvstor.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
    Probably caused by :nvstor.sys ( nvstor+74d4 )
    BugCheck 133, {0, 281, 280, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    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: 0x133_DPC_nvstor+74d4
      BIOS Version                  P1.70
      BIOS Release Date             03/03/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec  3 08:06:16.646 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\120312-27109-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:2 days 20:50:18.363
    *** WARNING: Unable to verify timestamp for nvstor.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
    Probably caused by :nvstor.sys ( nvstor+9e64 )
    BugCheck D1, {120, 2, 1, fffff88001046e64}
    BugCheck Info: DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    Arguments: 
    Arg1: 0000000000000120, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
    Arg4: fffff88001046e64, address which referenced memory
    BUGCHECK_STR:  AV
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: AV_nvstor+9e64
      BIOS Version                  P1.70
      BIOS Release Date             03/03/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Fri Nov 30 09:11:50.665 2012 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\113012-27187-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16384.amd64fre.win8_rtm.120725-1247
    System Uptime:7 days 3:59:52.351
    *** WARNING: Unable to verify timestamp for nvstor.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvstor.sys
    Probably caused by :nvstor.sys ( nvstor+9e64 )
    BugCheck 1E, {ffffffffc0000005, fffff88000b70e64, 0, ffffffffffffffff}
    BugCheck Info: KMODE_EXCEPTION_NOT_HANDLED (1e)
    Arguments: 
    Arg1: ffffffffc0000005, The exception code that was not handled
    Arg2: fffff88000b70e64, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: ffffffffffffffff, Parameter 1 of the exception
    BUGCHECK_STR:  0x1E_c0000005_R
    PROCESS_NAME: System
    FAILURE_BUCKET_ID: 0x1E_c0000005_R_nvstor+9e64
      BIOS Version                  P1.70
      BIOS Release Date             03/03/2011
      Manufacturer                  To Be Filled By O.E.M.
      Product Name                  To Be Filled By O.E.M.
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Sat Dec  8 09:49:31.259 2012 (UTC - 5:00)**************************
    KMWDFILTER.sys              Thu Dec  3 20:35:13 2009 (4B186751)
    nvmf6264.sys                Wed Apr 20 18:49:36 2011 (4DAF6300)
    nvstor.sys                  Mon Sep 12 19:53:04 2011 (4E6E9B60)
    AtihdW86.sys                Tue Aug 21 22:26:37 2012 (5034435D)
    atikmpag.sys                Thu Sep 27 21:12:52 2012 (5064F994)
    atikmdag.sys                Thu Sep 27 22:14:57 2012 (50650821)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Dec  8 01:27:43.193 2012 (UTC - 5:00)**************************
    AODDriver2.sys              Thu Apr  5 05:23:37 2012 (4F7D6499)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Dec  3 08:06:16.646 2012 (UTC - 5:00)**************************
    hiber_nvstor.sys            Mon Sep 12 19:53:04 2011 (4E6E9B60)
    
    http://www.carrona.org/drivers/driver.php?id=KMWDFILTER.sys
    http://www.carrona.org/drivers/driver.php?id=nvmf6264.sys
    http://www.carrona.org/drivers/driver.php?id=nvstor.sys
    http://www.carrona.org/drivers/driver.php?id=AtihdW86.sys
    http://www.carrona.org/drivers/driver.php?id=atikmpag.sys
    http://www.carrona.org/drivers/driver.php?id=atikmdag.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    hiber_nvstor.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
      My System SpecsSystem Spec

  3. #3


    Posts : 5
    Windows 8 RP


    I freshly installed my OS, formatting my drive, and just finished doing all the steps you told me, except for the removal of my chinese mouse's driver that changes the dpi. Dont think its a big deal. Anyways, I will post back as soon as I get another BSOD (hopefully not). Thanks for the help usasma!
      My System SpecsSystem Spec

DPC_Watchdog Violation
Related Threads
BSOD On computer boot DPC_WATCHDOG in BSOD Crashes and Debugging
Hi All- Recently I started getting a blue screen upon my laptops boot and using bluescreenview has linked it to igdkmd64.sys. I have tried installing intels latest drivers, as well as installing MSI's last driver build and the error still happens. Oddly enough the reboot after the blue screen...
I have been having seemingly random BSOD DPC_WATCHDOG ever since I updated to Windows 8.1. This can occur either when I'm playing games, using Visual Studio 2012, or browsing the web. Any help would be great.
Solved BSOD DPC_WATCHDOG 0x133 in BSOD Crashes and Debugging
Hi i have this bsod but can't understand why.. i can stay ok for 1 week.. and today i had 3 bsod in 20min... it is totally random. Pls help me :)
bsod/dpc_watchdog mainly among others in BSOD Crashes and Debugging
happens while playing games. if u could take a look at my dmp file would be appreciated; thanks!
Dear freinds & experts, I am facing some blue screen error ... DPC_WATCHDOG VIOLATION, immediately after connecting my hotspot shield. Can you please explain me how to resolve this issue. My OS is Windows 8 32 bit and Antivirus is NOD32. thanks, SHIJO
Hmm, if I browse through the BSoD and Debugging section of the forum, why did I see most is reports of DPC_WATCHDOG reports, such as VIOLATION or TIMEOUT?
Bsod dpc_watchdog-violation in BSOD Crashes and Debugging
Hope someone can help here. I am starting to wish I stuck with Win 7 Professional which was stable and running well. Have had nothing but problems with Win8 and hard to believe this will be released commercially soon. I am getting somewhat random BSOD screens, but it does seem to happen more...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook