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

[rednoW]

Hy, my Vega'64 (Samsung) config for CNR and TeamRed miner. Draws more power but adds 1.8Khs.

your temps are high and hw errors in teamred miner is a bad sign

[1624552496]

1624552496

[1624552496]

1624552496

[Zorg33]

your temps are high and hw errors in teamred miner is a bad sign

7 HWs for 3 days runtime is not that bad actually.

[ingyenfrag]

Hy, my Vega'64 (Samsung) config for CNR and TeamRed miner. Draws more power but adds 1.8Khs.
https://i.ibb.co/xs2R5qD/stable.png

Could you insert the CMD strap ?
What type of cards are those? 56 or 64?

[SamAlackass]

Anyone has any idea about what could be causing this?

I have already verified it isn't driver related and most of the times I get zeros from all cards. Some times it will work normally, some times I will only get readings from some cards, as in the log below.

Needless to say I can't set any timings for the cards not giving proper readings.

Code:

GPU 1:  Vega 10 XL/XT [Radeon RX Vega 56/64]    Memory state: 0x0 (unknown)
Timing 1          CL: 0   RAS: 0          RCDRD: 0        RCDWR: 0
Timing 2          RCAb (RC): 0    RCPb (RC): 0    RPAb (RP): 0    RPPb (RP): 0
Timing 3          RRDS: 0         RRDL: 0         RTP: 0
Timing 4          FAW: 0
Timing 5          CWL: 0          WTRS: 0         WTRL: 0
Timing 6          WR: 0
Timing 7          RREFD: 0
Timing 8          RDRDDD: 0       RDRDSD: 0       RDRDSC: 0       RDRDSCL: 0
Timing 9          WRWRDD: 0       WRWRSD: 0       WRWRSC: 0       WRWRSCL: 0
Timing 10         WRRD: 0         RDWR: 0
Timing 12         REF: 0
Timing 13         MRD: 0          MOD: 0
Timing 14         XS: 0
Timing 16         XSMRS: 0
Timing 17         PD: 0   CKSRE: 0        CKSRX: 0
Timing 20         RFCPB: 0        STAG: 0
Timing 21         XP: 0   CPDED: 0        CKE: 0
Timing 22         RDDATA: 0       WRLAT: 0        RDLAT: 0        WRDATA: 0
Timing 23         CKESTAG: 0
RFC Timing        RFC: 0

GPU 2:  Vega 10 XL/XT [Radeon RX Vega 56/64]    Memory state: 0x0 (unknown)
Timing 1          CL: 0   RAS: 0          RCDRD: 0        RCDWR: 0
Timing 2          RCAb (RC): 0    RCPb (RC): 0    RPAb (RP): 0    RPPb (RP): 0
Timing 3          RRDS: 0         RRDL: 0         RTP: 0
Timing 4          FAW: 0
Timing 5          CWL: 0          WTRS: 0         WTRL: 0
Timing 6          WR: 0
Timing 7          RREFD: 0
Timing 8          RDRDDD: 0       RDRDSD: 0       RDRDSC: 0       RDRDSCL: 0
Timing 9          WRWRDD: 0       WRWRSD: 0       WRWRSC: 0       WRWRSCL: 0
Timing 10         WRRD: 0         RDWR: 0
Timing 12         REF: 0
Timing 13         MRD: 0          MOD: 0
Timing 14         XS: 0
Timing 16         XSMRS: 0
Timing 17         PD: 0   CKSRE: 0        CKSRX: 0
Timing 20         RFCPB: 0        STAG: 0
Timing 21         XP: 0   CPDED: 0        CKE: 0
Timing 22         RDDATA: 0       WRLAT: 0        RDLAT: 0        WRDATA: 0
Timing 23         CKESTAG: 0
RFC Timing        RFC: 0

GPU 3:  Vega 10 XL/XT [Radeon RX Vega 56/64]    Memory state: 0x118 (800MHz)
Timing 1          CL: 17          RAS: 27         RCDRD: 13       RCDWR: 8
Timing 2          RCAb (RC): 39   RCPb (RC): 39   RPAb (RP): 12   RPPb (RP): 12
Timing 3          RRDS: 4         RRDL: 5         RTP: 5
Timing 4          FAW: 13
Timing 5          CWL: 6          WTRS: 3         WTRL: 7
Timing 6          WR: 13
Timing 7          RREFD: 7
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: 17
Timing 12         REF: 3120
Timing 13         MRD: 8          MOD: 12
Timing 14         XS: 216
Timing 16         XSMRS: 6
Timing 17         PD: 6   CKSRE: 8        CKSRX: 8
Timing 20         RFCPB: 128      STAG: 7
Timing 21         XP: 6   CPDED: 2        CKE: 6
Timing 22         RDDATA: 16      WRLAT: 4        RDLAT: 14       WRDATA: 1
Timing 23         CKESTAG: 2
RFC Timing        RFC: 208

GPU 4:  Vega 10 XL/XT [Radeon RX Vega 56/64]    Memory state: 0x118 (800MHz)
Timing 1          CL: 17          RAS: 27         RCDRD: 13       RCDWR: 8
Timing 2          RCAb (RC): 39   RCPb (RC): 39   RPAb (RP): 12   RPPb (RP): 12
Timing 3          RRDS: 4         RRDL: 5         RTP: 5
Timing 4          FAW: 13
Timing 5          CWL: 6          WTRS: 3         WTRL: 7
Timing 6          WR: 13
Timing 7          RREFD: 7
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: 17
Timing 12         REF: 3120
Timing 13         MRD: 8          MOD: 12
Timing 14         XS: 216
Timing 16         XSMRS: 6
Timing 17         PD: 6   CKSRE: 8        CKSRX: 8
Timing 20         RFCPB: 128      STAG: 7
Timing 21         XP: 6   CPDED: 2        CKE: 6
Timing 22         RDDATA: 16      WRLAT: 4        RDLAT: 14       WRDATA: 1
Timing 23         CKESTAG: 2
RFC Timing        RFC: 208

[Johnnydex]

Any update on this being implemented for Fiji?

[bobben2]

I saw a lot of Vegas but are there settings for RX 580 8Gb and 4Gb ?

thx

I have custom straps for my rx cards, it would be nice to be able to flash them back because right now I have to use older drivers due to signing issues

Can someone list a good starting point for 470 Hynix, Samsung and micron cards for eth/xmr

Use version 1.4.6 of the pixel patcher - then you can sign newer versions of the driver.  I have patched my 19.4.1 install with it.

You could use  WinAMDTweak --current from your custom bios, then store those timings and use them as a starting point after you have reverted the card back to orig.bios.


EDIT:
I had to verify what I just mentioned above:
I upgraded the driver on my test rig with 2 x RX 570 from 18.6.1 to 19.4.1, patched it and restarted the rig. 
I then learned I had to upgrade my OverDrivenTool because I no longer had fan control.  Great, eh
I found version 0.2.8. bet1 and am playing with it as we speak..  Seems like the new driver runs the cards cooler... less power Yay.

[ganzocrypt]

thx for the info !

So without reverting to stock bios the tool does not work or we get better results from stock?

please share your finding as the number of parameter are so many that is difficult to keep track.
Also my RX 580 8Gb is Hynex memory so might be different from others.

cheers

[keksik]

ok seems its time to update driver from 18.6.1 to the newest one and re-flashing all card back to stock.
as there are only few types of memory(as i flashed 40 cards already) it will be nice to share some good timings who are already tested.
there are hynix, samsung, micron/elpida and 4/gb variation if im not mistaken?

P.S. btw is better to push first mem frequency to max and then tweak straps or first use good straps and tune frequency? i did the later as flashed with polaris bios editor.
P.P.S. do we still need overdriventool or new tool is able to save config as in overdrivetool and load them via bat file?

thank you

[Divinity666]

Will there be Fiji support?

[Marvell2]

I saw a lot of Vegas but are there settings for RX 580 8Gb and 4Gb ?

thx

I have custom straps for my rx cards, it would be nice to be able to flash them back because right now I have to use older drivers due to signing issues

Can someone list a good starting point for 470 Hynix, Samsung and micron cards for eth/xmr

Use version 1.4.6 of the pixel patcher - then you can sign newer versions of the driver.  I have patched my 19.4.1 install with it.

You could use  WinAMDTweak --current from your custom bios, then store those timings and use them as a starting point after you have reverted the card back to orig.bios.


EDIT:
I had to verify what I just mentioned above:
I upgraded the driver on my test rig with 2 x RX 570 from 18.6.1 to 19.4.1, patched it and restarted the rig. 
I then learned I had to upgrade my OverDrivenTool because I no longer had fan control.  Great, eh
I found version 0.2.8. bet1 and am playing with it as we speak..  Seems like the new driver runs the cards cooler... less power Yay.

Hmm , I’ll have to work on this as well tonight as well , cooler is definitely better

I can’t find links to the 1.4.6 pixel patcher or winAMDTweak though

Are they in this thread?

[N2DCRYPT]

Hmm , I’ll have to work on this as well tonight as well , cooler is definitely better

I can’t find links to the 1.4.6 pixel patcher or winAMDTweak though

Are they in this thread?

Pixel patcher (lots of versions) is available online if you google, but be careful with that. I'm sure there are probably links to it in Matthev's bios modding thread as well.

WinAMDTweak will be available at Eliovp's Github site, check the first page of this thread.

