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 new PC


  • Please log in to reply
8 replies to this topic

#1 Frottery

Frottery

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:40 PM

Posted 08 June 2016 - 07:25 PM

Hi,

 

I recently upgraded my motherboard, processor, and RAM and have been getting intermittent BSOD CLOCK_WATCHDOG_TIMEOUT errors ever since. It doesn't seem to relate to any one thing, I did notice that there were a lot of duplicate drivers in device manager, not sure if that has anything to do with this.

 

Info

 

· OS - Windows 10
· 64 Bit
· reinstalled windows 10 recently but originally upgraded from windows 7
· Windows 10 free upgrade
· HDD's 3 and 7 years old, mobo,cpu, and ram < 5 weeks old, 2 x gtx 660 graphics cards ~4 years old
· Reinstalled OS ~1 week ago

· CPU - intel 6700k
· Video Card -  2 x gtx 660 run in SLI
· MotherBoard - ASUS z170-ar
· Power Supply - thermaltake 600w

· Laptop or Desktop - Desktop

 

Any help would be appreciated.

 

Thanks,

 

Elliott

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,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:40 AM

Posted 09 June 2016 - 08:18 AM

Your UEFI/BIOS (version 1801) dates from 2016.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a recent update.

Only 6 Windows Update hotfixes installed.  Most build 10240 (original release) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.

Only 1 memory dump in the uploaded reports.

If using a disk cleaner (such as CCleaner), please stop while we're troubleshooting.

 

Lot's of Live Kernel Events in the WER section of the MSINFO32 report

