• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The RX Vega 56 Owners Thread

Associate
Joined
29 Jul 2003
Posts
893
Location
London
sZjfM7D.jpg

Might be too large.

RGB strip is just used to light the case, and the motherboard accents are always on red for AMD. Coolant will be changed out for red stuff soon, might get a monoblock for the CPU/VRM and i will probably get a larger reservoir tube
Hello,

I had to double take when I saw this loop its not been setup right surely? Should be Res>CPU>GPU>RAD Or Res>RAD>CPU>GPU>RES.

You are going to get much higher temperatures with that setup.
 
Last edited:
Soldato
Joined
18 Oct 2002
Posts
11,038
Location
Romford/Hornchurch, Essex
Hello,

I had to double take when I saw this loop its not been setup right surely? Should be Res>CPU>GPU>RAD Or Res>RAD>CPU>GPU>RES.

You are going to get much higher temperatures with that setup.

nothing wrong with parallel setups.


i assume you turned power all the way up? makes a change me being lucky..

yeh power all the way up. My card seems to work better with the 64 bios, it pretty much never hits boost clocks with the 56 bios.
 
Last edited:
Associate
Joined
6 Dec 2013
Posts
1,877
Location
Nottingham
nothing wrong with parallel setups.
yeh power all the way up. My card seems to work better with the 64 bios, it pretty much never hits boost clocks with the 56 bios.

what about with the default turbo mode, does it boost with that? or is it just specifically when you apply custom clocks?

i do know that i had to reset everything a whole bunch of times early on, as i couldnt get boost clocks working either, but it was more of a thermal throttling issue. as soon as i turned the max fan speed up a bit 3400, the boosts started working. obviously this may not apply if your watercooled.
 
Soldato
Joined
18 Oct 2002
Posts
11,038
Location
Romford/Hornchurch, Essex
what about with the default turbo mode, does it boost with that? or is it just specifically when you apply custom clocks?

i do know that i had to reset everything a whole bunch of times early on, as i couldnt get boost clocks working either, but it was more of a thermal throttling issue. as soon as i turned the max fan speed up a bit 3400, the boosts started working. obviously this may not apply if your watercooled.

Turbo mode is even slower. At the moment I'm running default everything apart from +50% power target.

Now that I've upgraded to Vega56 everything I play is CPU (3.9ghz R7) limited so it doesn't really bother me anymore.
 
Last edited:
Associate
Joined
28 Aug 2017
Posts
28
You might find the following comparison between flashing the BIOS and using registry power play tables useful:

Vega 64 BIOS:

1) Flashing the BIOS is currently the only way to change the HBM2 voltage. It increases the voltage from 1250mV to 1355mV.
2) Higher HBM2 voltage may allow some increase in the stable HBM2 clocks. My silicon gets 960MHz at 1250mV and 1030MHz at 1355mV. Some silicon gets 1100MHz at 1355mV.
3) <deleted>
4) My silicon gets better improvements using power play tables.

Note: The AMD drivers sometimes fail to recognize Vega56 hardware immediately after it has been flashed to Vega64. Rebooting a second time may resolve this problem. If not, then you can try returning your motherboard to its default state, or removing the AMD drivers before flashing the card.

Registry Soft Power Play Table:

1) Allows arbitrary changes to clocks and voltages in all eight P-states.
2) Allows arbitrary changes to HBM2 clock rate, but voltage remains fixed at 1250mV.
3) Allows arbitrary changes to the power and current limits.
4) Allows increase to power boost slider shown in Wattman.
5) Works with AMD 17.9.2 drivers. I am currently testing with 17.9.3.
6) My silicon gets better improvements using power play tables, despite the lower HBM2 clocks.

Here are a few performance results with Superposition 8K on my Vega 56 silicon and stock cooling. The PPT figures are from the soft power play table given below. This PPT uses the Vega 56 BIOS, but sets the core clocks and limits to match the Vega 64.

Code:
BIOS | HBM2 | Core | Boost | HBM2 | Core | Superposition |
/PPT |  mV  |  mV  |  Hz+% |  MHz |  MHz |  FPS  | Score |
----- ------ ------ ------- ------ ------ ------- -------
V56  | 1250 | 1020 |  3.0  |  960 | 1535 |  19.1 |  2560 |
V56  | 1250 | 1155 |  3.5  |  960 | 1539 |  19.1 |  2560 |
V64  | 1355 | 1020 |  3.0  |  960 | 1575 |  18.8 |  2510 |
V64  | 1355 | 1155 |  3.0  |  960 | 1565 |  18.7 |  2500 |
V64  | 1355 | 1020 |  3.0  | 1030 | 1575 |  19.2 |  2570 |
V64  | 1355 | 1155 |  3.5  | 1030 | 1615 |  19.6 |  2620 |
V64  | 1355 | 1155 |  4.0  | 1030 | 1625 |  19.7 |  2630 |
PPT  | 1250 | 1020 |  3.0  |  960 | 1550 |  19.2 |  2570 |
PPT  | 1250 | 1155 |  3.5  |  960 | 1620 |  19.8 |  2640 |
PPT  | 1250 | 1155 |  4.0  |  960 | 1630 |  19.8 |  2650 |