[osirus466]

Do I still need to do any registry mods or ppt mods with this?  I have 2 vega 56 reference cards

[bobben2]

I saw a lot of Vegas but are there settings for RX 580 8Gb and 4Gb ?

thx

I have custom straps for my rx cards, it would be nice to be able to flash them back because right now I have to use older drivers due to signing issues

Can someone list a good starting point for 470 Hynix, Samsung and micron cards for eth/xmr

Use version 1.4.6 of the pixel patcher - then you can sign newer versions of the driver.  I have patched my 19.4.1 install with it.

You could use  WinAMDTweak --current from your custom bios, then store those timings and use them as a starting point after you have reverted the card back to orig.bios.


EDIT:
I had to verify what I just mentioned above:
I upgraded the driver on my test rig with 2 x RX 570 from 18.6.1 to 19.4.1, patched it and restarted the rig.  
I then learned I had to upgrade my OverDrivenTool because I no longer had fan control.  Great, eh
I found version 0.2.8. bet1 and am playing with it as we speak..  Seems like the new driver runs the cards cooler... less power Yay.

Hmm , I’ll have to work on this as well tonight as well , cooler is definitely better

I can’t find links to the 1.4.6 pixel patcher or winAMDTweak though

Are they in this thread?

WinAMDTweak (the command line version) should be available in this thread.   I DLed  the pixel patcher from here.  It seems legit.
https://www.monitortests.com/forum/Thread-AMD-ATI-Pixel-Clock-Patcher

My two test cards both have Elpida mem.  I simply used SRBPolaris bios editor with the one-click method to get good timing straps for my custom bios.
I will use that as a starting point to further tweak my cards, when I get the time.

[Mashy81]

Hy, my Vega'64 (Samsung) config for CNR and TeamRed miner. Draws more power but adds 1.8Khs.

your temps are high and hw errors in teamred miner is a bad sign

Bump your fans a bit more and you should be able to get your temps down a bit. I have been runing my vegas at 60C for nearlly 18months and they are still sweet as.
Try lowering WR a little and see if that gives a bit more.

[NefariousFool]

Eliovp:

RX series modifications suggestion?

quick question. The order of the listings vs the order of the timings list is there away you can flip the positions?

when you run a timings Query the order is PMG, RAS, CAS... but the tools GUI goes PMG, CAS, RAS... just curious.

and is there a possible typo on the CAS timings? there's tCCLD however in the query there's tCCDL is this a typo or a different setting?

-------

So far managed to increase stock bios RX 570 from 22.4 to 27.721 via the tool.

After i get above 30 mhs i'll go a head and post my settings.
As 29 to 33.4 mhs is achievable with a 570 via BIOS mod no point in posting things that are less than that currently.

------------

Also dunno if you or anybody else knows.. if you zero out all the P states on the core control it'll actually remove the P state out of Wattman. which is pretty sick I love it.

If you're running the memory tweak also noticing that when you set the P state setting it'll fight you using the Wattman so this tool will replace your management for ALL of your settings.

-----------

Previously i thought you had to setup batch files to run for the cards, which you can do, however you can also just export the settings and import them.
    I understand this is probably stating the obvious, however just thought i'd point it out anyways in case people didn't see it.

However when you import the Fan control settings are blank and you have to put them in manually every time. Can you fix this?
----------
The biggest AH HA moment was when you click the timing level changed it from the default 0 timing level to timing level 1 or 2 the crashing on the card when certain changes were applied stopped occurring. check it out guys.

Once again... Eliovp.. thank you for making such a kick ass tool!!

[clousian]

Eliovp:

RX series modifications suggestion?

quick question. The order of the listings vs the order of the timings list is there away you can flip the positions?

when you run a timings Query the order is PMG, RAS, CAS... but the tools GUI goes PMG, CAS, RAS... just curious.

and is there a possible typo on the CAS timings? there's tCCLD however in the query there's tCCDL is this a typo or a different setting?

-------

So far managed to increase stock bios RX 570 from 22.4 to 27.721 via the tool.

After i get above 30 mhs i'll go a head and post my settings.
As 29 to 33.4 mhs is achievable with a 570 via BIOS mod no point in posting things that are less than that currently.

------------

Also dunno if you or anybody else knows.. if you zero out all the P states on the core control it'll actually remove the P state out of Wattman. which is pretty sick I love it.

If you're running the memory tweak also noticing that when you set the P state setting it'll fight you using the Wattman so this tool will replace your management for ALL of your settings.

-----------

Previously i thought you had to setup batch files to run for the cards, which you can do, however you can also just export the settings and import them.
    I understand this is probably stating the obvious, however just thought i'd point it out anyways in case people didn't see it.

