Thread stuck in device driver.

theforce

theforce

theforce

Associate
Joined
5 Jan 2005
Posts
2,239
Location
Cyprus
Since l upgraded my monitor weird things are happening to my pc. Almost every time l cold boot my PC it bsods with "thread stuck in device driver". Sometimes the monitor simply looses signal and l have to restart the PC. Shutting down the monitor and starting it up again doesn't solve the issue.

I am using a Sapphire 380 connected to the screen via the DP cable that came with the Samsung monitor. I have updated the video drivers several times since then but the problem persists. I am using the latest BIOS available for my Z77 motherboard and l also uninstalled my Asus Xonar drivers just in case it was the device causing the issue but to no avail.

I have a new DP cable coming in tomorrow that hopefully will alleviate the problem but while it might solve the loss of signal l can't fathom a bad cable blue screening the system. Any ideas of what might be causing this?
 
AsRock Z77 Extreme 4
Intel i5 3570k @ stock (bows head in shame)
4x4GB Corsair Vengeance using the XMP profile.
Sapphire Radeon 380 4GB
Asus Xonar STX
Old Corsair Force SSD 128GB, 2HDD's & an optical drive.

I haven't updated the bios in ages since there aren't any new ones available. I was using DVI with my old Samsung monitor. I will try the other DP wire tomorrow and if it doesn't solve it, l will search if l have a spare HDMI cable to see if the issue persists. I will also disable the HDMI Audio driver. Wouldn't uninstalling it cause W10 to install it again on the next boot?

The weird thing is that it always happens during a cold boot. After l restart the machine after the BSOD or loss of signal the PC works fine. I have tested the RAM for hours with no errors showing up. Might just have to nuke everything and start with a fresh installation of Windows if all else fails.
 
Last edited:
Just an update. I have received the new DP cable but the issue persists. I've also enabled the optimised defaults for my motherboard but nothing changed. It's most probably a software error that a good old format will probably cure. Will format tomorrow on my day off and see if that helps with the "device stuck in thread" error.
 
I downloaded "whocrashed" which pointed to a "atikmdag.sys" error that caused the BSODs. Since then, l formatted the PC and installed the latest version of Windows 10, updated the motherboard's INF drivers with the ones found on AsRock's website. I was then greeted by the same BSOD using the drivers that came with Windows. I then installed the latest Catalyst drivers and l haven't had the issue since(that is some hours ago). Seems like a hardware error then?
 
Last edited:
Plec, l am using Windows 10 Pro x64 v1703. I didn't had a BSOD yet after installing the latest version of Catalyst drivers. The monitor still looses signal though. I finally managed to find an HDMI to HDMI cable and l hope this will resolve it. Unfortunately though, l am limited to 8bit colour instead of 10bit that the monitor supports via DP :(
Seems like a GPU or monitor error. If l lose signal with HDMI as well l will try the onboard intel gpu and see if that loses signal as well. If so, monitor RMA time.

Weird thing is that the monitor's driver disappears when you switch from DP to HDMI to DVI and you have to install the driver again for each different connection type.
 
Plec said:
What monitor do you have?
Click to expand...

It's a Samsung S27D850T. It's a 60Hz screen. Yes, l have installed the drivers for the monitor but as it seems if you connect the monitor with a different connection the monitor driver is back to generic display and you have to reinstall the driver again for the new type of connection you are using.
 
You must log in or register to reply here.
Back
Top Bottom