1.    25 Jun 2017 #1
    Join Date : Jun 2017
    Posts : 2
    Windows 10

    clock_watchdog_timeout and whea_uncorrectable_error


    Hi thanks in advance I woke up and my PC was in the bios screen saying there was a CPU fan error I am using a custom water loop system so this should have been set to ignore already. I went into bios to set it back to ignore and saved into windows then started to get BSOD so I removed overclock checked for malware and updated bios still kept getting BSOD so did a fresh install of windows and still getting the same problemsAttachment 141076
      My ComputerSystem Spec
  2.    25 Jun 2017 #2
    Join Date : Jun 2017
    Posts : 2
    Windows 10
    Thread Starter

    Looks like my overclock was still on for some reason doing stress test now so far so good. Maybe a voltage issue when I was overclocking?
      My ComputerSystem Spec
  3.    28 Jun 2017 #3
    Join Date : Apr 2017
    Posts : 8,839
    windows 10 professional version 1607 build 14393.969 64 bit

    Hi Darkway,



    Code:
    BugCheck 124, {0, ffffda0e3c9a78f8, 0, 0}Probably caused by : GenuineIntel
    Code:
    WHEA_UNCORRECTABLE_ERROR (124)A fatal hardware error has occurred. Parameter 1 identifies the type of errorsource that reported the error. Parameter 2 holds the address of theWHEA_ERROR_RECORD structure that describes the error conditon.Arguments:Arg1: 0000000000000000, Machine Check ExceptionArg2: ffffda0e3c9a78f8, Address of the WHEA_ERROR_RECORD structure.Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.
    Code:
    BugCheck BE, {ffff8217160f0190, 8000000003c00121, ffffd4812b2222c0, b}Probably caused by : memory_corruption
    Code:
    BugCheck 124, {0, ffff800945744038, 0, 0}Probably caused by : GenuineIntel
    Code:
    BugCheck 124, {0, ffffbb827a73c028, be000000, 800400}Probably caused by : memory_corruption
    Code:
    BugCheck 124, {0, ffffc98645f3b028, be000000, 800400}Probably caused by : GenuineIntel
    Code:
    BugCheck 124, {0, ffffc908d5a648f8, 0, 0}Probably caused by : GenuineIntel
    Code:
    BugCheck 124, {0, ffffb10e3632c028, be000000, 800400}Probably caused by : GenuineIntel


    Make sure that there is no over clocking while troubleshooting.

    Sometimes there are problems in the bios that produce bsod.

    The bios in your computer: BIOS Version/Date American Megatrends Inc. 3701, 3/30/2017

    To ensure that there are no improper bios settings please reset the bios.

    Sometimes there can be failure to boot after resetting the bios. So please make sure your files are backed up. Please make a backup image with Macrium: Macrium Software | Macrium Reflect Free
    And please create a restore point.



    Open administrative command prompt and type or copy and paste:


    1) winver (in the pop up about windows > view your windows version and build > type this information into the thread)


    2) sfc /scannow


    3) dism /online /cleanup-image /restorehealth


    4) chkdsk /scan


    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 copy > paste into the thread

    5)Run memtest86+ version 5.01 for at least 8 runs. This may take hours so plan to run it overnight.

    http://www.memtest.org/https://answe...f-ecc7b7ff6461

    For the memory testing it is critical that 8 or more runs be made so that the false negatives are reduced. Sometimes it may take runs into the teens to find problems with ram/dim.


    When Memtest86+ has completed 8 or more runs make an image of the results to post into the thread.


    6) run one of the SMART tests on your drives:
    CrystalDiskInfo - Software - Crystal Dew World
    HD Tune: http://www.hdtune.com/
    Hard Disk Sentinel - HDD health and temperature monitoring: Hard Disk Sentinel - HDD health and temperature monitoring


    When the SMART test has completed open the Microsoft snipping tool and make images of the results to post into the thread.

    7) run the Intel processor diagnostic tool and post an image of the result into the thread:
    The IntelĀ® Processor Diagnostic Tool
    Download IntelĀ® Processor Diagnostic Tool


    8) if you have frequent bsod where you are having difficulty completing the troubleshooting steps please place your computer in clean boot. If clean boot fails then use safe mode with command prompt or safe mode with networking.


    For clean boot open administrative command prompt and type or copy and paste:
    9) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)


    10) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)


    11) shutdown /r (you will reboot the computer so that it is in clean boot)

    TechNet Wiki

    Perform a Clean Boot in Windows 10 to Troubleshoot Software Conflicts Windows 10 Performance Maintenance Tutorials
      My ComputerSystem Spec
  4.    28 Jun 2017 #4
    Join Date : Nov 2015
    Posts : 2,871
    64bit Win 10 Pro ver 1709 Build 16299.64

    Quote Originally Posted by Darkway View Post
    Looks like my overclock was still on for some reason doing stress test now so far so good. Maybe a voltage issue when I was overclocking?
    Quite often you will need to increase the voltage if you are attempting to overclock. Cooling also needs to be more efficient to compensate for the extra heat generated.

    In practice, overclocking increases the risk of BSOD and so removing all overclocking and restoring BIOS to optimized defaults should be the answer.
      My ComputersSystem Spec

 


Similar Threads
Thread Forum
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...
BSOD Crashes and Debugging
BSOD CLOCK_WATCHDOG_TIMEOUT playing any Game
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...
BSOD Crashes and Debugging
CLOCK_WATCHDOG_TIMEOUT 101 BSOD on cold boot
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...
BSOD Crashes and Debugging
Solved CLOCK_WATCHDOG_TIMEOUT After Leaving PC for 5-10 Minutes
I've been getting this message for a while already. This happened not long after I moved (which was right at the end of last month), but not before then. I thought it was the Wi-Fi adapter driver, so I uninstalled its driver and downloaded a new one...
BSOD Crashes and Debugging
Playing any game (Clock_watchdog_timeout) and then (irql_not_less_or_e
Hello, I am at my wits end. Originally while playing a game I started about 6 months ago I started getting Clock_watchdog_timeout bsod. Now it has progressively gotten worse to the point of I could only play a game for about 15min. It was doing this...
BSOD Crashes and Debugging
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 15:43.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums