cancel
Showing results for 
Search instead for 
Did you mean: 

Drivers & Software

Adept II
Adept II

THREAD_STUCK_IN_DEVICE_DRIVER - RX 480 - 17.9.3

  • RX 480 (MSI gaming 8GB - NO OC)
  • Desktop
  • Windows 7 x64
  • Crimson 17.9.3
  • Display:
    • LG 34UC98-W 3440x1440 75hz over DP
  • Motherboard:
  • FX 8350 (NO OC)
  • PSU: Pure Power BQT L7 630W (88%)
  • RAM: 24GB (NO OC)

All games randomly hang. It can happen after 5 minutes. It can happen after 3 hours. When lucky, it sometimes does not happen at all. The rendered content of window becomes black and nothing happens. You need to terminate the app. Sometimes it terminates by itself. There is also no BSOD, but windows notifies that it had to reset the display because it went into an infinite loop.

After such a crash, when I try to open Radeon Settings, it crashes too. I checked windows events and it is always an 0xc0000005 exception code (access violation).

An exaxmple of an event rom the radeon settings crash attached as "exception1.xml". I think it just expected something in memory area, that was freed and located elsewhere by windows, when it did the reset, hence the 0x5 crash.

It does not seem to be related to GPU load. It even happen with very old games, where the GPU is not at heavy load and has 62° and ~100W consumption (chip only, but com on, even if the whole consumption is twice that much or even more it is still safe with the 630W). The highest the GPU even reach in temepratur is 73° for a moment. Usually it around is 69-71°.

I do not have any kind of crashes, when not running 3D applications. With RX480 and previously the HD7870 (same issues), I had dozens of iterations of "DDU, clean install", over multiple crimson major versions without any changes. Recently I bought an SSD drive and therefore had a fresh windows installation with everything up to date (patches, drivers) and it did not fix the problem in any way.

I initially had the FC bios version which is the last non-beta. Checking out the latest beta did also not resolve the problem (with default optimized settings too).

I wanted to find out, if it also crashes when I run, lets say 3dmark11. The fist run did cause a BSOD. The second two runs did not.
Initially I checked it myself via event monitor, but later found it easied with "whocrashed" tool, which confirmed my info:

-----------------------------------------------------------------------------

On Fri 13.10.2017 18:01:05 your computer crashed

crash dump file: C:\Windows\Minidump\101317-12573-01.dmp

This was probably caused by the following module: dxgkrnl.sys (dxgkrnl+0x6F63)

