• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Terrible experience with XFX RX 580

Status
Not open for further replies.
Ok. I installed driver v18.5.1 from May 23, 2018.

Clipboard02.jpg

Extended view now works perfectly. This is a bug in recent AMD drivers.

RadeonSettings.exe is no longer crashing.

Same cooler.

You're right, it is the same cooler. However, the card in the review is throttling.

1st FurMark screenshot, power output is lower then expected.

2nd FurMark screenshot, clock is at 1150 MHz.

It is also unknown if the reviewer tested the card in a open case, closed one, and room temperature.
 
Last edited:
I see a lot of insults here. How about being useful and recommend a driver that is known to be stable?

There were no insults. Only frustration with your inability to look at the situation as whole.

Edit: As you can see, half your problems were fixed by selecting a different driver. Likely, the rest of your issues can be fixed by finding the incompatibility. I would bet that most of the issues people have are software incompatibilities rather than hardware. Especially with how mature Polaris is and the fact that many of the low binned chips likely were sold during the mining boom.
 
I see a lot of insults here. How about being useful and recommend a driver that is known to be stable?
Answered that question days ago:
FYI, you may want to use October or November drivers. The new feature update in December always brings with it lots of bugs until they can get them ironed out in Q1'19. It's not a new SKU so older drivers should work well with it.

RadeonSettings.exe is no longer crashing.
Because they async'd loading the games list in the December driver but if you push its buttons right, it crashes. Known issue and a major reason why I said what I said days ago.

Extended view now works perfectly. This is a bug in recent AMD drivers.
First I've heard of it. There has to be something unique to your setup that is causing that particular problem. Without system specs listed, I'm not even going to guess.

You're right, it is the same cooler. However, the card in the review is throttling.

1st FurMark screenshot, power output is lower then expected.

2nd FurMark screenshot, clock is at 1150 MHz.

It is also unknown if the reviewer tested the card in a open case, closed one, and room temperature.
AMD cards throttle their GPU clock based on GPU load. It can be 300 MHz one second, 1560 MHz the next, and then 300 MHz.
 
Last edited:
Maybe it was another thread, but, stop using furmark. Both nvidia and amd called it a power virus and put measures in place on their cards for protection. I'm not familiar with what amd did, but I know nvidia when it runs this application, boost bins drop to well below 'gaming clocks'. So it's pretty useless in that respect. 3DMark or similar. No kombuster...no furmark for GPU testing.
 
It's easier to detect artifacts in FurMark from overclocking. Other apps and games have shiny/flashy textures making it hard to spot anomalies. 3DMark and Superposition have too many scenes with flashing and flying objects.
 
Last edited:
Youre all about overkill. :p

Said a different way, you arent testing what you are supposed to be testing when running furmark. Is xxxx clocks stable in [insert activity here] if you aren't testing that clock but actually testing xxxx -200mhz??

Measures were put in place from both camps to protect cards from that program. This may be part of the reason for wonky results. Use something else... 3DMark Fire Strike (Extreme) is solid. That second test is where things usually crap out if its borderline stable. I simply loop the test when I want a long stability test or max heat. :)
 
Youre all about overkill. :p

Said a different way, you arent testing what you are supposed to be testing when running furmark. Is xxxx clocks stable in [insert activity here] if you aren't testing that clock but actually testing xxxx -200mhz??

Overclocking AMD GPUs is different than Nvidia. Insufficient voltage results in artifacts and anomalies. Some are hard to spot.
 
It's easier to detect artifacts in FurMark from overclocking. Other apps and games have shiny/flashy textures making it hard to spot anomalies. 3DMark and Superposition have too many scenes with flashing and flying objects.

In theory, but it also doesn't put an accurate load on the card(because both camps now detect it and throttle their cards when it is running), so artifacts might never show up in furmark even if the card is unstable under actual load.
 
You can lead a horse to water...

On Nvidia, you run 3DMark in a loop for a few hours. If the OC isn't stable, something will crash.

On AMD, unless the OC is extremely unstable, you'll get temporal black artifacts within the textures.

