So today I went about updating my computers driver's and I must have went wrong somewhere since it's crashing every few hours or so I will list a crash report below
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 8/7/2016 7:40:50 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080716-37484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xE4901)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8010CEEE901, 0xFFFF94019A186458, 0xFFFF94019A185C80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
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 Sun 8/7/2016 7:40:50 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8010CEEE901, 0xFFFF94019A186458, 0xFFFF94019A185C80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
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 Sun 8/7/2016 7:02:33 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080716-37687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xE4901)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801B30FC901, 0xFFFF9E812E41F458, 0xFFFF9E812E41EC80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
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 Sat 8/6/2016 2:03:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080616-39671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0xA (0xC800000000, 0x2, 0x0, 0xFFFFF80062AFDDD2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 8/6/2016 8:42:42 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080616-62125-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x16A9BE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80DB498A9BE, 0xFFFFDD01FD906918, 0xFFFFDD01FD906140)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\WINDOWS\Minidump
Crash dumps are enabled on your computer.
On Sun 8/7/2016 7:40:50 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080716-37484-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xE4901)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8010CEEE901, 0xFFFF94019A186458, 0xFFFF94019A185C80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
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 Sun 8/7/2016 7:40:50 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0)
Bugcheck code: 0x7E (0xFFFFFFFFC0000005, 0xFFFFF8010CEEE901, 0xFFFF94019A186458, 0xFFFF94019A185C80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
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 Sun 8/7/2016 7:02:33 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080716-37687-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0xE4901)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF801B30FC901, 0xFFFF9E812E41F458, 0xFFFF9E812E41EC80)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
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 Sat 8/6/2016 2:03:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080616-39671-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x149F90)
Bugcheck code: 0xA (0xC800000000, 0x2, 0x0, 0xFFFFF80062AFDDD2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above.
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 Sat 8/6/2016 8:42:42 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\080616-62125-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x16A9BE)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80DB498A9BE, 0xFFFFDD01FD906918, 0xFFFFDD01FD906140)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
file path: C:\WINDOWS\system32\drivers\dxgkrnl.sys
product: MicrosoftR WindowsR Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.