Windows 10: BSOD CLOCK_WATCHDOG_TIMEOUT on New PC Build

Memtest completed 8 passes without any errors.

 

Here is the info from the WhoCrashed analysis:

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

Crash dumps are enabled on your computer.

On Sat 8/26/2017 12:49:12 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\082617-4171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFA50194347180, 0x7)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 8/26/2017 9:50:07 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\082617-4437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFA980F04C0180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 8/21/2017 9:59:12 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFF9900A8AD9180)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFF9900A8AD9180, 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

 

zbook asked: "In the logs I see a Nvidia graphics driver. Does your computer only have Nvidia graphics or are there hybrid Intel graphics?"

So, there are both. When I first built the system I did not yet have the NVIDIA graphics card, so it was using integrated graphics for a few days. When I got the NVIDIA card, I installed it and installed the NVIDIA drivers.

 

Reading the Display Driver Uninstaller instructions and about to perform that next.

Actually, as I re-read your responses, you're saying if I have updated the NVIDIA drivers since July 22nd I don't need to perform this step? I definitely have done that.

 

sfc /scannow seems stuck at verification 39 percent complete for the last 10 minutes or so.

 

Second time running sfc /scannow it worked fine. Here are the results:

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.


C:\WINDOWS\system32>sfc /scannow


Beginning system scan. This process will take some time.


Beginning verification phase of system scan.
Verification 100% complete.


Windows Resource Protection did not find any integrity violations.


C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth


Deployment Image Servicing and Management tool
Version: 10.0.15063.0


Image Version: 10.0.15063.0


[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.


C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is C Drive.


Stage 1: Examining basic file system structure ...
317440 file records processed.
File verification completed.
7542 large file records processed.
0 bad file records processed.


Stage 2: Examining file name linkage ...
388698 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.


Stage 3: Examining security descriptors ...
Security descriptor verification completed.
35630 data files processed.
CHKDSK is verifying Usn Journal...
40307496 USN bytes processed.
Usn Journal verification completed.


Windows has scanned the file system and found no problems.
No further action is required.


487806975 KB total disk space.
146637116 KB in 168901 files.
118568 KB in 35631 indexes.
0 KB in bad sectors.
441655 KB in use by the system.
65536 KB occupied by the log file.
340609636 KB available on disk.


4096 bytes in each allocation unit.
121951743 total allocation units on disk.
85152409 allocation units available on disk.


C:\WINDOWS\system32>powercfg.exe /hibernate off


C:\WINDOWS\system32>

 

zbook you asked for the memory.dmp file. I posted this previously and in checking the file currently in c:/Windows/MEMORY.DMP it looks like the exact same as the one I posted before, modified 6 days ago (same day and time as the last one I posted.) Here's the link to the one I posted before:

MEMORY.DMP - Google Drive

Would you still like me to upload a new version of it?

 

The prior version of the memory dump had corruption.

1) Please post a new version of the kernel memory dump file.

2) Make sure that there is no over clocking while troubleshooting.

Sometimes there are problems in the bios that produce bsod.

3) To ensure that there are no improper bios settings please reset the bios.

Sometimes there can be failure to boot after resetting the bios.

4) So please make sure your files are backed up.

5) Please make a backup image with Macrium:

Macrium Software | Macrium Reflect Free:

Macrium Software | Your Image is Everything

Place the backup image on another drive or in a cloud application.

6) Please create a brand new restore point.

How to Clear Your Computers CMOS to Reset BIOS Settings:
How to Clear Your Computers CMOS to Reset BIOS Settings

3 Ways to Reset Your BIOS - wikiHow:
3 Ways to Reset Your BIOS - wikiHow

7) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:

Speccy - Free Download - Piriform: Speccy - System Information - Free Download


HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID


SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer


1) download and install the Intel Processor Diagnostic Tool
When the test completes please use the Microsoft snipping tool to post an image into the thread.


Download Intel® Processor Diagnostic Tool: Download Intel® Processor Diagnostic Tool
The Intel® Processor Diagnostic Tool: The Intel® Processor Diagnostic Tool

 

Here's a newly uploaded copy of the MEMORY.DMP file.

MEMORY.DMP - Google Drive

 

