That said, on your (even modded Polaris) GPU, drop RFC for example.. just try it ;-)
Cheers!
Dropping RFC from 260 to 250 results in much lower hashrate on pool for my Vega rig. At least at 1107 MHz HBM clocks on CN_Turtle. So far I'm quite happy with --CL 16 --RAS 30 --RCDRD 14 --RP 12 --RC 44. Reported pool hash is spot on - and ultimately, that's what matters. It was said for Polaris cards )) |
|
|
|
Ethash is even better than cn-trtl wrt being able to drop core clock on vega. Where you may lose 5+% h/r on trtl by going to cclock p0 (852mhz), I saw zero h/r loss on ethash when doing the same, at least w/ stock timings. Should allow you to get your voltage down significantly - closer to 800mv.
why do you need such low gpu clocks if vega is perfectly capable of higher clocks with <800mv voltage?  it is vega56 pulse with hynix 20.5kh/s turtle btw vega56 ref samsung can do the same ... Wow, with Soft PP or AMD tweaking ? Great info 19.4.1 drivers allow you to control and disable (grey) all p-states via ODNT! (except mem p2 voltage) Just set mem P2 voltage to 800 with softpowerplay ))  And make working freq ~1200 Than test stability, than apply timings -rc 37 --rcdrd 12 --rcdwr 5 --rp 13 --faw 16 --rtp 4 --rrds 3 --rrdl 3 --CWL 6 --WTRS 4 --WTRL 9 --REF 12800 Use --cn_config L22+22 or --cn_config L20+20 for teamred )) And last but not least - screen of overnight testing no hw errors and h/r on the pool is ok  |
|
|
|
Ethash is even better than cn-trtl wrt being able to drop core clock on vega. Where you may lose 5+% h/r on trtl by going to cclock p0 (852mhz), I saw zero h/r loss on ethash when doing the same, at least w/ stock timings. Should allow you to get your voltage down significantly - closer to 800mv.
why do you need such low gpu clocks if vega is perfectly capable of higher clocks with <800mv voltage? it is vega56 pulse with hynix 20.5kh/s turtle btw vega56 ref samsung can do the same ... |
|
|
|
This is my lighter timing, hopefully stable:
--CL 19 --RAS 30 --RCDRD 12 --RCDWR 6 --RC 44 --RP 13 --RRDS 5 --RRDL 5 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248
please test it.
latest 19.4.1 drivers. win10 vega64 lc ~1360/1100@875 51.4mhs with claymore 12. But hbm temp is hot 70C and one weaker vega gives sometimes red incorrect shares 22.3 kh/s trtl, testing for pool speed and hw errors weaker vega lost hashrate to ~19.5kh/s after several hours and rig hangs after reboot attempt. Trying lo lower hbm2 clock from 1100 to 1090 ... |
|
|
|
This is my lighter timing, hopefully stable:
--CL 19 --RAS 30 --RCDRD 12 --RCDWR 6 --RC 44 --RP 13 --RRDS 5 --RRDL 5 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248
please test it.
latest 19.4.1 drivers. win10 vega64 lc ~1360/1100@875 51.4mhs with claymore 12. But hbm temp is hot 70C and one weaker vega gives sometimes red incorrect shares 22.3 kh/s trtl, testing for pool speed and hw errors Power Consumption at HW info ? 150 for eth and 135 for trtl |
|
|
|
This is my lighter timing, hopefully stable:
--CL 19 --RAS 30 --RCDRD 12 --RCDWR 6 --RC 44 --RP 13 --RRDS 5 --RRDL 5 --RTP 4 --FAW 18 --CWL 6 --WTRS 4 --WTRL 9 --WR 15 --WRRD 1 --RDWR 18 --REF 17000 --RFC 248
please test it.
latest 19.4.1 drivers. win10 vega64 lc ~1360/1100@875 51.4mhs with claymore 12. But hbm temp is hot 70C and one weaker vega gives sometimes red incorrect shares 22.3 kh/s trtl, testing for pool speed and hw errors |
|
|
|
Gigabyte rx vega56 gaming hynix trtl:19.75
1250\875 940\875
WinAMDTweak.exe --rp 15 --rc 34 --rfc 156 --rrd 3 --rcdrd 18 --rcdwr 3
Vega 56 - Hynix. algo cn-trtl. got a boost of approx 1.2 Khs --ras 22 --rp 12 --rc 34 --rcdrd 16 --rcdwr 10 --rtp 5 Holy shit! Thanks! This hynix bastard can do 19.9kh/s with stock bios and 940 mem clock! No need for mem voltage and clock boost via v64 bios )) winamdtweak --rc 34 --rcdrd 12 --rcdwr 5 --rp 12 --faw 16 --rtp 5 Update. --rp 12 to tight for my card => dead in some minutes. went to --rp 13 without performance lost Upd.2 --rc 34 seems stable but not needed. --rc 36 gives the same 19.9kh/s So, my current settings for long run testing are: --rc 36 --rcdrd 12 --rcdwr 5 --rp 13 --faw 16 --rtp 5 --rrds 3 --rrdl 4 |
|
|
|
|
this is my best settings so far for sapphire vega56 pulse hynix flashed with nitro vega 64 bios.
gpu-z clocks and voltages are 1280/1020@0.8063v
trtl: 19.27 kh/s with teamread
winamdtweak --rc 45 --rcdrd 12 --rcdwr 5 --rp 13 --faw 16
any tighter timings for --rp give gpu_dead
any tighter timings for --rc give hw errors
|
|
|
|
It doesn't start for me. Created a bat file containing the following:
WinAMDTweak.exe -help
pause
It opens, another screen flashes and then nothing.
What am I missing?
Win10, driver 18.6.1
run console with admin rights, use the utility from this console |
|
|
|
|
Guys, for all of you having issues with vega64lc you can try 1406/1130/905mv (880mv in fact) setup. It will give you 20.2khs and rock stability (hoping you adjust fan setting to keep HBM cool). Yes, it is not so efficient as 1290/960/825mv (800mv in fact) setup of original samsung based vega56 (19.8khs) but better than nothing ))
|
|
|
|
|
no powerplay tables at all. Not needed with latest drivers
|
|
|
|
my vegas 64 liquid didn't want to go below 875mv (850 in gpu-z) with soc clock 1107 (needed for mem clock 1100). It results in 19.6khs
For 1140 mem clock (1199 soc clock) they need 900mv (875 in gpu-z). It results in 20.2khs
It doesn't depend on gpu clock - only soc clock is setting min required voltage.
vega 56 ref samsung with stock bios is happily mines with 825mv (800 in gpu-z) with 940 mem clock resulting 19.5khs
That's not necessarily true... SOC and core appear to share power lines (which explains their relationship in bios/ppt) - I've seen many cases where a specific voltage which didn't seem to be enough for 1107 SOC was suddenly fine when I dropped core low enough. Ethash was a great algo to test this on, as you can run Vegas at p0 w/ no performance effect. CN-trtl is similar in this regard - while we may not be able to go all the way down to 850 Mhz cclock, 1100 is perfectly performant, and leaves a lot of power headroom for SOC/IF, resulting in lower required voltages. In short, it's really the combination of core clock + SOC clock which determines your voltage requirement. yes, thanks. I disable non needed power states on Overdriventool beta and now able to run my vegas 64LC at ~1280/1100@800mv with 19.6khs. gpu-z power readings 105-115wattI'm on win10 19.3.3 drivers how disable? disabe what? pls copy your overdrivetool profile... and ppt table... i use 800mv for all p1-5 state but vega64LE vork only with p7 870mv+  Only memory states disabled. You may need to reset/reboot system. Don't use Afterburner. It seems to conflict with this low settings for vega64lc (strange) ok thx you use 1548GPU or 1280gpu? first you say " run my vegas 64LC at ~1280/1100@800mv with 19.6khs." but in table i see 1548gpu What you set in OverdriveNTool or in Wattman is not what you will get. You'll get lower clock and voltage. At least according to gpu-z and similar apps. |
|
|
|
How to dual mine Loki and Turtle coins
What is it? Is it legit? I know coin developers was trying to avoid merge mining in the past ... |
|
|
|
my vegas 64 liquid didn't want to go below 875mv (850 in gpu-z) with soc clock 1107 (needed for mem clock 1100). It results in 19.6khs
For 1140 mem clock (1199 soc clock) they need 900mv (875 in gpu-z). It results in 20.2khs
It doesn't depend on gpu clock - only soc clock is setting min required voltage.
vega 56 ref samsung with stock bios is happily mines with 825mv (800 in gpu-z) with 940 mem clock resulting 19.5khs
That's not necessarily true... SOC and core appear to share power lines (which explains their relationship in bios/ppt) - I've seen many cases where a specific voltage which didn't seem to be enough for 1107 SOC was suddenly fine when I dropped core low enough. Ethash was a great algo to test this on, as you can run Vegas at p0 w/ no performance effect. CN-trtl is similar in this regard - while we may not be able to go all the way down to 850 Mhz cclock, 1100 is perfectly performant, and leaves a lot of power headroom for SOC/IF, resulting in lower required voltages. In short, it's really the combination of core clock + SOC clock which determines your voltage requirement. yes, thanks. I disable non needed power states on Overdriventool beta and now able to run my vegas 64LC at ~1280/1100@800mv with 19.6khs. gpu-z power readings 105-115wattI'm on win10 19.3.3 drivers how disable? disabe what? pls copy your overdrivetool profile... and ppt table... i use 800mv for all p1-5 state but vega64LE vork only with p7 870mv+ Only memory states disabled. You may need to reset/reboot system. Don't use Afterburner. It seems to conflict with this low settings for vega64lc (strange) |
|
|
|
my vegas 64 liquid didn't want to go below 875mv (850 in gpu-z) with soc clock 1107 (needed for mem clock 1100). It results in 19.6khs
For 1140 mem clock (1199 soc clock) they need 900mv (875 in gpu-z). It results in 20.2khs
It doesn't depend on gpu clock - only soc clock is setting min required voltage.
vega 56 ref samsung with stock bios is happily mines with 825mv (800 in gpu-z) with 940 mem clock resulting 19.5khs
That's not necessarily true... SOC and core appear to share power lines (which explains their relationship in bios/ppt) - I've seen many cases where a specific voltage which didn't seem to be enough for 1107 SOC was suddenly fine when I dropped core low enough. Ethash was a great algo to test this on, as you can run Vegas at p0 w/ no performance effect. CN-trtl is similar in this regard - while we may not be able to go all the way down to 850 Mhz cclock, 1100 is perfectly performant, and leaves a lot of power headroom for SOC/IF, resulting in lower required voltages. In short, it's really the combination of core clock + SOC clock which determines your voltage requirement. yes, thanks. I disable non needed power states on Overdriventool beta and now able to run my vegas 64LC at ~1280/1100@800mv with 19.6khs. gpu-z power readings 105-115watt I'm on win10 19.3.3 drivers |
|
|
|
|
my vegas 64 liquid didn't want to go below 875mv (850 in gpu-z) with soc clock 1107 (needed for mem clock 1100). It results in 19.6khs
For 1140 mem clock (1199 soc clock) they need 900mv (875 in gpu-z). It results in 20.2khs
It doesn't depend on gpu clock - only soc clock is setting min required voltage.
vega 56 ref samsung with stock bios is happily mines with 825mv (800 in gpu-z) with 940 mem clock resulting 19.5khs
|
|
|
|
welldone! ref vega 56 samsung with stock bios real gpu clock ~1330mhz, mem clock 940mhz, 850mv => 19,4 khs!
Pitty, that my vega64 liquids are doing only 0,2khs better with 1100 mem clock and 1370 gpu clock, 875mv
vega56 sapphire pulse with hynix - max I was able to get - 18.4khs
Nice, thanks for reporting back! This is interesting since it's a confirmed 19.4 kh/s for a ref V56 with _stock_ bios, although with samsung mem. The hynix nrs around 18.4 kh/s are also familiar, I've seen other users hitting the same nr. And yeah, for this algo we can saturate the mem bandwidth with the samsung V56s. The diff between my ref V56s and my V64 LC is 19.50 vs 19.58 kh/s  , pretty much the same experience as for you. OS question though: I'm guessing this is on win10? yes, win10 with 19.3.3 drivers and level 1 timings |
|
|
|
|
welldone! ref vega 56 samsung with stock bios real gpu clock ~1330mhz, mem clock 940mhz, 850mv => 19,4 khs!
Pitty, that my vega64 liquids are doing only 0,2khs better with 1100 mem clock and 1370 gpu clock, 875mv
vega56 sapphire pulse with hynix - max I was able to get - 18.4khs
|
|
|
|
There is only one other miner that I know of that is compatible with NiceHash running the MTP algo. It's Bminer and it's horrible, constantly get "GPU1: Result for XXXXXXX does not validate on CPU" all the time even with no oc on the cards. It's so bad that it's unusable.
I don't see mtp in list of bminer supported algos. Why? )) |
|
|
|
|
Show Posts
