You said it's only been past month? From the crashdumps it looks like you've been suffering since May, with one crash that month, one in June, four in July, and four in August. Have those previous crashes been resolved?
The crashdumps report a lot of various memory corruptions, from solitary bit changes in code to messed up CPU registers that may have been grabbed from bad memory references. I cannot ascertain exact cause without a kernel dump (MEMORY.DMP
in Windows directory).
You should be able to get a better answer if you let Driver Verifier
crash your system a couple times and send us the minidumps from there. If I find that nothing has changed in the crashdumps that DV churns out, then you are looking at hardware problems, which is pretty much what I suspect right now. However, if it is caused by hardware failure, crashdumps will not be all that valuable in ascertaining exactly what hardware it is that's doing it.
If you wish, you may run a couple of hardware tests. First start off with Memtest
and run that overnight. If you see any red on the screen, that's good evidence you have bad RAM. If you wish, you may also run Prime95
. Have it go on Torture Test with Blend overnight. If you see the system has crashed or it has reported errors, then run it another night only this time with Large FFTs instead of Blend. If those also report issues or your system crashes during it, then you have either a bad CPU, motherboard, or PSU, with the CPU being prime suspect.