THREAD_STUCK_IN_DEVICE_DRIVER

  • 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 :-(