However when you import the Fan control settings are blank and you have to put them in manually every time. Can you fix this?
----------
The biggest AH HA moment was when you click the timing level changed it from the default 0 timing level to timing level 1 or 2 the crashing on the card when certain changes were applied stopped occurring. check it out guys.

Once again... Eliovp.. thank you for making such a kick ass tool!!

As I'm running stock bios for my RX cards on XMR dude, any enhancements would be appreciated that you've found this far. It'll help me (and others) see where to be begin with tweaking their own Polaris set up. Finally, does this tool work in conjunction with srb miner?

[doktor83]

As I'm running stock bios for my RX cards on XMR dude, any enhancements would be appreciated that you've found this far. It'll help me (and others) see where to be begin with tweaking their own Polaris set up. Finally, does this tool work in conjunction with srb miner?

It does, you just have to use the --disabletweaking parameter, to disable the built-in tweaking.

[bobymoore]

I got this error https://postimg.cc/YjQTd7krhttps://postimg.cc/YjQTd7krand program don't open.

[NefariousFool]

I got this error https://postimg.cc/YjQTd7krhttps://postimg.cc/YjQTd7krand program don't open.

IF You have an on-board video device or a non AMD card in your system you will get those errors.
The GUI is based off of Overdrive N Tool code. As a result it will ONLY work with an all AMD environment.

I am not sure if Eliovp has a solution to that particular issue, so for now as you get to test and run your settings be sure to disable your onboard adapter and run your system  with 2 cards, 1 to  view your screen and the 2nd to test and configure your settings.

ALSO A MUST HAVE this link
https://www.overclock.net/attachments/47806

That is the R_timings program you need.  You will also need the Polaris BIOS tool.

You can then read the BIOS and get the timing straps and use Power shell to convert that timing to the appropriate settings.

There are a few things that are incorrect in the GUI. Such as the following:
Under the CAS Timing. - tR2R is actually TCCDS / tCCLD is actually TCCDL

In your timings settings you will NOT get an RAS setting.
In your timings settings you do not need to configure ALL the settings you can simply configure the
RMG Timing, CAS timing, RAS timing, Misc Timing, and Dram Timings.


You will also note that on the bottom right there is a Timing level setting.
Default (0) - will get you 18 to 20 mhs
Level 1 - 21 to 25 mhs
Level 2 - 27 to 30 mhs

SO you will want to set your timing level to 2.

As for your memory and core settings that is what you nomrally configure I am still tweaking.
I was able to get 29.921 Mhs with 2300 / 900 / 1175 / 900 I did get a share but it locked up after 10 min.
I am still working on settings but i wanted to take the time to respond to your question and post an update to my findings this evening.

Thank you!

[bobymoore]

I got this error https://postimg.cc/YjQTd7krhttps://postimg.cc/YjQTd7krand program don't open.

IF You have an on-board video device or a non AMD card in your system you will get those errors.
The GUI is based off of Overdrive N Tool code. As a result it will ONLY work with an all AMD environment.

I am not sure if Eliovp has a solution to that particular issue, so for now as you get to test and run your settings be sure to disable your onboard adapter and run your system  with 2 cards, 1 to  view your screen and the 2nd to test and configure your settings.

ALSO A MUST HAVE this link
https://www.overclock.net/attachments/47806

That is the R_timings program you need.  You will also need the Polaris BIOS tool.

You can then read the BIOS and get the timing straps and use Power shell to convert that timing to the appropriate settings.

There are a few things that are incorrect in the GUI. Such as the following:
Under the CAS Timing. - tR2R is actually TCCDS / tCCLD is actually TCCDL

In your timings settings you will NOT get an RAS setting.
In your timings settings you do not need to configure ALL the settings you can simply configure the
RMG Timing, CAS timing, RAS timing, Misc Timing, and Dram Timings.


You will also note that on the bottom right there is a Timing level setting.
Default (0) - will get you 18 to 20 mhs
Level 1 - 21 to 25 mhs
Level 2 - 27 to 30 mhs

SO you will want to set your timing level to 2.

As for your memory and core settings that is what you nomrally configure I am still tweaking.
I was able to get 29.921 Mhs with 2300 / 900 / 1175 / 900 I did get a share but it locked up after 10 min.
I am still working on settings but i wanted to take the time to respond to your question and post an update to my findings this evening.

Thank you!

I had made  a good set up for my two vega 56@64 and I got 2200 hash,but when I restart windos show that message error,so I go back to srb miner and profiles,but I get about 2160 hash,i have only two vegas and not another gpu like onboard,i think is a windows bug,i cant understand that erroe,i format pc a week before, I use 18.5.1 driver,because I I use 19.4.1 or newer one card gives only half power,another bug I think.yesterday I  was happy because I did 2250+ with my vega this tool and red team,but after restart everything lost.