The results at boost +4.0% are unstable.

Hellm has posted a variety of power play table improvements on OCN: http://www.overclock.net/t/1633446/preliminary-view-of-amd-vega-bios/250

I have put together a PPT reg file that alters the clocks and power limits on the Vega56 to match those on a Vega64. How to use it:

1) Copy the contents of the following code section into a file with a .reg extension, e.g. "PPT.reg".

Code:
Windows Registry Editor Version 5.00

; Vega 56 air - adjusted to match V64 air clocks and power limits.
; % max power increment (50%)
; mV P0-P7 (P0=800mV, 900, 950, 1000, 1050, 1100, 1150, P7=1200mV)
; mV HBM2 (V56: 1250mV) (V64: 1350mV) NB: this setting does not seem to work.
; Hz clock rate (/10) P0-P7 (V56: P0=852, 991, 1138, 1312, 1200, 1474, 1538, P7=1590) (V64: P0=852, 991, 1084, 1138, 1200, 1401, 1536, P7=1630)
; Hz clock rate (/10) HBM2 (V56: 800) (V64: 945)
; W Socket TDP power limit (V56: 165W) (V64: 220W)
; W Battery TDP power limit (V56: 165W) (V64: 220W)
; W Small TDP power limit (V56: 165W) (V64: 220W)
; A TDC current limit (300A)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000]
"PP_PhmSoftPowerPlayTable"=hex:A7,02,08,01,00,5C,00,EF,06,00,00,0E,2C,00,00,1B,\
  00,48,00,00,00,80,A9,03,00,F0,49,02,00,\
    32,00,\
  08,00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,01,5C,00,40,02,37,02,94,00,\
  8F,01,B4,00,1E,01,7A,00,8C,00,AD,01,00,00,00,00,63,02,00,00,90,00,99,02,5E,\
  01,34,01,88,01,68,36,02,00,71,02,02,02,00,00,00,00,00,00,08,00,00,00,00,00,\
  00,00,05,00,07,00,03,00,05,00,00,00,00,00,00,00,01,08,\
    20,03,\
    84,03,\
    B6,03,\
    E8,03,\
    1A,04,\
    4C,04,\
    7E,04,\
    B0,04,\
  01,01,\
    46,05,\
  01,01,84,03,00,06,60,EA,00,00,00,40,19,01,00,01,DC,4A,01,00,02,00,77,01,00,03,\
  90,91,01,00,05,6C,B0,01,00,07,01,08,\
    D0,4C,01,\
  00,00,00,80,00,00,00,00,00,00,\
    1C,83,01,\
  00,01,00,00,00,00,00,00,00,00,\
    70,A7,01,\
  00,02,00,00,00,00,00,00,00,00,\
    88,BC,01,\
  00,03,00,00,00,00,00,00,00,00,\
    C0,D4,01,\
  00,04,00,00,00,00,00,00,00,00,\
    44,23,02,\
  00,05,00,00,00,00,01,00,00,00,\
    00,58,02,\
  00,06,00,00,00,00,01,00,00,00,\
    B8,7C,02,\
  00,07,00,00,00,00,01,00,00,00,\
  00,04,60,EA,00,00,00,40,19,01,00,00,DC,4A,01,00,00,90,5F,01,00,00,00,08,28,\
  6E,00,00,00,2C,C9,00,00,01,F8,0B,01,00,02,80,38,01,00,03,90,5F,01,00,04,F4,\
  91,01,00,05,D0,B0,01,00,06,C0,D4,01,00,07,00,08,6C,39,00,00,00,24,5E,00,00,\
  01,FC,85,00,00,02,AC,BC,00,00,03,34,D0,00,00,04,68,6E,01,00,05,08,97,01,00,\
  06,EC,A3,01,00,07,00,01,68,3C,01,00,00,01,04,3C,41,00,00,00,00,00,50,C3,00,\
  00,00,00,00,70,11,01,00,01,00,00,\
    24,71,01,\
  00,02,00,00,01,08,00,98,85,00,00,40,B5,00,00,60,\
  EA,00,00,50,C3,00,00,01,80,BB,00,00,60,EA,00,00,94,0B,01,00,50,C3,00,00,02,\
  78,FF,00,00,40,19,01,00,B4,27,01,00,50,C3,00,00,03,B4,27,01,00,DC,4A,01,00,\
  DC,4A,01,00,50,C3,00,00,04,80,38,01,00,90,5F,01,00,DC,4A,01,00,50,C3,00,00,\
  05,DC,4A,01,00,00,77,01,00,90,5F,01,00,50,C3,00,00,06,00,77,01,00,00,77,01,\
  00,90,5F,01,00,50,C3,00,00,07,00,77,01,00,90,91,01,00,00,77,01,00,50,C3,00,\
  00,01,18,00,00,00,00,00,00,00,0B,E4,12,60,09,60,09,4B,00,0A,00,54,03,90,01,\
  90,01,90,01,90,01,90,01,90,01,90,01,00,00,00,00,00,02,04,31,07,\
    DC,00,\
    DC,00,\
    DC,00,\
    2C,01,\
  00,00,59,00,69,00,4A,00,4A,00,5F,00,73,00,73,00,64,00,40,00,90,92,97,60,96,\
  00,90,55,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,02,02,D4,30,00,\
  00,02,10,60,EA,00,00,02,10


