If SFC is still reporting errors the OS may be corrupt or alternatively the HDD may have issues, the latter can sometimes be reported as a memory issue in the mini dumps which incidentally your last crash dump suggested bad memory, see what I have highlighted in red below;
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80057065df9, Address of the instruction which caused the bugcheck
Arg3: ffffd00020313db0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
Debugging Details:
------------------
TRIAGER: Could not open triage file : e:\dump_analysis\program\triage\modclass.ini, error 2
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
nt!MiProtectPrivateMemory+b1
fffff800`57065df9 4c89442450 mov qword ptr [rsp+50h],r8
CONTEXT: ffffd00020313db0 -- (.cxr 0xffffd00020313db0)
rax=fffff6803e765cc8 rbx=0000007cecb99000 rcx=0000098000000000
rdx=0000007ffffffff8 rsi=0000000000000001 rdi=0000000000000000
rip=fffff80057065df9 rsp=ffffd000203147e0 rbp=ffffd000203148e0
r8=0000007cecb99fff r9=0000000000000001 r10=0000070000000000
r11=0000007fffffffff r12=ffffe00084368080 r13=ffffe0008325b640
r14=fffff6803e765cc8 r15=ffffe00084047ec0
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nt!MiProtectPrivateMemory+0xb1:
fffff800`57065df9 4c89442450 mov qword ptr [rsp+50h],r8 ss:0018:ffffd000`20314830=0000000000000000
Resetting default scope
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x3B
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff800574c454f to fffff80057065df9
STACK_TEXT:
ffffd000`203147e0 fffff800`574c454f : 00000000`07cecb99 ffffd000`20314a28 00000000`00000000 7fffffff`fffffffc : nt!MiProtectPrivateMemory+0xb1
ffffd000`203149c0 fffff800`573b7b91 : ffffe000`84368080 ffffe000`84368080 ffffd000`20314b18 ffffd000`20314b08 : nt!MiProtectVirtualMemory+0x52f
ffffd000`20314ac0 fffff800`571774b3 : ffffd000`00000000 0000007c`000003e8 00000000`00000000 0000007c`eb44dc18 : nt!NtProtectVirtualMemory+0x155
ffffd000`20314b90 00007ffe`703b16ca : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000007c`eb44dbf8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7ffe`703b16ca
FOLLOWUP_IP:
nt!MiProtectPrivateMemory+b1
fffff800`57065df9 4c89442450 mov qword ptr [rsp+50h],r8
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt!MiProtectPrivateMemory+b1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
DEBUG_FLR_IMAGE_TIMESTAMP: 550f41a6
STACK_COMMAND: .cxr 0xffffd00020313db0 ; kb
IMAGE_NAME: memory_corruption
FAILURE_BUCKET_ID: X64_0x3B_nt!MiProtectPrivateMemory+b1
BUCKET_ID: X64_0x3B_nt!MiProtectPrivateMemory+b1
Followup: MachineOwner
Worth mentioning is that the reported PROCESS_NAME: svchost.exe is not telling us anything helpful about the crash as it does not name a specific service as the cause
Can you check to see is a CBS log has been created by the last SFC, see below;
Navigate to C:\Windows\Logs\CBS folder. You'll see CBS.log file.
The file may be large so upload it to http://www.mediafire.com/ and then post the download link here.
How to use mediafire http://en.kioskea.ne...es-to-mediafire
Once the above has been done test the HDD with Seatools for Windows, if available do both the short and extended tests please, details here