More
referral
Increase your income with Hive. Invite your friends and earn real cryptocurrency!

Vega 56 and Vega 64 guide

Hi, I share my straps in case they can help you, I am not an expert in this, I only go up or down 1 by 1 the RC and the RCDRD until there are no errors.

GPU 0,1,2,4 Shappire 64 to bios 56.
GPU 3 Asus Xtrix 64 to 56.
GPU 5 Vega 64 Liquid Cooling

GPU 0 and 1:
CORE @ 1050
VDD @ 800,795
MEM @ 1027

Strap:
amdmemtweak --CL 20 --RC 37 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 20 --REF 65535 --RFC 248 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 13 --RCDWR 12

GPU 2:
CORE @ 1020
VDD @ 800
MEM @ 1020

Strap:
amdmemtweak --RC 38 --RP 12 --WR 14 --CWL 8 --FAW 12 --RAS 26 --REF 20600 --RFC 244 --RTP 6 --RRDL 5 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 13 --RCDWR 12

GPU 3:
CORE @ 1050
VDD @ 790
MEM @ 1027

Strap:
amdmemtweak --CL 20 --RC 37 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 20 --REF 65535 --RFC 248 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 14 --RCDWR 12

GPU 4:
CORE @ 1050
VDD @ 790
MEM @ 1027

Strap:
amdmemtweak --CL 20 --RC 37 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 20 --REF 65535 --RFC 248 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 12 --RCDWR 12

GPU 5:

CORE @ 1050
VDD @ 800
MEM @ 1027

Strap:
amdmemtweak --RC 38 --RP 12 --WR 14 --CWL 8 --FAW 12 --RAS 26 --REF 20600 --RFC 244 --RTP 6 --RRDL 5 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 14 --RCDWR 12

2 Likes

@kumuss , thanks for sharing that’s great . Can you clarify and confirm if the sapphire cards referred above are Sapphire Nitro+ Vega 64 (Flashed to sapphire Vega 56 Bios )

Also are you using --eth_config=B or the defaults (–eth_config=A) on the flight sheet

has anyone done any wall testing for gigabyte cards? I’ve seen several comments about them drawing more power. on my windows rig with similar settings to those here, I am getting 55mh/s on my gigabyte OC 56 blower card and 53.5 on my asus strix 64 with 56 bios flash. the power difference at the wall is staggering though…
239W for the gigabyte and 185 for the asus! I really need to get them on Hive to adjust SOC and be able to get mem power state under 900mv without messing with windows registry.

Right, the cards are Sapphire Nitro + Vega 64, Flashed to sapphire Vega 56 Bios. I am using --eth_config = B448

Anyone noticed something weird with reporting from HiveOS to Ethermine pool. Here is the problem .

i have 2 Mixed rigs with both AMD Vega 64/56 Cards and Nvidia 3070 cards . Each using 2 Mining software (T-Rex for Nvidia Cards and TeamRedMiner for AMD cards ) and mining to the same wallet and same ethermine pool. They have been running for about 30 Hours. But on ethermine pool it seems to be reporting only AMD cards hashrate when it comes to reported hashrate but when it comes to Current hashrate it seems to be close to accurate. is this common or a known issue. it does not seem to affect the current hashrate that is used for average hashrate calculations.


RIG 1: (3 x Nvidia RTX 3070 + 5 x Vega 64(flashed to 56 Bios ) )

Miners on HiveOS:
T-Rex for Nvidia Cards @ Total Hashrate = 187.4 MH/s
TeamRedMiner for AMD Vega Cards @ Total Hashrate = 262.7 MH/s
Total Hashrate = 450.1 MH/s

On Ethermine pool:
Reported Hashrate = 262.7 MH/s
Current Hashrate = 410.7 MH/s


RIG 2: (2 x Nvidia RTX 3080 Ti + 3 x Vega 64(flashed to 56 Bios ) + 2 x Vega FE 16GB)

Miners on HiveOS:
T-Rex for Nvidia Cards @ Total Hashrate = 163.8 MH/s
TeamRedMiner for AMD Vega Cards @ Total Hashrate = 247.5 MH/s
Total Hashrate = 411.3 MH/s

On Ethermine pool:
Reported Hashrate = 247.5 MH/s
Current Hashrate = 380.7 MH/s


i know that it takes time for the current hashrate to average out and be stable on ethermine pool. Any idea , why the reported hashrate will only report for AMD cards instead of the total hashrate for both Nvidia and AMD cards ??

