I use memtweak –CL 20 --RAS 26 --RCDRD 12 --RCDWR 12 --RC 38 --RP 12 --RRDS 3 --RRDL 5 --RTP 6 --FAW 12 --CWL 8 --WTRS 4 --WTRL 9 --WR 13 --REF 24000 --RFC 239
for all vega64(Flashto56)
mem temp 90c is too high? how to decrease
Set a target mem temp in auto fan settings and enable auto fan. Mine are set to mem temp 60.
Why is it set at REF 30? That’s for RXxxx cards.
What miner are you using? As you have both Nvidia and AMD you should use one that is capable for both together (e.g. Phoenixminer) or you could configure 2 different miners in the same flight sheet with some extra arguments (more complex).
yea i mine on phoenixminer but on vega 64 still dont details about power,temp or another info
Can you please remove the DPM, REF and MVDD from that OC and test?
the first time you wrote it, I deleted it, but without changes
either hiveos won’t show it at all during installation or it will pop up like this but you can’t dream of doing anything.
Greetings, I am fairly new to all this. I have two rigs - one running HiveOS and one running Windows 10. I migrate the various different cards I have over form the Windows rig to the HiveOS rig when I feel I have got it as optimised as I would like. So far she was running just fine with: 1x2080ti and 1x 2070 and 1x 5700XT and one RX480/8 - all giving good MH/s. And then today I tried to add my Vega64 Liquid Cooled.
On the Windows rig with TeamRedMiner and Wattman at:
Core Clock is at 994 Mhz at 980Mv
Fan is 1134rpm temp is 50c
VRM is 1200 Mhz at 950mV
Power Limit is 50
Power consumed is 151W
I get a solid 47.86 MH/s average over days.
Now I put it into the HiveOS rig and the existing 4 cards all do what they did before - but the Vega64 only gives 7.771 MH/s and pulls 77W. And the values for the OC are all the same as WattMan…any idea what is wrong here?
The HiveOS rig is using an ASUS Strix Z270 MB with Intel i7-7700K and an 850W Platinum Corsair PSU
The 4 existing cards are on risers and supplied by a separate HP 1100W (240v) Server PSU
The Vega64 is installed on the MB as I do not have any more risers (ordered)
Any ideas or suggestions would be most welcomed. Am hoping to finally turn off the Windows Rig…
Have you tried switching it with one of your other GPU before further troubleshooting?
Hello Chenne, thank you for your suggestion. Yes I did try substituting it for the RX580, using its riser and then it went up to around 17Mh/s. I gave up after a few hours and put it back in the Windows rig where it immediately went back to almost 48Mh/s and is running now…with the price of ETH where it is I am suffering FOMO with the rigs being down 
In this case…Windoze wins the day…I will just leave it in the smaller Win10 rig churning away…
Hello Desert,
Just a brief glance at the numbers, and you might have mixed up the memory OC with the core. I havent heard of vegas getting 1200 on memory. Try 1100 on core, 1000 memory with 900 core voltage, and try tuning from there.
The 1200 on memory just seems a bit high.
for me my vegas sometimes start on low hashrates because they start on low states … reapplying OC solves problem … agresive OC too …
@Banhammer you are absolutely correct - actually not sure where I got 1200 - too much coffee. In Windows it is 930 (1860). I put it back in to my HiveOS rig and managed to get it somehow to 38.75 Mh/s with 1000-1-980-960 (a predefined template). The problem is the moment I try to change anything the rig hangs and I have to force it off as it become unresponsive. Frustrating - but I see many have issues with the Vega64 cards so I am not alone…
I love the activity on this thread so I thought I would report back; Its been stable for over a week;
Do read the guide here:
“teamredminer/ETHASH_TUNING_GUIDE.txt at master · todxx/teamredminer · GitHub”
- Flashed all Vega 64’s BIOS to Vega 56’s;
- power saving and stability
- “The hardcore Vega 64 Samsung setup these days is to flash it with a
corresponding Vega 56 bios and apply advanced timings and powerplay table
mods. This lowers the HBM2 (mem) voltage to 1.25V and therefore the power draw
while still being able to run a high mem clock and produce a nice 50+ MH/s
hashrate, sometimes as much as 53-54 MH/s.”
- I’m now back on the default A mode;
- “For Vega 56/64, the A-mode is already very capable of delivering high hashrates
at an efficient power draw. However, the B-mode creates a slight shift in core
vs mem clock ratio necessary to sustain a specific hashrate. It will use all
available vram on the gpu. Early reports show that at many custom timing mods,
the B-mode is slightly harder to keep stable over time.”
- “For Vega 56/64, the A-mode is already very capable of delivering high hashrates
- I start the rig with the following OC’s.
- Core: 1100Mhz, Core Voltage: 850mV, Memory Clock: 960Mhz, Fan: 60%, Power Limit 150W
- I then apply the straps of:
amdmemtweak --CL 20 --RAS 26 --RCDRD 12 --RCDWR 12 --RC 38 --RP 12 --RRDS 3 --RRDL 5 --RTP 6 --FAW 12 --CWL 8 --WTRS 4 --WTRL 9 --WR 13 --REF 24000 --RFC 239
2 Likes
My worker has 1 vega 56 and 2 rx 580. How can I apply that code to my vega 56 only?
amdmemtweak --i 2 --CL 20…
-i ‘gpu number’ or 2,3 for multiple gpus.
Hey man i have the same card with the same memory. Been struggling to keep it stable with straps. Please keep me updated if u manage to get more MHs and stable
Hello all,
thank you all. Im getting really good results out of my vega gpu’s.
Can anyone help me with this invalid shares? The Miner is working for 5h and three invalid shares are not that much, but what can i do to avoid this? reduce mem or core? More VDD?
is there a rule? Dead GPU = more VDD and invalid shares = to high memory clock?
I tried to reduce memory clock but after some time the inv shares are still there…
And every time i change the overclock while the miner is runing one of the gpu’s die and TRM reboot.
What can i do to avoid this?
thanks for advise
1 Like
You can try a bit more voltage, but with invalids you usually need to ease off on the memory a bit. Either loosen timings slightly, or lower memory overclock. Going to 1005 and 1015 should work. Try it and see.
Sorry to only reply now, thought I would update incase it helps anyone. It turned out conflicts were a bad riser. Such a headache to troubleshoot, but got there.
Also, found a way to apply straps automatically! Will post below.
Found this forum post Automatic straps guide
Follow the instructions, and the straps will apply, even in the latest version!
Basically,
- under worker options, enable GUI on boot
- start hive shell
- use the command sudo nano /etc/xdg/openbox/autostart
- go to the bottom, and write out your straps
- at the end of every strap, put &
- make sure there is a blank line under the last strap
- save and exit
There you go! I am so happy that I don’t have to keep my rig in maintenance anymore, and it will restart itself if it goes down.
Good luck!
2 Likes