Please do the following:
- open Event Viewer (run eventvwr.msc from the "Run" dialog)
- expand the Custom Views category (left click on the > next to the words "Custom Views")
- right click on the "Administrative Events" heading
- select "Save all Events in Custom View as..."
- save the file as Admin.evtx
- zip up the file (right click on it, select "Send to", select "Compressed (zipped) folder")
- upload it with your next post (if it's too big, then upload it to a free file-hosting service and post a link here).

FYI - If we're looking for Event ID 41 errors (unexplained shutdowns), there's more info on that here:  http://support.microsoft.com/kb/2028504

While waiting for a reply, please monitor your temps with this free utility:  http://www.cpuid.com/softwares/hwmonitor.html

 

I'm learning as I go along.  Looking at the events in the WER section, they seem related to some video issues (STOP 0x117 and STOP 0x141 errors) with your nVidia drivers.

I don't think that we'll learn much from the Admin event logs that I requested, but I'd suggest:

- download a fresh set of the latest W10 compatible video drivers from the nVidia website
- uninstall the current video drivers

- install the freshly downloaded video drivers

- monitor for further problems.
 

Please note these older drivers.  They should be updated to the latest, W10 compatible version.  If unavailable, the programs that installed them should be uninstalled.:

SCDEmu.SYS                   Mon Apr 12 04:52:25 2010 (4BC2DF49)

http://www.carrona.org/drivers/driver.php?id=SCDEmu.SYS

Most likely from PowerISO

 

tap0901.sys                  Thu Nov 24 13:50:27 2011 (4ECE91F3)

http://www.carrona.org/drivers/driver.php?id=tap0901.sys

This is associated with several different programs, TAP-Win32 Adapter V9 or OpenVPN driver or COMODO

 

AsIO.sys                     Wed Aug 22 05:54:47 2012 (5034AC67)

http://www.carrona.org/drivers/driver.php?id=AsIO.sys

Usually associated with the Asus AISuite or PCProbe utilities.

 

Beyond this I have these 5 suggestions:
1.  Get ALL available Windows Updates.  It may take several trips to get them all
2.  Get ALL available, compatible updates for your OS from the manufacturer's website (to include BIOS/UEFI).
3.  Get ALL available, compatible updates for the programs and any additional hardware installed on your computer from the developer's website
4.  Start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
5.  If all of the hardware tests pass, then run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

 

 

Analysis:

The following is for information purposes only. The following information contains the relevant information from the blue screen analysis:

**************************Tue Jun  7 18:38:24.847 2016 (UTC - 4:00)**************************
Loading Dump File [C:\Users\john\SysnativeBSODApps\060816-94734-01.dmp]
Windows 10 Kernel Version 10240 MP (8 procs) Free x64
Built by: 10240.16841.amd64fre.th1_st1.160408-1853
System Uptime:0 days 0:51:53.453
Probably caused by :Unknown_Image ( ANALYSIS_INCONCLUSIVE )
BugCheck 101, {18, 0, ffffd0018a180180, 2}
BugCheck Info: CLOCK_WATCHDOG_TIMEOUT (101)
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffd0018a180180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.
BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC
PROCESS_NAME:  foobar2000.exe
FAILURE_BUCKET_ID: ZEROED_STACK_CLOCK_WATCHDOG_TIMEOUT_8_PROC
CPUID:        "Intel® Core™ i7-6700K CPU @ 4.00GHz"
MaxSpeed:     4000
CurrentSpeed: 4008
  BIOS Version                  1801
  BIOS Release Date             03/24/2016
  Manufacturer                  System manufacturer
  Baseboard Manufacturer        ASUSTeK COMPUTER INC.
  Product Name                  System Product Name
  Baseboard Product             Z170-AR
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``




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:

**************************Tue Jun  7 18:38:24.847 2016 (UTC - 4:00)**************************
SCDEmu.SYS                   Mon Apr 12 04:52:25 2010 (4BC2DF49)
tap0901.sys                  Thu Nov 24 13:50:27 2011 (4ECE91F3)
AsIO.sys                     Wed Aug 22 05:54:47 2012 (5034AC67)
intelppm.sys                 Thu Jul  9 23:12:59 2015 (559F383B)
e1d65x64.sys                 Thu Aug 13 05:14:29 2015 (55CC5FF5)
TeeDriverW8x64.sys           Thu Oct  8 14:13:00 2015 (5616B22C)
asmtxhci.sys                 Sun Oct 11 22:51:07 2015 (561B201B)
asmthub3.sys                 Sun Oct 11 22:51:12 2015 (561B2020)
iaStorA.sys                  Wed Nov  4 05:27:49 2015 (5639DDA5)
dc3d.sys                     Fri Nov  6 14:14:22 2015 (563CFC0E)
RTKVHD64.sys                 Fri Jan 22 10:09:21 2016 (56A24621)
WirelessKeyboardFilter.sys   Wed Mar 16 03:48:01 2016 (56E90FB1)
nvhda64v.sys                 Thu Mar 24 15:26:36 2016 (56F43F6C)
nvvad64v.sys                 Tue Apr 12 04:46:52 2016 (570CB5FC)
VBoxDD2R0.r0                 Thu Apr 28 09:04:58 2016 (57220A7A)
VBoxNetAdp6.sys              Thu Apr 28 09:04:58 2016 (57220A7A)
VBoxNetLwf.sys               Thu Apr 28 09:04:58 2016 (57220A7A)
VBoxUSBMon.sys               Thu Apr 28 09:04:58 2016 (57220A7A)
VBoxDDR0.r0                  Thu Apr 28 09:04:59 2016 (57220A7B)
VMMR0.r0                     Thu Apr 28 09:05:52 2016 (57220AB0)
VBoxDrv.sys                  Thu Apr 28 09:05:52 2016 (57220AB0)
NvStreamKms.sys              Sun May  1 17:00:16 2016 (57266E60)
nvlddmkm.sys                 Thu May 19 21:34:38 2016 (573E69AE)

 

http://www.carrona.org/drivers/driver.php?id=SCDEmu.SYS
http://www.carrona.org/drivers/driver.php?id=tap0901.sys
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
http://www.carrona.org/drivers/driver.php?id=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=iaStorA.sys
http://www.carrona.org/drivers/driver.php?id=dc3d.sys
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
WirelessKeyboardFilter.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=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=VBoxDD2R0.r0
http://www.carrona.org/drivers/driver.php?id=VBoxNetAdp6.sys
http://www.carrona.org/drivers/driver.php?id=VBoxNetLwf.sys
http://www.carrona.org/drivers/driver.php?id=VBoxUSBMon.sys
http://www.carrona.org/drivers/driver.php?id=VBoxDDR0.r0
http://www.carrona.org/drivers/driver.php?id=VMMR0.r0
http://www.carrona.org/drivers/driver.php?id=VBoxDrv.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.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 Frottery

Frottery
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:40 PM

Posted 09 June 2016 - 09:41 PM

Thanks for the reply,

 

I've updated all motherboard specific drivers, updated my graphics driver but for some reason it would only display 2 of my 3 screen so I rolled back the the version before the latest and now it works. Also updated the three you posted and updated windows to the latest patch. I've attached the EventViewer report.

 

Also ran memtest and the hdd test and no errors came up.

 

I've been running hwmonitor since i built the machine and all the temps seem fine, CPU sits ~60-65 c under full load with p95. The GPU 2 gets hot and runs at ~85c under load but GPU 1 which the monitors are hooked up to runs at ~65-70c under load.

 

Haven't run driver verifier as I'm at work but will post the results ASAP.

 

EDIT:

 

I delete duplicate drivers that keep showing up for my monitors but they get reinstalled when I reboot the computer, is this normal? Not sure if erasing this stabilises the machine but I haven't been getting the BSOD on sessions where i delete the extras, it's hard to tell if this is the cause because the BSOD is so sporadic anyway. This makes me think that it might be that my GPU is dying :(

 

Cheers,

Elliott

Attached Files


Edited by Frottery, 09 June 2016 - 11:22 PM.


#4 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:40 AM

Posted 10 June 2016 - 05:10 AM

I wouldn't suggest deleting drivers (and, as you've seen, it doesn't do any good anyway).

This is normal, and is a part of the protection built into Windows.

Why are you deleting them?  How do you know that they're duplicates?

 

An overheating GPU is an overheating GPU - no matter what it's hooked up to.

If you're not using the one that's overheating, please physically remove it form the system to see that helps.

 

I'm late for work, but will try to get back to this either this afternnon (UTC-5, east coast of the US) or in the early morning.

Good luck!


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.

#5 RoCC

RoCC

  • Members
  • 1 posts
  • OFFLINE
  •  
  • Local time:10:40 AM

Posted 10 June 2016 - 06:15 AM

I started to have the exact same problem a few days ago without having ever tried to overclock or something. Rig is 3 months old and so is my i6600k.

Booting into Windows left me with a BSOD "clock_watchdog_timeout" or "whea_uncorrectable_error" after 10-60 seconds after logging on.

Google results indicated that in most cases this behavior is connected to the CPU.

 

 

In my machine it is clearly connected to a faulty CPU core.

Try to set the number of active CPU cores in your BIOS to "1" and boot into Windows. For me that worked flawlessly.

Then set it to "2" and so on and try each time to run Windows and maybe start a run with Intel Processor Diagnostic Utility.

 

In my case it is core 2 which is faulty.



#6 Frottery

Frottery
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:40 PM

Posted 10 June 2016 - 07:31 AM

I'll have to try that out, I'm currently running the driver verifier so I'll let the system run for a while and then try that out. I ran the diagnostic before and it passed but I'll try it again with cores blocked out.

 

Cheers



#7 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:40 AM

Posted 10 June 2016 - 03:52 PM

Not much info from the Admin log file (as I expected)

It does let us know that the system can't produce minidumps from the full memory dumps.

 

Have you run the rest of the hardware diagnostics?

If so, what were the results?  Theres several tests for video on that page.

 

We'll also be waiting for the results of Driver Verifier.
If it doesn't create a minidump, then we'll have to look at the MEMORY.dmp file in C:\Windows (it gets replaced after each SSOD).


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.

#8 Frottery

Frottery
  • Topic Starter

  • Members
  • 4 posts
  • OFFLINE
  •  
  • Local time:06:40 PM

Posted 12 June 2016 - 05:05 AM

FYI I've reinstalled windows as of now, my LAN stopped working all together and audio was doing funny things and i need my computer to work so i reinstalled. I've run chkdsk on both my hard drives and they both came up clean. If I'm getting BSOD still after tomorrow I'll run the driver verifier for another extended period (ran for ~24 hrs but there were no crashes) and run the full suite on hardware stress tests.

 

Ran furmark for an hour or so and there were no crashes from it even with both cards plugged in, is there a recommended time to run this for?

 

Cheers



#9 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,090 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:04:40 AM

Posted 12 June 2016 - 06:15 AM

At times a clean reinstall is the easiest/quickest fix.

chkdsk is a check of the file system on the hard drive, not a test of the hard drive itself.

 

The Furmark test should be run long enough to see the temperatures level out and stay stable.

If the system doesn't have a temp sensor on the video card, then we let it run for a while to see if problems happen.

If you run into any other problems, then we start looking at the video card(s)


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.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users