r/Amd•
Koreenium

Can GPU's mend themselves?

Discussion

I know that many things have break-in period. I would assume that GPU's might have this aswell? But what I have experienced is bit odd. Not sure if the card has mended itself or I have caused even more damage.
A while ago when the RX 580 got realeased I flashed one of those bioses on my RX 480 and it caused damage to memory or something related to it, not sure but it did cause damage. Before damage I was able to run my memory at 2220mhz and got 0 errors, at 2250mhz I got maybe 1-10 errors per hour. After the damage I got around 50-100 erros per hour with memory at 2220mhz and with 2250mhz around 1000+ errors per hour. So I accepted that I fucked up. Oh well. But I decided to mine some coins and I got my card to run at 27mh/s with 2200mhz memory. I was getting over night about 600 memory errors, fine. Then I decided to edit memory timings to make them tighter for better mining power. Got mining power to 29mh/s with memory at 2175mhz and around 600 memory errors per hour. But now couple of weeks later I can mine over night at 30mh/s with memory at 2220mhz and I only get around 10-20 memory errors. What the? How is this possible? Did my card mend itself or is it not showing memory errors properly anymore? I don't have artifacting or any other issues when mining.
Only things I did to the memory besides changing timings was changing the memory voltage (actually voltage controller voltage?) from 1v to 0.9v to save power when mining.

Posted Jun 15, 2017, 1:09 PM UTC

09
loveTooAMD1800X @ 4GHz | 2x16 3000CL15@2933 | Fury @ 1100/533 | B350-PLUS•

what

4
KoreeniumOP[ RX 480 Nitro+ | 1300mhz @ 1056mv ] --- [ i5 3570K ]•

yes

3
loveTooAMD1800X @ 4GHz | 2x16 3000CL15@2933 | Fury @ 1100/533 | B350-PLUS•

^what

2
kims681i5-6500| RX 480 Strix 8GB•

If you want to mend anything, you first need a hammer

4
KoreeniumOP[ RX 480 Nitro+ | 1300mhz @ 1056mv ] --- [ i5 3570K ]•

I don't think my RX 480 is made in russia.

2
Sen91•

Lol

2
kekate•

sick lol

2
Portbragger2•

No. No. No.

I tell you something. 99% of the people who say "oh my GPU died" or "since I did that I get artifacts I believe I damaged my card"... have a SOFTWARE ISSUE.

Cards don't mend themselves. And on the other hand cards also don't get damaged as easily as some think or "self-destruct" after a small number of 2-3 years ...

And people also need to stop blaming everything that happens on component degradation... that's not how it works. Yes sure this phenomenon exists, but it doesn't manifest itself in the way like people describe their issues. If you have a degrading component... the card works normally up to the point where it just doesn't anymore.

I use a GTX 8800 in a old fun rig of mine... and I use that card for what... 10 years now? I had so many times where drivers or OS updates caused problems ... and one could think "oh my GPU is dead" but it was always fixable through driver reinstall / OS reinstall / something else....

The card is still running like a champ.

So please. Stop labeling your hardware as "dead" or "dying" or "damaged" when it is still running but just has an issue which has to be fixed by properly reinstalling drivers/system because something got fucked up.

There's nothing more to say, because talking more about it gives me cancer.

2
KoreeniumOP[ RX 480 Nitro+ | 1300mhz @ 1056mv ] --- [ i5 3570K ]•

I am certain that my card has physical damage because I used different bios that was designed to work with completely different voltage controller. After using this other bios I not only get a lot more memory errors but my card artifacts far more when these memory errors happen. Also none of the softwares can read GPU VRM and other power values correctly anymore. GPU core current, GPU core power, GPU VRM current in/out and GPU VRM Power In/out don't show any values when idling while they always showed values before. All the values are also much lower than they were before.
This is not a software related problem as reinstalling software did not fix or imrpove any of this. Neither did going back to original BIOS.

3