2) If you have flashed the BIOS before then flash it back to Vega 56.
3) Open Wattman and press Reset.
4) Set Wattman to Custom and turn on manual voltage setting (but do not change the voltage).
5) Click on the "PPT.reg" file.
6) Reboot.
7) Open Wattman and press Reset.

The new soft power play table will now be in action. You can continue to use Wattman as usual.

You can get rid of the power play table changes by running regedit and deleting the key added by the PPT.reg file, i.e.:

Code:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e968-e325-11ce-bfc1-08002be10318}\0000] : "PP_PhmSoftPowerPlayTable"


I have indented the contents of the PPT.reg file so that the numbers that can be changed are each shown on a separate line as either two or three bytes in little endian hexadecimal format. The comments in that file describe what each of the numbers does (note that the clocks are all specified in units of 10Hz, so 945MHz = 94500*10Hz and becomes 94500 in decimal, 017124 in hexadecimal and "24,71,01,\" in the PPT.reg file). You can convert from decimal to hexadecimal easily using the windows 10 calulator in "programmer" mode.

I advise that you stick to evenly stepped voltages for the states P0-P7 to provide stability. Setting P6=P7=1150mV seems to give the best performance. P6=P7=1020mV seems to give the best performance per watt. Note that AMD ship all versions of the Vega with the same scale of voltages.

The clocks should always rise gradually with gentler increases at both ends of the scale. AMD ships its versions of Vega with a wide variety of clock scales:

Code:
V56 air: P0=852,  991, 1138, 1312, 1200, 1474, 1538, P7=1590
V64 air: P0=852,  991, 1084, 1138, 1200, 1401, 1536, P7=1630
V64 AIO: P0=852, 1138, 1302, 1348, 1408, 1560, 1668, P7=1750
VFE AIO: P0=852,  991, 1138, 1269, 1348, 1440, 1528, P7=1600


I suspect that Vega 56 with a water block might get beyond 1750MHz at 1155mV, but a second Vega 56 would boost performance much more than going to water cooling.
 
Last edited:
Associate
Joined
8 Sep 2017
Posts
92
Location
Australia
3) Flashing the BIOS does not work with the AMD 17.9.2 drivers. It is unlikely to work with later drivers or multiple GPU set ups.

Works fine for me and works fine with 17.9.3 as well.......don't know where this info came from but it's incorrect none the less.



I suspect that Vega 56 with a water block might get beyond 1750MHz at 1155mV, but a second Vega 56 would boost performance much more than going to water cooling.

Silicone lottery so I HIGHLY doubt these clocks at these volts....perhaps 1 in every 100 may but even doubt that!.....1250mv + 50%PL will net majority of cards 56 (flashed to AIO) - 64 (flashed to AIO) - 64 AIO higher success at 1700+MHz but there are no guarantees as to how much + there will be. Majority of cards won't do over 1700MHz stable under stress without the extra +50mv over 1200mv that the AIO bios offers.
 
Associate
Joined
28 Aug 2017
Posts
28
works for me?

Okay. Cool. When I tried the AMD 17.9.2 drivers with a Vega 64 flashed Vega 56 then they refused to recognize the GPU was any kind of AMD card. Kind of dispiriting, but probably something weird with my set up. I will have to try again.

I think it took Steve at Gamerz nexus +95% PL ( about 400w) to get 1742 stable.

There we are. Absolutely insane, but not impossible. And, yes, of course, in real life, under volting is the way to go. The power/performance ratio makes anything over 1050mV look silly.
 
Back
Top Bottom