I know I’m replying to some very old posts, but these were the only ones I could find about this matter, and I managed to solve it, so maybe you guys still have those cards wandering around as paperweights; they can be saved!
I thus now encountered the same issue; an MSI Vega 56 that already ran for many months on both ETH or ERG suddenly appeared as Radeon Pro V320 after an update and wouldn’t mine anymore. When I transferred it to another rig it stayed identified as Radeon Pro V320…
Flashing it in that state to MSI Vega 56 Airboost 2018 gave errors.
But I managed to flash it back to MSI Vega 56 Airboost 2018 by using the bios switch trick; booting with the safety bios on made it appear as Vega 56 again; when fully booted I flipped the switch back to flashable bios and then forced flashed the bios and rebooted; now it’s up and running again.
However no idea how it has gotten identified as Radeon Pro V320 in the first place though…

Thanks for sharing, no matter how old post and issues, its appreciated that you share a solution.
Maybe someone can benefit from your findings :slight_smile:
I got my powercolor back online, connected it to windows PC and did DDU, installed some old radeon drivers…dont remember the vers.number now for sure… ( Crimson ReLive 17.2.1 ? ), after that it was found in hive and has been mining stable +55mh ever since :+1:

1 Like

ya you gotta change the name of the worker on the flight sheet for the NVIDIA cards. Assuming you are using two flightsheets just add a different name to one and it will report them separately.

For T-Rex, super easy, just put something in the Worker Name field.

image

1 Like

I picked up a Vega 56 XFX with Hynix memory and it seems like any straps I apply that people say work for Hynix cause it to crash. Any suggestions? My Vega 56 Sapphire with Samsung is running great so this XFX with Hynix seems a little tricky. I need to reapply thermal paste on the XFX also. The mem temps are around 90 and my Sapphire is around 73 mem temp.

I have a Vega 56 XFX as well and i can’t get it to go above 43 for Eth or mine Ergo at all. Same as you, i can’t get any straps to work but i have another non-XFX that rocks

1 Like

I guess I might just try to fix the overheating issue and sell it . I haven’t tried ERG on it yet. Live and learn…

So I have 3 Vegas that can run under 775 vdd, but throw invalids. Bumping them to 775 got rid of invalids on all 3. Ive heard that vdd being too low can cause invalids but never seen it before this. GPU 0 is my best example, always throws the most invalids on this rig, and after bumpping vdd up to 775 11 days at 100%. Also looks like my new card GPU 5 might need RC 38, already at RCDRD 13 on that.

1 Like

For mining ERGO on Autolykos V2
I’ve been constantly having issues with the Hynix cards and after lots of trial and error, I finally found a strap that’s the most stable.

Core Clock, Mhz: 1350
Core Voltage, mV: 900
Memory Clock, Mhz: 900
Fan, %: 80

RX Vega 56 (Hynix) OC Strap:
amdmemtweak --RC 36 --RP 14 --FAW 12 --RAS 20 --REF 65535 --RRDL 0 --RRDS 0 --RCDRD 19

1 Like

Thanks@ss-silver , that worked great. you rock!!!

1 Like

Hey, would ony one have an oc for MSI Radeon Vega 56? its a blower card. hash is fine stable at 55.25 but its pulling 140w compared to my nitro and sapphire which are both 110w. thanks

Air Boost

Anyone had problems with running rx 5000 series with vegas?
I heard it is not recommended to mix vegas.
BIOS is loading, everything, until it runs miner then instantly screen turns blank
In maintenance mode it shows as NAVI 14.

@nvm I have just sold it, 150$ profit so I can buy another trusty Vega :smiley:

Those straps worked on the Vega 56 Sapphire Hynix mem I grabbed, but my XFX hynix mem still keeps crashing. I was happy I was able to reapply the thermal paste and pads for the first time and the temps dropped by 25c on the mem. Just so frustrating I can’t keep it stable.

I’m just going to sell it and try to grab something else.

edit…those straps were going fine then I just started getting blasted with invalid shares. Any idea what I could change to fix that? I took off the memtweak and the invalid shares stopped

I used to have the same problem, I didn’t want to switch the bios in case I get stuck with the same thing again. My solution was to get the card in my computer and use AMD VBFlash / ATI ATIFlash 2.93

EDIT: happened to me today, similiar in a way that i flashed the wrong bios for my card and the whole rig wouldn’t boot… Info i posted earlier was misleading in the end I didn’t use the dos version but the windows version 2.93
Switching card to other bios using bios switch before turning on the computer. When booted, switch back to the “problem bios” switch and run this command from cmd:
amdflash.exe -f -p 0 bios.rom (you have to save rom you’re going to use to c:/amdflash/bios.rom)

For this to work you have to have bios switch on your card and 1 working bios in either position

If anyone needs more info I can provide, cheers!

1 Like

Question: Did anyone really see any difference with memory clock between 0 and 5, as in 1025 and 1027? I can’t seem to see the difference with any of my cards no matter the clocks, change is visible for me only at mem steps of 5 (1020,1025,1030,1035, etc…). Using both A and B mode in TRM…