Windows 10: BSOD clock_watchdog_timeout

Page 1 of 2 12 LastLast
  1.    16 Apr 2017 #1

    BSOD clock_watchdog_timeout

    So I got this bsod CLOCK_WATCHDOG_TIMEOUT. PC froze at 30% while it was auto restarting.
    Added 2 more ram sticks and this happens a day after.
    Had issue with the ram's software (to control RGB).
    They are G.skill Trident Z RGB. Installed the software after adding ram, pc froze couple times within 10 minutes. Had to uninstall and it was ok.

    Can someone help me with the minidump read, thank you.
      My ComputerSystem Spec

  2. Ztruker's Avatar
    Posts : 6,419
    Windows 10 Pro X64 17134.191
       19 Apr 2017 #2

    Do you still need help with this?

    If so, the first thing to do is uninstall the software and see if that makes a difference. If not then remove the new ram and see if that helps. If it does then swap in one of the new ram modules in place of one of the old ones and see what happens. Continue testing till you find the one causing the problem.

    I can't see testing all the ram as it would take a couple days to test 32GB. Swapping and testing the ram is a better method in your case I think.

    THe last dump only shows 16GB of ram, when did you add the additional 16GB, before or after the BSODs occurred?
      My ComputersSystem Spec

  3.    22 Apr 2017 #3

    BSOD happened after I added 2x8 gb ram.
    haven't got the bsod again until now.
      My ComputerSystem Spec

  4. Ztruker's Avatar
    Posts : 6,419
    Windows 10 Pro X64 17134.191
       22 Apr 2017 #4

    Run dm_log_collector again and upload the zip file. Let's see if any new dump was saved.
      My ComputersSystem Spec

  5.    22 Apr 2017 #5

    There. Thank you.
      My ComputerSystem Spec

  6. Ztruker's Avatar
    Posts : 6,419
    Windows 10 Pro X64 17134.191
       22 Apr 2017 #6

    One new dump:
    BugCheck 7F, {8, ffff8280938b7b30, ffff8280938ddb20, fffff800cd0602f7}
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    Probably caused by : memory_corruption
    Followup:     memory_corruption
    This means a trap occurred in kernel mode, and it's a trap of a kind
    that the kernel isn't allowed to have/catch (bound trap) or that
    is always instant death (double fault).  The first number in the
    bugcheck params is the number of the trap (8 = double fault, etc)
    Consult an Intel x86 family manual to learn more about what these
    traps are. Here is a *portion* of those codes:
    If kv shows a taskGate
            use .tss on the part before the colon, then kv.
    Else if kv shows a trapframe
            use .trap on that value
            .trap on the appropriate frame will show where the trap was taken
            (on x86, this will be the ebp that goes with the procedure KiTrap)
    kb will then show the corrected stack.
    Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT
    Arg2: ffff8280938b7b30
    Arg3: ffff8280938ddb20
    Arg4: fffff800cd0602f7
    Almost surely defective RAM. Try the RAM swap and test process I mentioned in my earlier post to identify the one (or two but probably one) module causing the problem.
      My ComputersSystem Spec

  7.    22 Apr 2017 #7

    how do you actually test the ram? I used the windows memory diagnostic tool, didn't show any error.
      My ComputerSystem Spec

  8.    22 Apr 2017 #8

    ok, removed the 2 new sticks. will keep you updated.
      My ComputerSystem Spec

  9. Ztruker's Avatar
    Posts : 6,419
    Windows 10 Pro X64 17134.191
       22 Apr 2017 #9

    We recommend running memtest86+ but with 32GB of ram as I said, it would take several days to run a 8 passes which is the minimum recommended for a thorough test. If you want, you can remove the old ram and install the new ram then run memtest86+ overnight and see what it shows:
    Follow this tutorial: MemTest86+ - Test RAM - Windows 10 Forums

    MemTest86+ is a diagnostic tool designed to test Random Access Memory (RAM) for faults. MemTest86+ will verify that:

    • RAM will accept and keep random patterns of data sent to it
    • There are no errors when different parts of memory try to interact
    • There are no conflicts between memory addresses

    Memtest86+ runs from bootable media to isolate the RAM from the system, no other components are taken into account during the test.

    warning   Warning
    MemTest86+ needs to run for at least 8 passes to be anywhere near conclusive, anything less will not give a complete analysis of the RAM.

    If you are asked to run MemTest86+ by a Ten Forums member make sure you run the full 8 passes for conclusive results. If you run less than 8 passes you will be asked to run it again.

    Note   Note
    MemTest86+ has been known to discover errors in RAM in later passes than the eighth pass. This is for information only; if you feel there is a definite problem with the RAM and 8 passes have shown no errors feel free to continue for longer.

    Running 8 passes of MemTest86+ is a long and drawn out exercise and the more RAM you have the longer it will take. It's recommended to run MemTest86+ just before you go to bed and leave it overnight.

    Take a picture when done and post in the forum please.
      My ComputersSystem Spec

  10.    24 Apr 2017 #10

      My ComputerSystem Spec

Page 1 of 2 12 LastLast

Related Threads
Man, I don't even know what to do with this computer anymore... Just a few days ago, out of the blue, my laptop blue screens with the CLOCK_WATCHDOG_TIMEOUT error every other startup, literally. Google Chrome is refusing to open. I have done a...
Hi! So I have got 2 BSOD while playing. First one said whea uncorrectable error and other one said clock_watchdog_timeout. During that last BSOD it did not create a dumpfile because it stayed at 50% and I had to restart. I have attached logs to this...
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...
CLOCK_WATCHDOG_TIMEOUT 101 BSOD on cold boot in BSOD Crashes and Debugging
Hi, I am a system administrator in the company I work for. One user's pc has a frequent BSOD error (see title). Most of the time BSODs happen in the morning, when the user turns on the pc, but sometimes he gets BSOD also during the day. The pc...
I spent all weekend building up a new computer: CPU: Intel Core i7-6700K 4.0GHz Quad-Core Processor CPU Cooler: NZXT Kraken X41 106.1 CFM Liquid CPU Cooler Motherboard: Gigabyte GA-Z170X-Gaming 7 ATX LGA1151 Motherboard Memory: G.Skill...
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 12:18.
Find Us