After examinating your latest dump. I'm very sure that it is hardware error.
One minidump crashes at IRQL x'1c' which is clock level interrupt and two mindumps crash with bugcheck code 8E and nt status code x'1d'. Most likely the culprit is faulty M/B.
BugCheck 1000008E, {c000001d, 804ecd2c, b87df998, 0}
Probably caused by : hardware ( afd!AfdPoll+87c )
BugCheck 1000008E, {c000001d, bf801642, b91abcd4, 0}
Probably caused by : hardware ( win32k!ValidateHwnd+b9 )
BugCheck 1000000A, {68, 1c, 1, 804dc4b1}
Probably caused by : memory_corruption
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000068, memory referenced
Arg2: 0000001c, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 804dc4b1, address which referenced memory
Debugging Details:
------------------
WRITE_ADDRESS: 00000068
CURRENT_IRQL: 1c
FAULTING_IP:
nt!KeWaitForSingleObject+25f
804dc4b1 894668 mov [esi+0x68],eax
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: CODE_CORRUPTION
BUGCHECK_STR: 0xA
LAST_CONTROL_TRANSFER: from f76d0ea8 to 804dc4b1
STACK_TEXT:
b98838fc f76d0ea8 00000000 00000000 00000000 nt!KeWaitForSingleObject+0x25f
b988391c f76d0db6 864d2d40 00010000 e10fc3c8 Ntfs!NtfsWaitSync+0x1c
b9883ae4 f76d36fe 864d2d40 864e1008 e10fc3c8 Ntfs!NtfsNonCachedIo+0x30e
b9883bc4 f76d2fbf 864d2d40 864e1008 00000001 Ntfs!NtfsCommonRead+0xbdd
b9883c64 804e13d9 865ba158 864e1008 86771700 Ntfs!NtfsFsdRead+0x22d
b9883c74 f7774459 b9883ca0 804e13d9 866aaaa8 nt!IopfCallDriver+0x31
b9883c7c 804e13d9 866aaaa8 864e1008 806ff410 sr!SrPassThrough+0x31
b9883c8c 8056f50b 864e1198 864e1008 8633db08 nt!IopfCallDriver+0x31
b9883ca0 8057f13f 866aaaa8 864e1008 8633db08 nt!IopSynchronousServiceTail+0x60
b9883d38 804dd99f 000004b8 00000000 00000000 nt!NtReadFile+0x55d
b9883d38 7c90eb94 000004b8 00000000 00000000 nt!KiFastCallEntry+0xfc
WARNING: Frame IP not in any known module. Following frames may be wrong.
0417fe28 00000000 00000000 00000000 00000000 0x7c90eb94
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
804dc486 - nt!KeWaitForSingleObject+23d
[ 4e:ce ]
1 error : !nt (804dc486)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BIT
STACK_COMMAND: kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
BUCKET_ID: MEMORY_CORRUPTION_ONE_BIT
Followup: memory_corruption
---------
0: kd> r
eax=0000b7d8 ebx=b9883b20 ecx=00000000 edx=00000000 esi=00000000 edi=865bc360
eip=804dc4b1 esp=b98838bc ebp=b98838fc iopl=0 nv up ei pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
nt!KeWaitForSingleObject+0x25f:
804dc4b1 894668 mov [esi+0x68],eax ds:0023:00000068=????????