Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Clock Watchdog Timeout - BSOD - Windows 10


  • Please log in to reply
2 replies to this topic

#1 Bickslow

Bickslow

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:44 PM

Posted 05 November 2016 - 07:13 PM

Over the past year or so I've been encountering the Clock Watchdog Timeout error when playing video games (Final Fantasy XIV: Heavensward mostly).  After trying a variety of small things (uninstalling anti-virus and other programs that may have conflicted) I decided to just re-install Windows 10 and start fresh.  It happens on a nightly basis now, but only when playing games.  I've used the BIOS to make sure nothing is overclocked.  Chdsk seemed fine.  I'm currently letting "driver verifier" do it's thing in the background.  I've used NirSoft's "Blue Screen Viewer" to try and read the mini dump files as well as windows event viewer, but I don't really know what I'm doing.

I narrowed it down to ntoskrnl.exe + 14a3b0, but reading around online leads me to understand that knowing that doesn't help because of how broad it specifically is. I also tried using the windows debugging tool and have attached the results from "!analyze -v" as a .txt file.

I will be trying the RAM test and HDD diagnostics next.

 

· OS:  Windows 10 Pro
· x64
· What was original installed OS on system? Windows 7 to Windows 10 free upgrade
·
Retail
· Age of system (hardware): 2 years
· Age of OS installation:  1 week

· CPU:  i5-4670K
· Video Card:  Nvidia GTX 960; EVGA
· MotherBoard:  ASRock Z87 Extreme4
· Power Supply – EVGA NEX 750B

· System Manufacturer – Built personally
·
Exact model number - NA

· Desktop



Any and all help is greatly appreciated!

 

 

Attached Files



BC AdBot (Login to Remove)

 


#2 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,089 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:44 PM

Posted 07 November 2016 - 06:48 AM

ntoskrnl.exe (also seen as ntkrnlpa.exe, ntkrnlmp.exe, or ntkrpamp.exe) is the kernel (core) of the Windows operating system.  It is protected by security features and the Windows System File Checker.  As such, if ntoskrnl.exe was to blame, you'd be experiencing many more problems other than the occasional BSOD.

In most cases ntoskrnl.exe was blamed because a driver (typically a 3rd party driver) has corrupted the memory space that ntoskrnl.exe considers as it's own.  When this happens, ntoskrnl.exe typically finds unknown data (from the 3rd party driver) in it's memory space.  At this point the OS panics and throws a BSOD to prevent damage to the system.

If the culprit (the offending 3rd party driver) hasn't exited yet, then a BSOD analyst may be able to find traces of it in the reports/dumps.  If the culprit has exited, then the chase is on and further tests/reports will be needed to help identify what actually caused it (the reports are the one's that you've uploaded already :0).

More info here:  https://en.wikipedia.org/wiki/Ntoskrnl.exe

BTW - nice work with the debugger!  We massage the dump files a bit more, so you'll see different results when I post my analysis......

More info on the STOP 0x101 errors here:  http://www.carrona.org/bsodindx.html#0x00000101

FYI - this is a difficult problem, and most often it's the result of hardware problems/compatibiliity issues/or even low-level drivers

 

Your UEFI/BIOS (version 2.70) dates from 2014.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  If you are able to install the update through Windows (without booting from an external drive), then go ahead and update it.  WARNING - if the computer might shut down during this procedure, please don't do it, as this may physically damage the computer and prevent it from booting.
FYI - W8 and W10 communicate more with the UEFI/BIOS than previous versions of Windows, so it's important to ensure that the UEFI/BIOS is kept up to date (and that outdated UEFI/BIOS' may be the cause of some compatibility issues).

Only 3 Windows Update hotfixes installed.  Most build 114393 (1607) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

Please uninstall the Intel Smart Connect software and disable it in the BIOS/UEFI.  It's not supported under Windows 10.

 

When you're done running Driver Verifier, I'd suggest also trying these free hardware diagnostics:  http://www.carrona.org/hwdiag.html

Please run ALL of the tests and let us know the results.

 

 

