You have some memory corruption. Please run memtest86 by following these instructions.
RAM - Test with Memtest86+
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck A, {70a0a117a, 2, 1, fffff8000357ac9f}
Probably caused by : memory_corruption ( nt!MiIdentifyPfn+26f )
Followup: MachineOwner
You are getting graphics driver errors.
I see your graphics driver is up to date so can you please follow these instructions on how to safely remove and install graphics drivers.
NVIDIA Drivers - Avoid Problems
Code:
fffff800`00b9c5d8 fffff800`032cf169 : 00000000`0000000a 00000000`000dc09f 00000000`0000000a 00000000`00000001 : nt!KeBugCheckEx
fffff800`00b9c5e0 fffff800`032cdde0 : fffff880`049ec420 fffff880`010c0f04 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff800`00b9c720 fffff880`0f6b553f : 00000000`00000000 fffff880`0f64e7de fffffa80`0dc0d8e0 00000000`00000000 : nt!KiPageFault+0x260
fffff800`00b9c8b0 00000000`00000000 : fffff880`0f64e7de fffffa80`0dc0d8e0 00000000`00000000 00000000`00000000 : nvlddmkm+0x21253f
This indicates your graphics driver is causing a page fault by accessing a certain page of memory that is isn't authorized to do so.
Code:
nt!NtWaitForWorkViaWorkerFactory+0x1fc:
fffff800`032b4d7d f04c0fb129 lock cmpxchg qword ptr [rcx],r13 ds:fffffa80`1387e220=????????????????
A compare and exchange call has been made which has failed.
It wouldn't surprise me if your CPU is failing from the amount of different bugchecks you are having.
Please follow these instructions on how to run Prime95 to stress test your CPU
Hardware - Stress Test With Prime95
You are also having errors for your network drivers.
Please enable Driver Verifier to find the driver responsible.
Follow these instructions.
Driver Verifier - Enable and Disable
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck D1, {fffff88101b4608c, 2, 0, fffff88001a853a1}
Probably caused by : tcpip.sys ( tcpip!memmove+1d1 )
Followup: MachineOwner
Post back the results.