Windows 10: BSOD CLOCK_WATCHDOG_TIMEOUT (101) While playing games Solved

  1.    09 Aug 2018 #1

    BSOD CLOCK_WATCHDOG_TIMEOUT (101) While playing games


    Hello. Im getting this BSOD while playing games, randomly. Most of the time it happens late in the game session. I need to know if its a driver issue or a hardware-overclocking issue. My i7 4770k is at 4.7ghz at 1.29v, but it seems stable, besides Im not getting the typical overclock bsod which is WHEA. The last BSOD was playing Assassins Creed Origins, but it happens with most of the games. Ill attach the required file below.
    Forgot to say that RAM also runs fine, tested on memtest86, no errors.
    BSOD CLOCK_WATCHDOG_TIMEOUT (101) While playing games Attached Files
    Last edited by pathfinder1234; 09 Aug 2018 at 10:17. Reason: Forgot to say that RAM also isnt the error
      My ComputerSystem Spec

  2.    10 Aug 2018 #2

    Hi, please change system language to english and upload a new log collector zip file

    Can you provide us with the kernel memory dump please? Its located in C:\Windows\MEMORY.DMP.
    You can upload it to an cloud service like dropbox or onedrive.
      My ComputerSystem Spec

  3.    16 Aug 2018 #3

    Hello BSODHunter thank you for the answer. I dont seem to find the MEMORY.DMP in Windows Files. It only appears the Minidump folder. Is there an alternative place for the Kernel memory dump to be placed? Thank you.
      My ComputerSystem Spec

  4.    16 Aug 2018 #4

    Please check Windows settings below:
    Configure Windows 10 to Create Minidump on BSOD
    How To Configure Various Dump Files In Windows 10 - YouTube

    If you are using CCleaner or other cleaning tools, deleting of memory dumps should be disabled.
    CCleaner.com - System files
    Alternatively, do not use cleaning tools as long as the problem is not solved.

    After doing this please wait for further crashes and post a new log collector zip.

    Also check for MEMORY.DMP


    And please dont forget to change system language to English before running log collector again:
    Add, Remove, and Change Display Language in Windows 10
    How To Change Language In Windows 10 Operating System - YouTube
      My ComputerSystem Spec

  5.    17 Aug 2018 #5

    Hello. Heres the log collector in english and the dropbox link to the MEMORY.DMP. Ive got 2 BSODS since the post. WHEA 0x124 and CLOCK WATCHDOG 0x101. Ive tried giving more voltage to sistem agent (Memory controller), and more to digital and analog I/O Voltage. Vcore still remains at 1.296v, VRIN At 1.942v and Vring at 1.250v. Ive not touched the uncore, it is on auto. Assassins Creed Origins runs fur a pretty long time before it crashes, so its not an immediate crash, so I feel if I tweak a few more things it will be stable, but I need to know that BSODs are not software related. As Ive said early RAM is not the issue, passes MemTest. Please help me to find what is causing this!

    Dropbox - MEMORY.DMP
    BSOD CLOCK_WATCHDOG_TIMEOUT (101) While playing games Attached Files
      My ComputerSystem Spec

  6.    18 Aug 2018 #6

    In the dumps there is nothing which point to a driver problem (directly). But since the analyzing is never 100 % sure...its only that what "I" found:

    Code:
    0x00000101:    [SPECIAL] CLOCK_WATCHDOG_TIMEOUT (2018-08-18 04:54:51) [Windows 10] 
     
    CAUSED BY:     Unknown_Image     
     
    PROCESS:       Steam.exe
    Code:
    0x00000124:    [SPECIAL] WHEA_UNCORRECTABLE_ERROR (2018-08-17 22:46:40) [Windows 10] 
     
    CAUSED BY:     GenuineIntel_PROCESSOR_MAE     
     
    WHEA Notify:   Machine Check Exception 
         Type:     Micro-Architectural Error 
         Error:    Internal timer (Proc 6 Bank 4) 
     
    PROCESS:       System

    "Internal timer": Internal CPU timer fault. Hardware issue affecting CPUs timing mechanism.

    In your case, a hardware error is very likely. By adjusting and overclocking the system probably does not run so stable.

    What I discovered in windows eventlog are some NVIDIA graphic drivers crashes. Probably owed to the overclocking.
    Code:
    2018-05-31 07:17:55  Warning: Display driver nvlddmkm stopped responding and has successfully recovered:
    2018-05-31 07:29:04  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-06-13 22:40:10  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-06-13 22:51:37  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-06-14 00:33:28  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-06-14 05:48:07  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-06-14 07:06:39  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-06-14 17:06:13  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-06-14 17:31:36  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-07-13 05:21:40  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-07-27 02:19:02  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-07-30 05:03:06  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-07-30 05:47:59  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-07-30 05:50:51  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-07-30 05:56:13  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-07-30 06:06:48  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-07-30 06:16:12  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.   
    2018-08-02 01:12:23  Warning: Display driver nvlddmkm stopped responding and has successfully recovered.

    In general, we do not support overclocked systems here in the forum, as this can lead to inexplicable behavior of the system.
    First and foremost, it makes sense to revert every overclocking, reset the BIOS, reset and remove OC profiles in any OC software. After this u should wait for further crashes.

    A little tip:
    U should disable fast startup because there are many errors in eventlog too:
    Code:
    2018-06-05 07:28:54  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-06-07 05:32:53  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-06-26 11:09:25  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-06-30 20:59:24  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-07-12 02:25:13  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-07-23 01:21:06  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-07-23 01:28:27  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-07-28 18:28:52  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-07-28 21:06:26  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-08-03 17:59:59  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-08-07 02:49:24  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-08-07 08:47:27  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-08-08 00:50:03  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-08-08 01:56:23  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-08-10 15:51:01  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-08-10 18:55:38  Error: Windows failed fast startup with error status 0xC00000D4.   
    2018-08-17 13:23:15  Error: Windows failed fast startup with error status 0xC00000D4.
    HowTo disable: Turn On or Off Fast Startup in Windows 10

    U should also have a look on this: https://forums.overclockers.co.uk/th...#post-25610301
    Code:
    0x101 = increase vcore
    0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
    Last edited by BSODHunter; 18 Aug 2018 at 08:47.
      My ComputerSystem Spec

  7.    18 Aug 2018 #7

    Thank you for the answer Bsod Hunter. Yes I will remove overclocks and wait for crashes. Also I will remove fastboot. Just one question: Do you think or do you know if increasing Uncore will give me more stability with the overclock? Because is almost the only thing I never touched since I had this processor. I always have it on auto and it says it's at 3.5ghz, but I've heard it should be 3-5ghz below the Core clock(in my case I have 4.7ghz on the core, so uncore should be 4.4ghz-4.2ghz, right?) Thank you again.
      My ComputerSystem Spec

  8.    20 Aug 2018 #8

    Sorry, unfortunately I have no experience for that. Maybe u can ask in an overclocking forum.
      My ComputerSystem Spec

  9.    21 Aug 2018 #9

    I got it stable increasing more System agent and I/O Voltages. thanks for all!
      My ComputerSystem Spec

  10.    22 Aug 2018 #10

    Glad to hear that your problem is now fixed. Let us know if there are any other problems.
      My ComputerSystem Spec


 

Related Threads
Hello Everyone, I have been getting the BSOD lately. It has been happening when playing Civilization 6. The latest one had the CLOCK_WATCHDOG_TIMEOUT on it. Any help would be greatly appreciated! Thank you! Tim
Hi, I've had Multiple BSOD's While playing (High End) games. While playing games such as GTA IV or Player Unknown i have had multiple BSOD, this only seems to happen on games that require a lot of power to run. I have played games like ORI &...
Hey everybody, I've been struggling with this issue for a while, I thought I resolved it a few months ago but it has come back and I'm out of ideas. Ever since upgrading to Win10 at the start of last year I've started getting Clock Watchdog...
A friend of mine is having bsod issues when playing certain games, example: Rainbox six siege, Battlefield One (BETA) and a few others. Wondering if anyone can give us a clue as to the cause. Windows Format is done, but to no avail,...
BSOD CLOCK_WATCHDOG_TIMEOUT playing any Game in BSOD Crashes and Debugging
Constantly getting CLOCK_WATCHDOG_TIMEOUT, while playing anything. GTA V it happens 10-20 minutes of starting the program. CS:GO it crashes 20-30 minutes later. I've tried analyzing the DMP files but they point to ntkrnlmp.exe. I've...
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:09.
Find Us