Windows 10: Thread_stuck_in_device_driver

Hello,

I've been trying to solve this issue for a whole week, and no progress at all. I first noticed this problem when I put my PC to sleep, and on the wake up, I would get BSOD (THREAD_STUCK_IN_DEVICE_DRIVER). Same thing happened when I would make shutdown from windows, and when turning my PC back on, I would get the same BSOD. I tried reinstalling my GPU drivers on all possible ways found on the internet (using DDU, manually through device manager, etc) with no success.
Fun thing is that I also tried formatting my disk and I tried installing fresh windows 7, and would get exact same issue.

So today, I completely formatted my disk again, installed fresh Windows 10 pro x64, made all Windows updates, and updated my GPU driver. During that process my computer had to restart multiple times, and it booted successfully every time. First thing I did after that was to shutdown my computer and turn it back on, and I got it again (THREAD_STUCK_IN_DEVICE_DRIVER). You may think that my GPU is faulty, but I tried it in my friends computer 2 days ago with 14.9 Catalyst drivers, and it run without any problems, waking up from shutdown and sleep worked flawlessly.

Please help!

:)

 

Windows 10 Issue with AMD Radeon HD 7970m, possible failed GPU?

I´m having a similar problem with my ATI 7970M.

The only diference is that on the BSOD I received the message "THREAD_STUCK_IN_DEVICE_DRIVER"

 

THREAD_STUCK_IN_DEVICE_DRIVER

Any more ideas?

 

Hello harko and welcome to 10forums! *Smile

Even though you say that you have tried reinstalling the GPU drivers, they are still older than the latest version available for your GPU, so please without further ado head over to AMD drivers and download:
AMD Support

NOTE! Though before installing the new driver I would recommend that you perform a full removal of the current drivers! I would recommend that people use Revo Uninstaller to remove the GPU drivers.

Cheers, Boris *Smile

 

I did full removal of current drivers with Revo Uninstaller as you instructed me, installed new drivers (16.3) and got the same exact issue. Please don't tell me to wait for newer drivers to be released because there's something else which is causing this problem (possibly windows 10 update???) because I've been running Windows 10 for more than 6 months without any problems.

I attached new file.

Thanks

 

FYI, if you are overclocking anything please revert back to stock while troubleshooting. Overclocking pushes the component a (small) bit what may cause various of problems if it appears to be unstable.

I see 3 0xEA crashes which is thread_stuck_in_device_driver, all of them seem to be caused by the AMD display drivers due to a TDR (Timeout Detection and Recovery) problem. Besides of that there is also a 0x10E crash which is a crash that focuses more on the vram.
Your display drivers are certainly updated, but please try to remove the display drivers a little different and make sure to install with no software.
Please uninstall everything of AMD using Display Driver Uninstaller and install new drivers from AMD.
Attachment 69737

If above doesn't help, please stress test your graphics card using furmark.
Make a screenshot of the result after the test and post it *Smile





Diagnostic test

GPU TEST


Run Furmark tutorial



Note Run Furmark for around 30 minutes



Warning Your GPU temperatures will rise quickly while Furmark is running. Keep a keen eye on them and abort the test if temperatures rise too high
Code: ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 100000EA, {ffffe00032f28040, 0, 0, 0} *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+24 ) Followup: MachineOwner 1: kd> lmvm atikmdag Browse full module list start end module name fffff801`e9110000 fffff801`ea61f000 atikmdag T (no symbols) Loaded symbol image file: atikmdag.sys Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys Image name: atikmdag.sys Browse all global symbols functions data Timestamp: Wed Nov 04 22:39:32 2015 (563A7B14) CheckSum: 014AB74E ImageSize: 0150F000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_MEMORY_MANAGEMENT_INTERNAL (10e) The video memory manager encountered a condition that it can't recover from. By crashing, the video memory manager is attempting to get enough information into the minidump such that somebody can pinpoint what lead to this condition. Arguments: Arg1: 000000000000001d, The subtype of the bugcheck: Arg2: ffffe000382f42a0 Arg3: 0000000000000000 Arg4: 0000000000000000[/quote]

 

I'm sorry for the late response. I now have dual boot with windows 7 and this same windows 10, my computer was updating windows 7 for a whole day so I couldn't respond. Just to let you know, Windows 7 is now fully updated with latest GPU drivers, and BSOD is still there...


Anyway, I did everything by your instructions on Windows 10. Uninstalled everything with DDU, extracted drivers with 7-zip, and installed it through device manager as shown in instructions. Tried to make a shutdown, resulting in same BSOD when turning computer back on.
So I installed Furmark, and ran it with the same settings as stated in instructions for around 30 min. There was no artifacts, everything seemed fine, max temp was 73°.
PS. I really don't think GPU is the problem since I tried it at my friends computer and it worked without any problems whatsoever.


New dump file and requested screenshot are in attachment.

 

I think the problem also might be that there aren't any drivers for either W8.1 and W10.

So I don't think your motherboard has even been tested for running Windows 10.

You may however want to try and run this update tool from Intel, for example the motherboards Chipset drivers are from Intel.
Intel® Driver Update Utility

Cheers, Boris *Smile

 

This update tool finds nothing to download for my computer.

Well that could be the problem but I got the same exact issue on Windows 7 so I don't know if this is due to windows or it's hardware related.
I ran MEMTEST for 10 passes and there was no errors, made disk check, also with no errors, stressed cpu and gpu without errors, so I really don't know what to do... *Sad

 

Okay I did some more digging and troubleshooting and it surely is your graphics card that is causing your PC to crash, and if you have tried rolling back the graphics card drivers and you haven't found a stable driver then it's safe to say that the GPU is faulty and needs to be replaced.

 

As much as it's reasonable to think my gpu is faulty there is as much reason to think it's not. I mean, I tried it in another configuration few days ago (after I got this issue) and it worked like the first day I bought it. It still does the job even on my computer, only problem is that damn startup. At my friend's computer there was no startup issues whatsoever, but here on mine there is.
Is it possible that my motherboard is one to blame, I kinda get that feeling because that's the only thing that we cannot really test. Is there a way that there's some hardware related issue on motherboard that make's it look like it's GPU's fault when in fact, that's not the case??

 

harko, please do these two things:

right click on the Windows logo key in the left bottom corner -> command prompt(admin) and type these commands:

sfc /scannow - press enter and let it run, it might take some time.

Dism /Online /Cleanup-Image /CheckHealth - same as above, press enter and let it run.

 

So I did this sfc scan and got the following:

Code: "Verification 100% complete. Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not supported in offline servicing scenarios."[/quote] Dism returned the following:

Code: Deployment Image Servicing and Management tool Version: 10.0.10586.0 Image Version: 10.0.10586.0 No component store corruption detected. The operation completed successfully.[/quote]
I attached this log from sfc.

 

Alright thanks, I'll have a look tomorrow, off to bed!

 

The SFC log isn't required, it is ONLY required when SFC cannot fix the problem(s) *Smile