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.
Attachment 154192
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
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: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.
Last edited by zbook; 19 Sep 2017 at 23:57.
"The DM log collector last mini dump file was 8/27/2017.
The memory dump was partially corrupt and could not be debugged."
Any guesses as to why these two things are happening and/or what I can do to get proper dumps?
"Are you using: Intel® System Support Utility for Windows
What Intel hardware / software are you using?"
My CPU is an Intel i7-7700k.
For software, I have the Intel Processor Diagnostic Tool installed (PASSED), as well as the Intel Extreme Tuning Utility. These were recommended previously to check the CPU and make sure there is no overclock (there isn't.) Would you like me to install the Intel System Support Utility?
Since the crash last night there have been three further crashes this morning. I don't know if it's worth posting the minidump and memory.dmp file if it will still be outdated information? I will say that when the crashes happen, they seem to happen in swarms. No crashes for awhile, then a number of crashes in succession over a day or so.
Last edited by heyjaso; 20 Sep 2017 at 08:09.
Whenever there is a bsod please post a new zip:
BSOD - Posting Instructions - Windows 10 Forums
Earlier in the thread the memory dump was partially corrupt and it has happened again. Using Ccleaner clean the memory dump. Then using Whocrashed perform a crash dump test. Post the whocrashed results into the thread. And post a new zip.
Download and install Bluescreenview: Blue screen of death (STOP error) information in dump files.
Uninstall the Intel software that was the faulting application in post #23 and #74.
Review what was done with Prime95.
What was the duration of testing?
What was the maximum temperature?
Plan to stress test GPU and repeat Prime95:
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
FurMark - GPU Stress Test Windows 10 Performance Maintenance Tutorials
Just in case this is useful to someone in the future, I was able to resolve this issue. After doing a clean install of the system and having the error continue to occur, I performed a warranty replacement with Intel for the CPU. Put the new CPU in and the system has been running perfectly ever since. Thanks for the help in trying to diagnose this!
Quote