Haven't reset CMOS yet but ran the Intel Processor Diagnostic Tool. Result: Pass

 

open file explorer > this PC > local c: drive > search for
%SystemRoot%\MEMORY.DMP
C:\Windows\MEMORY.DMP

For the memory dump file please rename it to memory.old.dmp

Download and install whocrashed: Resplendence Software - WhoCrashed, automatic crash dump analyzer

In the left upper corner above ananlyze click tools > crash dump test > type ACCEPT >

After the crash dump > click analyze > post result into the thread

Use file explorer to find the memory.dmp and post a share link into the thread.


After resetting the bios and posting the new memory.dmp file please read the following information carefully.
It is very important to read the warning on temperature monitoring before performing this test.

Again please reset the bios before performing this test.

And again make sure that there is no over clocking.

Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials


Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials


Please use the Microsoft snipping tool to post images into the thread.


Take Screenshot in Windows 10 Windows 10 General Tips Tutorials



Code: ************* Symbol Path validation summary **************Response Time (ms) Location Deferred SRV*C:\SymCache*Symbol information Symbol search path is: SRV*C:\SymCache*Symbol information Executable search path is: ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** No module list information. Delay kernel load. ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** KdDebuggerData.KernBase < SystemRangeStart Windows 8 Kernel Version 15063 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x00000000`00000000 PsLoadedModuleList = 0xfffff803`449e15c0 Debug session time: Mon Aug 21 21:59:12.223 2017 (UTC - 5:00) System Uptime: 0 days 3:28:46.546 ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** No module list information. Delay kernel load. ************************************************************************** THIS DUMP FILE IS PARTIALLY CORRUPT. KdDebuggerDataBlock is not present or unreadable. ************************************************************************** KdDebuggerData.KernBase < SystemRangeStart Loading Kernel Symbols No module list information. Delay kernel load. GetContextState failed, 0x80004002 CS descriptor lookup failed GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get program counter GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 101, {18, 0, ffff9900a8ad9180, 6} GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057. GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 ReadControl failed - kernel symbols must be loaded first ReadControl failed - kernel symbols must be loaded first ReadControl failed - kernel symbols must be loaded first GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 Unable to get current machine context, HRESULT 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002 GetContextState failed, 0x80004002[/quote]

 

Belowis the crash dump result from WhoCrashed. I am currently uploading the new MEMORY.DMP, it is almost 3 GB in size.

Next will be the CMOS reset. And then Prime95 test.

Re: overclocking, I have not made any changes to set any overclocking anywhere. BIOS was set to load defaults earlier today. Apart from that, what can I be checking to see if anything is overclocked perhaps by default?




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

Crash dumps are enabled on your computer.



On Sun 8/27/2017 4:53:37 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\082717-4218-01.dmp
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x199D6B5F, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.



On Sun 8/27/2017 4:53:37 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x199D6B5F, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\WINDOWS\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.



On Sat 8/26/2017 12:49:12 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\082617-4171-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFA50194347180, 0x7)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Sat 8/26/2017 9:50:07 AM your computer crashed
crash dump file: C:\WINDOWS\Minidump\082617-4437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C560)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFA980F04C0180, 0x6)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
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).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.




Conclusion
4 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

 

The memory dump file should be small or not exist as you just renamed it.
The system control panel was not yet modified to save to memory.dmp so it should be empty.
So having it so large already is puzzling.

Please post an image of the search results for each memory.dmp and memory.old.dmp

Download and install either of these and post images of the tabs into the thread:

CPU-Z | Softwares | CPUID: CPU-Z | Softwares | CPUID
HWinfo diagnostic software: HWiNFO - Download

 

It is strange, I know, but I did do just as you asked. Both are listed in C:\Windows\

 

download and install ccleaner: (use the free edition)
CCleaner - Free Download or try CCleaner Professional - Piriform

Do not use the registry cleaner portion of ccleaner.

View the windows tab scroll to system > make sure that memory dumps is checked.

View the tabs for ccleaner and scroll through all of the settings and make sure that you un-check whatever you do not want cleaned.
Then run ccleaner to clean the memory dump file

Once you have ran ccleaner to clean the memory dump file please use file explorer again and post images of the search results