Windows 8 and 8.1 Forums


  1. #1

    Posts : 5
    Windows 8 x64


    Hey, got some problems with my PC for 2 weeks now, I receive random BSOD with CLOCK_WATCHDOG_TIMEOUT error caused by hal.dll and ntoskrnl.exe. I reinstalled windows from scratch, 2 days worked fine, now I get the blue screen again and I cannot solve this :/
    I attached W8 log collector archive, maybe someone can give a hand.

      My System SpecsSystem Spec

  2. #2

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

    There's only 1 memory dump in the uploaded files. If you're using a disk cleaning tool (such as CCleaner), please stop while we're troubleshooting.

    Your BIOS dates from 2007. Please check at the manufacturer's website to see if there are any BIOS updates available for your system. Also check the readme file to see if they apply to the problems that you are having. Please be advised that flashing the BIOS is a very unforgiving process - and one mistake can physically damage your motherboard.

    The report about Windows Updates is missing. Please be sure that you have all Windows Updates - most Win8 systems have around 50 Windows Updates.

    D: drive only has about 7% free space. Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance. Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty)

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

    If this doesn't fix the BSOD's, then please try these free hardware diagnostics: Hardware Diagnostics

    The following is for informational purposes only.
    **************************Fri Mar 22 20:27:47.407 2013 (UTC - 4:00)**************************
    Loading Dump File [C:\Users\Owner\SysnativeBSODApps\032313-19858-01.dmp]
    Windows 8 Kernel Version 9200 MP (4 procs) Free x64
    Built by: 9200.16496.amd64fre.win8_gdr.130108-1504
    System Uptime:0 days 7:55:33.207
    Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
    BugCheck 101, {31, 0, fffff880009b8180, 1}
    BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
    Arg1: 0000000000000031, Clock interrupt time out interval in nominal clock ticks.
    Arg2: 0000000000000000, 0.
    Arg3: fffff880009b8180, The PRCB address of the hung processor.
    Arg4: 0000000000000001, 0.
    PROCESS_NAME:  uTorrent.exe
      BIOS Version                  F2
      BIOS Release Date             11/02/2007
      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.
    **************************Fri Mar 22 20:27:47.407 2013 (UTC - 4:00)**************************
    AODDriver2.sys              Tue Mar  6 04:55:00 2012 (4F55DEF4)
    Rt64win7.sys                Tue Jun 12 10:00:29 2012 (4FD74B7D)
    bdfndisf6.sys               Tue Aug 28 10:25:03 2012 (503CD4BF)
    gzflt.sys                   Wed Aug 29 10:52:43 2012 (503E2CBB)
    trufos.sys                  Fri Sep  7 10:08:07 2012 (5049FFC7)
    bdfwfpf.sys                 Wed Oct 17 08:12:10 2012 (507EA09A)
    avchv.sys                   Wed Oct 31 13:05:22 2012 (50915A52)
    atikmpag.sys                Fri Nov 16 14:39:13 2012 (50A69661)
    atikmdag.sys                Fri Nov 16 15:18:02 2012 (50A69F7A)
    avc3.sys                    Fri Jan 11 12:55:29 2013 (50F05211)
    avckf.sys                   Fri Jan 11 12:59:30 2013 (50F05302)
      My System SpecsSystem Spec

  3. #3

    Posts : 5
    Windows 8 x64

    I did not overcloak my system. This is a fresh installed windows (1 week or so) thats why I dont have any other dump files. With the old windows os crashes were often (1-2 per day). After I posted here I uninstalled all AMD applications, because I had a feeling that AMD stuff (graphic drivers and applications) caused the problem. At this moment I dont even have the driver installed (I use the windows driver).
    Is there any problem if I leave it this way or I can have improvements with ATI driver only on my pc (installed like you described in your reply)?
    No BSOD since I uninstalled AMD VISION Engine Control Center.
      My System SpecsSystem Spec

  4. #4

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

    If the computer meets your needs the way that it is now, I don't see any problem with leaving it in this state.
      My System SpecsSystem Spec

Related Threads
Solved Clock_watchdog_timeout in BSOD Crashes and Debugging
Blue screen started yesterday, both times I was playing a game. This is the first time I have had any bsod/lockups. Let me know if you need anymore info. Thanks for your time.
BSOD & Clock_Watchdog_Timeout in BSOD Crashes and Debugging
Hello fellas, Barely new windows 8 user on my 3.5 years old Dell Studio 1557 (not the least problematic series, for sure). So, I like Windows 8 so far, but I have been having BSOD lately with the Clock_Watchdog_Timeout error. Even though I have no clue, I suspect it could be something...
Clock_watchdog_timeout in BSOD Crashes and Debugging
I get this blue screen every so often (it happened when I first tried typing this too, haha) and they started about a day ago. From other threads on this it looks like a driver problem, but I have no idea WTF I'm doing so any help would be appreciated.
CLOCK_WATCHDOG_TIMEOUT Error in BSOD Crashes and Debugging
Hello guys I been getting this error like 6 times this week, when I installed Windows 8 pro 64bit. and have got it recently when I was editing with After effects. Your help would be greatly appreciated:confused:. Edit Happened again upload newer version
Clock_watchdog_timeout in BSOD Crashes and Debugging
I saw another thread on this, but couldn't find the files GMan indicated to delete. Once or twice per night, my computer will freeze completely. Sometimes, I'll see a BSOD which briefly shows CLOCK_WATCHDOG_TIMEOUT. DxDiag is here: MGA dxdiag -
Bsod: Clock_watchdog_timeout in BSOD Crashes and Debugging
CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 00000030, Clock interrupt time out interval in...
clock_watchdog_timeout in BSOD Crashes and Debugging
Every now and then my system stops working and I get a screen with this message before I need to turn off and restart. Anyone have any ideas what this message might mean? I never saw it at all in windows 7 which ran as stable as a rock.
Eight Forums Android App Eight Forums IOS App Follow us on Facebook