Windows 10: Brand new Build. BSod CLock_Watchdog_Timeout and Freezes.

I spent all weekend building up a new computer:
CPU: Intel Core i7-6700K 4.0GHz Quad-Core Processor
CPU Cooler: NZXT Kraken X41 106.1 CFM Liquid CPU Cooler
Motherboard: Gigabyte GA-Z170X-Gaming 7 ATX LGA1151 Motherboard
Memory: G.Skill Ripjaws V Series 32GB (4 x 8GB) DDR4-2400 Memory
Storage: Western Digital BLACK SERIES 4TB 3.5" 7200RPM Internal Hard Drive
Storage: Western Digital BLACK SERIES 4TB 3.5" 7200RPM Internal Hard Drive
Storage: Crucial MX200 250GB
Storage: Crucial MX200 500GB
Video Card: EVGA GeForce GTX 750 Ti 2GB Superclocked Video Card
Case: Fractal Design Define R5 w/Window (Black) ATX Mid Tower Case
Power Supply: SeaSonic 650W 80+ Gold Certified Semi-Modular ATX Power Supply
Monitor: Dell P2715Q 60Hz 27.0" Monitor

Build went fine. Bios looked fine. installed OS, went fine.
installed newest online drivers
added a WD green 3TB drive form my exitsing PC with data - Started migrating large amounts of data and got a couple freezes.
Once data was transferred everything seemed OK
Browsing online - nothing CPU intensive and got BSoD with the clock_watchdog_timeout error
started getting random freezes and the same cwt BSod here and there.

Loaded Adobe Lightroom 6 and tried to process a photo. Within 30 seconds of entering in develop module I get either a complete freeze or the BSoD clock watchdog error.

Talked to a friend at MS who said all she could find on that error was that it was possibly hardware related.

Looking for some help please.

Thanks!

:)

 

BSOD / FREEZE Problems with WINDOWS 10

DISCUSSION: The following is recent BSOD/FREEZE occurances. I'm not interested in finding the cause of each one, but rather, when is Microsoft/AMD/et al going to upgrade Windows 10 and/or AMD
drivers to better handle interrupts and multiple threads.

Configuration: HP 500-314 Computer with: Windows 10 (64 bit), Processor: AMD A8-7600 [Radeon R7 Graphics, 10 Compute Cores (4C + 6G), 3100 MHz, 2 Core(s), 4 Logical Processor(s)], 8 GB Memory,
2 TB HD, 500 GB External HD (Iomega).

RECENT BSOD/FREEZE OCCURANCES:

31.Dec.2015: 03:45:00 AM : TWC_Online : BLACKSCREEN, Auto-Restart : c:/Windows : NO Minidump; Logs: dosvc, WindowsUpdate :
10.Jan.2016: 4:32 AM : FREEZE while watching CBS 'Blue Bloods' on TWC_Online. Hard Power-Off required to restart computer :

21.Jan.2016: 1:13 PM: Watching “The Blaze” live broadcast: BSOD (CLOCK_WATCHDOG_TIMEOUT) with NO Auto-Restart. Hard Power-Off to Restart :

23.Jan.2016: 4:17 AM: Watching TWC Online: FNC : Freeze, then BSOD (CLOCK_WATCHDOG_TIMEOUT) : waited 10 minutes: with NO Auto-Restart. Hard Power-Off to Restart :

4.Feb.2016: 5:25 AM: BSOD [THREAD_STUCK_IN_DEVICE_DRIVER] w/Auto-Restart: while watching TWC_Online (Channel 37) :

20.Feb.2016: 7:55 PM: three + hours into Defender Full Scan: BSOD [CLOCK_WATCHDOG_TIMEOUT] :

21.Feb.2016: 1:35 AM: BSOD [CLOCK_WATCHDOG_TIMEOUT] w/ NO Auto-Restart: while watching TWC_Online (Channel 37) :

21.Feb.2016: 12:23 PM: BSOD [THREAD_STUCK_IN_DEVICE_DRIVER] w/Auto-Restart: while watching TWC_Online (AMC) :

22.Feb.2016: 3:25 AM: FREEZE while watching TWC (Billions) :

2.Mar.2016: 6:52 AM: BSOD [THREAD_STUCK_IN_DEVICE_DRIVER]. Preceeded by: deletion of several files from File Explorer “Quick Access” list, then attempt to access TWC_Online via desktop shortcut. :

 

Freezing and BSOD Clock_Watchdog_Timeout

Clock Watchdog timeout is usually a Processor error but rarely faulty drivers or overclocking can be a cause too.

If you are overclocking STOP.

Run a Prime95 CPU test:

Prime95 - Stress Test Your CPU

Also enable verifier to check if any driver is misbehaving:

Driver Verifier-- tracking down a mis-behaving driver.

Upload the newer dumps when you get Driver_Verifier_detected_voilation

 

Hi nosamk,

Welcome to the 10forums.

It seems your system has sometimes problems with generating a minidump from the memory dump.
Please try following:

• Open an admin command prompt
• Copy/paste "sfc/scannow" (without quotes) and press enter
• When it finished reboot your system
• Open again an admin command prompt
• Enter sfc/scannow again

If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
Code: Event[2362]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2015-10-12T17:27:07.000 Event ID: 1005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: DESKTOP-AVDU8OD Description: Unable to produce a minidump file from the full dump file.[/quote] If the Sound Blaster Recon3Di device is a headset, please disable every other sound device in sound manager (search sound).
The program is causing lots of trouble, code below is just 1 error of the several errors.
Code: 10/13/2015 2:01 AM Application Error Faulting application name: CtHdaSvc.exe, version: 6.0.101.1042, time stamp: 0x55892600 Faulting module name: CtHdaSvc.exe, version: 6.0.101.1042, time stamp: 0x55892600 Exception code: 0xc0000005 Fault offset: 0x0000367b Faulting process id: 0x1ec Faulting application start time: 0x01d1055b1689f6ac Faulting application path: C:\Windows\sysWow64\CtHdaSvc.exe Faulting module path: C:\Windows\sysWow64\CtHdaSvc.exe Report Id: 570a3e86-9e04-4b00-9d8c-a1f2bb3315d5 Faulting package full name: Faulting package-relative application ID:[/quote]

 

Thanks axe. I'm running memtest currently. on 5th pass 16+ hours - trying to get to 8. I'll try this when its complete

 

Can you explain why you are running memtest?
What memtest are you running?

 

found another thread on here with some getting random freezes and one of the suggestions was to run it.

memtest86+ 5.01

 

There is a problem with BSOD's, freezes and crashes, there are many causes for them, what for another solves the problem doesn't have to solve it for you and sometimes makes it only worse.

I will check the dump now as I couldn't do it earlier due to internet problems.
The internet speed at school isn't as good as home.

 

OK. I'll kill the test and run the sfc/scannow

 

Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

 

Ran sfc/scannow twice. both results were "Windows Resource Protection did not find any integrity violations"

also. soundblaster recon is not a headset

 

restarting now running driver verifer as instructed

 

nothing really seems to be happening. Should I be actively using the computer or just letting it sit?

 

It is better to not activily use your pc, it could suddenly dramatically slow down in performance due to the stressed drivers.

 

Still nothing.

Should I open Lightroom and develop? That seemed to cause a crash everytime