Now the 3D demos on 3DMark are full with flashing textures. Nearly impossible to spot artifacts.
 
No issues here spotting problems when helping amd users out. But you keep on keeping on...on just trying to help.
 
Maybe it was another thread, but, stop using furmark. Both nvidia and amd called it a power virus and put measures in place on their cards for protection. I'm not familiar with what amd did, but I know nvidia when it runs this application, boost bins drop to well below 'gaming clocks'. So it's pretty useless in that respect. 3DMark or similar. No kombuster...no furmark for GPU testing.

Both green and red throttle back, it was after 7970 amd started to do it

Maybe it was another thread, but, stop using furmark. Both nvidia and amd called it a power virus and put measures in place on their cards for protection. I'm not familiar with what amd did, but I know nvidia when it runs this application, boost bins drop to well below 'gaming clocks'. So it's pretty useless in that respect. 3DMark or similar. No kombuster...no furmark for GPU testing.
Youre all about overkill. :p

Said a different way, you arent testing what you are supposed to be testing when running furmark. Is xxxx clocks stable in [insert activity here] if you aren't testing that clock but actually testing xxxx -200mhz??

Measures were put in place from both camps to protect cards from that program. This may be part of the reason for wonky results. Use something else... 3DMark Fire Strike (Extreme) is solid. That second test is where things usually crap out if its borderline stable. I simply loop the test when I want a long stability test or max heat. :)
You can lead a horse to water...
In theory, but it also doesn't put an accurate load on the card(because both camps now detect it and throttle their cards when it is running), so artifacts might never show up in furmark even if the card is unstable under actual load.

No issues here spotting problems when helping amd users out. But you keep on keeping on...on just trying to help.

Well, I mean at first the card was at fault, then the second card was defective too, now the OP complaints about the drivers... except it works fine with AMDGPU in Linux? Shame on me for suggesting that it's likely something wrong with the OP's setup. Now I remember why I unsubbed. :kookoo:

Has he been living under a friggin rock since 2012?

For someone who used to run a website that had modified ATi drivers certainly has proven he can't troubleshoot worth a crap.
 
Last edited:
Maybe it was another thread, but, stop using furmark. Both nvidia and amd called it a power virus and put measures in place on their cards for protection. I'm not familiar with what amd did, but I know nvidia when it runs this application, boost bins drop to well below 'gaming clocks'. So it's pretty useless in that respect. 3DMark or similar. No kombuster...no furmark for GPU testing.
It's not just that, but both modern AMD and nVidia cards have a power caps. If that amount of power is exceeded, a lower power state is used (for AMD, but I'm sure nVidia does the same thing but in a fancier, more progressive way.)
Both green and red throttle back, it was after 7970 amd started to do it
You know, it's not so much that it sees Furmark and it throttles it, but the way Furmark hits the GPU and fully loads it so power draw will hit the cap and it will prevent it from ever hitting its highest power state. Likewise if you have a game that can't utilize all of a GPUs parts at the same time, there is less power draw at the same frequency so the power cap doesn't become the limiting factor and it clocks up.

It's really just two things:
  1. The power cap
  2. Temperature
If the maximum for either is exceeded, the GPU clocks down. Plain and simple.

I feel like the OP is playing out of an old rule book. I haven't had to think about the "hard to see" artifact problem when overclocking since I had a 4850.
 
It's not just that, but both modern AMD and nVidia cards have a power caps. If that amount of power is exceeded, a lower power state is used (for AMD, but I'm sure nVidia does the same thing but in a fancier, more progressive way.)

You know, it's not so much that it sees Furmark and it throttles it, but the way Furmark hits the GPU and fully loads it so power draw will hit the cap and it will prevent it from ever hitting its highest power state. Likewise if you have a game that can't utilize all of a GPUs parts at the same time, there is less power draw at the same frequency so the power cap doesn't become the limiting factor and it clocks up.

It's really just two things:
  1. The power cap
  2. Temperature
If the maximum for either is exceeded, the GPU clocks down. Plain and simple.

I feel like the OP is playing out of an old rule book. I haven't had to think about the "hard to see" artifact problem when overclocking since I had a 4850.

