BSOD CLOCK_WATCHDOG_TIMEOUT on New PC Build

Page 7 of 8 FirstFirst ... 5678 LastLast

  1. Posts : 38,419
    windows 10 professional version 1607 build 14393.969 64 bit
       #61

    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
      My Computer

  2. Spectrum's Avatar
    Posts : 546
    seL4
       #62

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


  3. Posts : 50
    Windows 10
    Thread Starter
       #63

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

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


  4. Posts : 50
    Windows 10
    Thread Starter
       #64

    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?


    Attachment 150781
    Last edited by heyjaso; 28 Aug 2017 at 11:31.
      My Computer


  5. Posts : 50
    Windows 10
    Thread Starter
       #65

    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?

    Attachment 150803
      My Computer


  6. Posts : 38,419
    windows 10 professional version 1607 build 14393.969 64 bit
       #66

    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.
      My Computer


  7. Posts : 50
    Windows 10
    Thread Starter
       #67

    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 :)

    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.
      My Computer


  8. Posts : 38,419
    windows 10 professional version 1607 build 14393.969 64 bit
       #68

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


  9. Posts : 50
    Windows 10
    Thread Starter
       #69

    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

      My Computer


  10. Posts : 50
    Windows 10
    Thread Starter
       #70

    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
      My Computer


 
Page 7 of 8 FirstFirst ... 5678 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 04:36.
Find Us




Windows 10 Forums