I haven’t mined since 2018, so I am a bit rusty, and totally new to HiveOS.
Sorry for n00b question, but which BIOS did you use when flashing that last card (GPU07)?
I have 4 of those, and with the same situation (flashed with 64-BIOS)
Can’t get the over 41 MH/s …
Are you using Hive OS for flashing the Vega cards, or something else?
Could you also screenshot the Overclock template, please? I want to be certain I have all the fields filled in correctly
Thanks
I think I found it. Is it this one?
At least it has the same version (102 at the end) as yours.
My original BIOS is called 100 at the end of that number.
Still can’t get it to work tho, trying to take baby steps, but I find this difficult with my n00biness…
Please advice on where I should start, and where to proceed from there.
All this strap-stuff is new to me as well… :’(
@Smining570 my Asus is a rog strix 56, my 64 is a reference card.
@S_Grim that MSI reference bios will work, i’ve tested that one and got same performance as the one I used and they both say 102. Yep I flash in HiveOS directly from my rig now. In the past i was putting the card in a windows machine and using ATI flash but HiveOS is alot easier.
Here the OCs, straps are just copy and paste into the OCs now.
okay, thanks. i was trying all sorts of combos but it seems that my asus is “bad” and dosn´t tolerate high values. its hashing +54 now and it looks like i haveto come down with allmost all my oc´s now when weather warmed so much here…summer 
well, its great that summer is comming 
Im gonna try to stabilyze my rigs again and then after look again for optimisation. If u dont mind, ill ask for your advice when i get stuck with something…there is still lot to learn about straps…and vega´s…they seem to have mind of their own…just when u think they are okay, another issue rises… when some factor change…in the rig or other way…in my set up i get issues with other cards when i change some value with vega…must be psu related, i do have enough wattage but anyway. I dont know am i just unlucky or what but these rigs keeps me quite busy… 
sorry for the Newbie question but struggling to get vaga 56 & 64 to hash more the 0.
Question ? When Flashing cards dose it have to be done from host computer or can It be done remotely?
Using BIOS from
[VGA Bios Collection | TechPowerUp](https://vega 56 VIOS)
and added many straps on this thread but no HASH
On hive OS free version
Booting on thumb drive Have SSD coming today
Tried Polaris BIOS Editor but couldn’t get it to accept old 64 bios.
Mining ETH
ASUS B250
thanks for any help setting up second rig and taking a bigger bite
u cant patch vega bios on polar, thats for gpus with polar chip only…to my knowledge anyways ?
Try to put “default” values to your vega, look at the firs post on this thread for reference. then boot up and see if miner starts hashing…then study values for your card and apply default straps to get going, on tuning tab, in config settings, there is a small i symbol, when u put your mouse on top of that, it will open recommended values for your card, just copy your choice by clicking it, it will copy them to clopboard or paste them straight to the extra config field… that should work…and get u started. read this whole thread and then u know what to do for sure
@ss-silver Thanks for confirmation on that BIOS.
Flashing went smooth, but I cannot seem to get higher hash rate than 45’ish MH/s.
The OC you posted just makes the rig reb00t after a few moments, even before starting the miner (TeamRedMiner). I tried lowering the Core Clock in steps, and upping the Core Voltage a bit, finally getting somewhat stable results just below 45 MH/s.
I kept the straps tho, as I have no clue as to what all those commands mean. (Please point me in the direction of learning more about straps).
Here is my current settings:
And results:
Any suggestions?
Where can I look for error logs or something similar for better troubleshooting btw?
Looks like the amdmemtweak did not work, values are all red. Try deleting the space and two dashes before CL 20 and re-typing them, sometimes copy / paste brings in weird characters. Since amdmemtweak is white that is formatted correctly, but something right after that is wrong causing the rest to show as invalid.
If re-typing that part doesnt work try setting that advanced config on the cards individually, under that card’s OCs
Not having those straps on with those settings would crash the rig, I cannot run mem that high without straps.
This link has definitions to what you are changing with those straps, biggest ones that impact hash and invalids/ crashes… in my opinion are:
Active to READ command delay (RCDRD) my cards range from 12-18
Active to Active command period (RC) I do 37 for Samsung and 36 for Hynix
Oh… Thanks, still learning here 
Woah, check this out!
Thanks a bunch!
This is awesomesauce!
I really hope this will work for a long time now, and not just a few minutes.
I will report back later
Thanks again!
Sick! nice ya still runs stable for me, been up 3 days minus me stopping the miner to change the strap on my new vega. That one threw a couple invalids yesterday so I dropped rcdrd to 13 then it threw 3 more in 8 hours, but none past 20 hours.
If it keeps throwing invalids I’ll try something like rcdrd 18, mem 1028 whenever this rig goes down… No way I’m turning off the rig when profits are this high
Speaking of invalids…
Should I adjust accordingly? Like you did?
Ya thats too many you can try RCDRD 18 Mem 1028 but Ive only used that setting when I was learning my 64 so not very tested.
Could also try increasing RCDRD by 2 at a time until you stop the invalids. Then see if you can lower it by one or not.
Are you using TeamRedMiner? that setting should hit 55
I think you need to start with higher vdd, like 850, and when you’ve found your max stable hashrate (24h without rejects) try lower it in small steps of 10 and test a few hours again.
Maybe this one can’t handle the higher mem clock too, maybe lower to 1010 and test.
Vega’s are all about patience 
There is a lot of info in this very long topic, but it’s worth the read!
Thanks!
I updated OC for that card now, will let it run for a while and monitor it.
It even increased to 21 invalids since I posted my previous comment…
Thanks.
I have skimmed this thread for a few hours today already
Learned a lot. Especially by you two, @ss-silver and @oni. Thanks a lot guys!
Really appreciated it!
The GPU index is not set. It is the number of the GPU for which you want to apply that strap.
Or you set the straps card by card, then the GPU index will be added automatically.
Or you set it in the overall OC for all cards, but then you have to define for which gpu you set it.
You can add more than 1 index to the same straps. Or you can add multiple different straps for different gpu’s.
Also toggle “aggressive undervolting” on.
Yes, since all cards are the same, I started with an OC template and added that to the entire rig (3 Vega 56).
But now I edited the OC for that troublesome card that gave the invalids.
I toggled the Aggressive thingie off after seeing the screenshot from @ss-silver . But perhaps I should turn it back on? 
Thanks for the response.
Here are the cards at default
Cards with config form first post
Cards with config field from clipboard.
@ss-silver :
The rig crashed with Mem 1028 (and RCRD at 18)
So I edited OC a bit like @oni mentioned, going down to Mem 1010 and VDD up to 850. (and also toggle Agressiveness on)
Hasn’t been long yet, but for now it runs ok, albeit a bit slower than the other cards.
If it is still running ok when I go to bed in an hour, I will leave them on during the night to check the results tomorrow.
I dont see why vega´s are not starting to mine…maybe mem too high and hive cant apply oc…try all vega´s core to 1000
