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

[twilightprotege]

as in these?

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

[1675739106]

1675739106

[1675739106]

1675739106

[1675739106]

1675739106

[1675739106]

1675739106

[Zorg33]

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.

[kibatronic]

This is a great tool, thanks to the author!

I finally got my Vega 56's (v64 BIOS) stable running the HBM at 1100MHz by increasing the CL to 21. I am using SRB 1.8.2 mining Monero (CNv4) with the following settings:

Core: 1447MHz 0.900V (0.870V according to HWiNFO)
Mem: 1100MHz

Timings: --CL 21 --RP 12 --REF 15600 --RC 45 --RFC 244 --FAW 20 --RCDRD 12 --RCDWR 8

4 cards averaging 2060H/s each, total system pulling 820W from the wall.

EDIT:

Testing now with 0.850V core voltage (0.825V according to HWiNFO) total system power 740W.

Lowered --REF to 7800 due to incorrect share popping up, hashrate dropped to 2040H/s per card .

[Mashy81]

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

[iRonNuke]

Anyone having some good timings for Radeon VII? I'm thinking of Cryptonight R algorithm. I like to run my Radeon VII at low core and memory but I'm getting lower hashrate than my Vega 56 at same clockspeeds...

[iRonNuke]

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

[mingdao]

Well that's fun... Vega FE's can crack the 2800 H/s threshold on CN-Heavy Algos

https://i.imgur.com/IUZtjAL.jpg

Which drivers and settings are you using?

[Mashy81]

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

[mingdao]

Guys, any suggestions for Vega FE for 18.6.1/CnR on TeamRed?
I am efficiency focussed, running custom Wattman profile with -25 PL, core between P6 1353/890 - P7 1407/890, mem 1100/880.
Everything I try gives me instacrash.
Thanks.

[misterkit]

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

Same issue here.  I tried directing the output to a file and the file is empty.  It appears that the WinAmdTweak.exe will open a NEW window instead of printing to the same current one.  The new window opens, prints the results, and then quickly closes. 

[JuanHungLo]

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

Are you running the cmd as administrator?

[misterkit]

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

Are you running the cmd as administrator?

I also tried that.  Doesnt make a difference.  You can see the command opening a new window and values being printed to it but quickly closing....

[wei0339]

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

Are you running the cmd as administrator?

I also tried that.  Doesnt make a difference.  You can see the command opening a new window and values being printed to it but quickly closing....

OS:win 10
DRIVE:  18.5.2 & 18.6.1
GPU: VEGA 56*6 & vega56*7
run "WinAMDTweak.exe --i", Open a new window and close it in less than 1 second.
run "WinAMDTweak.exe --help > a.txt"   , There is "a.txt" file size 0k.

OS:WIN7
DRIVE: only nvidia drive
GPU:GTX 970 & 1060
run "WinAMDTweak.exe --i", Display the text "No AMD display devices have been found!"
run "WinAMDTweak.exe --help > a.txt"   , There is "a.txt" file size 3k.

OS:WIN7
DRIVE: 18.5.1
GPU:R7 200 Series
run "WinAMDTweak.exe --i", No text displayed‧
run "WinAMDTweak.exe --help > a.txt"   , There is "a.txt" file size 3k.

Guess may be executed under win10 seems to have problems.

When there is free time, try vega56*6 to install v19.4.1 driver.

[misterkit]

I'm running on win 10...

[dragonmike]

I use th --current command to find current values. It loads all values and then closes. How to get it to stay open. I add pause but still no good.

Just start a command prompt and run it within? Or run it but add >file.txt after and it will output to a file.

Thanks. But that still does the same and when I add file the file.is created but empty

Are you running the cmd as administrator?

I also tried that.  Doesnt make a difference.  You can see the command opening a new window and values being printed to it but quickly closing....

It doesn't matter, the timings are still being applied.
Make sure you start your overclocking, then the miner, and whilst the miner is running, apply tweaked timings.
You'll see the hashrate go up immediately.

[misterkit]

I'd like to get the starting/current values before applying any changes so seeing the output of --current is important.  I've tried a few of the settings posted in this thread and the rig dumps shortly thereafter so I wanted to take a more methodical approach.

On my win 10/AMD 19.4.2/Team Read on Vega 56 I am getting 2.048 kh/s.... so I am unsure how much farther I can push it using this tool.

[misterkit]

ok I was able to get around this....

I created a batch file with the commands that I wanted.  The batch file has this:

WinAMDTweak.exe -i 0 --current > i0.current.txt

Then I ran the CMD prompt as admin (instead of running the batch file as admin) and it generated the file for me.

[N2DCRYPT]

@Eliovp,

I've a Radeon Pro Duo Polaris that I'm messing around with on your tool; the gpu is recognized just fine, with all the parameters, but the settings won't stick. For example, if I try to bring down the CL value from default 24 to 22 using --CL 22, I get the "successfully applied new CL settings" to both gpus, but when I check the settings again using --current CL is still at 24. Any ideas why the settings aren't sticking?

Thanks!

Edit: I run amdmemtweak after I've already put the mining load on the GPU (PhoenixMiner). I'm using ROCm on Linux.

[misterkit]

Ok - what am I doing wrong?

WinAmdTweak.exe -i 0 --current

gives the settings for all GPU's instead of just the first one.

I also tried:
WinAMDTweak.exe -i 0 --rcdrd 19 --rcdwr 4 --rc 35 --rp 13 --rrds 4 --rrdl 5 --rfc 148 --REF 15600

and instead of applying it to the first one it did it to all GPU's.  I dont think the -i flag works in this usage.

[rednoW]

Ok - what am I doing wrong?

WinAmdTweak.exe -i 0 --current

gives the settings for all GPU's instead of just the first one.

I also tried:
WinAMDTweak.exe -i 0 --rcdrd 19 --rcdwr 4 --rc 35 --rp 13 --rrds 4 --rrdl 5 --rfc 148 --REF 15600

and instead of applying it to the first one it did it to all GPU's.  I dont think the -i flag works in this usage.

facepalm

--i 0
DOUBLE!!!