@cscheat
Timings were published for 51.5mh around page 8 by N2DCRYPT

and also by me here
Try them.

Use the tool under load when the last timing strap is active. The other straps do not matter.

For those having issues with running the tool as admin and from a bat file. Please keep in mind that you have to run the bat file itself as admin, otherwise the tool will open in another cmd instance and you won't see any otput (if run as admin is set in the tool's properties). Also you must use full path to the tool or first cd to the folder because admin cmd always starts from system32 folder.
I hope there won't be any more question in this matter as it makes this thread very noisy.

Add pause to the batfile as I already said.
Getting a little kindergartenish.

put this in a .bat file:


and run it as admin

Yes.

I tried stock timings from V56 on V64 bios and memory set at low freq.
But there are 3 values in it that cause instant crash of gpu.
Rddata, wrlat and rc 39
The first two seems to be unable to change on the fly. And rc is simply too low because there must some unrevealed parameters in the timing strap that also needs to be changed paralelly.

However without these 3 params the v56 timing gives the same hashrate in CN algos at 925MHz as the stock timing at about 1050M.

Anyone got into this?

Also in the jedec pdf the mode register bitmaps are different than the structure in eliovp's tool. So it would need a bit of trying to find the missing values.

Try my timings if you want to run ethash 51+ mh.
pbfarmer's timings are better for CN algos.

Also you may have to increase core clk to benefit from faster mem.

Just download the windows binaries from releases.

What memclk?
I got instacrash with this. Also you can try to lower FAW to even 12. After some discussion it seems lower FAW is better.

It's better called Vddci which stands for I/O Voltage
"VDDCI is the I/O bus voltage (between memory and GPU core)"

source

A good reading on this matter:
https://www.micron.com/about/blog/2013/december/addressing-the-tfaw-effect-for-ddr3

Anyone analyzed the built-in HBM tuning in the driver?

I just started looking at it and seems it modifies RRD values and probably some others too.
Might get some good ideas from there....

noice!

 

Someone posted it earlier that it remains.
Of course only when rebooting without cutting power.

Update: just to mention that I can't test all algos with the same driver under win10.
18.6.1 is faster in CN algos, but much slower than 19.3.3 in argon2d for example.

They vanish into the void. except for FAW afaik

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.

get the optimized values from the public straps with a decoder tool to use with amdmemtweak

also I heard there's a tool that can bring down stable voltages by a LOT...

Okay, i'm on the track again...
currently 2370h/s @1550MHz core and 1100MHz mem (~180W reported by driver, so sth like 220W on the wall)

1100 mem, 1500 core
I just raised the core, hr went up to ~2200, but that is the max.

But maybe the miner sw is not the fastest on CN-R, it's a fork of XMRig.
Going to try TRM

Update: with teamredminer on default setting it's 2300 h/s