BSOD with no reason

[Jari_1]

Oke so i've made myself a nice gaming computer last month but now for a couple of weeeks it started blue screening left right and center without any reason. It happens randomly but around 50% more when playing CSGO. Also from time to time games just crash without BSOD. I've tryed so much that i just lost count.
Lost for hope here i am hoping someone out here can help me.

 

[Colif]

check temperatures as it could be overheating, clean dust out of fans and heatsinks (unlikely it is dusty after 1 month)

what parts in PC?

can you download and run whocrashed: http://www.resplendence.com/whocrashed
it will look at errors and might show us cause

copy/paste results in here

 

[Jari_1]

check temperatures as it could be overheating, clean dust out of fans and heatsinks (unlikely it is dusty after 1 month)

what parts in PC?

can you download and run whocrashed: http://www.resplendence.com/whocrashed
it will look at errors and might show us cause

copy/paste results in here

Overheating is not it i'm pretty sure becaus it doesnt get to warm (30°C - 40°C)

Also quick note: I've already talked to NVidia and they tryed fixing it to no succes.

MOBO: MSI H170A
Processor: Intel I7 6900 (stock cooler)
PSU Corsair CS550M
Graphics card = MSI GTX1070 8G
RAM = 16Gb DDR4

On Sun 9-10-2016 18:04:14 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100916-16234-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x95CD2)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8010DEE5CD2, 0xFFFFC9817FAE9F40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Sun 9-10-2016 18:04:14 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!g_TdrForceTimeout+0x3DCD6)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8010DEE5CD2, 0xFFFFC9817FAE9F40, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Sat 1-10-2016 20:37:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\100116-12593-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A2B0)
Bugcheck code: 0x74 (0x2, 0xFFFFDF009CC319F0, 0x2, 0xFFFFFFFFC000009A)
Error: BAD_SYSTEM_CONFIG_INFO
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that there is an error in the registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 19-9-2016 14:13:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091916-12937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0B0)
Bugcheck code: 0x74 (0x2, 0xFFFFE2801A99C9F0, 0x2, 0xFFFFFFFFC000009A)
Error: BAD_SYSTEM_CONFIG_INFO
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check indicates that there is an error in the registry.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Tue 13-9-2016 20:19:32 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091316-14984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0D0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF803E06BB380, 0xFFFF9A0190195390, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
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 an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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 Tue 13-9-2016 19:19:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091316-12218-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x5DC94)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFB65C847EDC94, 0xFFFFD28076BF09E0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32kbase.sys
product: Microsoft® Windows®-besturingssysteem
company: Microsoft Corporation
description: Base Win32k Kernel-stuurprogramma
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
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.



On Tue 13-9-2016 18:58:48 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091316-14468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A0D0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800D74E0808, 0x0, 0xFFFFFFFFFFFFFFFF)
Error: KMODE_EXCEPTION_NOT_HANDLED
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 a kernel-mode program 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 Tue 13-9-2016 14:40:18 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091316-12390-01.dmp
This was probably caused by the following module: netio.sys (0xFFFFF8005DD416FC)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF8005DD416FC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\netio.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Network I/O Subsystem
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.



On Mon 12-9-2016 19:51:40 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091216-13093-01.dmp
This was probably caused by the following module: cfosspeed6.sys (0xFFFFF809574DFDBC)
Bugcheck code: 0xD1 (0x0, 0x2, 0x1, 0xFFFFF809574DFDBC)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\cfosspeed6.sys
product: cFosSpeed Driver
company: cFos Software GmbH
description: cFosSpeed Driver
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: cfosspeed6.sys (cFosSpeed Driver, cFos Software GmbH).
Google query: cFos Software GmbH DRIVER_IRQL_NOT_LESS_OR_EQUAL



On Mon 12-9-2016 19:36:01 GMT your computer crashed
crash dump file: C:\Windows\Minidump\091216-13078-01.dmp
This was probably caused by the following module: nvlddmkm.sys (0xFFFFF800C8BD5CF7)
Bugcheck code: 0xD1 (0xFFFFB18175668300, 0x2, 0x0, 0xFFFFF800C8BD5CF7)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_d3851cb7c8216f9e\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 372.70
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 372.70
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 372.70 , NVIDIA Corporation).
Google query: NVIDIA Corporation DRIVER_IRQL_NOT_LESS_OR_EQUAL

 

[clintittech]

