Windows 8 and 8.1 Forums


DPC_WATCHDOG_VIOLATION when restarting desktop

  1. #1


    Posts : 4
    Windows 8.1 Pro

    DPC_WATCHDOG_VIOLATION when restarting desktop


    I am getting the dreaded DPC_WATCHDOG_VIOLATION on my newly setup Windows 8.1 rig.
    Configuration:
    Gigabyte H87-HD3 Motherboard,
    Haswell i5 4570,
    16GB RAM and a
    Kingston 240GB SSD (no other h/w on the M/b).
    Logitech Wireless Keyboard K520 + mouse using unified USB receiver.

    The SSD is setup as SATA, AHCI is ON. UEFI is set to 'UEFI and Legacy'. I did not use the Intel drivers while setting up the SSD, I let Windows partition/format the Drive.

    The System is stable otherwise but on almost all 'Restart' it freezes just after the Startup Screen comes up. Most of the times it crashes before password entry, occasionally it gets to password entry but freezes and crashes with DPC_WATCHDOG_VIOLATION soon after. If I power off and start, no issues.


    Often I have seen that the network connection showing a yellow exclamation before crashing. I have tried updating the network drivers but no avail. (I am using on-board LAN no WIFI adapter in the system).

    Also after much digging I recalled I started seeing the issue after HyperV was installed by Windows Phone 8 SDK, so as a last ditch when I removed Hyper V (Control Panel->Add/Remove features), things started working and the crashes on Reboot stopped.

    However I want to use Hyper V (WP8 development) and since this is a new rig, want to know if there is a h/w fault some where. Any insights will help.

    My investigation into the Dump files using WinDbg showed issues with Audio Driver, but does it imply the audio driver is bad or the h/w is bad, anyway to verify?

    The zip created by SF Diagnostic tool is attached. Thanks a ton.
    Last edited by sumitkm; 24 Mar 2014 at 17:28. Reason: Corrected DPV to DPC in title.

      My System SpecsSystem Spec

  2. #2


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


    Is there any particular reason that you did not choose to use UEFI and SecureBoot when installing Win8/8.1?

    It appears that you have 2 audio devices - a Realtek and a USB device.
    Please update the Realtek device to the latest, Win8.1 compatible version of their software: Realtek
    Also, please uninstall any software for the USB audio device and physically remove it from the system (temporarily).

    If this solves the BSOD, then try re-installing the USB audio device, making sure that it's drivers are also Win8.1 compatible.
    If not, please hold off on reinstalling the USB audio device until the system is stable.

    vmm.sys dates from 2011 and is (IMO) most likely not compatible w/Win8.1 I'd suggest uninstalling the program that it belongs to.
    (FYI - this post shows an alternative fix by using a downloaded file. BE CAREFUL if trying this and be sure to scan any downloaded files with an updated antivirus. Be sure to backup your system and set a system restore point prior to trying this
    Windows 8 DRIVER_IRQL_NOT_LESS_OR_EQUAL (vmm.sys) - Microsoft Community).

    vmm.sys likely belongs to an outdated Microsoft Virtual program - so it's best just uninstalling it (rather than replacing the vmm.sys driver). DO NOT manually remove the driver without posting back here. I can provide instructions to safely remove it manually if needed.

    I have seen issues with Virtual Box in the past, so it may be best to uninstall it also (for the time being) if you haven't already.

    If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions: Driver Verifier Settings



    Analysis:
    The following is for informational purposes only.
    Code:
    **************************Mon Mar 24 09:53:08.761 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032414-6953-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:08.412
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+13e )
    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:  MsMpEng.exe
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 24 07:10:23.234 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032414-6562-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:07.885
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+13e )
    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:  svchost.exe
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 24 07:01:18.246 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032414-7531-02.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:07.897
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+13e )
    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:  System
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 24 06:34:42.942 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032414-6609-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:08.592
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+13e )
    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:  vmms.exe
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 24 05:58:03.863 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032414-7531-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:08.513
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+13e )
    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:  sqlservr.exe
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 22 22:32:18.657 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-6734-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:08.308
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+13e )
    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:  svchost.exe
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 22 22:10:58.734 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-6828-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:08.385
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+13e )
    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:  System
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 22 20:47:00.005 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-7468-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:08.656
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+13e )
    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:  svchost.exe
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 22 20:32:12.787 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-7015-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:08.437
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+13e )
    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:  svchost.exe
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 22 20:19:46.709 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-7437-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:08.360
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+13e )
    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:  svchost.exe
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 22 20:12:45.854 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-6796-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:08.505
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+97 )
    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:  sqlservr.exe
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 22 19:56:05.816 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-8828-01.dmp]
    Windows 8 Kernel Version 9600 MP (4 procs) Free x64
    Built by: 9600.16452.amd64fre.winblue_gdr.131030-1505
    System Uptime:0 days 0:02:10.466
    Probably caused by :HDAudBus.sys ( HDAudBus!HdaController::Isr+13e )
    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:  svchost.exe
    FAILURE_BUCKET_ID: 0x133_ISR_HDAudBus!HdaController::Isr
    CPUID:        "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz"
    MaxSpeed:     3200
    CurrentSpeed: 3193
      BIOS Version                  F5
      BIOS Release Date             08/03/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      Product Name                  H87-HD3
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    
    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:
    **************************Mon Mar 24 09:53:08.761 2014 (UTC - 4:00)**************************
    vmm.sys                Wed Dec 28 08:28:47 2011 (4EFB198F)
    iaStorA.sys            Thu Aug  1 21:39:52 2013 (51FB0DE8)
    dump_iaStorA.sys       Thu Aug  1 21:39:52 2013 (51FB0DE8)
    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)
    TeeDriverx64.sys       Thu Sep  5 14:02:18 2013 (5228C72A)
    Rt630x64.sys           Mon Sep  9 02:47:07 2013 (522D6EEB)
    Wnv.sys                Tue Oct  8 03:36:59 2013 (5253B61B)
    AppleCharger.sys       Sun Oct 27 21:59:21 2013 (526DC4F9)
    RTKVHD64.sys           Tue Oct 29 06:18:58 2013 (526F8B92)
    iwdbus.sys             Tue Dec 17 17:47:38 2013 (52B0D48A)
    igdkmd64.sys           Wed Jan 22 17:42:16 2014 (52E04948)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Mon Mar 24 07:10:23.234 2014 (UTC - 4:00)**************************
    VBoxNetFlt.sys         Tue Feb 25 12:24:25 2014 (530CD1C9)
    VBoxNetAdp.sys         Tue Feb 25 12:24:26 2014 (530CD1CA)
    VBoxUSBMon.sys         Tue Feb 25 12:24:26 2014 (530CD1CA)
    VBoxDrv.sys            Tue Feb 25 12:30:06 2014 (530CD31E)
    ииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииииии``
    **************************Sat Mar 22 22:32:18.657 2014 (UTC - 4:00)**************************
    RTKVHD64.sys           Tue Nov  5 06:39:41 2013 (5278D8FD)
    
    http://www.carrona.org/drivers/driver.php?id=vmm.sys
    http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
    http://www.carrona.org/drivers/driver.php?id=dump_iaStorA.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.
    http://www.carrona.org/drivers/driver.php?id=TeeDriverx64.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    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=AppleCharger.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    http://www.carrona.org/drivers/driver.php?id=iwdbus.sys
    http://www.carrona.org/drivers/driver.php?id=igdkmd64.sys
    http://www.carrona.org/drivers/driver.php?id=VBoxNetFlt.sys
    http://www.carrona.org/drivers/driver.php?id=VBoxNetAdp.sys
    http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
    http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
      My System SpecsSystem Spec

  3. #3


    Posts : 4
    Windows 8.1 Pro


    Hello John,
    Thanks for that wealth of info, I am truly surprised how much info one can glean when you know what to look for :-).

    1. UEFI stuff: This is my first build with UEFI, so wasn't sure if I should touch the BIOS defaults. All I knew was the SATA should use AHCI so I ensured mode was set to AHCI (not RAID or IDE) in the BIOS. What I meant by my comment above is, Intel provides a set of drivers (RST I believe) that one can use during Windows Setup (while formatting/partitioning) by loading them separately, I didn't do that. I let Windows Setup partition the drive. I provided this info with reference to this thread dpc_watchdog_violation windows 8.1

    2. Audio Devices: Yup, the second Audio device is a Blue Yeti USB microphone with built in headphone jack. It does not come with any drivers and uses Windows' default drivers. For all practical purposes it's a USB sound card. It is working fine both as mic as well as speaker thru the headphone out.
    I did the following:
    a. Unplugged Device
    b. Uninstalled Hyper-V
    c. Opened Device Manager
    d. Went to View and forced it to show hidden devices
    e. Uninstalled the Yeti
    Attachment 40238
    f. Then I uninstalled what I thought was HD Audio Controller for the Yeti
    Attachment 40239
    g. Restarted
    h. Installed Hyper V.
    i. Restarted and splat! Got another DPC_WATCHDOG_VIOLATION (latest SF Diagnostics Zip attached)
    j. Surprisingly, now when I go back to Device Manager the HD Audio Controller is back (even though invisible by default). How do I get rid of it completely.

    3. VMM.Sys: Yes, I forgot to mention I had installed Oracle Virtual Box. Once it was clear that the issue is with Hyper V. I uninstalled it. But apparently Virtual Box has left it's trail as seen below.
    Attachment 40241
    As to updating VMM.sys from the link you provided, I downloaded and compared it with my existing VMM.sys. Both seem to be the same:
    Attachment 40242
    Attachment 40243
    So, I'll need help in getting rid of all the unnecessary VBox related DLLs. I can live without Virtual Box if Hyper V is working fine.

    Only thing pending is re-installing Realtek Audio drivers from Realtek's site (I have tried it before, currently I am running the ones that came with the M/b).

    Will report back once I've switched the drivers.

    Thanks again,
    Sumit.
      My System SpecsSystem Spec

  4. #4


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


    Sumit, I also have encountered some problems when using Hyper-V alongside with any virtualization softwares such as Vmware or the Oracle Virtual Box.

    Make sure that these are completely removed from the system. Also, are you sure that your installation media for the Hyper-V is not corrupt?
      My System SpecsSystem Spec

  5. #5


    Posts : 4
    Windows 8.1 Pro


    Looks like this issue is finally resolved! Thanks everyone for your comments and time. This is what I did:

    1. Reset Windows 8.1 and asked it to do a complete wipe out and reinstall. I wasn't going to reset, but I was getting weird errors and it seemed that even though my Windows account was Admin I didn't have Admin privileges to add new users to my machine and so on. So I decided to reset it anyways. The Admin privilege issue is probably to do with my O365 email account, but that's a different story.
    2. Installed minimal drivers from Intel to ensure I didn't have any yellow exclamation marks in device manager. (Did not install Realtek LAN or Soundcard drivers, used Windows provided ones.). Even though it wasn't intentional, but my Blue Yeti mic remained connected through the reset, so drivers for it were installed by default.
    3. Updated Windows repeatedly till there were no updates left.
    4. Installed Windows Phone SDK 2012 and immediately got the DPC Error on reboot.
    5. Installed SP4 for Visual Studio 2012. Rebooted, no good, got DPC error.
    6. Uninstalled Visual Studio 2012 and checked if Hyper V was still on. It was, after I rebooted I saw there were no more DPC errors. Rebooted three four times to ensure it wasn't a false positive.
    7. Found an article on MSDN acknowledging issue with Gigabyte motherboards only. Solution was to either disable USB 3 or update BIOS or both Windows 8 fails to boot after installation of Client Hyper-V feature on Gigabyte systems.
    8. Installed Gigabyte AppCenter Utility and updated drivers again via it (it said there were newer versions of the Intel Drivers, even though I had downloaded them from their site couple of hours earlier).
    9. Installed "@BIOS" utility. Updated BIOS via the @BIOS utility. Motherboard came with version F5. I upgraded to F6.
    10. Rebooted as required
    11. Re-installed VS2012. Installed VS2012 SP4, and rebooted, no more DPC. Tried around 5-6 times, so far no more DPC_WATCHDOG_VIOLATION errors.


    Somewhere between Step 8 and 11 (either new drivers or BIOS update, I think the latter) the issue got fixed.

    Once again, thanks to usasma and blueelvis for their time.

    P.S. Hat tip to Gigabyte for the excellent BIOS update utility, that only requires you to click a few buttons and reboot (given a steady internet connection).
      My System SpecsSystem Spec

  6. #6


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


    This is great to hear! Thanks for letting us know. Good luck!
      My System SpecsSystem Spec

DPC_WATCHDOG_VIOLATION when restarting desktop
Related Threads
Solved :( message when restarting in BSOD Crashes and Debugging
When I go to restart, I get a message with sad-face, :(, and some text that flashes on the screen very quickly but then goes away. Windows reports that it will try and repair, it cycles, then does the same thing over and over. If I shut down with the power-switch, then power back on, all is OK....
windows 8.1 keeps restarting in General Support
hi, I installed a fresh new copy of windows 8.1 pro x64 on my laptop (hp pavilion dv6-3112ee core i3) the installation went fine but after 30 minutes my laptop started random restarts, I tried restore and start up diagnostics and I even re installed it again I had a windows 7 ultimate x64 and it...
windows 8 keep restarting in Performance & Maintenance
hi; yesterday i tried to install a free copy of camtasia 8 :o the video showed a way so i can register the program free the way suggested was to go to c:/windows/system32/drivers/ect/ then try to change the security properties of the host file and add a states called everyone but isn't...
restarting frequency in General Support
​hi every body i have a problem with my pc and i wish you will help me when i connect the monitor to the built in video there is no problem , but when i connect the monitor to (nvidia gtx 465) the windows did not open and write "windows preparing automatic repair" after that, the computer...
Windows 8 keeps restarting! in General Support
Hi, this is my first post so I'm very sorry if its in the wrong place, as my laptop was restarting I "stupidly" I must say turn it off before it was finished restarting, now when I start it i won't stop going into recovery mode and restarting again without letting me do anything, I've tried going...
Solved Windows 8 restarting in BSOD Crashes and Debugging
9841 Can someone help me solve this?
Is Yours restarting ?? in General Support
Hellow, I successfully installed windows 8 developer preview using VHD ( Virtual Hard Disk ) It worked fine and I installed my mother board drivers too, later on It started to restart, after restart it was working for few minutes and and again restart, When after a restart it asked to send the...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook