Lot of 0x101 crashes. These cannot be debugged without access to a kernel dump (that big ole MEMORY.DMP
located in your Windows directory). These can commonly be caused by CPU issues, but software can also be attributed to it. I did see a couple of 0x124 bugchecks (WHEA errors), but there's no crashdump associated with em so I can't tell exactly what hardware error it's reporting about. I could check the MCi_Status info, but I'm not gonna even bother at the moment, given that it means whipping out the Intel CPU manual and comparing bit flags. Regardless, having the 0x124 crashes mingled in with the 0x101 has me believe we're dealing with hardware problems here.
Just to make absolutely sure, though, you should first update your BIOS, as well as all drivers
related to your motherboard components. Do not
install USB "drivers", and if you have already, uninstall. In addition, if you have any motherboard software like OCing tools and whatnot, uninstall all of them. They are extremely buggy, gimmicky, and I've seen them trigger hardware failure like the 0x124 bugchecks.
Next are a few hardware checks. These aren't 100% guaranteed to find a problem, but they're far better than nothing. Run them in order listed. Here they are:
- 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 basic tests aside from the Fix all
or the advanced ones.
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 latest version of 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. If you can get the system to crash during high load logging, that's even better.