Win10 Random BSOD .. at my wits end

[moster_999]

Hi I am pretty much a pc novice, I bought a bundle new from CCL UK back in Nov 16 which just needed win10 installing. I installed Win10 and worked fine for a month or so then i started getting BSOD maybe twice a day, i have read many things on here about BSOD and i think i have tried most of them from mem tests to hdd tests to temp checks etc driver removals and restores, flashed the FW on the mobo etc .. finally i did a full format and re install .. and yes you guessed it its still doing it. What I will say is if i run general windows apps office mail etc its fine. I only every see it happen during a game when switching screens i run a 2 screen setup. Apologies in advice for the rant its just doing my head in 🙁 . i wonder if some expert would be able to take the time to help me, ill go back and get what logs you may need just ask. sorry if its in the wrong area.

Windows version: Windows 10 , 10.0, build: 14393
Windows dir: C:\Windows
Hardware: Gigabyte Technology Co., Ltd., F2A78M-HD2
CPU: AuthenticAMD AMD A10-7860K Radeon R7, 12 Compute Cores 4C+8G AMD586, level: 21
4 logical processors, active mask: 15
RAM: 7459426304 bytes total

Crash Dump Analysis

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 30/01/2017 12:48:40 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFC403E72ED800)
Bugcheck code: 0xEA (0xFFFFC403E72ED800, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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.
Google query: THREAD_STUCK_IN_DEVICE_DRIVER



On Sun 29/01/2017 15:13:18 your computer crashed
crash dump file: C:\Windows\Minidump\012917-8375-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22DFF)
Bugcheck code: 0x100000EA (0xFFFFBF0206CE2800, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
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 a thread in a device driver is endlessly spinning.
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 29/01/2017 10:39:53 your computer crashed
crash dump file: C:\Windows\Minidump\012917-8234-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22DFF)
Bugcheck code: 0x100000EA (0xFFFFD48563E5E080, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
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 a thread in a device driver is endlessly spinning.
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.

 

[Colif]

I would try this: http://www.tomshardware.com/faq/id-2767677/clean-graphics-driver-install-windows.html

All the errors mention Direct X, its likely to be your Graphics drivers.

 

[moster_999]

Thanks Colif, I have how followed the steps detailed. Time to see how it goes

 

[moster_999]

well i was just about to post to say its seems to be ok after running for around 5 hrs switching screens often then boom it goes again

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 30/01/2017 21:41:52 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: Unknown (0xFFFF8C09C0D515C0)
Bugcheck code: 0xEA (0xFFFF8C09C0D515C0, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER
Bug check description: This indicates that a thread in a device driver is endlessly spinning.
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.
Google query: THREAD_STUCK_IN_DEVICE_DRIVER



On Sun 29/01/2017 15:13:18 your computer crashed
crash dump file: C:\Windows\Minidump\012917-8375-01.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x22DFF)
Bugcheck code: 0x100000EA (0xFFFFBF0206CE2800, 0x0, 0x0, 0x0)
Error: THREAD_STUCK_IN_DEVICE_DRIVER_M
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 a thread in a device driver is endlessly spinning.
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.

 

[Colif]

I had a feeling it wouldn't be that easy, this error seems to follow AMD around. As soon as I saw I knew you had an AMD machine... its been a problem for 6 months, you might try some of the suggestions in that post.

updating Motherboard BIOS might help