New
#21
Try and switch to an active dump.
BSOD CLOCK_WATCHDOG_TIMEOUT on New PC Build
-
-
New #22
-
New #23
There is an Intel application/driver that is a recurrent faulting application:
IntelCpHDCPSvc Intel Content Protection HDCP Service
It has been creating minidumps.
In the logs I see a Nvidia graphics driver. Does your computer only have Nvidia graphics or are there hybrid Intel graphics?
1) Download and install Whocrashed: http://www.resplendence.com/whocrashed
2) In system control panel > advanced system settings > startup and recovery > un-check automatic restart so that you have time to view the bsod window. Sometimes it is helpful to be able to view the stop code or view the misbehaving driver. If you see the stop code and don't have a mini dump created you will then have useful information.
3) Open Whocrashed > in the left upper corner click analyze > post the results into the thread.
4) Above analyze click tools > crash dump test > type: ACCEPT > post results into the thread
5) after the above steps post a brand new zip file into the thread:
BSOD Crashes and Debugging - Windows 10 Forums
The best way to fix the misbehaving Nvidia driver is to uninstall everything Nvidia using Display driver uninstaller and install new drivers from the computer manufacturer's website or from the Nvidia website.
The computer manufacturer's web site is preferred. Enter the computer's serial or product number and the operating system to view available drivers.
If you use the Nvidia web site be sure the "clean install" box is checked and only install the graphics driver and the physx driver.
Official Display Driver Uninstaller DDU Download
Display Driver Uninstaller Download version 17.0.7.2
Display Driver Uninstaller: How to use - Windows 7 Help Forums
NVIDIA
Code:8/17/2017 12:48 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: 0xbd4 Faulting application start time: 0x01d316fa2763e8de 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: 3e17ec16-846a-453b-beee-e19492a4fe14 Faulting package full name: Faulting package-relative application ID: 8/17/2017 12:48 PM Windows Error Reporting Fault bucket 120568863720, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: IntelCpHDCPSvc.exe P2: 1.0.0.1 P3: 57f81a3e P4: IntelCpHDCPSvc.exe P5: 1.0.0.1 P6: 57f81a3e P7: c0000005 P8: 000000000000347f P9: P10: Attached files: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_IntelCpHDCPSvc.e_17caa9aedfc3c4d8af6e3058443fa15fcb71_1485d419_cab_16797935\minidump.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7898.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7898.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER78A9.tmp.txt \\?\C:\Windows\Temp\WER78AA.tmp.appcompat.txt C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_IntelCpHDCPSvc.e_17caa9aedfc3c4d8af6e3058443fa15fcb71_1485d419_cab_16797935\memory.hdmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_IntelCpHDCPSvc.e_17caa9aedfc3c4d8af6e3058443fa15fcb71_1485d419_25418f6c Analysis symbol: Rechecking for solution: 0 Report Id: 3e17ec16-846a-453b-beee-e19492a4fe14 Report Status: 268435456 Hashed bucket: a986a2ffcdf7da4001964044dedc4e57 8/17/2017 12:48 PM Windows Error Reporting Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: IntelCpHDCPSvc.exe P2: 1.0.0.1 P3: 57f81a3e P4: IntelCpHDCPSvc.exe P5: 1.0.0.1 P6: 57f81a3e P7: c0000005 P8: 000000000000347f P9: P10: Attached files: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_IntelCpHDCPSvc.e_17caa9aedfc3c4d8af6e3058443fa15fcb71_1485d419_cab_16797935\minidump.mdmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7898.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7898.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER78A9.tmp.txt \\?\C:\Windows\Temp\WER78AA.tmp.appcompat.txt C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_IntelCpHDCPSvc.e_17caa9aedfc3c4d8af6e3058443fa15fcb71_1485d419_cab_16797935\memory.hdmp These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_IntelCpHDCPSvc.e_17caa9aedfc3c4d8af6e3058443fa15fcb71_1485d419_cab_16797935 Analysis symbol: Rechecking for solution: 0 Report Id: 3e17ec16-846a-453b-beee-e19492a4fe14 Report Status: 4 Hashed bucket:
Code:Event[942]: Log Name: System Source: Service Control Manager Date: 2017-07-22T21:10:22.043 Event ID: 7045 Task: N/A Level: Information Opcode: N/A Keyword: Classic User: S-1-5-18 User Name: NT AUTHORITY\SYSTEM Computer: ENDICOTT-PC Description: A service was installed in the system. Service Name: Intel(R) Content Protection HDCP Service Service File Name: %SystemRoot%\System32\DriverStore\FileRepository\igdlh64.inf_amd64_0745f11ce6fc197c\IntelCpHDCPSvc.exe Service Type: user mode service Service Start Type: auto start Service Account: LocalSystem
On 7/22/2017 the Nvidia graphics driver was a faulting application:
Code:7/22/2017 11:05 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 5575c39d-03a9-4677-82ca-b75dec0f0361 Problem signature: P1: 141 P2: ffffc7043376f010 P3: fffff80b9096fb28 P4: 0 P5: 2b6c P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170722-1759.dmp \\?\C:\Windows\Temp\WER-8822875-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA404.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA406.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERA417.tmp.txt \\?\C:\Windows\Temp\WERFAD2.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_3d56ecbfd7be2527d1a82c517839f95196b3c11_00000000_cab_0852fbea Analysis symbol: Rechecking for solution: 0 Report Id: b6365a34-89ad-4127-b883-234d7da3ce35 Report Status: 268435456 Hashed bucket:7/22/2017 10:59 PM Windows Error Reporting Fault bucket LKD_0x141_Tdr:6_IMAGE_nvlddmkm.sys_Pascal_3D, type 0 Event Name: LiveKernelEvent Response: Not available Cab Id: 06c5fc52-6829-4a4e-9e9e-9a1e473c4e47 Problem signature: P1: 141 P2: ffffc7043376f010 P3: fffff80b9096fb28 P4: 0 P5: 2b6c P6: 10_0_15063 P7: 0_0 P8: 256_1 P9: P10: Attached files: \\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20170722-1759.dmp \\?\C:\Windows\Temp\WER-8818500-0.sysdata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94C2.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94C2.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER94D2.tmp.txt \\?\C:\Windows\Temp\WERB357.tmp.WERDataCollectionStatus.txt These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_3d56ecbfd7be2527d1a82c517839f95196b3c11_00000000_cab_0c0ab46f Analysis symbol: Rechecking for solution: 0 Report Id: 469c93c0-941c-46f9-bb5c-f3a4e63eb696 Report Status: 268435456 Hashed bucket:
-
New #24
-
New #25
The Intel application driver I have not yet figured out its function and was wondering if it were related to graphics.
In one of the Intel threads they suggested uninstalling the Intel graphics driver (IntelCpHDCPSvc.exe stops working every time I b... |Intel Communities) but I did not see that in the computer specs yet.
The Nvidia graphics had produced a Watchdog dump. If you had replaced this driver between 7/22 and today then there is no need to replace it as there has been no recurrent dump. If you had not replaced the driver since 7/22 then you can replace it with the steps above.
1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /restorehealth
4) chkdsk /scan
5) powercfg.exe /hibernate off
6) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread
7) open file explorer > this PC > local disk c: > in the right upper corner search type: C:\WINDOWS\MEMORY.DMP
8) using one drive or drop box please post a share link with the memory.dmp file
Code:Windows failed fast startup with error status 0xC00000D4.
Code:Windows failed to resume from hibernate with error status 0xC0000411.
Code:Event[3051]: Log Name: System Source: volmgr Date: 2017-08-13T17:02:05.036 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ENDICOTT-PC Description: Dump file creation failed due to error during dump creation.
Code:Event[3170]: Log Name: System Source: volmgr Date: 2017-08-14T07:59:16.052 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ENDICOTT-PC Description: Dump file creation failed due to error during dump creation.
Code:Event[3460]: Log Name: System Source: volmgr Date: 2017-08-16T20:39:31.895 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ENDICOTT-PC Description: Dump file creation failed due to error during dump creation.
Code:Event[3510]: Log Name: System Source: volmgr Date: 2017-08-16T20:42:55.208 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ENDICOTT-PC Description: Dump file creation failed due to error during dump creation.
Code:Event[3908]: Log Name: System Source: volmgr Date: 2017-08-21T17:22:37.817 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ENDICOTT-PC Description: Dump file creation failed due to error during dump creation.
Code:Event[3959]: Log Name: System Source: volmgr Date: 2017-08-21T17:25:30.849 Event ID: 161 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: ENDICOTT-PC Description: Dump file creation failed due to error during dump creation.
Code:Event[3986]: Log Name: System Source: Microsoft-Windows-WER-SystemErrorReporting Date: 2017-08-21T17:25:34.896 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, 0xffffd700eeac0180, 0x0000000000000006). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.
-
New #26
-
New #27
For the memtest86+ version 5.01
Please make at least 8 or more runs.
The more runs the better.
The testing is not run by time but by passes.
There is a significant incidence of false negatives if fewer than 8 passes are made.
A false negative is a pass when there is malfunctioning RAM.
Just 1 error is a fail and you can abort testing.
Then test 1 RAM module at a time in the same DIMM.
https://answers.microsoft.com/en-us/windows/wiki/windows_10-update/memory-problems/21c3f63f-f570-4522-b2ef-ecc7b7ff6461
https://www.tenforums.com/tutorials/14201-memtest86-test-ram.html
When Memtest86+ version 5.01 has completed 8 or more passes please use a camera or smart phone camera to take a picture and then post an image into the thread.
The information that you had entered for the computer is displaying 8 GB RAM. The information in the logs is displaying 16 GB RAM.
Computer Type: PC/Desktop
OS: Windows 10
CPU: i7-7700k
Motherboard: GIGABYTE GA-Z270-HD3P
Memory: CORSAIR - Vengeance LPX 2-Pack 8GB DDR4 DRAM
Graphics Card: GIGABYTE GeForce GTX 1070 DirectX 12 GV-N1070WF2OC-8GD 8GB
Please update the computer specs:
How To Fill Out Your System Specs
How To Fill Out Your System Specs
System Specs - Fill in at Ten Forums:
System Specs - Fill in at Ten Forums Windows 10 General Tips Tutorials
In the left corner below in your post you find 'My System Specs'.
After clicking it you can find a link a little below that says 'Update your System Spec', click on this link to get to the page where you can fill in your system specs.
System Info - See Your System Specs - Windows 7 Help Forums
In addition to the information in the links please add the following information to the system specs:
PSU, cooler, case, peripherals (mouse, keyboard, joystick)
Also enter information about anything attached to the computer (wired or wireless) printer, xbox etc.
-
New #28
-
-
New #29
Memtest completed 8 passes without any errors.
Attachment 150680
-
New #30
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
Quote
Related Discussions
