Stumped! Constant BSOD with new R7 260X OC, tried everything.

Toggle sidebar Toggle sidebar
T

tankboy

Honorable
Feb 1, 2014
4
0
10,510
So I've been trying to fix this problem for days. My old GeForce 9600 GSO video card blew up, so I bought a new Sapphire R7 260X OC, and every time I boot my computer I get BSOD within a few minutes.

When I installed it I did the following:
I uninstalled the NVIDIA drivers
Turned computer off
Removed the old card
Connected the new card
Turned computer on
Installed the AMD drivers

I've tried reinstalling the 13.12 driver. I've tried doing the complete uninstall/delete outlined here (http://www.overclock.net/t/988215/how-to-properly-uninstall-ati-amd-software-drivers-for-graphics-cards) and installing the new 14.1 beta. I've flashed the BIOS. I've updated every driver I can think of, including chipset.

Here's a screenshot of my system and crash report (this one is from a few days ago, but the crash info is still exactly the same):

11v4f35.png


Sometimes before the BSOD the display will flicker black, come back and a warning will show up in the bottom corner that "The display driver stopped responding and has recovered." AMD says that this is a windows issue - I was going to follow the instructions for workaround here: http://forums.amd.com/game/messageview.cfm?catid=444&th...
but it keeps blue-screening before I can get into the graphics key in the registry.

I'm about ready to heave the thing out the window. Any help greatly appreciated!
 
Sort by date Sort by votes
C

cklaubur

Distinguished
Oct 4, 2006
1,745
1
20,460
Try making the registry changes in Safe Mode.

That being said, there are lots of reports of issues like this regarding the 14.1 Beta drivers, myself included. My computer would bluescreen like yours, but I ended up uninstalling the drivers, rebooting, using the procedures in your first link to make certain the drivers were removed, then installing the drivers again and disabling ULPS so my second card wasn't running at full load all the time. That seemed to fix the worst of the bluescreens, but I still get a hiccup from the driver every once in a while.

Casey
 
Upvote 0 Downvote
J

johnbl

Polypheme
Nov 4, 2012
10,072
185
67,090
Bug Check 0x100000EA: THREAD_STUCK_IN_DEVICE_DRIVER_M
(graphics driver bug in this case)

Basically, the device driver is very timing dependent. There are multiple threads of execution going on in parallel. These threads synchronize communication by using various software locking mechanisms. When you use a overclocked card the timing between the processes can sometimes mess up and the threads can deadlock. This is a very common programming error. The only thing you can really do is update the drivers OR change your graphics card's overclock down until you find a setting that does not cause your driver to hang. I would suggest that you reduce your card and memory overclock to the standard clock rate for the reference card. Later I would increase the clock rates up I got more stable driver.

You can use the verify.exe and enable deadlock detection on the graphics drivers if you want to confirm the cause of the problem. It will force a bugcheck when deadlock conditions occur . Be sure to turn of the verify when you are done or it will slow down your system and cause extra bugchecks for you.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom