I am at my wits end, and am finally reaching out for some help.
 
My computer specs are as follows:
EVGA SuperNOVA 750 G2, 80+ GOLD 750W
MSI Z97 GAMING 5 Motherboard
i5 4690k (stock speed)
16 GB Crucial RAM DDR3 1600
Samsung SSD 250GB
Windows 10 Pro 64 bit
EVGA GTX 1070 ACX 3.0 Black Edition
 
Whatever game I try, within about 20-30 minutes I crash to desktop or end up with a major BSOD.
 
I reinstalled a fresh copy of Windows 10 Pro. I cleaned up drivers using DDU in safe mode and installed the latest Nvidia driver 373.06.
 
Any help would be appreciated. Sorry if I'm posting this in the wrong forum.
 
My BSOD reports are as follows:
On Fri 10/21/2016 5:06:45 AM your computer crashed
crash dump file: C:\Windows\Minidump\102116-4296-01.dmp
This was probably caused by the following module: (nt+0x11793D)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801C253093D, 0xFFFFD0005F569198, 0xFFFFD0005F5689B0)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
description: NT Kernel & System
Bug check description: This indicates that a system thread generated an exception which the error handler did not catch.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10/21/2016 5:06:45 AM your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF801C253093D, 0xFFFFD0005F569198, 0xFFFFD0005F5689B0)
Error:
Bug check description: This bug check indicates that a system thread generated an exception that the error handler did not catch.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 10/20/2016 4:21:57 PM your computer crashed
crash dump file: C:\Windows\Minidump\102016-3671-01.dmp
This was probably caused by the following module: (nt+0x142970)
Bugcheck code: 0x139 (0x3, 0xFFFFD000B1399810, 0xFFFFD000B1399768, 0x0)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
description: NT Kernel & System
Bug check description: The kernel has detected the corruption of a critical data structure.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 10/20/2016 12:50:22 PM your computer crashed
crash dump file: C:\Windows\Minidump\102016-4218-01.dmp
This was probably caused by the following module: (nt+0x142970)
Bugcheck code: 0x1A (0x5002, 0xFFFFF79940000000, 0x7F0B, 0x2000577DFFFFFFE)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 10/20/2016 1:38:35 AM your computer crashed
crash dump file: C:\Windows\Minidump\102016-4718-01.dmp
This was probably caused by the following module: (nt+0x142970)
Bugcheck code: 0x1A (0x41792, 0xFFFFF6BFFF6230B0, 0x400000000000000, 0x0)
Error:
file path: C:\Windows\system32\ntoskrnl.exe
product:
company:
description: NT Kernel & System
Bug check description: This indicates that a severe memory management error occurred.
This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue).
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.  
 
 

Wow... you were right. The crash reports kept making me suspect it was bad Nvidia drivers, but it looks like it was a bad memory stick all along.
 
Using one of the memory sticks made everything run smoothly. When I swapped it out for the other (bad) one, things started crashing as usual.
 
I ran memtest86 on the "bad" one but only got an error in test 4. Is that enough to constitute a "bad" memory stick?
 
 

Thank you. I decided that I am going to send in the bad ram stick for RMA.
 
I wouldn't have been able to figure out this issue without you guys. Thanks so much.