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

Vega 56 and Vega 64 guide

I had something sorta like. Opened, cleaned & repasted the GPU and changed the riser and all USB and power wires. Yes, in stead of troubleshooting I changed everything. Lazy me, but it worked, and probably faster than troubleshooting :sweat_smile:. Back at 55ish :wink:
PS: core can be lowered to around 1050 and vdd too to save some watt’s.

Guys

Thanks for tips.
I changed risers, cables, reflashed bios and no sucess.
I’ll try to open the card, clean and repast. Let you know if work again.

Take out all the over clocks and run it blank. Restart/power cycle your rig.

Hello dear friends
Unfortunately, my xfx vega 56 card had a problem and it is not known if it was mining before the update.
Now, according to the photo you see, there is no reaction
But the card works and gives an image
Could there be a problem with the BIOS?
Thank you for your help
If you have a BIOS of this model and send it to me, thank you

Hi. What is your Amdmemtweak settings ?
I have an Asus Vega 56 “Hynix” on my rig, I just mine to 50Mh + 900Mh to
Thanks

TRM has introduced R-mode. For Vega’s it could shave off a few Watts or give a small hashrate boost:

Although right now I’m having issues upgrading my testrig:

But once that is resolved I’m gonna try and run the public beta :star_struck:

Any experiences may be shared here!

Have fun!

Got my test rig running in R mode; no noticeable benefits till now; set core -200 like in their manual and getting VDD down bit by bit now, got wattage to approximately the same; need more fine-tuning.
I had a few rig hangs which needed a hard power cycle though :roll_eyes:.
However, my test rig doesn’t have the most stable Vega’s to start with; that’s why they’re on the test rig :crazy_face: 2x MSI Airboost 56 Hynix and 1x Gigabyte Gaming OC 64 > 56. These make testing and fine-tuning a pain in the *ss :sweat_smile:

R-Mode

1 Like

I’ve put my test rig back on B mode for now. Too many rig hangs and not enough time for the time being to dive into it deeper. Will try again later. Probably with one of the other stable rigs then.

You have a YT guide how to do it here :

The thing with Vegas is that you can go below 800mV but it becomes unstable with R mode when the memory clock is above 960. So you can try doing something like 900 Mhz core clock, 781mV, 960 mem clock and see if it works. It is not for the maximum hashrate, but the efficiency should be really good!

1 Like

Well, as temperatures are rising and summer is coming, I’ll need to dive into a more efficient mode anyway.
Maybe I’ll test a rig next weekend.

R-mode

0 and 1 uses
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

2 uses
amdmemtweak --CL 20 --RC 36 --RP 12 --WR 14 --CWL 8 --FAW 12 --RAS 22 --REF 65535 --RFC 249 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 13 --RCDWR 12

0 invalids, 0 crashes more than 24 hours

1 Like


R-Mode, Sapphire Radeon RX Vega 64’s with 56 BIOS (all Samsung memory chips)
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
I’ve lowered about 20w per card on the software, at the wall almost 200w saving if my TPLINK Kasa is correct.
Hope this helps others as a good start.

1 Like

My Vega reference rig was running too hot; at 55MH/s they ran at almost 80°C HBM. It is probably still a safe temperature, but I don’t like it and try to keep my HBM’s closer to 60°C. Off course during summer this is very difficult.
So below test is not about the highest hashrate, but to lower temperatures.
Although they’re only at 50MH/s now, they run about 10-15°C lower and 200W less at the wall (1220W now, 1410W before), so that’s a big win for me, and they’ll survive summer like this :sweat_smile:

SoC Frequency = 910Mhz

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

Going lower than 755mV VDD didn’t work; as in the rig didn’t crash, but in the background (saw on mining screen) set the VDD to 1000mV (and thus higher Watts again). Don’t know why. Maybe a built in safety?

During coming days I’ll try to do my non-reference rig with Asus Strix’es and Gigabyte Gaming OC’s.

My non-reference rig :


0 = Asus Arez Strix 56
1 & 2 = Asus Rog Strix 64 > 56
3 to 7 = Gigabyte Gaming OC 56

They mostly work with the same settings as my reference rig; being core 925, mem 900 and soc 910.
I do have some exceptions in the other settings:
All but 4 works with:
amdmemtweak --CL 20 --RC 36 --RP 10 --WR 14 --CWL 8 --FAW 12 --RAS 20 --REF 65535 --RFC 216 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 11 --RCDWR 12
4 works with:
amdmemtweak --CL 20 --RC 36 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 21 --REF 65000 --RFC 216 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 13 --RCDWR 12
And 4, 6 & 7 need a but higher mvdd to lessen the errors. Still finetuning there.

Again, these are not to have the highest possible hashrate, but to lower the HBM temperatures and survive summer.
Before R mode this rig was running at 426.5MH/s @ 1300W.
Now with R mode it is running at 399.5MH/s @ 1165W.
And most importantly; HMB temperature dropped around 10 to 15°C.

EDIT: I’ve changed some values on the Gaming OC’s as below are more for Hynix memory and above are more for Samsung:
3, 5, 6 & 7:
amdmemtweak --CL 20 --RC 36 --RP 12 --WR 14 --CWL 8 --FAW 12 --RAS 22 --REF 65000 --RFC 216 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 11 --RCDWR 12
4:
amdmemtweak --CL 20 --RC 36 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 21 --REF 65000 --RFC 216 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 13 --RCDWR 12

