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

First thing I would do is remove the Malwarebytes software using the link: http://www.malwarebytes.org/mbam-clean.exe

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

Code:

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
 MBAMChameleon+0x26d88

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.

Code:

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 - Overclock.net Community

Code:

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:

Code:

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%

SFC:
The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
DISM:
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.
CHKDSK:
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...

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

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!