Backup your critical data and consider creating a disk image of your current install.
Then open an Admin Command prompt and type
chkdsk C: /R
hit enter
respond "Y" when prompted to run on next restart
exit the command prompt and restart your computer.
Let the native Check Disk utility run until completed, it can take a while, so best to just walk away and let it do its' thing.
Your system should reboot itself and then you need to check Event Viewer to inspect the results of the scan.
Both the dump files suggest "memory corruption" and seem to point to the page file / virtual memory
11/0616 Dump File.....
STACK_TEXT:
ffffc481`9adc6900 fffff801`14cd8508 : 00000000`1999d9d1 ffffc481`9adc69e4 00000000`00000000 fffff801`14c87779 : nt!MiObtainReferencedVad+0x301
ffffc481`9adc6980 fffff801`14cd8270 : da0a127b`5fb0ff59 00000000`00000001 ffffc481`9adc6cc0 00000000`00000000 : nt!MiAllocateVirtualMemory+0x288
ffffc481`9adc6b70 fffff801`1496b093 : 00000000`00000000 00000000`00000001 00000000`00000000 ffffc481`00000000 : nt!NtAllocateVirtualMemory+0x40
ffffc481`9adc6bd0 00007ffd`d1445164 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000040`12c7cbe8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`d1445164
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff801148baea2 - nt!MiResolvePrivateZeroFault+212
[ f6:d4 ]
fffff801148baecb-fffff801148baecc 2 bytes - nt!MiResolvePrivateZeroFault+23b (+0x29)
[ fb f6:ea d4 ]
fffff801148baee8-fffff801148baee9 2 bytes - nt!MiResolvePrivateZeroFault+258 (+0x1d)
[ 80 fa:00 ee ]
fffff801148bd017-fffff801148bd018 2 bytes - nt!MiGetPage+97 (+0x212f)
[ 80 fa:00 ee ]
fffff801148bd22a-fffff801148bd22b 2 bytes - nt!MiGetFreeOrZeroPage+7a (+0x213)
[ 80 fa:00 ee ]
fffff801148bd492-fffff801148bd493 2 bytes - nt!MiGetFreeOrZeroPage+2e2 (+0x268)
[ 80 fa:00 ee ]
fffff801148bd4e8-fffff801148bd4e9 2 bytes - nt!MiGetFreeOrZeroPage+338 (+0x56)
[ 80 fa:00 ee ]
fffff801148bdb5a - nt!MmAccessFault+9a (+0x672)
[ f6:d4 ]
fffff801148bdbfb - nt!MmAccessFault+13b (+0xa1)
[ f6:d4 ]
fffff801148bddd6-fffff801148bddd7 2 bytes - nt!MmAccessFault+316 (+0x1db)
[ fb f6:ea d4 ]
fffff801148bdde4 - nt!MmAccessFault+324 (+0x0e)
[ f6:d4 ]
fffff801148bdeef - nt!MmAccessFault+42f (+0x10b)
[ f6:d4 ]
19 errors : !nt (fffff801148baea2-fffff801148bdeef)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: LARGE
STACK_COMMAND: .cxr 0xffffc4819adc5ef0 ; kb
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_LARGE
102516 Dump File
STACK_TEXT:
ffffd200`2e9ec2b8 fffff802`7c4036da : 00000000`00000050 ffffc411`776ce248 00000000`00000000 ffffd200`2e9ec5b0 : nt!KeBugCheckEx
ffffd200`2e9ec2c0 fffff802`7c2f500a : 00000000`00000000 00000000`00000000 ffffd200`2e9ec5b0 ffffe208`b5a99948 : nt! ?? ::FNODOBFM::`string'+0x2624a
ffffd200`2e9ec3b0 fffff802`7c3d78fc : 00000000`00000002 00000000`00000000 ffffe208`c3f51840 ffffa785`eed6f1f0 : nt!MmAccessFault+0x9ca
ffffd200`2e9ec5b0 fffff802`7c2b1ad4 : fffff802`7c6dacd6 00000000`006461c8 ffffd200`2e9ec830 ffffd200`2e9ec7e8 : nt!KiPageFault+0x13c
ffffd200`2e9ec748 fffff802`7c6dacd6 : 00000000`006461c8 ffffd200`2e9ec830 ffffd200`2e9ec7e8 00000000`00000000 : nt!HvpFaultCellWithClustering+0x24
ffffd200`2e9ec750 fffff802`7c6da7ed : ffffd200`2e9ec9f0 00000000`00000004 0000002a`00000002 00000000`00000017 : nt!HvpGetCellPaged+0x76
ffffd200`2e9ec780 fffff802`7c6d73a4 : ffffe208`c3f51870 ffffd200`2e9ec9f0 00000000`00000002 0000002a`11afe470 : nt!CmQueryValueKey+0x28d
ffffd200`2e9ec8c0 fffff802`7c3d8f93 : 00000000`00000afc fffff802`7c6f3e8b 00000000`00000000 00000000`00000000 : nt!NtQueryValueKey+0x634
ffffd200`2e9ecbd0 00007ffe`69245134 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000002a`11afe3a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`69245134
CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
fffff8027c307942 - nt!MiIssueHardFault+312
[ fa:98 ]
1 error : !nt (fffff8027c307942)
MODULE_NAME: memory_corruption
IMAGE_NAME: memory_corruption
FOLLOWUP_NAME: memory_corruption
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MEMORY_CORRUPTOR: ONE_BYTE
FAILURE_BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
BUCKET_ID: MEMORY_CORRUPTION_ONE_BYTE
PRIMARY_PROBLEM_CLASS: MEMORY_CORRUPTION_ONE_BYTE
IF the drive turns out OK then check your physical memory modules
Download Memtest86+
from this location here. Burn the ISO to a CD and boot the computer from the CD from a cold boot after leaving it off for an hour or more.
Ideally let it run for at least 7 passes / 6-8 hours. If errors appear before that you can stop that particular test. Any time Memtest86+ reports errors, it can be either bad RAM or a bad Mobo slot. Perform the test RAM sticks individually as well as all possible combinations. When you find a good one then test it in all slots. Post back with the results.
See
this Guide to using Memtest 86+
Not sure how you went about "re-installing" Windows 10 but somehow you ended up with several old drivers, which you should probably address.
Either update / upgrade them or uninstall them
HECIx64.sys 9/17/2009
Impcd.sys 2/26/2010
bcmwl664.sys 9/1/2010
iaStor.sys 9/13/2010
stwrt64.sys 12/1/2010
IntcDAud.sys 8/23/2011
igdkmd64.sys 11/26/2012
