Pages:
Author

Topic: AMD Mem Tweak XL - Read/modify timings/pp/straps on the fly - page 42. (Read 58892 times)

jr. member
Activity: 225
Merit: 1
whats the real difference between trm .4.3 and .4.4.  I know obviously the intensity deal 14*14, instead of the +/-.  I can make thinks work great in .4.3 but in .4.4 my hash rate sucks ass


Using the *  instead of + activates a different vega mode which complements the memtweak tool.
jr. member
Activity: 225
Merit: 1
Grate tool, thanks, but my 4 vega crash after while, I wonder what to use in pstates? Maby there is the fault?
[https://ibb.co/qrXvT7d]

Voltages are way higher than all of my vegas. Maybe drop your core down. But that shouldn't be the problem at that voltage
Maybe heat is the issue.
Or memory tweak options you have don't work with your cards.
Are all cards.the same?
newbie
Activity: 61
Merit: 0
Grate tool, thanks, but my 4 vega crash after while, I wonder what to use in pstates? Maby there is the fault?
[https://ibb.co/qrXvT7d]https://ibb.co/qrXvT7d
newbie
Activity: 4
Merit: 0
whats the real difference between trm .4.3 and .4.4.  I know obviously the intensity deal 14*14, instead of the +/-.  I can make thinks work great in .4.3 but in .4.4 my hash rate sucks ass
newbie
Activity: 2
Merit: 0
Hey,

i am trying to get some good tweaks for ETH mining with Radeon VII / RX580.

Radeon VII :
C:\amdtweak>WinAMDTweak.exe --i 1 --current
GPU 1:  Radeon VII      Memory state: 0x11E (1200MHz)
Timing 1          CL: 22          RAS: 33         RCDRD: 14       RCDWR: 10
Timing 2          RCAb (RC): 47   RCPb (RC): 47   RPAb (RP): 14   RPPb (RP): 14
Timing 3          RRDS: 4         RRDL: 4         RTP: 5
Timing 4          FAW: 16
Timing 5          CWL: 7          WTRS: 4         WTRL: 9
Timing 6          WR: 16
Timing 7          RREFD: 8
Timing 8          RDRDDD: 3       RDRDSD: 2       RDRDSC: 1       RDRDSCL: 3
Timing 9          WRWRDD: 3       WRWRSD: 2       WRWRSC: 1       WRWRSCL: 3
Timing 10         WRRD: 1         RDWR: 21
Timing 12         REF: 3900
Timing 13         MRD: 8          MOD: 15
Timing 14         XS: 270
Timing 16         XSMRS: 8
Timing 17         PD: 8   CKSRE: 20       CKSRX: 20
Timing 20         RFCPB: 160      STAG: 4
Timing 21         XP: 8   CPDED: 2        CKE: 8
Timing 22         RDDATA: 20      WRLAT: 5        RDLAT: 18       WRDATA: 1
Timing 23         CKESTAG: 66
RFC Timing        RFC: 260

- on GUI beta tool it looks differend names.
- anyone have any tweaks for Radeon VII for ETH? THX
- gui BETA tool on Radeon VII showing as:
https://imgur.com/a/e5vAf03 RAS2RAS 255 etc is this ok? or not yet implemented? If not could u please implement it.

is it possible to pass parameters with GUI tool? Like i want to apply original values (only some) for Radeon VII. Cant get thees parameters working with non GUI version:(
WinAMDTweak.exe --i 1 --TRCDW 31 --TRCDWA 31 --TRCDR 31 --TRRD 15 --TR 127
WinAMDTweak.exe --i 1 --TR2W 31 --TW2R 31 --TCL 31
WinAMDTweak.exe --i 1 --TRP_RDA 127 --TRP 63 --TRFC 511
WinAMDTweak.exe --i 1 --TFAW 31 --TCRCRL 7 --TCRCWL 31 TFAW32 15
WinAMDTweak.exe --i 1 --ACTRD 27 --ACTWR 22 --RASMACTRD 44 --RASMACTWR 49

- old tool showing as current: RFC Timing  RFC: 260 and BETA GUI showing  tRFC 511
- ohgodadecode showing me differend values WinAMDTweak.exe --i 1 --current (should be showing same)
 as C:\amdtweak>ohgodadecode.exe BBB000000000000022889D0073EE8D53805515133ECF560C004E26017E0514206A8900A00200312 01C143840C5303F17
When i get this working i will send my tweaking results. THX for this awesome tool

jr. member
Activity: 36
Merit: 7

1. With Polaris when we BIOS tweak we are setting up timing straps and matching timings.
However with the tool there is no option to actually configure those said timing straps. Do you think this is why people are having issues with Polaris not seeing much performance increase? Thus far the  most improvement our community has gotten is .2 hash on ETH.


If you already have a good strap for a specific algo in your bios, this tool can't do anything to help your performance - you are setting the same parameters.  This is useful for instances where you can't (or don't want to) edit straps in bios (e.g. vega,) have a bios strap good for one algo but not for another and don't want to reflash (e.g. going from ethash to cn,) or simply want to test new timings live.



Trying to see what we can get for an improvement w/out flashing the bios for some of the new guys coming into the community. And save the hassle of flashing bios on older cards.
So all the fun.

Thank you for the response!


1. With Polaris when we BIOS tweak we are setting up timing straps and matching timings.

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

Thank you!! I will mess with this some more. And post any results. I am trying to simplify some of the newer miners coming process and eliminate the need to flash bios for cards for the newbies.

Loving the tool!
member
Activity: 340
Merit: 29

1. With Polaris when we BIOS tweak we are setting up timing straps and matching timings.
However with the tool there is no option to actually configure those said timing straps. Do you think this is why people are having issues with Polaris not seeing much performance increase? Thus far the  most improvement our community has gotten is .2 hash on ETH.


If you already have a good strap for a specific algo in your bios, this tool can't do anything to help your performance - you are setting the same parameters.  This is useful for instances where you can't (or don't want to) edit straps in bios (e.g. vega,) have a bios strap good for one algo but not for another and don't want to reflash (e.g. going from ethash to cn,) or simply want to test new timings live.

jr. member
Activity: 144
Merit: 2
1. With Polaris when we BIOS tweak we are setting up timing straps and matching timings.

Use the tool under load when the last timing strap is active. The other straps do not matter.
jr. member
Activity: 36
Merit: 7
Hey all,

For those that want to try out my GUI version of this.

Link

Has:
- Memory Clock / State control (change clocks, voltages, disable/enable states)
- Refresh values on screen
- Save all values
- Load saved values
- ..


Some shots








Bestest thing ever! Thank you for ALL your work.

2 questions.
1. With Polaris when we BIOS tweak we are setting up timing straps and matching timings.
However with the tool there is no option to actually configure those said timing straps. Do you think this is why people are having issues with Polaris not seeing much performance increase? Thus far the  most improvement our community has gotten is .2 hash on ETH.

2. Can you add a night version? the white is soooo bright when 90% of your windows are set to night mode. LOL

legendary
Activity: 1050
Merit: 1293
Huh?
Installed all NetFrameWorks still cant start GUI - Win7 and 10

Make sure you copy those 3 included files to the same directory, (driver, pretty important), i just noticed i didn't include them all Cheesy haha
Release has been updated.

Also, run as admin.

Will release a new version soon without EIO.dll and manifest added so it auto asks to start as admin Smiley

I'll update post asap!

Cheers!
jr. member
Activity: 225
Merit: 1
Cant wait to try the gui version. Thanks mate
hero member
Activity: 848
Merit: 500
Hey Mashy, sorry sir, no XMR address.
You can always use a shift service if you want to tip.
coinswap, changelly.. etc..
Get yourself one, I'll be happy to mine some XMR for you Smiley

Haha, ok ok, you convinced me ;-)

Check OP Smiley

And thank you!
Check your address at web.xmrpool.eu. Keep up the good work Smiley
Installed all NetFrameWorks still cant start GUI - Win7 and 10
newbie
Activity: 2
Merit: 0
Hey Mashy, sorry sir, no XMR address.
You can always use a shift service if you want to tip.
coinswap, changelly.. etc..
Get yourself one, I'll be happy to mine some XMR for you Smiley

Haha, ok ok, you convinced me ;-)

Check OP Smiley

And thank you!
Check your address at web.xmrpool.eu. Keep up the good work Smiley
newbie
Activity: 47
Merit: 0
I have a Win 10 - Vega 56 rig

One Hynix card causes a dead GPU when trying 19.4.2, latest TR and have tried both of the suggested Hynix setttings.  Anyone have one that is working for them?   I've tried:

WinAMDTweak.exe --gpu 03 --RAS 24 --RCDRD 19 --RCDWR 4 --RC 35 --RP 13 --RRDS 4 --RRDL 5 --RFC 148 --REF 15600

and

WinAMDTweak.exe --gpu 03 --RAS 22 --RCDRD 17 --RCDWR 4 --RC 35 --RP 13 --RRDS 4 --RRDL 4 --RFC 148 --REF 15600

Both of these cause a dead gpu/restart
try this-

--rcdrd 19 --rcdwr 4 --rc 35 --rp 14 --rrds 4 --rrdl 5 --rfc 148 --REF 15600
or
--rp 14 --rc 42 --rfc 156 --rrd 3 --rcdrd 18 --rcdwr 3

not best but work

iff any have good setup for vega56/stockbios/hynix pls send ..

Thanks that did help out.
newbie
Activity: 417
Merit: 0
Hey all,

For those that want to try out my GUI version of this.

Link

Has:
- Memory Clock / State control (change clocks, voltages, disable/enable states)
- Refresh values on screen
- Save all values
- Load saved values
- ..


Some shots

http://eliovp.com/screenshot1.png

http://eliovp.com/screenshot2.png


wow. THX man..
legendary
Activity: 1050
Merit: 1293
Huh?
Hey all,

For those that want to try out my GUI version of this.

Link

Has:
- Memory Clock / State control (change clocks, voltages, disable/enable states)
- Refresh values on screen
- Save all values
- Load saved values
- ..


Some shots





hero member
Activity: 935
Merit: 1001
I don't always drink...
I noticed something interesting with AMD drivers 19.3.3, Win 10-64.  My Vegas 56/64 used to "throttle back" after reaching GPU temps over 80 C.  This is due to the environment and warmer weather.  (I know I need to relocate this particular rig.)

Now since using the new OverdriveNTool beta and AMD Mem Tweak with:

Quote
GPU_P0=852;800
GPU_P1=852;850
GPU_P2=852;850
GPU_P3=852;850
GPU_P4=852;850
GPU_P5=852;850
GPU_P6=852;850
GPU_P7=1450;855
Mem_P0=167;800;0
Mem_P1=500;800;0
Mem_P2=800;800;0
Mem_P3=1100;860
Mem_TimingLevel=0
Fan_Min=400
Fan_Max=2400
Fan_Target=75
Fan_Acoustic=2400
Power_Temp=85
Power_Target=-5
Fan_P0=30;30
Fan_P1=40;45
Fan_P2=50;60
Fan_P3=55;90
Fan_P4=60;100
Fan_ZeroRPM=0

Quote
WinAMDTweak.exe --CL 12 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 10 --RRDS 3 --RRDL 3 --RTP 5 --FAW 20 --CWL 7 --WTRS 4 --WTRL 9 --WR 16 --WRRD 1 --RDWR 19 --REF 7800 --MRD 8 --MOD 15 --PD 8 --CKSRE 10 --CKSRX 10 --RFC 260

Now, there is no throttling back and the hashrate appears unaffected.

Any ideas which is causing that, the new OverdriveNTool or the AMD Memory Tweak?
newbie
Activity: 11
Merit: 0

I have now run ~72 hours w/o any issues with 24 Vega64 GPUs(good and bad ones) mixed in 4 separate rigs ... CNR with core 1407Mhz /860-970mV , Mem 1080-1100Mhz/860-970mV.

I would say this is pretty stable setup. Pool side 24h avg hashrate fluctuates in the range 54,1-54,4 kH/s

--CL 19 --RAS 28 --RCDRD 12 --RCDWR 5 --RC 44 --RP 12 --RRDS 3 --RRDL 3 --REF 15600 --RFC 250

I am happy and have in my mind... "dont touch when things go smoothly".




That’s an insane voltage range, and I can’t fathom how 970mv could possibly be necessary. Between 9 64s and a flashed 56, I run avg 834mv, none over 850, for similar clocks/timings.  That puts me @ 178w per GPU at the wall.

At 970, you’re running at least 35% higher power, meaning over 240w per card.

It sounds like you have some ppt issues or something, maybe you’re running your SOC @ 1200mhz unnecessarily (it should be 1107 @ your clocks.)  Although, even then, you prob shouldn’t need much more than 925mv.

Oops... I made a quick check with HWtool and yes... I really have SOC max @ 1199Mhz. I have used the Hellae 920mV PPT and then adjusted with Overdrive Ntool the Core P7 and Mem P3. I havent touch the SOC. After memory timings my rigs are pulling like 1420-1500w from the wall per rig. My rigs run like 150w w/o GPUs and after OverdriveNtool the wattage is ~250w before the miner starts and all the GPU led lights are fully on.
This sounds to me like 1270 to 1350w with 6 GPU and on avg. like 210 - 225w/GPU. :O

Thanks for pointing out the SOC. I need to drop to 1107.


When I tried to scribble down a new Vega tuning guide to include in the TRM 0.4.4 release, I was debating if I should have mentioned this or not. I opted not to, that text was long enough already anyway.

However, I know more than a few skilled and knowledgeable Vega tuners that ALL have been stuck with old PPTs from the fall of 2017 (brnsted, Hellae) that for some reason all have 1200 for SoC. At the time, I guess it was considered highly beneficial for stability. Fast forward a few years to times where you don't make $10/day/Vega and power draw is a crucial part of your setup, this trade-off no longer holds.

In the common Google sheet (https://docs.google.com/spreadsheets/d/1-rhYsaRXO1ahk3PyrEgT9gXzs7ImAzh-sbqtgwy8HQg) used for PPT tweaking you can edit the SOC clk value but guess what: it doesn't change any nrs in the PPT, the cells aren't connected(!!!). You have to change the SOC clk value in cell AE26, then manually copy cells AG-AI:26 to T-V:11. You can probably guess why I may sound a little pissed off  Grin.


Yeah.... I fixed my file so that these cell are now connected. Will test today what kind of mV I can get with 1107Mhz SOC.


please post the PPT for reduced SOC.Thanks in advance.
newbie
Activity: 1
Merit: 0
Hi! Please, share the settings of characteristics for R9 370 4Gb for different protocols. Thanks apriori.
donator
Activity: 1610
Merit: 1325
Miners developer
What you did (and Claymore is going to), is a direct consequence of eliovp releasing his open-source tool. You could have been giving him credit at least before putting it (in whatever form) into your paid miner.

Just to clarify: Yes I'm going to use some parts of Eliovp's code/work but I have his permission for that.
Pages:
Jump to: