AMD Mem Tweak XL - Read/modify timings/pp/straps on the fly

[lexele]

decreased rfc:

--CL 16 --RAS 30 --RCDRD 12 --RCDWR 5 --RC 44 --RP 10 --RRDS 3 --RRDL 5 --RTP 5 --FAW 20 --CWL 7 --WTRS 4 --WTRL 9 --WR 16 --WRRD 1 --RDWR 19 --REF 17550 --MRD 8 --MOD 15 --PD 8 --CKSRE 10 --CKSRX 10 --RFC 250

Edit: eth/claymore crashes win rig ; SRBminer/XMR seems ok for now at 2150kh/s but power hungry.

[Miner Addict]

At first, happy with Windows Edition, tweak many value as others, CL low - crash, RFC high - crash etc

But with others correct Value, doesn't change anything : ETH 44-45 Mh & CNR 2050 hz

So, someone done with 51 Mh ETH True ? How about Windows ?

[Zorg33]

So, someone done with 51 Mh ETH True ? How about Windows ?

It's already in this thread... with exact values.

[rednoW]

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

Code:

--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

[Anwil]

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

Code:

--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

--rp 14 Stable for this memory,

[kamisama233]

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

Code:

--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

--rp 14 Stable for this memory,

excellent! is there any settings for cnr algo?

[Iamtutut]

I have nothing to compile the files, does anybody could share a compiled version for windows please ?

[Anwil]

WinAMDTweak.exe --rp 14 --rc 37 --rcdrd 18 --rcdwr 8 --ras 24 --rfc 156  
V56 1200\900 hynix memory 18.45 tartl  stable result , if the memory 900

[dragonmike]

I'm also stable with the same timings and --rfc 250 which gave me an additional boost. Modified timings would be

Code:

--rp 10 --rc 44 --rfc 250 --rrd 3 --rcdrd 12 --rcdwr 5

Thank you for the info.
I will give it another go.

BTW for current version '--rrd 3' should be replaced with '--rrds 3 --rrdl 3' otherwise it won't be set

Edit: Tried it again on my ref V64 Samsung, but same... it crashes after about 1 min.
BTW what's the point in such low rcd if you don't set ras accordingly?

Have you managed to find a good value for RAS to go with the low RCD?

I ran some tweaked timings overnight but the hashrate on pool is not living up to expectations. Some GPUs give hardware errors, some just seem to have substantially lower hashrate on pool. Trying to loosen up some timings... but this is going to be a long process.

[Glane]

Who tested with AMD Radeon RX 560 (Polaris 21) 4GB VRAM (Hynix)? Supported with this tool?

[heavyarms1912]

I have nothing to compile the files, does anybody could share a compiled version for windows please ?

it's available on git -> releases.
https://github.com/Eliovp/amdmemorytweak/releases

Code:

EIO.dll
96 KB
IOMap.sys
31.3 KB
IOMap64.sys
33.3 KB
WinAMDTweak.exe

[Iamtutut]

Thanks a lot !

[Zorg33]

Have you managed to find a good value for RAS to go with the low RCD?

OK... I'm revealing my secrets.
Here are the formulas straight from wikipedia, not hard to find.



If you check ras, rcd, wr, rp, rc you can clearly see the formulas were used.
These values are not hocus pocus. They are calculated according to specific rules.

So if you change ras, you should change rc too and vica-versa

[hammuh]

I changed a few things in the timings from todxx/kerney to (hopefully) improve compatibility with more air cooled Vega 64s w/ Samsung:

--rp 12 --rc 45 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5

This should also work for bios flashed 56 -> 64 w/ Samsung. However, I noticed hashrate drop overnight. If anyone has ideas lmk.

For Vega 56s w/ Samsung and original bios:

--rp 12 --rc 37 --rrds 3 --rrdl 3 --rcdrd 12 --rcdwr 5 --ras 25

Also based off of recommended settings from todxx/kerney, changed "rc" to work with Vega 56 w/ Samsung and original bios. Does not work with Hynix.

Edit: added --ras 25 so that RC = RAS + RP

[dragonmike]

Have you managed to find a good value for RAS to go with the low RCD?

OK... I'm revealing my secrets.
Here are the formulas straight from wikipedia, not hard to find.



If you check ras, rcd, wr, rp, rc you can clearly see the formulas were used.
These values are not hocus pocus. They are calculated according to specific rules.

So if you change ras, you should change rc too and vica-versa

Ah thanks, that's actually what I was looking for.
My days of tweaking DDR timings are several years back... Fun to experiment with HBM actually!

One important thing though: observe the hashrate on the pool. Whilst miner hashrate might look higher, tight timings will decrease effective hashrate if your GPUs can't cope. TRM will show you that figure on the column most to the right. Have a look, you might be surprised.

[hammuh]

Thank you. This is very useful.

I checked default timing values and indeed it seems that RC = RAS + RP.
For example for Vega 64 defaults... RC(47) = RAS(33) + RP(14)... true

However I am not seeing the same for the other formula RAS = RCD + WR
For example for Vega 64 defaults... RAS(33) = RCDRD(16) + RCDWR(10)... nope.

Anyone have more information on this?

Have you managed to find a good value for RAS to go with the low RCD?

OK... I'm revealing my secrets.
Here are the formulas straight from wikipedia, not hard to find.



If you check ras, rcd, wr, rp, rc you can clearly see the formulas were used.
These values are not hocus pocus. They are calculated according to specific rules.

So if you change ras, you should change rc too and vica-versa

[Zorg33]

However I am not seeing the same for the other formula RAS = RCD + WR
For example for Vega 64 defaults... RAS(33) = RCDRD(16) + RCDWR(10)... nope.

Sure it's good.
RAS = MAX(RCDRD,RCDWR) + WR !

Anyone got a tool for displaying memory errors under linux? (other than trm)

[N2DCRYPT]

Anyone have more information on this?

I found the following web-page useful.

http://alexanderhuzar.angelfire.com/files/ram_timings.htm

HBM2 is SDRAM, so I assume similar discussions about SDRAM timings are applicable here as well. You'll note that the yellow "timing" column lists and discusses many of the parameters we're altering here.

Edit: one of the interesting things I've gathered from these tests (apologies if it's obvious to the more technically inclined) is how "subjective" pure memory frequency is. I've been quick to hate V56 stock memory, and hynix stock memory, because it's "slower", at least in terms of pure frequency. But what you notice when you look into the guts of the ram timings, is that the V56 memory timings (both Samsung and Hynix) are much tighter to begin with, which helps explain why you get higher hashrates at lower memory Mhz frequencies.

Perhaps there is little point in flashing Vega bioses anymore, now that this tool is available. Tweak the timings you have, and the "effective" data read/write speed will likely converge for most of these gpus, at least on memory bound algorithms, anyways.

[Zorg33]

Very nice finding!

BTW I managed to reach 51.6mh, but in CN-R I can't get past 2150 2180h/s no matter what i try.
What is the trick there?

[heavyarms1912]

Very nice finding!

BTW I managed to reach 51.6mh, but in CN-R I can't get past 2150h/s no matter what i try.
What is the trick there?

at what clocks on cnr?