Hehe yeah the parameters are so many, that indeed the Vega’s never stop to be tuned.
I have been using your straps with my Hynix Vega for a couple of weeks now without problems, it’s just that I can’t seem to get stability with lower voltages (855mV seems to be the most stable for me - which is quite a lot).
I will try your last settings and see how it goes!
I u feel like having an adventure! …try switch to mode eth mode B. That allows you to lower your core and vdd.
Tune cards with mode A first as good as u can get them, even with a bit high vdd, then switch to mode B and start comming down first with core until u see that your hash dropping–then back up a touch.
Next vdd, down one card at the time like 5 to 10 mV at the time until gpu dies…then back up a bit and your done. Happy mining!..tuning… 
2 Likes
Well I been using eth mode B since day 1 with my Vega! Also been doing this method you describe to fine tune. That’s how I came up to my settings of 1010 Core and 855mV. With 1000 Core I started losing a bit of hashrate, and with 850mV I was getting a random GPU DEAD every now and then (sometimes in 10 hours, sometimes in 3 hours). Ever since I went up to 855mV, I never had a dead gpu again. But it uses so much power and generates too much heat for these hot days. Anyway, will see how it goes with 1000 Core / 800 mV.
Btw, which eth conf number are you using? I find best results with B446
3 Likes
Okay, so you know all this, well maybe the post will help someone else anyways.
I had 488 on all but switched back to autotune, in team red manual it states,
“There generally isn’t any upside from a performance perspective specifying the intensity manually, but for gpus running displays, or gpus becoming too hot, you might want to tune it down to lower the hashrate.”
I have had good results with autotune and no real issues with gpus, well one is running a bit hot, so maybe i need to dial that down at some point if this ambient heat continues. Well see how these values works in the long run, have had now +30hrs without any issues so i think that they might good for now.
2 Likes
Hello again guys. I tried now the timings and clocks mentioned by Smining570 and aminer, as you could see in the picture above, looks good untill now.
And yes you are right 
tuning with Vegas never stops, btw these are cards from 2017 and still good performing its just insane!
2 Likes
can i know which once are real vega 56 or are these all vega 64 with flashed 56 bios?
all others are 56 only gpu2 is 64 flashed to 56
1 Like
man your wattage consumption is crazy. well done.
I see you have one Vega56 with Samsung memory. You need to use different timings and clocks for this one. They generally perform better than Hynix, maybe you can reach 55 MH/s. Read a few posts above, @Smining570 has had some impressive results with his Samsung vegas.
Otherwise, your Hynix ones are looking good. You can try reducing your voltage a bit, try 850 first, then 840. Maybe your cards can take a bit lower voltage than mine!
@Smining570 Whenever I tune my cards, I use autotune for a few times and take note of what TeamRedMiner uses. Sometimes it chooses a config that has worse results (don’t know why). Afterwards, I kinda “cycle” these configs manually to see what’s best for me. That’s how I ended up with B446 anyways. It wasn’t all manually chosen.
So, I now have it set to this to avoid the process of auto-tuning that has been done lots and lots of times in the past.
Also, I only have one Vega (sadly). If I had a rig of 4-5 or more, I would probably go with autotune too!
1 Like
I’ve double checked, and my Hynixes at 960 have their SOC automatically at 1028.
Maybe different biosses set the SOC differently?
These are Gigabytes with bios 113-EXT33736-001.
And the tests I did in that earlier post were with Samsungs on MSI Airboost 2018 bios which were also set to 1028 when mem was at 960.
My Hynix Vega is a Sapphire Pulse with bios 113-376XL-UO2. I haven’t reflashed it, so it should be the stock bios, although I bought it used so I can’t be sure if the previous owner had reflashed it (he said he didn’t, but I can never tell for sure).
So you think that each vendor uses different mem states in their respected bioses?
The only way to know for sure is to flash different biosses on the same gpu and test them all at 960 mem to see at which SOC they are set automatically.
But I don’t feel like flashing them Gigabytes as they have no bios backup like the other Vega’s…
And I lack time lately to fiddle around with my beloved rig 
Nah I think it’s too much of a hassle to go through all this. Just to know if different bioses use different soc states. Let’s leave it as it is 
Just about to pick up a asus Vega 64, what’s the recommended bios to flash for the asus model.
Thanks
This is really interesting! I knew you could set every gpu to a different mode, but I didn’t know you could set them to a specific config.
Since the higher ambient temperatures last months, I was also looking at B-mode to lower Watts and thus temperatures. But my 13x Vega rig has 2 disobedient Vega’s which FFS I can’t configure with --eth_config=B. They run normal in A-mode, but when I set the entire rig to B-mode, these 2 always die, no matter what I tried in the past; even higher VDD than A-mode.
I have since then set the rig to --eth_config=B,B,B,B,A,B,B,A,B,B,B,B,B which works fine, but those 2 considerably consume more Watts and consequently their temps are a few °C higher than the other 11 Vega’s, which bothers me off course
Now that I know you can set different configs, I started looking to the miner log and to what auto config sets them, they sometimes vary from boot to boot. I’ve logged several boots on these 13 Vega’s (where 4 & 7 are those set to A-mode):
0 B448 B456 B448 B432
1 B448 B464 B440 B449
2 B448 B480 B452 B480
3 B528 B448 B432 B456
4 A448 A449 A452 A448
5 B640 B464 B448 B592
6 B512 B448 B448 B461
7 A448 A488 A448 A452
8 B448 B496 B464 B484
9 B544 B464 B452 B456
10 B447 B447 B464 B432
11 B480 B464 B448 B472
12 B448 B448 B448 B440
So, a few questions to the power saving --eth_config=B guru’s in here:
Is there more info on how TRM chooses that config? Why does it vary?
And I know Smining570 quoted the manual:
But why wouldn’t it be better off to set the higher configs amongst the logged ones per gpu for higher hash?
And for the 2 A-mode ones, the lower ones for lower hash and maybe lower temps?
And the most important thing to me; how the hell can I get those 2 bloody Vega’s running on B-mode? Any experiences with this? Should I try to set them manually to a fix lower B-mode config?
I have one hynix stable at 755 and one at 760 
also with cores 1000 and mem 940, but I have also mvdd on 1270 for all my Vega’s
1 Like
Oh sweet thanks @oni when you say all vegas does that include any running at 1028 or 1107 SOC levels?
Do you set a VVDCI?
Here is what im messing with today, just hit 1 hour uptime with these
1 amdmemtweak --CL 21 --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 18 --RCDWR 12
2 amdmemtweak --CL 21 --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 18 --RCDWR 14
3 amdmemtweak --CL 21 --RC 37 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 20 --REF 24000 --RFC 239 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 15 --RCDWR 12
4 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
5 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 11 --RCDWR 12
1 Like
Yes, all. I used to only up those that had a few invalid shares, but for simplicity I ended up setting them all at 1270, even if they don’t all need it. Maybe for Watt and temp savings I should dial them down again too.
No, I haven’t messed with VVDC yet.