Windows 8 and 8.1 Forums

hal dll and ntoskrnl.exe watchdog violation

  1. #1

    Posts : 4
    windows 8

    hal dll and ntoskrnl.exe watchdog violation

    problems with random crashes, seems to be completely random as i can't find any triggers or anything... will try to post more info but crashes varying from every 10 minutes to 10 days with not much in common kinda makes it hard to post. (3rd attempt btw)
    *update* minidumps were deleted as of last crash (just after posting this thread)
    *update* finally managed to upload a .zip file of my minidup

      My System SpecsSystem Spec

  2. #2

    Posts : 4
    windows 8

    i may have found a fix for the problem, will give an update tomorrow whether or not it works. main reason i won't say it now is due to it having a good chance of breaking your system completely. at least i think so.
      My System SpecsSystem Spec

  3. #3

    Posts : 4
    windows 8

    false positive, the fix merely delayed the BSOD but all in all not worth the hassle
      My System SpecsSystem Spec

  4. #4

    Posts : 4
    windows 8

    ok, everyone experiencing issues with hal.dll and ntoskrnl.exe, try turning off your pc completely. Then remove any power cables and batteries that may be attached, (no a CMOS flash is not nessecary) now leave it for a few hours while.. watching tv, or hanging out with friends, or you know. Doing just whatever
      My System SpecsSystem Spec

  5. #5

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

    Sorry for the delay in responding. There just aren't that many people who do BSOD analysis, so at times we get a bit overwhelmed!

    Responding to your own posts makes it look like the topic is being read - and it makes it look like it's only 1 day since the last response instead of the 4 days since the original post (it's how the forum sor

    Do your still need help with this problem? If so, Please provide this information so we can provide a complete analysis (from the Pinned Topic at the top of the forum): Blue Screen of Death (BSOD) Posting Instructions Please use Option 1 as it provides Event Viewer logs.

    I will be notified if you reply to this topic and will respond within 48 hours.

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

    LGVirHid.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
    Logitech Gamepanel Virtual HID Device Driver

    LGBusEnum.sys Mon Nov 23 20:36:48 2009 (4B0B38B0)
    Logitech Keyboard

    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. Removing some drivers may make the system unstable - so if you're unable to find updates, post back for info on the one's that can/cannot be safely removed.

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

    The following is for informational purposes only.
    **************************Wed Jun  4 17:09:38.215 2014 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\John\SysnativeBSODApps\060514-27203-01.dmp]
    Windows 8 Kernel Version 9600 MP (8 procs) Free x64
    Built by: 9600.17041.amd64fre.winblue_gdr.140305-1710
    System Uptime:0 days 0:22:59.969
    *** WARNING: Unable to verify timestamp for usb8023x.sys
    *** ERROR: Module load completed but symbols could not be loaded for usb8023x.sys
    Probably caused by :usb8023x.sys ( usb8023x+2cfe )
    BugCheck 133, {0, 501, 500, 0}
    BugCheck Info: DPC_WATCHDOG_VIOLATION (133)
    Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
        component can usually be identified with a stack trace.
    Arg2: 0000000000000501, The DPC time count (in ticks).
    Arg3: 0000000000000500, The DPC time allotment (in ticks).
    Arg4: 0000000000000000
    BUGCHECK_STR:  0x133
    PROCESS_NAME:  System
    FAILURE_BUCKET_ID: 0x133_DPC_usb8023x+2cfe
      BIOS Version                  FB
      BIOS Release Date             01/23/2013
      Manufacturer                  Gigabyte Technology Co., Ltd.
      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.
    **************************Wed Jun  4 17:09:38.215 2014 (UTC - 4:00)**************************
    LGVirHid.sys                Mon Nov 23 20:36:48 2009 (4B0B38B0)
    LGBusEnum.sys               Mon Nov 23 20:36:48 2009 (4B0B38B0)
    usbfilter.sys               Tue Aug 28 21:27:12 2012 (503D6FF0)
    pffilter.sys                Sun Nov 18 21:07:18 2012 (50A99456)
    LGSHidFilt.Sys              Thu May 30 11:16:33 2013 (51A76D51)
    HWiNFO64A.SYS               Fri Nov 22 10:45:10 2013 (528F7C06)
    SmartDefragDriver.sys       Mon Dec 23 05:05:52 2013 (52B80B00)
    AODDriver2.sys              Tue Feb 11 06:06:52 2014 (52FA044C)
    Rt630x64.sys                Tue Feb 18 06:44:16 2014 (53034790)
    RTKVHD64.sys                Mon Feb 24 10:43:38 2014 (530B68AA)
    AMDACPKSL.SYS               Tue Mar 11 19:49:44 2014 (531FA118)
    AtihdWB6.sys                Tue Mar 11 19:50:02 2014 (531FA12A)
    atikmpag.sys                Thu Apr 17 21:07:07 2014 (53507ABB)
    atikmdag.sys                Thu Apr 17 22:13:16 2014 (53508A3C)
      My System SpecsSystem Spec

hal dll and ntoskrnl.exe watchdog violation

Similar Threads
Thread Forum
Dpc Watchdog Violation (133)
Hi, I have a problem. But I do not know english. I uploaded the dump file. Thanks for help.
BSOD Crashes and Debugging
DPC Watchdog Violation BSOD Caused By Driver: ntoskrnl.exe
Hello my computer has been freezing/crashing over the past few months - I have still not managed to fix this problem. My computer will simply freeze (unable to do anything) and it will require a hard-reset, after restarting there will be no error logs etc. This happens under GPU intensive tasks...
BSOD Crashes and Debugging
DPC WatchDog Violation
I have Samsung NP-RV515 A01-US. I upgraded to 128gb ssd. I got dpc watchdog violation for the first time today after runing updates. Uninstalling doesn't help. Upon boot every time after 60 seconds. No luck. I know there are threads here about this but not my exact issue. After running...
BSOD Crashes and Debugging
DPC Watchdog Violation BSOD
Hi, Recently, I have had several DPC_Watchdog_Violation Blue Screens after waking my PC up from sleep/hibernation. After clicking the mouse to wake up the computer, the screen would go on, but the keyboard and mouse would not react any further, giving the impression that the computer is frozen....
BSOD Crashes and Debugging
Please help me out, DPC watchdog violation.
I am getting DPC watchdog violation issue when i turned on my laptop today...I dont know what to do now, please help me out.:cry:
BSOD Crashes and Debugging
DPC Watchdog Violation
Hello, I recently refreshed Windows 8 have been running into "Watchdog" reboots. My guess is that it is something network related. I am using a Linksys wmp54g adapter, which hasn't been supported by Linksys for a couple of years. The funny thing is that I never had this issue with my...
BSOD Crashes and Debugging
BSOD Watchdog Violation
I Upgraded from vista after trying the comusmer preview a few moths back(which worked flawlessly btw) and now after installed windows 8 I've come across this watchdog violation. I'm assuming its a driver error. I have an ati HD4870 and I know AMD will stop supporting these older graphics cards and...
BSOD Crashes and Debugging

Eight Forums Android App Eight Forums IOS App Follow us on Facebook