Windows 8 and 8.1 Forums


Windows 8.1 DPC_WATCHDOG_VIOLATION BSOD - NewBuild

  1. #11


    Posts : 16
    Windows 8


    FYI - There was also another driver involved in the crash; I will still continue with the steps outlined above...

    Attachment 32901

      My System SpecsSystem Spec

  2. #12


    Posts : 16
    Windows 8


    Disabled the Wifi/Bluetooth adapter via the BIOS instead. Removed the overclock from the system. Immediately experienced a DPC_WATCHDOG BSOD 5mins into restart with events of usbehci "timeout occurred while waiting for the EHCI host controller Interrupt on Async Advance Doorbell response". I am downloading and installing the latest NVIDIA drivers v331.93 prior to posting a new SF_Diagnostic_Tool dump for you to eval.
      My System SpecsSystem Spec

  3. #13


    Posts : 16
    Windows 8


    SF_Diagnostic_Tool dump attached...
      My System SpecsSystem Spec

  4. #14


    Posts : 16
    Windows 8


    Currently crashed without anything in the event log. I did get a crash-dump analysis from WhoCrashed of the same driver issue as referenced above, even after the new drivers were installed... I entered a post on their forum in response to another person with the same results...
    https://forums.geforce.com/default/t...fset=2#4043986
      My System SpecsSystem Spec

  5. #15


    Posts : 16
    Windows 8


    Crashed again... nvlddmkm.sys cited by WhoCrashed, as above...

    https://forums.geforce.com/default/t...fset=2#4043986

    Absolutely nothing in the event log prior to the crashes now... (?)
      My System SpecsSystem Spec

  6. #16


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


    Please zip up the contents of C:\Windows\Minidump and upload it with your next post.
    If you have difficulties, try copying it to the Desktop and zipping it from there.
      My System SpecsSystem Spec

  7. #17


    Posts : 16
    Windows 8


    As requested.
      My System SpecsSystem Spec

  8. #18


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


    Please note the drivers below that date from before the release of Windows 8.1 (17 Oct 2013) - check to see that each and every one is compatible w/Windows 8.1 (at the manufacturer's website). If not, you must either remove the device and it's software - or locate a Windows 8.1 compatible update on the web.

    Also, ensure that you update the Intel Management Engine to the latest, Win8.1 compatible version available from http://downloadcenter.intel.com I suspect that the 2012 version isn't compatible w/Win8.1 (from my experience at work - detailed here: Win8.1 and Intel Management Engine (HECKIx64.sys) - Sysnative Forums )

    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Thu Dec  5 11:15:10.599 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\120513-6203-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 0:57:48.765
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :nvlddmkm.sys ( nvlddmkm+1a08d9 )
    BugCheck 133, {1, 1e00, 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: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  dwm.exe
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+1a08d9
    CPUID:        "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
    MaxSpeed:     3600
    CurrentSpeed: 3600
      BIOS Version                  4502
      BIOS Release Date             10/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Dec  4 11:31:14.946 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\120413-6140-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 0:29:37.578
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13e32 )
    BugCheck 133, {1, 1e00, 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: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  dwm.exe
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
    MaxSpeed:     3600
    CurrentSpeed: 3600
      BIOS Version                  4502
      BIOS Release Date             10/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Dec  4 10:04:34.634 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\120413-6156-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 0:09:25.266
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13e32 )
    BugCheck 133, {1, 1e00, 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: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  dwm.exe
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
    MaxSpeed:     3600
    CurrentSpeed: 3600
      BIOS Version                  4502
      BIOS Release Date             10/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Dec  4 08:51:32.628 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\120413-5921-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 1:36:17.235
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by :nvlddmkm.sys ( nvlddmkm+1a08d9 )
    BugCheck 133, {1, 1e00, 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: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm+1a08d9
    CPUID:        "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
    MaxSpeed:     3600
    CurrentSpeed: 4549
     
    Processor may be overclocked!
    Expected Frequency:   3600
    Actual Frequency:     4549
    Overclock Ratio:      1.26361
     
      BIOS Version                  4502
      BIOS Release Date             10/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Tue Nov 26 16:08:03.268 2013 (UTC - 5:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\112613-6312-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.16422.amd64fre.winblue_gdr.131006-1505
    System Uptime:0 days 3:13:04.875
    Probably caused by :ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13e32 )
    BugCheck 133, {1, 1e00, 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: 0000000000001e00, The watchdog period.
    Arg3: 0000000000000000
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  OUTLOOK.EXE
    FAILURE_BUCKET_ID: 0x133_ISR_nt!_??_::FNODOBFM::_string_
    CPUID:        "Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz"
    MaxSpeed:     3600
    CurrentSpeed: 4549
     
    Processor may be overclocked!
    Expected Frequency:   3600
    Actual Frequency:     4549
    Overclock Ratio:      1.26361
     
      BIOS Version                  4502
      BIOS Release Date             10/15/2013
      Manufacturer                  System manufacturer
      Product Name                  System Product Name
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Thu Dec  5 11:15:10.599 2013 (UTC - 5:00)**************************
    adfs.SYS             Mon Nov  3 11:48:14 2008 (490F2B4E)
    AsUpIO.sys           Mon Aug  2 22:47:59 2010 (4C57835F)
    ICCWDT.sys           Wed Aug 18 04:27:45 2010 (4C6B9981)
    mv_process.sys       Tue Feb 22 04:22:20 2011 (4D63804C)
    ASUSFILTER.sys       Tue Sep 20 11:46:33 2011 (4E78B559)
    AsIO.sys             Wed Aug 22 05:54:47 2012 (5034AC67)
    HECIx64.sys          Mon Dec 17 14:32:21 2012 (50CF7345)
    ElbyCDIO.sys         Mon Mar  4 04:21:51 2013 (513467AF)
    point64.sys          Fri Apr 12 08:15:29 2013 (5167FAE1)
    nvhda64v.sys         Sun Jun 16 08:38:07 2013 (51BDB1AF)
    e1c64x64.sys         Thu Jun 20 17:59:00 2013 (51C37B24)
    mv91cons.sys         Fri Jun 21 02:18:21 2013 (51C3F02D)
    VClone.sys           Wed Jul 24 11:02:55 2013 (51EFEC9F)
    Rt630x64.sys         Fri Jul 26 03:01:35 2013 (51F21ECF)
    iaStorAV.sys         Wed Jul 31 20:00:49 2013 (51F9A531)
    dump_iaStorAV.sys    Wed Jul 31 20:00:49 2013 (51F9A531)
    asmtxhci.sys         Fri Aug 16 15:28:42 2013 (520E7D6A)
    asmthub3.sys         Fri Aug 16 15:28:54 2013 (520E7D76)
    RTKVHD64.sys         Wed Aug 21 00:48:22 2013 (52144696)
    intelppm.sys         Thu Aug 22 04:46:35 2013 (5215CFEB)
    vmbkmclr.sys         Thu Aug 22 07:39:04 2013 (5215F858)
    winhvr.sys           Thu Aug 22 07:39:52 2013 (5215F888)
    Wnv.sys              Tue Oct  8 03:36:59 2013 (5253B61B)
    nvvad64v.sys         Wed Oct 30 11:01:48 2013 (52711F5C)
    AnyDVD.sys           Sat Nov  9 16:37:51 2013 (527EAB2F)
    nvlddmkm.sys         Sat Nov 23 11:28:53 2013 (5290D7C5)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Dec  4 10:04:34.634 2013 (UTC - 5:00)**************************
    nvvad64v.sys         Fri Sep 27 16:25:30 2013 (5245E9BA)
    nvlddmkm.sys         Mon Nov 11 08:24:05 2013 (5280DA75)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Wed Dec  4 08:51:32.628 2013 (UTC - 5:00)**************************
    btfilter.sys         Fri Jun 29 03:00:07 2012 (4FED5277)
    athwbx.sys           Mon Jul 15 03:29:50 2013 (51E3A4EE)
    
    http://www.carrona.org/drivers/driver.php?id=adfs.SYS
    http://www.carrona.org/drivers/driver.php?id=AsUpIO.sys
    http://www.carrona.org/drivers/driver.php?id=ICCWDT.sys
    mv_process.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.
    http://www.carrona.org/drivers/driver.php?id=ASUSFILTER.sys
    http://www.carrona.org/drivers/driver.php?id=AsIO.sys
    http://www.carrona.org/drivers/driver.php?id=HECIx64.sys
    http://www.carrona.org/drivers/driver.php?id=ElbyCDIO.sys
    http://www.carrona.org/drivers/driver.php?id=point64.sys
    http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
    e1c64x64.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.
    http://www.carrona.org/drivers/driver.php?id=mv91cons.sys
    http://www.carrona.org/drivers/driver.php?id=VClone.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    iaStorAV.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.
    dump_iaStorAV.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.
    http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
    http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=intelppm.sys
    vmbkmclr.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.
    winhvr.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.
    Wnv.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.
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=AnyDVD.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=btfilter.sys
    athwbx.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

  9. #19


    Posts : 16
    Windows 8


    I have work to do. I see your instructions on these drivers. That would be a lot to search out... I have noted EHCI USB type crashes and I noted an EHCI option in the BIOS of this Mobo. There is an enable/disable for it. The description is to enable it if you have a non EHCI OS installed for handing off signals, or something. I enabled it, for now, even though I know (think) Windows should be able to handle this. I have not crashed since this change, but I have things disabled and I have only run the system for a few hours since this change. I will do what I can to keep the community updated on this, if anyone is finding this useful, and post if/when next crash.

    I have lost so much work time to this problem... :-(

    FYI... These problems were occurring under Windows 8 too. These problems were what prompted my rebuild to Windows 8.1 on this system; they simply increased in frequency to the point of "pain". Now they persist... but ceased for this moment, I hope its over...
      My System SpecsSystem Spec

  10. #20


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


    There are many different reasons that this might be happening.

    Let's discuss the BSOD troubleshooting process that I use. It consists of 3 steps:
    1) Rule out 3rd party drivers
    2) Rule out hardware (which includes compatibility issues along with low-level driver issues)
    3) Rule out Windows issues (this presumes that you have ALL Windows Updates)

    Ruling out the 3rd party drivers is the most important step - as over 90% of BSOD's are caused by them.
    Start with those highlighted in RED and fix them first - as they are most likely to be the cause of their problem (simply because they date from well before Win8/8.1 came out)

    adfs.sys:
    This Adobe file from 2008 is critical to remove. Uninstall Adobe Reader and check to see if that removes it.
    If not, then remove other Adobe products until the driver is gone.
    If you wish, you can then reinstall these programs using the latest, Win8.1 compatible version available from the Adobe website.

    AsUpIO.sys:
    This is a driver related to the Asus hardware monitoring utilities
    Uninstall them from Control Panel...Programs...Uninstall a program

    ICCWDT.sys:
    The Intel Watchdog Timer driver is most likely a part of the Intel Management Engine package. Download the latest, Win8.1 compatible version from http://downloadcenter.intel.com and install it. Then check to see if the old driver is removed. If not, post back and we'll see about manually removing it. FWIW - this should also update the problematic HECIx64.sys driver.

    mv_process.sys:

    This is a part of the Marvell controller drivers package
    Please download and install the latest, Win8.1 compatible version for your system.
    If an 8.1 compatible version isn't available at the PC/mobo manufacturer's website, then try the Marvell website

    ASUSFILTER.sys:
    Update this from the Asus support website. It is a USB hub filter driver made by Asus.
      My System SpecsSystem Spec

Page 2 of 3 FirstFirst 123 LastLast
Windows 8.1 DPC_WATCHDOG_VIOLATION BSOD - NewBuild
Related Threads
BSOD - DPC_WATCHDOG_VIOLATION - Windows 8.1 in BSOD Crashes and Debugging
Hello all, I was hoping I might be able to receive some assistance from somebody my technically-minded than me. I've recently had three crash dumps occur, causing a BSOD. I've researched the web to find out what might have caused the issue and have used the following program to discover...
Hi, I've been getting hard locks where the audio continues to work while everything else becomes unresponsive that eventually degenerate into a BSOD with a DPC_Watchdog_Violation. Having looked at some of the events, I think it's probably some kind of SSD driver issue but I wanted to see if...
DPC_WATCHDOG_VIOLATION bsod error on windows 8 in BSOD Crashes and Debugging
Guys, i am facing critical issue on my pc due to several days, Every time i formatted my pc,then after sometime it gives a bsod error & restart then pc cant start then windows start screen loading & loading...... I updated all driver & ssd firmware but no result. I collect dmp files &...
windows 8 BSOD DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
hi, I need help regarding my bsod its always DPC_WATCHDOG_VIOLATION. my minidump says its always the halmacpi.dll that causes the problem. :(( I hope this will be fixed soon. I can't even use my pc properly.
Windows 8 BSOD with DPC_WATCHDOG_VIOLATION in BSOD Crashes and Debugging
Hello I am running windows 8 pro 32 bit system. I seem to be getting BSOD with DPC_WATCHDOG_VIOLATION message quite frequently when browsing internet, on specific sites. Any help is highly appreciated. Regards,
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...
I have been experiencing BSOD a lot of times now. But it occurs mainly with a few days as interval. The problem occurs randomly but occurs mainly while browsing. Been using google chrome and mozilla firefox. But today the most recent one occur while I was just idle in the desktop and no...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook