Windows 8 and 8.1 Forums

Clock_watchdog_timeout

  1. #11


    Posts : 1,851
    8250 x86 + 7 SP1 x86 + Ubuntu 12.04 LTS x86


    Quote Originally Posted by kadjar View Post
    Ugh.. I installed Windows 7, and I'm still getting the same issue.

    Is it possible that the issue is hardware? A faulty core, perhaps? I ran a sensor test using RealTemp and Prime 95, and it caused a crash about 20% of the way in. (Real Temp - CPU temperature monitoring)

    I've attached the latest minidump. Thank you so much.
    Installing Windows 7 was a complete step in the opposite direction. Now, everything we've done to try to eliminate the cause of the (usually hardware) 0x124 stop has been in vain and we are back to square one.

    If motherboard bios has not been updated to latest, do so. Regardless, set Optimized Defaults in it then save.

    Eliminate these drivers from the system:

    Code:
    FNETURPX FNETURPX.SYS Fri Oct 03 22:27:02 2008 (48E6D476)
    PxHlpa64 PxHlpa64.sys Tue Jun 23 19:16:35 2009 (4A416253)
    cfosspeed6 cfosspeed6.sys Mon Jul 04 09:18:51 2011 (4E11BDBB)
    AsrIbDrv AsrIbDrv.sys Thu Jan 08 03:39:16 2009 (4965BBB4)
    AxtuDrv  AxtuDrv.sys  Thu May 19 03:42:38 2011 (4DD4C9EE)
    Update:
    RTKVHD64 RTKVHD64.sys Tue Jun 14 07:28:43 2011

    from Realtek's site.

      My System SpecsSystem Spec

  2. #12


    Posts : 6
    Windows 8 Consumer Preview


    I uninstalled FNETURPX, PxHlpa64, and cfosspeed6, and updated the Realtek drivers. I could not find AsrIbDrv.sys or AxtuDrv.sys, however.

    I flashed the bios to the most updated version as well.

    I looked in the drivers folder for the other two drivers and ran a search. Are they hiding somewhere else?
      My System SpecsSystem Spec

  3. #13


    Posts : 1,851
    8250 x86 + 7 SP1 x86 + Ubuntu 12.04 LTS x86


    Quote Originally Posted by kadjar View Post
    I uninstalled FNETURPX, PxHlpa64, and cfosspeed6, and updated the Realtek drivers. I could not find AsrIbDrv.sys or AxtuDrv.sys, however.

    I flashed the bios to the most updated version as well.

    I looked in the drivers folder for the other two drivers and ran a search. Are they hiding somewhere else?
    Most excellent. We will wait for any problems to happen from here, and deal with things then if necessary.

    (Just make sure you've set Optimized Defaults and save, in the new bios.)

    If there are any new crashes, please post them. If not, congrats on fixing the machine.
      My System SpecsSystem Spec

  4. #14


    Posts : 1,851
    8250 x86 + 7 SP1 x86 + Ubuntu 12.04 LTS x86


    Another thing:

    I don't wish to over-complicate things for you, but if you're feeling confident enough that you know how to set up a dual-boot system with Windows 8 also, I wouldn't mind debugging that again for you if necessary.

    There are excellent tutorials on this site that can show you how. Or if you honestly really want 8, and only 8, then you can upgrade your current Windows 7 to it now. That is not going to help nor hurt our current efforts, as long as you don't install any more 3rd party software until the issue is completely fixed.

    Or keep Windows 7 alone as is.

    Your choice, and any of them are good from here. (No 3rd party non-physical hardware drivers!!! )
      My System SpecsSystem Spec

  5. #15


    Hi!
    I've been using Windows 8 for about a week and today, out of nowhere, i got the blue screen and the clock_watchdog_timeout error message.

    This is the archive containing the crash dump files.

    I'd be very grateful if you could help me
      My System SpecsSystem Spec

Page 2 of 2 FirstFirst 12
Clock_watchdog_timeout
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.
Solved Clock_watchdog_timeout in BSOD Crashes and Debugging
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,...
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
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