Windows 8 and 8.1 Forums


BSOD - CLOCK_WATCHDOG_TIMEOUT error

  1. #1


    Posts : 5
    Windows 8.1

    BSOD - CLOCK_WATCHDOG_TIMEOUT (caused by processor?)


    I've been getting BSOD for months now... it used to be occasional, but lately it has started occurring several times a day. I've tried reinstalling OS a couple times now... not sure if its one of the device drivers or any software that is causing it. Attaching the necessary info. Please help.
    Last edited by bhasindeepak; 26 Feb 2015 at 10:08.

      My System SpecsSystem Spec

  2. #2


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


    Hi bhasindeepak & Welcome to the forums ^_^,

    I have analysed your latest dump files (Which were created this month only) and below has been provided an analysis of the same for informative purposes. Please note that I did not find a Clock_Watchdog_Timeout in the latest dumps. Are you sure that is the error you are getting?


    DRIVER_POWER_STATE_FAILURE (9f)
    A driver has failed to complete a power IRP within a specific time.
    Arguments:
    Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
    Arg2: ffffe0015e9a5060, Physical Device Object of the stack
    Arg3: fffff802c8d9aaa0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
    Arg4: ffffe00164ac5650, The blocked IRP
    Code:
    0: kd> !irp ffffe001`64ac5650
    Irp is active with 4 stacks 3 is current (= 0xffffe00164ac57b0)
     No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
         cmd  flg cl Device   File     Completion-Context
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
       Args: 00000000 00000000 00000000 00000000
     [  0, 0]   0  0 00000000 00000000 00000000-00000000    
       Args: 00000000 00000000 00000000 00000000
    >[ 16, 2]   0 e1 ffffe00160f56050 00000000 fffff802c7582b3c-ffffe0015f4ddde0 Success Error Cancel pending
           Unable to load image \SystemRoot\system32\DRIVERS\e1y60x64.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for e1y60x64.sys
    *** ERROR: Module load completed but symbols could not be loaded for e1y60x64.sys
     \Driver\e1yexpress nt!PopSystemIrpCompletion
       Args: 00015400 00000000 00000005 00000003
     [  0, 0]   0  0 00000000 00000000 00000000-ffffe0015f4ddde0    
       Args: 00000000 00000000 00000000 00000000
    So, according to the analysis, your Intel Gigabit Network Adapter is causing the trouble. Below is a list of the 3rd party drivers present on your system -
    Code:
    **************************Thu Feb 26 09:30:34.707 2015 (UTC + 5:30)**************************
    npf.sys                     Fri Jun 25 22:20:58 2010 (4C24DE72)
    e1y60x64.sys                Wed Feb 16 01:51:13 2011 (4D5AE039)
    GEARAspiWDM.sys             Fri May  4 01:26:17 2012 (4FA2E2E1)
    hiber_iaStorAV.sys          Thu Aug  1 05:30:49 2013 (51F9A531)
    iaStorAV.sys                Thu Aug  1 05:30:49 2013 (51F9A531)
    dump_iaStorAV.sys           Thu Aug  1 05:30:49 2013 (51F9A531)
    intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
    nvlddmkm.sys                Wed Jul  2 23:12:02 2014 (53B4446A)
    hotcore3.sys                Sat Oct 11 04:08:17 2014 (54385FD9)
    UimFIO.SYS                  Sat Oct 11 05:55:03 2014 (543878DF)
    UimBus.sys                  Sat Oct 11 05:55:07 2014 (543878E3)
    uim_im.sys                  Sat Oct 11 05:55:27 2014 (543878F7)
    uim_devim.sys               Sat Oct 11 05:55:29 2014 (543878F9)
    http://www.carrona.org/drivers/driver.php?id=npf.sys
    http://www.carrona.org/drivers/driver.php?id=e1y60x64.sys
    http://www.carrona.org/drivers/driver.php?id=GEARAspiWDM.sys
    hiber_iaStorAV.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=iaStorAV.sys
    dump_iaStorAV.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=intelppm.sys
    http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
    http://www.carrona.org/drivers/driver.php?id=hotcore3.sys
    http://www.carrona.org/drivers/driver.php?id=UimFIO.SYS
    http://www.carrona.org/drivers/driver.php?id=UimBus.sys
    http://www.carrona.org/drivers/driver.php?id=uim_im.sys
    http://www.carrona.org/drivers/driver.php?id=uim_devim.sys

    Kindly update the highlighted drivers.

    Let me know how it goes ^_^

    -Pranav
      My System SpecsSystem Spec

  3. #3


    Posts : 5
    Windows 8.1


    Thanks Pranav.
    Most of the shut downs / BSOD occurrences happened when I was not watching the screen, but the one on 2/24 did show that error on the blue screen. I will try updating the drivers in the evening and watch the system performance.

    Best,
    Deepak
      My System SpecsSystem Spec

  4. #4


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


    Quote Originally Posted by bhasindeepak View Post
    Thanks Pranav.
    Most of the shut downs / BSOD occurrences happened when I was not watching the screen, but the one on 2/24 did show that error on the blue screen. I will try updating the drivers in the evening and watch the system performance.

    Best,
    Deepak
    Hi Deepak ^_^,

    Sure thing. Let me know how it goes ^_^.

    -Pranav
      My System SpecsSystem Spec

  5. #5


    Posts : 5
    Windows 8.1


    Pranav, when I try to update intel driver from https://downloadcenter.intel.com/dow...for-Windows-8- , it doesn't work, saying the network adaptor not found... thats strange, coz I can see this intel device in device manager.
    Though I haven't seen BSOD in the past 24 hours, I have witnessed hung system a couple times, where I had to do a hard boot for it to resume. Most of the drivers listed in your reponse are not valid anymore, as I didn't install all those softwares after I reinstalled OS.
      My System SpecsSystem Spec

  6. #6


    Posts : 5
    Windows 8.1

    Bsod - whea_uncorrectable_error


    I got another BSOD with a different error... WHEA_UNCORRECTABLE_ERROR. Attaching the dump records.

    The system was hung a few minutes ago and then it rebooted by itself. I looked p some troubleshooting tips for random hanging of Windows 8.1 and found a recommendation to run DISM tool DISM.exe /Online /Cleanup-image /Restorehealth. This was running when all of a sudden the BSOD appeared.

    Any help would be appreciated.
      My System SpecsSystem Spec

  7. #7


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


    Hi bhasindeepak ^_^,

    Unfortunately, it seems that there is no such dump like the WHEA_UNCORRECTABLE_ERROR in the ZIP File. Could you please do one thing? Please zip up all the files in the folder C:\Windows\Minidumps and then upload them in your next post.

    The link you gave me is of a driver which does not support the network card you are using. Sadly, there are no Windows 8.1 drivers available for the network adapter. Were you facing this problem while you were running Windows 7 as well? As of now, try disabling your network card (If you could take it out, that would be best) and see if it is still crashing or not.

    Also, start with these diagnostics -
    Hardware Diagnostics

    Let me know how it goes ^_^

    -Pranav
      My System SpecsSystem Spec

  8. #8


    Posts : 5
    Windows 8.1

    Minidump zip added


    file attached.

    The network adaptor is part of the motherboard... Can I get another NIC and permanently disable this one? I'm hoping that is a possibility. Please advise.
      My System SpecsSystem Spec

  9. #9


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


    Hi Deepak ^_^,

    Really sorry for the delayed response . Everyone seems to be busy with life. Anyways, I have analysed your dump files and they all blame the Intel Networking Driver except the latest one.
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: ffffe00071d650a0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff800dce397a0, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000004, Optional internal context dependent data.
    Code:
    6: kd> !error ffffffffc000009a
    Error code: (NTSTATUS) 0xc000009a (3221225626) - Insufficient system resources exist to complete the API.
    So, it seems that the Display Driver (NVIDIA's nvldmmkm.sys) did not have enough resources to complete the task it was supposed to do.

    The other dump files blamed your Network Adapter.

    Do one thing, disable the Network Adapter from Device Manager and monitor the system and see if it crashes or not. Also, check if you have any update in the Windows Update regarding this driver. My laptop is also old and most of the times, I find the driver update in Windows Update

    You could also try uninstalling the Intel Network Adapter driver from the Device Manager and then restart the system to let Windows install the driver automatically.

    Let me know how it goes ^_^.

    -Pranav
      My System SpecsSystem Spec

BSOD - CLOCK_WATCHDOG_TIMEOUT error
Related Threads
Hello folks. :geek: I may of made break through with a previous problem of mine, so Im posting this on Windows Eight Forums and Ubuntu forums to get knowledge from both sides to confirm my speculation. I had done a recent fresh install of Windows 8.1 a few days back and now I am in need of...
So yeah, im "new" here. Actually been using Seven forums for a while. Friend of mine been having a lot of bluescreens lately and unfortunately i have been unable pinpoint what the problem is so im asking your help and assistance. There have been several different bluescreen which come up while...
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 - Pastebin.com
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...
Eight Forums Android App Eight Forums IOS App Follow us on Facebook