Clock Watch Dog Timeout 0x00000101: 0x010; 0x00; 0x00b; and more Solved

Page 1 of 2 12 LastLast
  1.    25 May 2017 #1

    Clock Watch Dog Timeout 0x00000101: 0x010; 0x00; 0x00b; and more

    Been fighting these BSOD's ever since I upgraded to windows 10 pro (of course no issues with Windows 7!). As any good window user would do, I formatted about a month ago and started fresh to see if that would help; silly me.
    These errors are random and happen at anytime. Web surfing, gaming, or waking the computer from sleep. There are times I will get one right after another even after rebooting. Then there are times I can game for 6+ hours and have no issues. The irregularity is what frustrates me the must. I tried to do my due diligence by reading up, update any drivers, and so far no luck

    I hope you guys can help me because I am lost now.

    I appreciate any and all of your time and help.

    Hardware if helpful:
    Asus Rampage IV Extreme
    Intel I7 3930K 3.2Ghz OC'd to 4.7 Water Cooled
    32Gb DDR3 2400
    EVGA GTX 1080 (not overclocked)
    Creative SB Recon
    Samsung 850 Pro (Boot Drive)
    4 Other Mechanical HD's

    Event Viewer:
    The computer has rebooted from a bugcheck. The bugcheck was: 0x00000101 (0x0000000000000010, 0x0000000000000000, 0xffffcb01d5110180, 0x000000000000000b). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 00000000-0000-0000-0000-000000000000.

    Attachment 136641
      My ComputerSystem Spec

  2. philc43's Avatar
    Posts : 3,752
    64bit Win 10 Pro ver 1809 Build 17763.168 and W10 Insider Build 18290
       25 May 2017 #2

    First thing I would do is remove the Malwarebytes software using the link:

    In one of your dump files the following was found in the thread:

    ffffb301`c30c5da8  fffff803`34b36d88Unable to load image \SystemRoot\system32\drivers\MBAMChameleon.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for MBAMChameleon.sys
    *** ERROR: Module load completed but symbols could not be loaded for MBAMChameleon.sys
      My ComputersSystem Spec

  3.    25 May 2017 #3

    I am at work right now but will be home tonight.

    I will uninstall malwarebytes. It works pretty well, too bad it's causing an error.
      My ComputerSystem Spec

  4.    27 May 2017 #4

    After uninstalling Malwarebytes all seemed ok until just a minute ago when I got another BSOD with the clock watchdog error.

    attached is a new log:
    Attachment 136961
    Attachment 136960
    Attachment 136962

    I dream of a day when I don't get 1 BSOD for 24hrs !
    Last edited by Dalumberjack03; 28 May 2017 at 09:14. Reason: wording
      My ComputerSystem Spec

  5.    28 May 2017 #5

    0x00000124:    WHEA_UNCORRECTABLE_ERROR (25.05.2017 18:54:17) [Windows 10] 
    CAUSED BY:     0x124_GenuineIntel_PROCESSOR_MAE [18.07.1979]   
                   hal.dll  (Hardware Abstraction Layer DLL. NO Driver)  
    WHEA Notify:   Machine Check Exception 
         Type:     Micro-Architectural Error 
         Error:    Internal timer (Proc 6 Bank 3) 
    PROCESS:       nvsphelper64.exe 
    Usual causes:  Hardware, Incompatibility, May be driver corruption

    At first step u should remove every overclocking. OC is an usual cause for bluescreens. Since the most recent bsod dump shown an processor error its recommended to go back to stock.
    There are bunch of OC tools u are using:

    EVGA Precision XOC
    ASUS AI Suite II
    Corsair LINK 4

    These tools are known for causing bluescreens. Regarding to the last bsod dump just have look at this:
    Common BSOD Error Code List for Overclocking - Community
    0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
    0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)

    There is also a filesystem corruption found on C:
    2017-05-21T15 45:53.773  Error: A corruption was discovered in the file system structure on volume C:.  
    2017-05-21T15 45:53.775  Error: A corruption was discovered in the file system structure on volume C:.

    Repair Windows Filesystem:

    1. Open an elevated command prompt.
    2. In the elevated command prompt, type these commands below, and press Enter:

    dism /Online /NoRestart /Cleanup-Image /CheckHealth
    dism /Online /NoRestart /Cleanup-Image /ScanHealth
    dism /Online /NoRestart /Cleanup-Image /RestoreHealth
    dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup
    dism /Online /NoRestart /Cleanup-Image /AnalyzeComponentStore

    sfc /scannow

    chkdsk %systemdrive% /F /R /X
    fsutil dirty set %systemdrive%

    The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
    If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
    For example, you would use DISM to fix Windows component store corruption when a sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted. SFC should be able to repair the files afterwards.
    Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...
      My ComputerSystem Spec

  6.    28 May 2017 #6

    Corsair Link does not overclock .....all it does is control pump seed and cpu fan speed. Never seen it give a BSOD can crash from time to time, but thats about it. ASUS A1 Suite I would remove thou. Lots of crap in that suite.
      My ComputersSystem Spec

  7.    28 May 2017 #7

    Im Not sure if this comment helps this user. But I will put this information in my documentation
      My ComputerSystem Spec

  8.    28 May 2017 #8

    BSODHunter said: View Post
    Im Not sure if this comment helps this user. But I will put this information in my documentation
    Most all of your suggestions were pretty good, and I hope the user does them. As far as Corsair Link and EVGA Precision XOC, those 2 apps are made for specific tasks. XOC will allow you too OC your GPU. This user seems to be a Overclocker he might have something else giving him these BOSD's I run those exact same apps, with no issues at all. Your suggestions for SFC, DISM and CHKDSK are excellent ones. Just my 2 cents. :)
    Note: IF this user has there CPU oc'd too high, along with maybe his memory, this could give him BSOD's without question.
      My ComputersSystem Spec

  9. axe0's Avatar
    Posts : 13,823
    Windows 10 Pro
       28 May 2017 #9

    The mentioned software is indeed not all about overclocking, but the crashes in combination are neither.
    The programs are mentioned, because in the past many have been able to connect them to BSODs, like a specific version of Google Chrome has been connected to 0x124 crashes in the past because of a small feature it has.
      My ComputersSystem Spec

  10.    29 May 2017 #10

    Hey everyone,

    Thank you very much for all the responses. I just got off a 18+ hour duty shift. Currently, I am going to go pass out into a small coma for a bit. When I get up, I'm going to run through the suggestions and respond back more thoroughly about my current overclocks.

    Thanks again everyone, really appreciate the help!
      My ComputerSystem Spec

Page 1 of 2 12 LastLast

Related Threads
UAC timeout in Software and Apps
I have several pieces of software that take really long times to upzip and do preliminary operations before attempting to do the installation. Several times I have walked away to avoid staring at a flashing screen for 15 minutes (or because my...
I just bought battlefield 1 and after a couple days of playing i randomly got a clock watchdog timeout and then the next day a whea uncorrectable error. It happens without warning while im in the middle of the game. I havent had this problem with...
DM Log Collector was ran in safe mode and attached. 102728 The BSOD occurs very soon after logging in. Windows 10
94622 Computer has been blue screening infrequently over the months. It got much more frequent the past month(like every 30 min.) I went through some troubleshooting with System file checker, corrected a Opencl.dll file. Brought computer to a...
Solved Screens Won't Timeout in General Support
I have the "Turn off display after" set to 20 minutes: 39043 ...but they aren't timing out. Does anyone know what might be keeping this from working? Another setting? Some program is keeping it from timing out?
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 07:15.
Find Us