Topic: My 2 RX 480s voltages are like driving through mud (Read 122 times)

If that had worked when I done it it I wouldn't need to be using overdriventool, however my card doesn't seems to like to listen to that either, and just runs at the standard ~1v. But now that I've seen it may take a while for a voltage to change I'll try again. But I would think if it was BIOS that kind of stuff would be instant, no?

Test the right settings and flash bios. The only right way.

Alright, so I know I've tried blocks of different voltages, but in increasing voltage from p0 to p7, but as you had said I tried a different voltage for each. It did drop the voltage, but only to about .988mv or .981mv, not the actually set voltage. --- I take that back, about mid way through writing this it seems to have about 5 minutes after setting dropped it farther. However it's still not on the value I'm setting, and even if it was, why is it delayed? Example: https://imgur.com/a/xxFGrM5

change all the Pstate voltages, not just the last one. if you decrease the last value you should decrease all the values before too.
core clock and core voltage for each Pstate should be higher than previous values (so they rise gradually from P0 to P7) and then it will be fine.

New here, as I needed to ask a question. I've been fighting with wattman/overdriventool for quite a while now to try and change my cards voltages reliably, but I just can't figure out what is happening. I'll run through a scenario. The computer starts up, all voltages are stock/sometimes what they were "set" to last. I start PhoenixMiner up, and start to downvolt. I go to the last clock speed (in my case 1235MHz and 1200MHz) and knock it down to what I know the card can do. (I found these numbers with Wattool I2C offset. However, I'm going to be getting 580s soon and won't be able to use it. Also, the offset in theory won't work as well as the frequency based voltages as I would think that the frequency based voltages wouldn't crash the card when it goes to a lower state, since the offset is applied to whatever voltage the card is at.) So it will say 950, but I know I can go to 920. I set it, hit apply, and nothing. HWiNFO still says that card is running at .988v. So, I figured if it can't go down, go up. So I put in 1000mv, nothings happening, but I thought 988 might be too close to 1000 so it actually set it, but just isn't running at  that. I then tried 1050mv, and sure enough, it bumped it up to 1.019v. So I then thought, well maybe its like "unstuck" now, so I moved it down to 920 and it dropped it below 920 and crashed the card. Which just now as I'm writing this, makes sense why it went below, as it had in all of the other cases, but the fact that it was not doing what I was entering in reliably, isn't right. I've heard I should use afterburner instead, but I haven't had much luck with that and I need to be able to use Overdriventools ability to apply profiles through command line. I'm currently writing a little Powershell maintenance script that will detect if a card crashes and restart the computer, then when the computer restarts, it will bring everything back up like the miner, hardware monitor, etc. But when it brings everything back up, I want it to apply the voltage profile once it's started mining, and I was planning on doing that with Overdriventools cli. I know there are many other posts out there with people having the same problem, but they either haven't figured it out or were just told to use something else, which in my case, doesn't seem to be much of an option. Also, just to note, I was originally using the blockchain (17.2 or something) drivers, but just as a troubleshooting measure I'm now on the latest ones(20 something) but the problem still persists. Any help appreciated!