Windows 10: BSOD CLOCK_WATCHDOG_TIMEOUT on New PC Build

But a quick note to say THANK YOU for all your help as we go through this, zbook and Spectrum. You guys are excellent.

 

You'r welcome,
Reset bios first. Then prime95.
Confirm that memory dumps are working with whocrashed and file explorer.
Please post these into the thread:
whocrashed results for test dump
file explorer to view the size of the memory dump
memory dump share link
new zip file
BSOD - Posting Instructions - Windows 10 Forums

Depending on the results of the prime95 plan to use windows driver verifier. Read these links when you have time:
Microsoft Community
Enable and Disable Driver Verifier in Windows 10 Windows 10 Performance Maintenance Tutorials

 

How frequently are you getting bugchecks that are not caused by Whocrashed? The dump you just uploaded was a forced crash by WhoCrashed.

 

Last crash was yesterday, but to be honest I have not been on the computer that much except to diagnose the crashes. *Smile

 

I'm getting started on the Prime95 test but one think I couldn't answer for myself with any certainty was whether or not the system was overclocked (you had asked me to make sure it was not.) I installed the Intel Extreme Tuning Utility not to overclock but to see what it could tell me about the current state of the system in a way that I could understand. Here is a snapshot of the the Basic screen without me having touched anything. Is there anything in here I should change?

 

I started the Prime95 test but got skittish after a couple of minutes when I saw temps around 90C. See attached. Is there a recommended temperature for my i7-7700k where if it gets there, I should stop testing?

Edited to add that Googling tells me that some temps under stress on this CPU can get up to around 100C so maybe I shouldn't be so concerned?

 

The temperature threshold per this link is 80 degrees C:

I7-7700k safe temps - [Solved] - CPUs - Toms Hardware

It's possible that there are multiple sources so whatever you have found please post into the link.

Ideal testing is > or = to 3 hours.
The minimum is 45 minutes.
The longer the test the better the testing conditions and the more useful the results.

 

I saw this thread stating that max is 100C.

I7 7700k safe temps - [Solved] - CPUs - Toms Hardware

This one mentions typical operating ranges at 80-85C getting hot, but Prime95 is certainly not a normal temp range *Smile

Safe 100% Usage temps for 7700k - [Solved] - Overclocking

Overall I think it will be okay at 90C (max I saw in my test) for awhile, with a close eye on it.

 

Okay.
If there are bsod using prime 95 we will debug them.

 

After running for several days with no crashes, just experienced another CLOCK_WATCHDOG_TIMEOUT BSOD while browsing Youtube.

Link to the compressed ZIP is here (3.8GB compressed to 42megs?! Is that even possible?)

Memory Dump 9-2.zip - Google Drive


The Whocrashed analysis says:

On Sat 9/2/2017 9:09:22 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFE70077D59180)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFE70077D59180, 0x7)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT

 

Another crash, five minutes after that last post, doing the same thing (Youtube). Link to the memory.dmp at:

Second Crash 9-2.zip - Google Drive

Whocrashed analysis doesn't look like it changed from the last time I ran it, but I did analyze after this crash as well:

On Sat 9/2/2017 9:09:22 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFE70077D59180)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFE70077D59180, 0x7)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT

 

Two more crashes just occurred, one happened while writing a post about another! The new crashes do not seem to be reporting into Whocrashed.

Also the MEMORY.DMP file seems to be unchanged as well.

One thing I noticed- on the BSOD itself, the percent complete never seems to move. Stays at zero percent even after waiting up to 10 minutes. Is that related all to the lack of dump updates?

 

Whenever you have a bsod please post a new zip:

BSOD - Posting Instructions - Windows 10 Forums

If you can also post a new memory.dmp

 

It has been awhile but I had the same crash happen again tonight. Attached is the ZIP from the DM Log Collector Tool.

ENDICOTT-PC-Tue_09_19_2017_225619_62.zip

Also, here is a link to the MEMORY.DMP file.

MEMORY.zip - Google Drive

Here is the WhoCrashed analysis:

Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

You have performed a crash dump test. The test succeeded and the crash dump file was properly written out.

On Tue 9/19/2017 10:52:54 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFF9C00148B6180)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFF9C00148B6180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might also be caused because of overheating (thermal issue).
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT

 

The DM log collector last mini dump file was 8/27/2017.
The memory dump was partially corrupt and could not be debugged.

Code: **************************************************************************THIS DUMP FILE IS PARTIALLY CORRUPT.KdDebuggerDataBlock is not present or unreadable.************************************************************************** BugCheck 101, {18, 0, ffff9c00148b6180, 6}GetContextState failed, 0xD0000147Unable to get current machine context, NTSTATUS 0xC0000147***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057[/quote]
Are you using: Intel® System Support Utility for Windows
What Intel hardware / software are you using?

Code: 9/18/2017 12:20 PM Application Error Faulting application name: IntelCpHDCPSvc.exe, version: 1.0.0.1, time stamp: 0x57f81a3e Faulting module name: IntelCpHDCPSvc.exe, version: 1.0.0.1, time stamp: 0x57f81a3e Exception code: 0xc0000005 Fault offset: 0x000000000000347f Faulting process id: 0xad0 Faulting application start time: 0x01d330566668d7a0 Faulting application path: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_0745f11ce6fc197c\IntelCpHDCPSvc.exe Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\igdlh64.inf_amd64_0745f11ce6fc197c\IntelCpHDCPSvc.exe Report Id: 3ea8596d-3d60-4a54-a8d8-65237422e7f3 Faulting package full name: Faulting package-relative application ID:[/quote] Code: Event[7296]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-09-19T22:53:47.390 Event ID: 1005 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ENDICOTT-PC Description: Unable to produce a minidump file from the full dump file. Event[7297]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-09-19T22:53:47.390 Event ID: 1001 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ENDICOTT-PC Description: The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000018, 0x0000000000000000, 0xffff9c00148b6180, 0x0000000000000006). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.[/quote]