Are you sure it was just only 3 days ago? While majority of your crashes do appear from just yesterday, I do see one from March 21, another from May 5, and two from May 6. I think the Windows Update may be the cause for most of the crashes you're experiencing now, but the failure to update properly may have occurred by a much deeper problem.
I noticed particularly on a crashdump from May 6 that a CPU register had a memory address stored in it that got corrupted by one solitary bit. This is very often a hardware issue, and rarely does a software bug cause a solitary bit from some arbitrary cpu register to get scuffed up.
I recommend approaching this with some hardware tests. Here's my standard fare of them:
- 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.
Preferably you run these in the order presented. 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 newest 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.
CONTEXT: fffff880037aa640 -- (.cxr 0xfffff880037aa640)
rax=ffff78a002f53010 rbx=fffffa80015357e0 rcx=fffff8a00c3c8220
rdx=0000000000000002 rsi=0000000000000041 rdi=0000000000000001
rip=fffff80002fbe617 rsp=fffff880037ab020 rbp=0000000000001000
r8=0000000000000001 r9=fffffa80015357e0 r10=fffffa8001535288
r11=0000000000000002 r12=fffffa8001535280 r13=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
fffff800`02fbe617 48895808 mov qword ptr [rax+8],rbx ds:002b:ffff78a0`02f53018=????????????????