Bugcheck code: 0x100000EA (0xFFFFFA8019D61060, 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 Fri 13.10.2017 18:01:05 your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: atikmdag.sys (atikmdag+0x5A800)

Bugcheck code: 0xEA (0xFFFFFA8019D61060, 0x0, 0x0, 0x0)

Error: THREAD_STUCK_IN_DEVICE_DRIVER

file path: C:\Windows\system32\drivers\atikmdag.sys

product: ATI Radeon Family

company: Advanced Micro Devices, Inc.

description: ATI Radeon Kernel Mode 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. It is suggested you look for an update for the following driver: atikmdag.sys (ATI Radeon Kernel Mode Driver, Advanced Micro Devices, Inc.).

Google query: Advanced Micro Devices, Inc. THREAD_STUCK_IN_DEVICE_DRIVER

-----------------------------------------------------------------------------

Over the long period of troubles I can for certain tell, that it does not have anything to do with power draw or temperatur, because it happens random with measurements I did in background. They show no relation from crash moment to power or temperature. As said above, it can even crash on crapy old games. I would blame the game but the crash is the same type of crash as in new games.


I did run memtest86+ for 5 hours without any issues detected. HDD damage is excluded, as it continues to hang/crash even with the new SSD I just recently installed.
Not sure how "safe" it is, but any tools I used for V-readings did show it does not exceed the 5% neither negative, nor positive on load.

Also tried run on 60hz, disable freesync and 1000 other things, which would blow up the post here.


I had this kind of problem once - long time ago - which made me prefer nvidia cards. At some poin ATI/AMD managed to solve the driver problem (at least for me) and this made me like the products. Even though I kind of hate Nvidia and its policy for everything, I'm so annoyed by this now that even though I bought an freesync monitor, I think I will send the card back to amazon (~1 year warranty left) and replace it with an NVIDIA, when this isn't going to be solved soon.

Kind of the last attempt for me here :-(

Message was edited by: Matt B

We have updated the title of this discussion with relevant details to better describe your issue.

0 Kudos
31 Replies
Esteemed Contributor III

Re: THREAD_STUCK_IN_DEVICE_DRIVER

Try using the latest AMD driver from AMD Support. Its version 17.10.1 here: Desktop .

This post from Windows Forum : Thread stuck in device driver - RX480 | Windows Forum indicated a conflict with another .sys driver on the computer. It also makes one or two suggestions to correct it.

Here is a slightly older thread from this AMD Forum about the same issue with a RX-480. It also gives suggestions on how to correct the issue you are having. RX 480 BSOD and Driver Crash ​​. This will probably be more of help than the link above from Windows Forum.

Adept II
Adept II

Re: THREAD_STUCK_IN_DEVICE_DRIVER

As I said I have DDU & clean install over multiple MAJOR versions and the first thing you propose is try latest drivers ^^. Well I install them anyway, but I do not believe it will change much. Nothing in patch notes, that seem to be related to my problem.

None of the apps and drivers on my system running, which were mentioned conflicting in the discussions.

I'm not entirely sure what they mean by 150W max on PCIE and 6 pins. I have a 8 pin PCIE connector on the RX 480 (MSI gaming 8GB).

0 Kudos
Esteemed Contributor III

Re: THREAD_STUCK_IN_DEVICE_DRIVER

** Windows 7 and Windows 8.1 must be fully updated before attempting to install any AMD driver. All 'critical', 'recommended', and 'optional' (no language packs,etc) updates as well as any Service Packs (SP) must be installed before any attempt to install graphics drivers. If you do not get this message .... keep installing until you do:

0 Kudos
Adept II
Adept II

Re: THREAD_STUCK_IN_DEVICE_DRIVER

So this card requires RDS 8.0, RDC 8.1, DTLS and TLS1.1/1.2 for RDS to function properly?

Do you even know what it is?

I do.

Guessing around and pulling switches is not going to help.

0 Kudos
Esteemed Contributor III

Re: THREAD_STUCK_IN_DEVICE_DRIVER

Sometimes updating to the latest driver, even though it seems to not have anything to do with your issue, may fix the problem you are having with your GPU card.

Also by taking an Attitude with post that you feel are not helpful isn't going to help your cause with future posts in this forum. 

Adept II
Adept II

Re: THREAD_STUCK_IN_DEVICE_DRIVER

If you talk about the post with optional updates:

I personaly never give someone hints to do something, when I do not know why it should help him. Although I very like to help people and explain why something is the way it is. I don't like to introduce "damage" to others though. The hint obviously looks like "no matter what there is -  I have no clue, - just install it all" - I argued why the post was such one.

This method does not only not help fix the issue, it even increase entropy. This in turn can result in other issues, by adding up unnecessary changes. Many people are just unaware of this. The internet is full of "hints" like that. From the right point of view it looks like people suggest sorcery. Like dance around a pot of brew made of substances you don't know the effect of and it will heal you. Or propose exorcism as a solution for a health problem.

In your post I agreed its a good point to install update, even though it is goind to unlikely fix it, since I did it for over a year now ;P Nothing of "attitude" there. It just takes a while to see if the problem is gone or not. And the other poins were good to check and useful. They actually might have been my issue, but sadly not .

0 Kudos
Adept II
Adept II

Re: THREAD_STUCK_IN_DEVICE_DRIVER

So after driver update yestereday for 3 hours no crashes. But only a coincidence. Today it crashed harder than ever. Usually windows manages to recover, but this time I got a BSOD (which I could not see, even though autorestart is off, but I know from dump and event monitor).

-------------------------------------------------------------

On Tue 17.10.2017 19:49:13 your computer crashed
crash dump file: C:\Windows\Minidump\101717-12823-01.dmp
This was probably caused by the following module: atikmpag.sys (atikmpag+0xF818)
Bugcheck code: 0x116 (0xFFFFFA801CDE04E0, 0xFFFFF8800420F818, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR
-------------------------------------------------------------

On Tue 17.10.2017 19:49:13 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: atikmpag.sys (0xFFFFF8800420F818)
Bugcheck code: 0x116 (0xFFFFFA801CDE04E0, 0xFFFFF8800420F818, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\atikmpag.sys
product: AMD driver
company: Advanced Micro Devices, Inc.
description: AMD multi-vendor Miniport Driver
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.
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: atikmpag.sys (AMD multi-vendor Miniport Driver, Advanced Micro Devices, Inc.).
Google query: Advanced Micro Devices, Inc. VIDEO_TDR_ERROR

-----------------------------------------------------------

0 Kudos
Adept II
Adept II

Re: THREAD_STUCK_IN_DEVICE_DRIVER

Yep, they did not install important updates, and now? As you sure read I did. So what?

0 Kudos