Two attached dumps, one of which is a CACHE_MANAGER (34) bugcheck. This indicates that a problem occurred in the file system's cache manager.
If we run an .exr on the 2nd parameter of the *34 dump, we get the following:
Code:
1: kd> .exr 0xfffff88006def728
ExceptionAddress: fffff80036b12215 (nt!ExAcquireResourceSharedLite+0x00000000000000d5)
[COLOR=#ff0000][B] ExceptionCode: c0000005 (Access violation)[/B][/COLOR]
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 0000000000000000
Attempt to write to address 0000000000000000
It looks like this is being caused by an access violation. A c0000005 is a translated #GP code that the fault handler raises. #GP is a general protection fault, it implies a program tried to access protected memory and couldn't. The OS displays this as an access violation and its numerical form is c thousand 5. I can't seem to run a !vadump to get more info, sigh.
Very interestingly enough, in the other dump you attached which is a SYSTEM_SERVICE_EXCEPTION (3b) bugcheck, the first parameter is an exception code, which is 00000000c0000005. See anything familiar?
'c0000005'.
Okay, well... we've run Driver Verifier and it has not caught anything, and you've reinstalled Windows. We've done many passes of Memtest, so your RAM is likely healthy. We've run a chkdsk, however, I want to go the extra step and really make sure your hard drive is okay. Your OP says you have a Hitachi drive, so I am attaching a Hitachi diagnostics tool link: