You’re doing very well to have the memory running at 980, most of my Hynix can’t go above 960. At this point your best bet is to maximise efficiency by lowering power usage.
I’m currently running efficient settings and was able to get my core clock down to 1050 and VDD down to 775~790 for 99W in the best case scenario.
And if you’re really game, try setting this extra config in your flightsheet “–eth_config=B448” to shave off a few more W.
@KosherMiner Give my settings a try. Let me know if they are better or worse.
GPU 0-5 amdmemtweak --CL 20 --RC 36 --RP 14 --WR 14 --CWL 8 --FAW 12 --RAS 22 --REF 65000 --RFC 249 --RTP 5 --RRDL 6 --RRDS 3 --WTRL 9 --WTRS 4 --RCDRD 14 --RCDWR 12
GPU 6 amdmemtweak --RC 35 --RP 13 --RAS 22 --REF 65500 --RFC 148 --RRDL 4 --RRDS 4 --RCDRD 12 --RCDWR 4
GPU 7 amdmemtweak --RC 35 --RP 13 --RAS 22 --REF 65500 --RFC 148 --RRDL 4 --RRDS 4 --RCDRD 18 --RCDWR 4
I can get over 56-57 M/h if I put the core at 1100-1140 but your wattage take a huge hit.
I am sill lowering VDD GPU 1 & 7 don’t like less voltage.
Alan
2 Likes
@gsmonbob You may try RFC 300-320 and start lowering RCDRD and see where you end up before you get invalid shares
Alan
I don’t have it in my motherboard right now and I’ve forgotten exactly but it was something like 1000 core and 900 on the mem with 900 VDD. It would run for a few min and then just crash. I didn’t see any error messages to figure out exactly what was causing the issue.
Thank you Alan, I will give it a try 
I just tried the “–eth_config=B448” setting, my miner completely stops mining
Can you perhaps send a screenshot of the command in your flightsheet
See the ‘extra arguments’ section.
Thank you very much
Would that effect the RX 5500 XT thats on the same rig ?
Yes it will cause issues for the 5500XT. You will need to find out what the 5500XT usually tunes to and set that also. eg:
I am using eth_config=a still if you use the"b" don’t use a number hive os will tune to a new number. Also turn down the core by about 25-50 since it uses all the memory and less core means less watts. Note: config b get unstable over time on some systems.
I am having a heck of a time trying to get my vega 56’s stable.
Right now one of them seems semi-stable, although not sure about long term. The other used to crash but I think I finally have it just getting a lot of invalids. I have tried changing basically everything, voltage, core, mem etc but nothing seems to even have an effect on the invalids.
Any ideas on what the issue could be?
Check out my post with all my numbers above and let me know if it gets better. Shoot for about 55 mh
Pretty sure I was using those before I switched to these latest straps. I would get crashes on those, these just give me invalids it seems.
I really have no idea which numbers are the important timings or what effect they have.
I can try yours again tomorrow though, it seems to at least not be crashing right now, so going to leave it like this overnight.
Core 1080 memory 1020. Remove memory voltage. Change core voltage 900 to 850
If invalids raise rcdrd 12 to 13 or 14 in your strap
Alan
1 Like
Ok thanks, I will give it a try.
Lowering the voltage will help? I jacked it in a last ditch effort to make the invalids stop, seemed to have no effect though lol.
The lower voltage will help with your total watt consumption. I have mine down around 800 and getting over 50 mega hash. The two things that create invalid’s are mainly memory overclock and the RCDRD setting. Delete your current straps and select the Samsung strap again and run it. If you get invalid‘s increase the RCDRD to 14.
Hi, you have an idea? Using your settings will crash my rig and no change … only 28mh … no change with other settings
Well, I tried all those settings individually but seems the combo did improve things. Instead of 4 invalids per hour I woke up to 4 invalids after 8 hours.
I will try upping the RCDRD now and see if that improves things further.
It is odd since the other vega 56 has been running at 56mh and no crashes and only 2 invalids after 8 hours, just seems a lot more stable for some reason. It is an MSI airboost and the problem card is just a normal reference style MSI card.
Thanks for the help, finally some kind of improvement lol.
I had crashes running those straps as well, I switched to another one posted earlier in this thread and the crashes seem to of stopped but now chasing down invalid shares. The latest settings that were suggested a few posts up have improved it a lot for me though.
I am now raising the RCDRD to see if that will stop the invalid shares.
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 13 --RCDWR 12
Remove strap you should get 44 mh. You could reflash the bios also.