And then the last Vega’s on my finicky test rig:

0 & 1 = MSI Airboost 56
3 = Gigabyte Gaming OC 64 > 56

Same as above rigs, core 925, mem 900, soc 910.
0 has mvdd 1320
2 has mvdd 1200
(I don’t know why these aren’t showing in the overview as in my non-reference rig)

0 is running:
amdmemtweak --CL 20 --RC 36 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 21 --REF 65000 --RFC 238 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 14 --RCDWR 12
1 is running:
amdmemtweak --CL 20 --RC 36 --RP 12 --WR 14 --CWL 8 --FAW 12 --RAS 22 --REF 65000 --RFC 238 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 18 --RCDWR 12
2 is running:
amdmemtweak --CL 20 --RC 36 --RP 10 --WR 14 --CWL 8 --FAW 12 --RAS 20 --REF 65535 --RFC 216 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 13 --RCDWR 12

Before R mode this rig was running at 148.5MH/s @ 496W.
Now with R mode it is running at 145.5MH/s @ 470W.

Still not satisfied about these ones; but hey, that’s why they’re on the test rig :sweat_smile:

Really struggling with GPU3 below. It was running fine then I removed a 580 which died and GPU3 went into full meltdown. Settings, straps etc all the same but not I keep getting 'teamredminer: GPU 3: detected dead". It ran stable for months and now refuses to run for 10minutes. Tried many things.

Current strap: amdmemtweak --RC 37 --RP 11 --WR 13 --CWL 8 --FAW 12 --RAS 22 --REF 65535 --RFC 239 --RTP 6 --RRDL 5 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 12 --RCDWR 12

That’s a Hynix, but those straps are more for Samsung.

If it’s a reference card, try:
amdmemtweak --CL 20 --RC 36 --RP 13 --WR 14 --CWL 8 --FAW 12 --RAS 23 --REF 65000 --RFC 238 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 15 --RCDWR 12

If it’s a Gaming OC, try:
amdmemtweak --CL 20 --RC 36 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 20 --REF 65000 --RFC 238 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 13 --RCDWR 12

Both with higher or lower RCDRD depending on what yours can handle.

Or check your riser and power cables :wink:

Thanks for the suggestion Oni.

I tried those straps but card comes up as ‘dead’ crashes after a couple minutes.

Tried your suggestion on upping/lowering RCDRD and gave up at 20/10. In total around 50 (i’m not joking) combinations of straps and core/vdd/mem without success as the card keeps crashing in minutes. Nothing on, the card runs without crashes.

This POS is about to get binned lol.

@cuthy2k I have a couple suggestions. First I would suggest updating to the latest version of hiveos and using teamredminer version 0.10.0 if you haven’t already. You should also enable r-mode. You’ll use less power and generate less heat. To do that, add the following to the miner section of your flight sheet in the extra config arguments:
–kernel_vm_mode=RR
Also delete these options from the config if they’re in there:
–eth_big_mode_adjust=64
–eth_config=A
–eth_config=B

You’ll need to reboot the rig once the config is set in the flight sheet, if it doesn’t reboot on its own. And if it doesn’t start hashing after the reboot, you may need to manually select TRM version 0.10.0 in the flight sheet instead of “the latest”.

Read the tuning guide here:

Reduce the core clock to 900-950. Reduce the VDD to 750-800. Maybe start on the high end and reduce core/VDD by 5-10 until you lose stability. The guide says 925-950 should be enough. I’m currently running at 965 core and 800 VDD on my Vega 56s / 1020 core and 820 VDD on my Vega 64s, but I’m dual mining Eth+Ton which requires a higher core/VDD.

For the straps, I always start with the following:

amdmemtweak --CL 20 --RC 36 --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

If you get reboots or invalids, increase the RC by 1 and restart. If you’re still getting reboots or invalids, increase the RCDRD by 1. All of my Vegas (with the exception of two) are running with RC 37 and RCDRD 13. I’ve gone up to RC 38 and RCDRD 14, but I think you get a better hashrate if you reduce the memory clock instead of going above 37/13. But it’s also fine to use 38/14 if you’re having significant problems with a GPU.

Edit:
After messing around with my config a bit more, I’m getting the best hashrate keeping the RCDRD at 12 and the RC at 36-37. Start with RC at 36, if you get invalids or reboots, increase to 37. If you still get invalids or reboots, reduce the memory clock (as opposed to increasing the RCDRD). With r-mode: for Vega 64s I’m using 1020 core and 820 VDD, starting at 1060 memory clock. For Vega 56s, I’m using 965 core and 800 VDD, starting at 950 memory clock. I’ve found that some GPUs need a higher core clock and VDD, so if these settings don’t work try increasing each by 10 until it starts hashing. With these settings I’m averaging 51 MH/s with my Vega 56s, and 55 MH/s with my Vega 64s (which are all flashed with a Vega 56 bios). Again, this is dual mining Eth+Ton (with the max_dual_impact setting at 0.5), so you may be able to go lower on core/VDD, and you may also get a better hashrate.

2 Likes