Analysis:
The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:
**************************Sat Nov  5 01:35:58.947 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\110416-4718-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.351.amd64fre.rs1_release_inmarket.161014-1755
System Uptime:0 days 6:13:53.563
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, ffffd88148dcd180, 1}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd88148dcd180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  explorer.exe
FAILURE_BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_4_PROC
CPUID:        "Intel® Core™ i5-4670K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.70
  BIOS Release Date             01/21/2014
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z87 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Nov  4 01:49:41.884 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\110316-4781-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.351.amd64fre.rs1_release_inmarket.161014-1755
System Uptime:0 days 0:43:53.500
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, ffff89807c09e180, 3}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff89807c09e180, The PRCB address of the hung processor.
Arg4: 0000000000000003, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_4_PROC
CPUID:        "Intel® Core™ i5-4670K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.70
  BIOS Release Date             01/21/2014
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z87 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon Oct 31 04:45:43.302 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\103116-4843-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.351.amd64fre.rs1_release_inmarket.161014-1755
System Uptime:1 days 6:53:42.031
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {30, 0, ffffdf81d29cd180, 1}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffdf81d29cd180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_4_PROC
PROCESS_NAME:  System
FAILURE_BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_4_PROC
CPUID:        "Intel® Core™ i5-4670K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.70
  BIOS Release Date             01/21/2014
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z87 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat Oct 29 20:44:23.447 2016 (UTC - 5:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\102916-3421-01.dmp]
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Built by: 14393.0.amd64fre.rs1_release.160715-1616
System Uptime:0 days 2:47:28.062
Probably caused by :ntkrnlmp.exe ( nt!KxMcheckAbort+7b )
BugCheck 9C, {0, ffff9e01b564a760, 0, 0}
BugCheck Info: MACHINE_CHECK_EXCEPTION (9c)
Arguments:
Arg1: 0000000000000000
Arg2: ffff9e01b564a760
Arg3: 0000000000000000
Arg4: 0000000000000000
BUGCHECK_STR:  0x9C_GenuineIntel
PROCESS_NAME:  System
FAILURE_BUCKET_ID: 0x9C_GenuineIntel_STACKPTR_ERROR_nt!KxMcheckAbort
CPUID:        "Intel® Core™ i5-4670K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3400
  BIOS Version                  P2.70
  BIOS Release Date             01/21/2014
  Manufacturer                  To Be Filled By O.E.M.
  Baseboard Manufacturer        ASRock
  Product Name                  To Be Filled By O.E.M.
  Baseboard Product             Z87 Extreme4
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``



3rd Party Drivers:
The following is for information purposes only. My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

**************************Sat Nov  5 01:35:58.947 2016 (UTC - 5:00)**************************
lvrs64.sys                  Mon Oct 22 22:11:24 2012 (5085FCCC)
lvuvc64.sys                 Mon Oct 22 22:12:08 2012 (5085FCF8)
ISCTD64.sys                 Tue Nov 27 14:52:34 2012 (50B51A02)
nvhda64v.sys                Thu Apr 16 15:03:16 2015 (55300774)
TeeDriverW8x64.sys          Tue Jul  7 13:43:32 2015 (559C0FC4)
nvlddmkm.sys                Mon Jul 13 12:50:59 2015 (55A3EC73)
athw8x.sys                  Thu Jan 28 04:52:54 2016 (56A9E4F6)
e1i63x64.sys                Fri Mar  4 16:46:29 2016 (56DA0235)
intelppm.sys                Fri Jul 15 22:10:43 2016 (578997A3)
CorsairVBusDriver.sys       Thu Sep  8 08:00:48 2016 (57D152F0)
CorsairVHidDriver.sys       Thu Sep  8 08:00:50 2016 (57D152F2)


http://www.carrona.org/drivers/driver.php?id=lvrs64.sys
http://www.carrona.org/drivers/driver.php?id=lvuvc64.sys
http://www.carrona.org/drivers/driver.php?id=ISCTD64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=athw8x.sys
http://www.carrona.org/drivers/driver.php?id=e1i63x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=CorsairVBusDriver.sys
http://www.carrona.org/drivers/driver.php?id=[B]CorsairVHidDriver.sys



 
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.

#3 Bickslow

Bickslow
  • Topic Starter

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:04:44 PM

Posted 07 November 2016 - 12:04 PM

Thank you so much for the detailed and timely response!  I'm going to have a very busy next few days with work, but as soon as I have the chance to do everything you recommended I'll report back with more information.  






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users