Windows 10 Frequent, Semi-random BSODs (Thread stuck in device driver)

S

SpaceKitkat

Member
Joined
Sep 17, 2016
Messages
42
As the title says, almost* every time I launch a video game (specifically, a minecraft mod), I get a BSOD with the error "THREAD_STUCK_IN_DEVICE_DRIVER".
I'm also getting them more and more frequently just using google chrome, even just now while trying to get minidump log.
Checking the log, there was something about atikmdag.sys, and my problem seems to be very similar to this thread:
However, that thread's main solution was when someone checked the logs, they listed drivers that needed to be removed, and I don't think I have any of the same drivers.

After a bit of googling, a couple "easy" solutions were to update my BIOS and reinstall GPU drivers.
So I uninstalled all of my display drivers, deleted everything AMD, used DDU (Display Driver Uninstaller), restarted into my BIOS, updated my BIOS successfully, installed the new GPU drivers (Radeon Crimson edition software, for an R9 290), and restart my computer.

I've also performed several Windows diagnostics, including a RAM check, disk checks on all of my hard drives, and a "sfc /scannow" via CMD. All have come up with no errors.
I tried to add the minidump W7F log, but it said the file size was too large.. lol (RIP).
I've uploaded it to
but if it needs to be uploaded elsewhere, just let me know.
If any other logs are needed, I'll supply them ASAP. Any help is very much appreciated, as I work from home and this is currently my only available computer!
 
Solution
C
I had a look through your thread and signed up to chime in.

I have an R9 290 and the exact same problem, it has plagued me for the majority of the year. You may stop butchering your PC now.

It is categorically a result of AMD's drivers.

I am not exactly sure at what point the issue arose, but the same very frequent yet erratic BSOD/crashes on wake up have been present for the last dozen or more driver versions.

A poster on another forum found a BIOS altering solution that I didn't want to replicate, but this is what he discovered. It seems related to a new driver based power saving system that lowers the clock speeds of your card during idle situations. This was "improved" at some point over the 16.xxxx series of...
Sort by date Sort by votes
Hello Circinae,

thank you for that updated information. I also think it is annoying that we have to fight a regression introduced by AMD update.
For me with the newest driver and that Registry tweak i had only one crash yet.
I didn't check without the registry hack. It could also be the new driver or the crashes are still to come.

BR
 
Upvote 0 Downvote
Well, I can safely say that the newest Crimson driver update does not fix the BSODs at all. I only had Steam open, alt tabbed to open chrome (habit) and got a BSOD. I'll try that registry hack now.
 
Upvote 0 Downvote
All dump files were the same Bugcheck EA.

As already mentioned it's either the card or the driver itself. I tried to see if others had experienced anything like this by doing a search and I did find one case where it was eventually discovered that the fix lay within the driver. The users issue eventually stopped via a driver update.

Have you followed AMD's instructions on how to install the driver to the letter?

Link Removed

Other than that the only other thing I can suggest is pop over to Guru3D and try going through their drivers:
Link Removed

In fact two drivers were released last week by AMD, have you tried both?
Graphic Drivers
 
Upvote 0 Downvote
Yes, I have followed the instructions to the letter. I've removed/uninstalled all AMD drivers, ran DDU, restarted my computer, had no applications running, and installed the new drivers. (A total of 3 times now)
I have updated to to 16.11.2 this morning, and about 30 minutes later I had a BSOD, so the driver definitely has not fixed it.
I'm currently trying out Sven's idea using the RadeonMod program by Guru3D for the registry tweak, to disable Crimson Power Saving mode.
I'll report if I get any more BSODs.

Did you check out that thread I linked? The majority of the users posting there have almost the exact same issue that Sven, Circinae, and I are having, with our R9 290s. It seems that no one in that thread has found a solution either, though.


