I use this one with very good results:
But I see your replies above that MSI bios gives no start. Was it this 2018 version?
doesn’t start with the modification, and i have also my problem of the GPU0 VEga64 doesn’t start if i flash the bios
That seems correct
yes it is the 2018 version
yes i know but nothing to do, he doesn’t start
How far can you push their mems with those straps? Better hashrate or just more stable for the same hashrate?
I’ve quickly tried them on a few gpu’s, and most have the same hashrate, but some go lower in hashrate.
But they were stable already; maybe with your new straps I can push their mem higher. But that’s a step for tomorrow.
about your worker loosing connection, what mb you have? have u managed to solve this?
Please note that we’re all volunteers here and we’re not replying for the money. We all have our own lives and sometimes I’m not reading the topics for more than a week.
Although we are all here for the money, the cooperation of this forum is more to help each other to push to higher hashrates.
There is already a bunch of information in the meanwhile >600 post counting topic, but it’s worth the long read! But read entirely before starting to OC and strap.
We do try to help everybody, but bear in mind that Vega’s seem to have their own lives; there is no set and forget; every Vega seems different, and it takes a lot of trial and error to get yours to a >54MH/s hashrate.
You either love them or hate them, a Vega is not an easy mining GPU and not for the faint of heart.
Not to mention lots of headaches and discussions with the wife…
I have tried everything.
different configuration with different values in memory and core, but nothing I cap:
for vega64 = 45.5mh
for the vega56 (real56) hynix 48.5mh (with sometimes invalid)
for the vega56 (real56) samsung 52mh
these vega my are driving crazy … hihihih
luckily I can do some tests at work, otherwise the woman would not be happy … 
Thank you oni and @steroid . Useful info… I read a lot of posts of this thread and didn’t see this is typical for gigabytes.
I will use a wall wattmeter today to see if those 156W are real.
I belive there was few attempts to reach out to you for more info about your setup and issue description etc, after last such request for more info from u, next thing is u post is something like this instead of giving us the info required to even start to help u. I did saw pictures of your set up but u just cant assume that someone will try to solve your issue by picking up pieces of info from pictures when you dont even bother to type reguested info. sorry if u are dissapointet, but here many of us just dont have a chrystall ball to check whats wrong with your rig. If u post a proper info about your setup a description about issue and sympthoms, im sure here is plenty of folks that are more than happy to help 
Hi try to 56 hynix:
core 1020 - dpm 0 - vdd 830 - mem 960 mdpm 0 -pl 150
straps
amdmemtweak --CL 20 --RC 36 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 22 --REF 65535 --RFC 248 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 12 --RCDWR 12
Im getting with sapphire hynix, stable +52mh with these.
If straps dont work u can try to increase RCDRD to 13-14, that will decreace hash a bit. Mem is about max on 965 but core can go higher with the expence of stability.
For 56 Samsung:
core 1130 - dpm 0 - vdd - 830 - mem 1020 - mdpm 0 - pl150
straps
amdmemtweak --RC 37 --RP 12 --WR 14 --CWL 8 --FAW 12 --RAS 22 --REF 65535 --RFC 239 --RTP 6 --RRDL 5 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 12 --RCDWR 12
I have 56 samsung sapphire with these values, stable +55mh
Might be that core i a bit high for so experiment little with that and it wont hurt to start with mem 1010 and go up if gpu can handle it. Hope this helps
edit. run with eth config A
hey. I have this config as
–eth_config B
that has worked without =
I know its in trm usage guide as u wrote.
Looks like there is few ways to apply B mode.
Today I recieved two Vega 64 with samsung memories, and there was no way to apply straps, so I was getting only like 45MHs.
After flashing to reference Vega 56 all seems OK!:
Lets see if it’s 100% stable and then lets play with straps.
@oni I mesured the wattage… And the conclusion is that gigabyte tdp stimation is not wrong… The other are wrong!
My both Vega 64 went to 106 and 117W because undervolt, massive tdp reduction, but its not real. At the wall the consumption is arount 378W, so those vega are consuming 160-170W. HiveOS is wrong, and that means I need a new UPS.
790 VDD on the samsung at 1040 mem?! I gotta try this…
could not lower the vdd at all on the 56s, they died at 800, but got my 64 running at 800 now see if I can keep that up for a couple days there.
After about 5 hours it started dying alot so back to 812
hey. I have these 2 hynix 56, the last two from my vega´s that needs their final tuning, i have managed to get them to this point,
starps
amdmemtweak --CL 20 --RC 36 --RP 11 --WR 14 --CWL 8 --FAW 12 --RAS 22 --REF 65535 --RFC 248 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 12 --RCDWR 12
With these setting theyr stable for days,. i have been trying different values and tried allso ss´s hynix straps that was posted earlier, these couldnt handle those. looks like they run with RC36, WR dont change anything too much. I tried RFC from 248 to 244 ok to 239 and at some point quite soon they started spit invalids…naturally i tried one gpu at the time, it looks like thats not gonna give more hash anyway,to my understanding that got something to do with startup states, so with lower value gpu goes to p1-p2-p3 and higher value causes jump on startup straight to p2-p3 ??..might be be that im totally lost here 
anyway…for these straps, any ideas what to change to gain more hash without loosing stability…up with RCDRD, yes…but then need more mem and looks like 965 is max for both…stable anyway, same with core, allready maxed, some more and they both starts to give invalids. Is there something that im still missing? maybe a combination of several strap values that all needs to be changed? Silver? Or…should i just stop here with tuning and let them be. I will try later to lower vdd and see if i can make W better with all vega´s, but with these… hash is not too bad and they are stable…so, any suggestions ?
Yes indeed, from my observations you can add about +50% power consumption to HiveOS value and this gives approximate power consumption from the wall.
BUT
The question was if Gigabyte takes 30% more power than other vendors when you measure it.