First of all, this is sort of a crosspost with L1T forums, chaning it up since I don’t see a lot of activity on this kind of topics over there, so here goes:
I need a modern-ish low power-ish AMD card and I managed to pick up this GigabyteRX 5500 XT OC 8gb (the two fans model) for dirt cheap which would fit the bill of my use case if it worked reliably.
As luck would have it, it mostly works, it just has a bad habit of crashing the system as soon as I try to do anything graphical in nature with it. If I lower the power limit by 10~15%, however, it will happily benchmark for hours on end.
I did re-paste the die and check the thermal pads and all seemed to be in order (but again, if anyone has specific ideas here I’m all ears).
I thought about editing the vbios to lower the default power limit since I wanted a low power card in the first place, but it is my understanding that tools like YAABE don’t re-sign/checksum/whatever the vbios, which can be troublesome. Can anyone confirm or refute that?
So, again, the only logical move was to try and crossflash other random vbioses from models in the Navi 14 family and hope for the best.
So far I can report that:
-
The W5500 doesn’t work. Like flat-out refuses to even try posting. Nada. Zilch. Likely different enough silicon. Oh well
-
The Pro 5500M, of all things, seems to work but the outputs are, predictably, non-functional since no desktop boards were ever based on it.
-
the RX5500 works , reports 4gb or ram capacity but does still exhibit the crashing issue.
-
The RX5300 also works and is even less crash-prone than the original one but it will still crash under sustained heavy load. I’m also leaving 5 gigs or vram on the table, which is not so cool.
-
My self-modded take on my original vbios (85+15w power limit, RX5300 style) results in a non-booting machine. No idea if the issue lies in the bios mod, the missing checks or the custom version on AMDVBFLASH 2.93 plus I had to track down to ignore the checks.
With all of this nonsense said, does anyone have any idea what to do to either solve the underlying power delivery/overheating issue or edit the vbios?