Random BSOD on a new build.

[Bas_6_]

My PC sometimes randomly freezes or gets BSOD ( bsod only happens when gaming I believe ). All hardware is a couple days old and should be fine. I stress tested the gpu and there is no problem with it.

More info:

CPU: I7 6700k
Ram: 16Gb corsair vengeance pro
Gpu: GTX 980 Asus reference card.
Mobo: ASUS TUF S S1155
HD: one of my old builds.
PSU: 750 watt corsair platinum I believe.

Anyone know how to fix this?

 

[Colif]

Can you download and run who crashed: http://www.resplendence.com/whocrashed
it will look at the errors and give us a summary so we can see what you dealing with

Copy/paste results in here

 

[Bas_6_]

Can you download and run who crashed: http://www.resplendence.com/whocrashed
it will look at the errors and give us a summary so we can see what you dealing with

Copy/paste results in here

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 12-12-2016 16:21:21 your computer crashed
crash dump file: C:\Windows\Minidump\121216-24296-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A6F0)
Bugcheck code: 0xA (0xC10, 0xD, 0x0, 0xFFFFF802496D1501)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® 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.

Here is the log!

On Mon 12-12-2016 16:21:21 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: 0xA (0xC10, 0xD, 0x0, 0xFFFFF802496D1501)
Error: IRQL_NOT_LESS_OR_EQUAL
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.

 

[johnbl]

I would think that your bugcheck indicates that something is overwriting a drivers data with its data. the memory address 0xC10 is more likely to be part of some data structure than a real system memory address. This would be a bug in a device driver loaded on your machine or a side effect of a driver writing outside of its allocated memory space.

I would go to the motherboard vendor and update all of the drivers as a first step in trying to get rid of this problem.