Gigabyte WF3 Radeon R9 280x OC (R2.0) - Unstable?

Toggle sidebar Toggle sidebar
m3kun

m3kun

Honorable
Jan 14, 2014
31
0
10,530
Hello!

I got me the card mentioned in the topic and it comes with +100mhz factory overclock (1100mhz GPU). The cooler runs it at 65°C on load and everything is okay. The memory is not overclocked.

Now after using it for about 2 weeks i had two issues where the first suggestions to fix was to underclock (or "undo the oc").

1) Origin/Battlefield: directX crash - DXGI_ERRORDEVICE_HUNG

2) OBS (Open Broadcaster): Texture->Map crash, gpu hung, driver auto-reset.

Since all my other games and apps run totally fine, should i be worried ?? Should i really just downclock? Isn't the stability guaranteed by Gigabyte?

Help!
 
Solution
s4in7
It's probably a combination of the software and hardware--it's rare that factory OC isn't stable, but it sounds like the solution is to back it off to stock clocks using Afterburner and definitely notify Gigabyte to see what they say.
Sort by date Sort by votes
s4in7

s4in7

Honorable
Feb 14, 2014
913
0
11,360
Use MSI Afterburner to set the clocks back to stock and see if you still get the error--using catalyst control center to OC always results in crashing or throttling for me. Afterburner has been a savior :)

If you don't get the error after reverting to stock, then use Afterburner to clock it back to factory OC and see if it crashes.

What's your power supply by the way? Any chance you're close to maxing it out?
 
Upvote 0 Downvote
s4in7

s4in7

Honorable
Feb 14, 2014
913
0
11,360
Oh and before all that, express uninstall all AMD software from Programs and Features, download display driver uninstaller, reboot into safe mode and run Display Driver Uninstaller, reboot and install the latest 14.2 beta from AMD.
 
Upvote 0 Downvote
m3kun

m3kun

Honorable
Jan 14, 2014
31
0
10,530
Okay, i will do that. I thought i'll wait for final, but it's worth a shot.

My PSU is a Corsair AX860. Bought it for going crossfire soon, which is why i am extra worried about these issues with the Gigabyte factory OC.


UPDATE #1: I am on 14.2 catalyst now, with stock (oc) speed.

2 hours later, i am still playing BF3 with everything enabled and didn't crash. With the previous driver i had to disable "Ambient Occlusion" to not crash. But i have only tested one map, so take this with a grain of salt. Will keep this updated until it appears to be stable. Then the driver update to current beta is the solution.

UPDATE #2: After a longer break i went back into the game and crashed right away. I lowered the clockspeed to 1075 and went back in.. no issue since. So that brings us back to the original question: Is the "Gigabyte OC" flawed or is it just the software? Is this considered "normal"? Why does the software even care what my speed is? Shouldn't it just do whatever it does, only faster? hmmpf.. i'll report back.
 
Upvote 0 Downvote
s4in7

s4in7

Honorable
Feb 14, 2014
913
0
11,360
Are you setting the OC in Afterburner? If not, try that. Disable any OC you have in Catalyst Control Center or Gigabyte software and OC exclusively in Afterburner.

It sounds like your card isn't the issue...software is most likely the culprit so try Afterburner and let me know.
 
Upvote 0 Downvote
m3kun

m3kun

Honorable
Jan 14, 2014
31
0
10,530
Yup, i use Afterburner since i got my PC, but i never OC'd anything. The only "OC" in my system is the factory-OC from the card and is actually the default (in CCC).

After i installed the latest Beta driver i have not touched any setting so AMD's overdrive is disabled and everything else is "as installed", too. However, DirectX crashed on me again yesterday which means that the driver update didn't solve the problem.

Since then, the only thing i did was to under-clock it by 25mHz down to 1075 using Afterburner. I played with that speed for a few more hours and had no problems anymore. But i want to verify this so i will play some more now and see if it happens again.

I usually would say: "game/software is just poorly coded". But if underclocking the card helps, then it is something with card or am i wrong? Would be great if more owners of this card could chime in and share their experience.

Will report back in a 1-2 hours.
 
Upvote 0 Downvote
s4in7

s4in7

Honorable
Feb 14, 2014
913
0
11,360
It's probably a combination of the software and hardware--it's rare that factory OC isn't stable, but it sounds like the solution is to back it off to stock clocks using Afterburner and definitely notify Gigabyte to see what they say.
 
Upvote 0 Downvote
Solution
m3kun

m3kun

Honorable
Jan 14, 2014
31
0
10,530
So i still got those errors after all and did some more testing

For reference, these are the errors i am getting:
http://i.imgur.com/H23EhRX.jpg
http://i.imgur.com/9avUvG9.jpg

Affects Battlefield 3 and 4 and it is reported to affect all other games sold on the Origin platform (including the upcoming "Titanfall").

As you said, it is rare and it could be my hardware combination. But since it is limited to two applications at this point, i doubt that my hardware vendor of choice is at fault. The temperatures are fine and everything else is up to date and the card has good reviews everywhere.

If anyone reads this at a later date: Yes, i have used beta drivers in the screenshots, but the same message also appeared on stable drivers. It is not the drivers and also not AMD or Nvidia. If you google for the error message you will find all sorts of cards and chipsets. The only thing they have in common is that they try to play games from Origin (and that they probably have some sort of OC running).

The solution that works for my card (1100mhz default speed) is to down-clock the card by 25mhz to a total for 1075mhz using "MSI Afterburner".

Thanks for you help up to this point, s4in7! Much appreciated
 
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