Windows 8 and 8.1 Forums


BSOD DPC_WATCHDOG_VIOLATION error 0x0000013 random

  1. #1


    Posts : 3
    Windows 8

    BSOD DPC_WATCHDOG_VIOLATION error 0x0000013 random


    I got this brand new laptop a few days ago, and for the past 3 days I have gotten DPC_WATCHDOG_VIOLATION error 0x0000013 and I have no idea how to fix it. I do not have an SSD as I have read that this is a main cause of this error, also another thing to do with fast startup which I have turned off. I have updated all of my device drivers and yet it keeps crashing. The crashing is completely random, I could be browsing chrome, or listening to itunes, or playing minecraft, sometimes it will crash so fast after another crash that I can't figure out why it crashed. Attached is the minidump file. Please help me find the cause to this crashing it's upsetting me very much.

      My System SpecsSystem Spec

  2. #2


    Posts : 4
    Windows 8.1 Pro


    I can give you some raw inputs with respect to the crash dump you've attached. Looks like a Process called YCMMirage.exe was trying to do something on the USB Ports.

    Do you have a USB device that you can try without and check? Or try to update the driver usb80236.sys

    This is my rudimentary analysis, I've seem much more details from Admin, so if this doesn't make sense hang on.

    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DPC_WATCHDOG_VIOLATION (133)
    The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
    or above.
    Arguments:
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
    component can usually be identified with a stack trace.
    Arg2: 0000000000000504, The DPC time count (in ticks).
    Arg3: 0000000000000503, The DPC time allotment (in ticks).
    Arg4: 0000000000000000

    Debugging Details:
    ------------------


    DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

    BUGCHECK_STR: 0x133

    PROCESS_NAME: YCMMirage.exe

    CURRENT_IRQL: d

    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

    DPC_STACK_BASE: FFFFF8021FD4FFB0

    LAST_CONTROL_TRANSFER: from fffff80222a4df4b to fffff802228ce440

    STACK_TEXT:
    nt!KeBugCheckEx
    nt! ?? ::FNODOBFM::`string'+0x145a4
    nt!KeUpdateTime+0x2ec
    hal!HalpTimerClockInterrupt+0x86
    nt!KiInterruptDispatchNoLockNoEtw+0x1aa
    usb80236!CancelSendsTimerDpc+0xac
    nt!KiProcessExpiredTimerList+0x22a
    nt!KiExpireTimerTable+0xa9
    nt!KiTimerExpiration+0xc8
    nt!KiRetireDpcList+0x1f6
    nt!KxRetireDpcList+0x5
    nt!KiDispatchInterruptContinue


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    usb80236!CancelSendsTimerDpc+ac
    fffff880`08c69dd8 75a9 jne usb80236!CancelSendsTimerDpc+0x57 (fffff880`08c69d83)

    SYMBOL_STACK_INDEX: 5

    SYMBOL_NAME: usb80236!CancelSendsTimerDpc+ac

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: usb80236

    IMAGE_NAME: usb80236.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 51198a2e

    IMAGE_VERSION: 6.2.9200.16525

    BUCKET_ID_FUNC_OFFSET: ac

    FAILURE_BUCKET_ID: 0x133_DPC_usb80236!CancelSendsTimerDpc

    BUCKET_ID: 0x133_DPC_usb80236!CancelSendsTimerDpc

    ANALYSIS_SOURCE: KM

    FAILURE_ID_HASH_STRING: km:0x133_dpc_usb80236!cancelsendstimerdpc

    FAILURE_ID_HASH: {a33649e0-3f49-3074-35df-91e00215eed4}

    Followup: MachineOwner
    ---------

    0: kd> lmvm usb80236
    start end module name
    fffff880`08c67000 fffff880`08c72000 usb80236 (pdb symbols) C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\usb80236.pdb\2AB98922D8B449CF90A405B9804175E71\usb80236.pdb
    Loaded symbol image file: usb80236.sys
    Mapped memory image file: C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x64\sym\usb80236.sys\51198A2Eb000\usb80236.sys
    Image path: \SystemRoot\System32\drivers\usb80236.sys
    Image name: usb80236.sys
    Timestamp: Tue Feb 12 00:17:50 2013 (51198A2E)
    CheckSum: 00014210
    ImageSize: 0000B000
    File version: 6.2.9200.16525
    Product version: 6.2.9200.16525
    File flags: 0 (Mask 3F)
    File OS: 40004 NT Win32
    File type: 2.0 Dll
    File date: 00000000.00000000
    Translations: 0409.04b0
    CompanyName: Microsoft Corporation
    ProductName: Microsoftฎ Windowsฎ Operating System
    InternalName: usb8023.sys
    OriginalFilename: usb8023.sys
    ProductVersion: 6.2.9200.16525
    FileVersion: 6.2.9200.16525 (win8_gdr.130211-1605)
    FileDescription: Remote NDIS USB Driver
    LegalCopyright: ฉ Microsoft Corporation. All rights reserved.
      My System SpecsSystem Spec

  3. #3


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


    Nice work sumitkm!
    FYI - the PROCESS_NAME: line usually isn't significant in BSOD analysis - as BSOD's occur in the kernel space, and most of the process names are from the user space (a full explanation of this would take a lot longer to type!).

    I only use the PROCESS_NAME: line when I see a number of memory dumps (at least 4 or 5) that mention the same process (in this case chrome.exe is named once, YCMMirage.exe is named once, and System is named 3 times).
    In those cases I look into what drivers that process could be trying to access - and then concentrate on them.
    This does not mean that you should disregard the PROCESS_NAME:, but rather that you should understand that it's not often that it points at the solution.

    For example, YCMMirage.exe is a background program that launches the YouCam software.
    If the camera is USB, then it's reasonable to check into the USB drivers as you've mentioned

    Now, I haven't run the dump file myself - but from looking at the stack text there are 2 significant things:
    1) usb80236 (usb80236.sys), nt (ntoskrnl.exe), and hal (hal.dll) are the only drivers listed in the stack. Of them, the most info comes from usb80236 - it is a driver that is related to USB and to networking (FileDescription: Remote NDIS USB Driver)
    2) hal (hal.dll) is in the stack. I usually see this when there's a problem between the device and Windows ( Microsoft Windows library files - Wikipedia, the free encyclopedia ). In these cases, I tend to find that compatibility or hardware problems are the most common.

    Since Windows drivers are the least likely to be the problem (in a fully updated system), then it's most likely that a 3rd party driver or a hardware problem are causing this. It could be due to compatibility issues, so a look at the driver dates wouid probably help.

    I've run the memory dumps - so on with more of my opinion:

    The 5 memory dumps that were uploaded are essentially the same as the one that sumitkm posted.

    Interestingly, the oldest device driver in the memory dumps is from a Cyberlink program. This tends to support the theory that it's an incompatibility - but it is not proof. The "proof" will be getting a copy of the Cyberlink software that's certified to be Win8 compatible and installing it to see if that stops the BSOD's.

    Please note that I haven't seen issues with the 2012 version of AMD Overdrive as I did with the older versions - so this step may e unnecessary:
    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 Windows systems.
    NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.
    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 - Sysnative Forums

    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.
    There are a couple of other drivers that date from before the release of Win8 (26 Oct 2012). It would be advisable to check them to ensure that they are compatible with Win8 (if uncertain, just install the one that you're certain is compatible with Win8).

    BUT, note that there is a problem device (related to networking) in Device Manager:
    WAN Miniport (Network Monitor) #2 ROOT\MS_NDISWANBH\0001 This device is not working properly because Windows cannot load the drivers required for this device.
    If Network Monitor is installed, please uninstall it. If not, then please right click on the device and select "Uninstall" - then reboot the computer and check to see if the device shows a problem again..

    If this doesn't help 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 17:18:37.514 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032414-24180-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:0 days 0:05:58.225
    *** WARNING: Unable to verify timestamp for usb80236.sys
    *** ERROR: Module load completed but symbols could not be loaded for usb80236.sys
    Probably caused by :usb80236.sys ( usb80236+2dd8 )
    BugCheck 133, {0, 504, 503, 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: 0000000000000504, The DPC time count (in ticks).
    Arg3: 0000000000000503, 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_usb80236+2dd8
      BIOS Version                  F.31
      BIOS Release Date             12/04/2013
      Manufacturer                  Hewlett-Packard
      Product Name                  HP Pavilion 15 Notebook PC
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Mon Mar 24 17:12:17.254 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032414-30279-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:0 days 0:36:31.955
    *** WARNING: Unable to verify timestamp for usb80236.sys
    *** ERROR: Module load completed but symbols could not be loaded for usb80236.sys
    Probably caused by :usb80236.sys ( usb80236+2dd5 )
    BugCheck 133, {0, 504, 503, 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: 0000000000000504, The DPC time count (in ticks).
    Arg3: 0000000000000503, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  chrome.exe
    FAILURE_BUCKET_ID: 0x133_DPC_usb80236+2dd5
      BIOS Version                  F.31
      BIOS Release Date             12/04/2013
      Manufacturer                  Hewlett-Packard
      Product Name                  HP Pavilion 15 Notebook PC
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Sun Mar 23 20:41:33.856 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-29764-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:0 days 0:04:31.567
    *** WARNING: Unable to verify timestamp for usb80236.sys
    *** ERROR: Module load completed but symbols could not be loaded for usb80236.sys
    Probably caused by :usb80236.sys ( usb80236+2dd8 )
    BugCheck 133, {0, 504, 503, 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: 0000000000000504, The DPC time count (in ticks).
    Arg3: 0000000000000503, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
    PROCESS_NAME:  YCMMirage.exe
    FAILURE_BUCKET_ID: 0x133_DPC_usb80236+2dd8
      BIOS Version                  F.31
      BIOS Release Date             12/04/2013
      Manufacturer                  Hewlett-Packard
      Product Name                  HP Pavilion 15 Notebook PC
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Sun Mar 23 20:36:37.040 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-48297-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:0 days 0:25:14.739
    *** WARNING: Unable to verify timestamp for usb80236.sys
    *** ERROR: Module load completed but symbols could not be loaded for usb80236.sys
    Probably caused by :usb80236.sys ( usb80236+2dd2 )
    BugCheck 133, {0, 504, 503, 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: 0000000000000504, The DPC time count (in ticks).
    Arg3: 0000000000000503, 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_usb80236+2dd2
      BIOS Version                  F.31
      BIOS Release Date             12/04/2013
      Manufacturer                  Hewlett-Packard
      Product Name                  HP Pavilion 15 Notebook PC
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    **************************Sun Mar 23 20:06:25.045 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\032314-59670-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16628.amd64fre.win8_gdr.130531-1504
    System Uptime:0 days 22:05:02.088
    *** WARNING: Unable to verify timestamp for usb80236.sys
    *** ERROR: Module load completed but symbols could not be loaded for usb80236.sys
    Probably caused by :usb80236.sys ( usb80236+2dd2 )
    BugCheck 133, {0, 504, 503, 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: 0000000000000504, The DPC time count (in ticks).
    Arg3: 0000000000000503, 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_usb80236+2dd2
      BIOS Version                  F.31
      BIOS Release Date             12/04/2013
      Manufacturer                  Hewlett-Packard
      Product Name                  HP Pavilion 15 Notebook PC
    จจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจจ``
    
    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 17:18:37.514 2014 (UTC - 4:00)**************************
    CLVirtualDrive.sys           Mon Dec 26 08:26:47 2011 (4EF87617)
    AODDriver2.sys               Thu Apr  5 05:23:37 2012 (4F7D6499)
    GEARAspiWDM.sys              Thu May  3 15:56:17 2012 (4FA2E2E1)
    RNDISMP6.SYS                 Wed Jul 25 22:27:53 2012 (5010AB29)
    usbfilter.sys                Tue Aug 28 21:27:12 2012 (503D6FF0)
    WirelessButtonDriver64.sys   Wed Aug 29 23:11:29 2012 (503ED9E1)
    RimSerial_AMD64.sys          Mon Oct 22 16:51:51 2012 (5085B1E7)
    amd_sata.sys                 Fri Nov 30 04:00:42 2012 (50B875BA)
    amd_xata.sys                 Fri Nov 30 04:00:46 2012 (50B875BE)
    Rt630x64.sys                 Thu Dec 27 19:04:06 2012 (50DCE1F6)
    RtsP2Stor.sys                Wed Jan 23 03:26:31 2013 (50FF9EB7)
    SynTP.sys                    Tue Feb  5 22:26:11 2013 (5111CD53)
    usb80236.sys                 Mon Feb 11 19:17:50 2013 (51198A2E)
    AtihdW86.sys                 Thu Feb 14 17:11:12 2013 (511D6100)
    atikmpag.sys                 Mon Feb 25 23:28:21 2013 (512C39E5)
    atikmdag.sys                 Mon Feb 25 23:35:39 2013 (512C3B9B)
    Accelerometer.sys            Tue Feb 26 15:08:10 2013 (512D162A)
    hpdskflt.sys                 Tue Feb 26 15:08:12 2013 (512D162C)
    RTKVHD64.sys                 Thu Mar  7 05:31:01 2013 (51386C65)
    rimvndis6_AMD64.sys          Wed Mar 20 09:56:02 2013 (5149BFF2)
    rtwlane.sys                  Thu Jul 11 05:03:02 2013 (51DE74C6)
    RimUsb_AMD64.sys             Mon Nov 25 16:52:56 2013 (5293C6B8)
    aswRdr2.sys                  Tue Mar 18 16:32:20 2014 (5328AD54)
    aswKbd.sys                   Tue Mar 18 16:32:37 2014 (5328AD65)
    aswSnx.sys                   Tue Mar 18 16:32:53 2014 (5328AD75)
    aswNdisFlt.sys               Tue Mar 18 16:33:50 2014 (5328ADAE)
    aswRvrt.sys                  Tue Mar 18 16:34:02 2014 (5328ADBA)
    aswVmm.sys                   Tue Mar 18 16:34:12 2014 (5328ADC4)
    aswMonFlt.sys                Tue Mar 18 16:34:52 2014 (5328ADEC)
    aswSP.sys                    Tue Mar 18 16:40:59 2014 (5328AF5B)
    aswStm.sys                   Tue Mar 18 16:41:44 2014 (5328AF88)
    
    http://www.carrona.org/drivers/driver.php?id=CLVirtualDrive.sys
    http://www.carrona.org/drivers/driver.php?id=AODDriver2.sys
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    RNDISMP6.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=usbfilter.sys
    http://www.carrona.org/drivers/driver.php?id=WirelessButtonDriver64.sys
    http://www.carrona.org/drivers/driver.php?id=RimSerial_AMD64.sys
    http://www.carrona.org/drivers/driver.php?id=amd_sata.sys
    http://www.carrona.org/drivers/driver.php?id=amd_xata.sys
    http://www.carrona.org/drivers/driver.php?id=Rt630x64.sys
    http://www.carrona.org/drivers/driver.php?id=RtsP2Stor.sys
    http://www.carrona.org/drivers/driver.php?id=SynTP.sys
    usb80236.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=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=Accelerometer.sys
    http://www.carrona.org/drivers/driver.php?id=hpdskflt.sys
    http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
    rimvndis6_AMD64.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=rtwlane.sys
    http://www.carrona.org/drivers/driver.php?id=RimUsb_AMD64.sys
    http://www.carrona.org/drivers/driver.php?id=aswRdr2.sys
    http://www.carrona.org/drivers/driver.php?id=aswKbd.sys
    http://www.carrona.org/drivers/driver.php?id=aswSnx.sys
    http://www.carrona.org/drivers/driver.php?id=aswNdisFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswRvrt.sys
    http://www.carrona.org/drivers/driver.php?id=aswVmm.sys
    http://www.carrona.org/drivers/driver.php?id=aswMonFlt.sys
    http://www.carrona.org/drivers/driver.php?id=aswSP.sys
    aswStm.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

  4. #4


    Posts : 3
    Windows 8


    Unfortunately I am not versed in computer tech language so I have no idea how to uninstall the drivers CLVirtualDrive.sys and AODDriver2.syshow would I go about doing this with detailed instructions. With you saying that Cyberlink YouCam causing a problem with the drivers I have uninstalled the program entirely. I tried updating from win8 to win8.1 to see if that would do anything but when it restarts to finalize the process it blue screens and reverts to win8. Just in a simple way how can I uninstall the drivers listed?
      My System SpecsSystem Spec

  5. #5


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


    Uninstall your Cyberlink software. If there's more than one Cyberlink program, uninstall them all.
    If that fixes the BSOD's, then we'll see about finding free replacements if you need them.

    As for the AODDriver2.sys - let's hold off on that as I haven't seen errors from it recently.
    If the BSOD's persist, then try the instructions I gave in my last post. Here's another copy of them:
    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 Windows systems.
    NOTE: these symptoms were from the previous release of OverDrive. The new release uses the same driver name, but is dated from 4 November 2013.
    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 - Sysnative Forums

    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.
    Don't forget to fix the network problem also:
    BUT, note that there is a problem device (related to networking) in Device Manager:
    WAN Miniport (Network Monitor) #2 ROOT\MS_NDISWANBH\0001 This device is not working properly because Windows cannot load the drivers required for this device.


    If Network Monitor is installed, please uninstall it. If not, then please right click on the device and select "Uninstall" - then reboot the computer and check to see if the device shows a problem again..
    Finally, if the BSOD's don't stop, please run Driver Verifier according to these instructions: Driver Verifier Settings
      My System SpecsSystem Spec

  6. #6


    Posts : 3
    Windows 8


    So as of now I've uninstalled the driver "WAN Miniport (Network Monitor) #2", under the device manager there was a code 31 error with a little yellow ! beside it, so I have uninstalled that and it appears to be gone, and I have uninstalled everyhing related to Cyberlink from the control panel. As of now I have not performed anything around the AMD Overdrive I'll leave that. Hopefully this fixes the issues. Also this morning I got an update from windows8 to windows8.1 and I was wondering if that would do anything to solve my problem, so I tried it two seperate times and it blue screened mid update for both and reverted to windows 8. Any solutions on that?
      My System SpecsSystem Spec

  7. #7


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


    Hold off on the 8.1 update for now.
    Get 8 working well, then update all drivers and get all Windows Updates
    Then try again.

    I tried for 4 months to get 8.1 to install on my Samsung NP780!
      My System SpecsSystem Spec

BSOD DPC_WATCHDOG_VIOLATION error 0x0000013 random
Related Threads
Hi! I hope I've managed to gather all necessary information, thanks for supplying this forum. I get DPC_WATCHDOG_VIOLATION BSOD from time to time - it seems mostly to occur when laptop is not connected to a power-cord. Hopefully I'll upload the necessary SF Debug files. Many thanks in...
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...
BSOD - Random - Error: DPC_Watchdog_Violation in BSOD Crashes and Debugging
Hi, I am posting here to see if anyone can help me identify the culprit behind my random BSOD's that seem to spur up at random and happen at least 2-3 times a day. It started this at first on June 3rd. And from how it happens, there doesn't seem to be anything that I do that triggers the BSOD. I...
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