Edit: Going back to that thread I linked, the "more like this" sidebar has several more threads with the same problem. It seems like no one has found a solution, other than rolling back to older drivers, or.. buying an NVIDIA GPU. Rolling back to previous drivers is about as bad as having these BSODs, as most of the games I play are ones released recently, that don't have the optimization of AMD's drivers from 6+ months ago.

Edit2: Threads that have similar issues: Blue Screen Of Death THREAD_STUCK_IN_DEVICE_DRIVER | Community
THREAD_STUCK_IN_DEVICE_DRIVER | Community
thread_stuck_in_device_driver | Community
THREAD_STUCK_IN_DEVICE_DRIVER THREAD_STUCK_IN_D... | Community
AMD Radeon R9 200 Driver Crashes in Windows 10 | Community

I'm sure there's even more than that, but this issue is very clearly an AMD driver issue, and not one that any of us can correct just by updating. It seems our only solutions, at the moment, are to roll back to 15.11 or 15.12, or just buy an NVIDIA.


That said, I'm still testing this registry tweak, so I'll still report back if there's any more BSODs.
 
Last edited:
Upvote 0 Downvote
Hello SpaceKitkat,

i contacted AMD support regarding this issue. I will point them to our thread and the thread of the others to proof that it is not a fault of our card but a driver regression problem.
My computer after the registry fix is pretty reliable. I only had one crash after i wanted to leave a game after some hours of play.

BR

Sven
 
Last edited:
Upvote 0 Downvote
You could if you want the optimisations install a set that works and then update to the latest but only install the application profiles.
 
Upvote 0 Downvote
I can say with confidence that using Clock Blocker and changing the "Default" setting to "Block", then having it enabled stops the crashes, regardless of the driver version (I'm running the latest). Make sure the program is set to start when Windows starts and as I mentioned before, it will increase your gfx card's idle temperatures (from 46C to 51C for me) and obviously the energy consumption. You are able to give it custom setting for particular applications, so with more tweaking you can probably find a better set up.

EDIT: This was mainly aimed at SpaceKitKat as this is a third, albeit a less than perfect, alternative.
 
Upvote 0 Downvote
Hello Circinae,

this is a very valuable information as it proves the point that the current DVFS (dynamic voltage and frequency scaling) software implementation is broken and the root cause of the mess.
The old driver not crashing proves that it can work with our cards and the cards are not broken (AMD / XFX argumentation was: your card is broken RMA it, if out of warranty, which I am, you are on your own).
The summary is that it is a fault introduced by driver changes (driver regression) and has nothing to do with our cards.

AMD should analyze their changes and fix it.

It is interesting that your card goes to 51°C only. My card went to 90°.
Can you describe which settings you used with the C[l]ock blocker ?
 
Upvote 0 Downvote
I'm still testing out the tweak in RadeonMod, but so far I haven't had any BSODs, and I've been stressing alt-tabbing a lot.
That said, it's only been one day. lol
 
Upvote 0 Downvote
Hello Circinae,
i don't understand how it can not work. Didn't you run the Radeon Mod with Administrator rights ?
In my understanding it is just modifying the registry. After that you have to reboot of course.
BR

Sven
 
Upvote 0 Downvote
The RadeonMod Registry hack is not working for me.
I already had 3 BSOD since then.

Circinae please can you post your ClockBlocker settings. For me the heat is getting very large.
 
Upvote 0 Downvote
sven31415 said:
61 ° C with the fan running at 42% (which is already a lot).
Click to expand...
That's not too bad actually. If it starts to get to temps like 90 - 100c then you may need to check the heatsink. Try removing the side panel and run the test again.
If the temps are a lot lower then you know it's possibly an airflow problem.
 
Last edited:
Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

  • Solved
Windows 10 BSOD for nearly a year - DEVICE STUCK IN DEVICE DRIVER
Replies
3
Views
1K
kemical
P
  • Solved
Windows 10 Thread stuck in device driver - RX480
Replies
12
Views
5K
kemical