Hi, try installing the latest Windows Updates and Hardware Drivers (especially the video card driver).
Also I advise you to avoid beta versions of drivers, and drivers from Microsoft / Windows updates.

 

[Jari_1]

Hi, try installing the latest Windows Updates and Hardware Drivers (especially the video card driver).
Also I advise you to avoid beta versions of drivers, and drivers from Microsoft / Windows updates.

Windows was up to date. and video card drivers are now up to date aswell. But that can't be the issue if it has been crashing for so long.

 

[clintittech]

If there are software issues (outdated drivers), they do not always occur immediately. Also check for the latest mainboard drivers and BIOS updates.

I noticed that your PSU outputs 550W, in my opinion, it is better to use an 700W PSU or higher on a high performance / workstation / gaming, especially when a dedicated graphics card is being used.

 

[Colif]

list goes from newest to oldest, 1st two errors are dx, that is caused by GPU card, and your last bsod was also GPU card

netio.sys is normally lan drivers

rest mentioned are parts of windows

 

[Jari_1]

list goes from newest to oldest, 1st two errors are dx, that is caused by GPU card, and your last bsod was also GPU card

netio.sys is normally lan drivers

rest mentioned are parts of windows

How would i go about fixing that?

 

[Jari_1]

If there are software issues (outdated drivers), they do not always occur immediately. Also check for the latest mainboard drivers and BIOS updates.

I noticed that your PSU outputs 550W, in my opinion, it is better to use an 700W PSU or higher on a high performance / workstation / gaming, especially when a dedicated graphics card is being used.

They told me 550W was fine, but how would i check to make sure?

MSI update says everything is up to date.

 

[Colif]

Is that a H170A Gaming Pro? Go Here and download Live Update 6 and use it to download latest drivers for motherboard

if its a different model, find it on MSI site and download that program. I wish my motherboard had an app that made it so easy.

edit: lol. nvm this after last post

 

[clintittech]

If there are software issues (outdated drivers), they do not always occur immediately. Also check for the latest mainboard drivers and BIOS updates.

I noticed that your PSU outputs 550W, in my opinion, it is better to use an 700W PSU or higher on a high performance / workstation / gaming, especially when a dedicated graphics card is being used.

They told me 550W was fine, but how would i check to make sure?

MSI update says everything is up to date.

Regarding the PSU, I checked on NVIDIA's specs for the GTX1070, and it states that the graphics card draws 150W and the recommended wattage is 500W.
One should always keep in mind that other components use power (including mainboard, CPU, hard drives/SSDs, DVD Writers etc.)
From nvidia's specs, the PSU should be enough, but one must also take my above statement into consideration.
Also if your computer BSOD's only during gaming, then it is either the PSU is being overloaded, or a corrupted GPU driver...
Do you have an extra PSU with higher wattage than 550W? If yes, try using that and see how the computer behaves.
Also check Event Viewer for any warnings/errors.

 

[Jari_1]

If there are software issues (outdated drivers), they do not always occur immediately. Also check for the latest mainboard drivers and BIOS updates.

I noticed that your PSU outputs 550W, in my opinion, it is better to use an 700W PSU or higher on a high performance / workstation / gaming, especially when a dedicated graphics card is being used.

They told me 550W was fine, but how would i check to make sure?

MSI update says everything is up to date.

Regarding the PSU, I checked on NVIDIA's specs for the GTX1070, and it states that the graphics card draws 150W and the recommended wattage is 500W.
One should always keep in mind that other components use power (including mainboard, CPU, hard drives/SSDs, DVD Writers etc.)
From nvidia's specs, the PSU should be enough, but one must also take my above statement into consideration.
Also if your computer BSOD's only during gaming, then it is either the PSU is being overloaded, or a corrupted GPU driver...
Do you have an extra PSU with higher wattage than 550W? If yes, try using that and see how the computer behaves.
Also check Event Viewer for any warnings/errors.

I dont have a diffrent PSU and its not only when gaming. It has happend on startup aswell.

Also i flaged your post as answer by accident.

EDIT: i ran a PSU calculator http://outervision.com/b/19uGRt

 

[Jari_1]

Is that a H170A Gaming Pro? Go Here and download Live Update 6 and use it to download latest drivers for motherboard

if its a different model, find it on MSI site and download that program. I wish my motherboard had an app that made it so easy.

edit: lol. nvm this after last post

BIOS is now up to date aswell!