Yup any program that acts like furmark will cause the card to go into a "safe mode".
 
Yup any program that acts like furmark will cause the card to go into a "safe mode".
Not "safe mode," but to a power state that keeps power draw under the limit. It clocks down just enough to keep power and temperature reasonable.
 
Has he been living under a friggin rock since 2012?

For someone who used to run a website that had modified ATi drivers certainly has proven he can't troubleshoot worth a crap.

A lot of people here have a serious problem with the English language.

Or perhaps its difficult for you to see negative feedback regarding a specific brand or company.

God forbid if someone says something negative about AMD.

I already solved all of the problems with the card. There was nothing wrong in my setup.

As @FordGT90Concept said, AMD's December drivers are packed with bugs.

I contacted XFX regarding the DP electrical issue. Waiting for them to check the latest return inventory.

No issues here spotting problems when helping amd users out. But you keep on keeping on...on just trying to help.

Final Fantasy XV Benchmark is completely free of charge, brutal on both GPU and VRAM (uses up to 8GB on highest quality) can run in a loop and without motion blur. Textures are less flashy than 3DMark and Unigine Superposition.
 
Last edited:
:slap:
A lot of people here have a serious problem with the English language.

Or perhaps its difficult for you to see negative feedback regarding a specific brand or company.

God forbid if someone says something negative about AMD.

I already solved all of the problems with the card. There was nothing wrong in my setup.

As @FordGT90Concept said, AMD's December drivers are packed with bugs.

I contacted XFX regarding the DP electrical issue. Waiting for them to check the latest return inventory.



Final Fantasy XV Benchmark is completely free of charge, brutal on both GPU and VRAM (uses up to 8GB on highest quality) can run in a loop and without motion blur. Textures are less flashy than 3DMark and Unigine Superposition.

The only thing I saw you do was gripe and moan about the problem instead of fixing it. Now you suddenly appear again after being silent...

Fyi I already knew about the driver problems as of late, that's why you go back to an old driver derp, also it happens with greenies too.

It's easier to detect artifacts in FurMark from overclocking. Other apps and games have shiny/flashy textures making it hard to spot anomalies. 3DMark and Superposition have too many scenes with flashing and flying objects.

Try Unigen Heaven.
 
Last edited:
Final Fantasy XV Benchmark is completely free of charge, brutal on both GPU and VRAM (uses up to 8GB on highest quality) can run in a loop and without motion blur. Textures are less flashy than 3DMark and Unigine Superposition.
Cool. Use it instead of Furmark. Anything but furmark was the takeaway.
 
I already solved all of the problems with the card. There was nothing wrong in my setup.

Running a grounding an extra grounding cable is not fixing the problem. It is masking it. I would send you one of my ex mining 580s free of charge but I want to save the hassle of having to explain that the card isn't bad.
 
Running a grounding an extra grounding cable is not fixing the problem. It is masking it. I would send you one of my ex mining 580s free of charge but I want to save the hassle of having to explain that the card isn't bad.

You already restored the bios right?
 
All seriousness, they are likely going to sit on my shelf and collect dust or be emergency GPUs for friends or family. My plan was to try and do something fun with them but time is getting tough to come by.

I backed-up the original bioses so I should be good to go if I ever need them.
 
Running a grounding an extra grounding cable is not fixing the problem. It is masking it. I would send you one of my ex mining 580s free of charge but I want to save the hassle of having to explain that the card isn't bad.

The card isn't bad. Either the entire PCB is messed up, or one of the resistors.

You telling me to buy a new cable without DP_PWR, but it is part of the specification.

DP_PWR supplies power to a LED on the card.

That's right! there is a LED for DP connectivity on the card that lights up (if DP is plugged) even when the system is off.

Or in other words, the XFX RX 580 GTS XXX is expecting to receive voltage from DP.

But some of the voltage goes to undesired locations for some reason. XFX needs to figure out why.

People here keep saying "something is wrong with your setup", while it was thoroughly tested.
 
Last edited:
Status
Not open for further replies.
Back
Top