I saw two older crashdumps, one dated Feb 6 and the other Jan 7, that look unrelated. I take it these are unrelated to your current predicament?
Anyways, the rest of them are unanimous: WHEA errors caused by an internal CPU timer failure. There was one 0x101 bugcheck but one can't debug 0x101 bugchecks without at least a kernel dump. Still, 0x101 can and often do occur from CPU failure, especially when it involves timing errors like what you're evidently experiencing.
I have seen a few times motherboard software cause these problems. Motherboard software is extremely buggy and is very gimmicky, none of it is recommended, even temp monitors and OCing tools. If you need to overclock, it's best to do it straight from the BIOS/UEFI. Speaking of OCing, since we're dealing with a timing issue here, it's best that if you have OCed anything to reset everything
to factory defaults, as event3horizon
clearly pointed out. We're talking "safe settings" for your BIOS/UEFI, not some predefined performance settings or anything like that.
If things don't stabilize after resetting things, then go and uninstall any and all motherboard software, including USB "drivers
". Only leave drivers for motherboard components (again, no USB drivers, as it's software posing as drivers) like LAN, Chipset, etc.
does not resolve your problem, then I'm afraid we're dealing with hardware failure here. Primary suspect is CPU, followed by RAM, PSU and Motherboard, in order of possibility. I have seen GPU failure also cause this, but it's very rare. If you wish, you can run some hardware tests as followed:
- 7+ passes
- Torture Test; Large FFTs; overnight (9+ hours)
- Run twice (if any of the tests work on your GPU; ATI cards will need to install the ATI APP SDK
as it requires OpenCL)
All of these (excluding MemtestCL) are included in the UBCD
if you prefer a Live CD environment (which is the best environment to test hardware on). Note that Prime95 currently does not work on the UBCD. Also, please provide us temps/voltages using HWInfo
with Sensors only
option checked. Log two 30-minute instances: one for idle, and one for high load.