• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

R9-290(X) Voltage Control

Also, instead of a memory voltage setting you have Aux. It reads the same as GPU-Z's VDDCI which is supposed to be the memory, but I'm assuming by the change in name that it controls other parts of the chip. However I haven't seen anything to explain the change.
 
Doesn't help much. I got 25mhz more out of my 290s by overvolting. I can do 1150 stable now and without artifacts.
 
Doesn't help much. I got 25mhz more out of my 290s by overvolting. I can do 1150 stable now and without artifacts.

There are ways to get more than 100mV buy using some command line augments if you want to push your chips higher.
Thanks, VRM state/id/location seem to be pretty similar to mine R290 (Hawaii PRO Press Sample).
You can alter voltage on it even with current MSI AB beta by sending commands to VRM via MSI AB command line:

To set +100mV offset:
MSIAfterburner.exe /wi4,30,8d,10

To restore original voltage:
MSIAfterburner.exe /wi4,30,8d,0

Use it at your own risk 😉


Almost correct, but you're thinking in right direction. Offset is adjusted in 6.25mV steps and specified in hexadecimal format. So 10 hexadecimal = 16 decimal = 16 * 6.25 mV = 100 mV. 5 results in 5 * 6.25 = 31.25 mV. To set it to 50 mV you should use 8.

By default I2C write commands (/wi) apply to currently selected GPU only. But there are additional /sg<GPU_INDEX> command line switches allowing you to specifiy target GPU for the next commands. So the next command line will apply settings to both GPU0 and GPU1:

MSIAfterburner.exe /sg0 /wi4,30,8d,10 /sg1 /wi4,30,8d,10
 
you can also use asus GPU tweak, don't know if you need a asus bios though.
 
So afterburner doesn't overvolt MSI cards unless you fool around with command line options?

If it has the same controller chip as the reference design it'll work out of the box no matter the vendor, just with a strict 100mV limit. You can only go past that by using the command line options or flashing with an Asus BIOS and using GPU Tweak.
 
you can also use asus GPU tweak, don't know if you need a asus bios though.

Yes, you have to flash with an Asus BIOS to get voltage control with that program. Sucks that they felt the need to put a vendor lock on a program that is pretty much a copy of Afterburner, but to each their own.
 
Ok, cuz that is the one I used to flash to 290X with, as recommended by OCN. So far appears to work btw.
 
Yes, as per GPUZ and higher heaven score.
 
So far at 1050/1275 @ 1250mV. Should I try for higher? Also, unsure if I have memory voltage control.
 
So far at 1050/1275 @ 1250mV. Should I try for higher? Also, unsure if I have memory voltage control.

You should be able to get close to 1100 on the core without extra voltage and ~1130-1150 with a little more. As for the memory, the Aux setting allowed me to get another 50Mhz with 50mV offset.
 
I highly doubt that but im prepared to be pleasantly surprised

I am too. It would be great is someone would run 3Dmark 06 feature tests before and after to see if it's actually unlocking shaders or if the 290X BIOS is just changing memory timings netting a little higher score in benchmarks.
 
I am too. It would be great is someone would run 3Dmark 06 feature tests before and after to see if it's actually unlocking shaders or if the 290X BIOS is just changing memory timings netting a little higher score in benchmarks.

That should not be hard for one to do, as the card has dual bios. The 1 dip switch setting should be the original 290 bios, and the other should be the flashed 290x version.

If I remember reading the review, it said one is a read only, and the other is a read/write.
 
Last edited:
Yes, as per GPUZ and higher heaven score.

GPU Z is just a database, it doesn't count your shaders. It is reading your false BIOS. Score could be a fluke or due to higher clocks.

290s aren't 290x for a reason, and it isn't marketing gimping stable chips.
 
Back
Top