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

flashing 5700 with custom bios is not a problem any more  
the only problem is bios editor for Navi... hexeditor is our friend and shostt58 

1st test mod bios (straps) rx5700

hex editor, tl866
1500 to 2000 mhz
gpu 0 mod, gpu 1 orig bios

atiflash block flashing, need help about this
drivers block high frq timings (1750-1890 - hashrate about 54mh)

https://youtu.be/nhIiZyTPv94

may be help me, and help i

Given that tREF controls how frequently the memory is refreshed (to overcome charge decay,) the main issue w/ a too high tREF is you will encounter data corruption as bits start flipping from not being refreshed frequently enough (this effect is accelerated by heat.)  And since a refresh is a series of reads/writes, i would think it should not be that different from other workloads as far as the memory is concerned - if anything the core will likely be working harder as it probably doesn't have to do much during a refresh.  It is possible that a refresh is easier on the mem than your standard gaming workload due to r/w size/frequency or something like that, in which case, yes, the mem would draw more power and generate more heat as it does less refreshing and more 'real' work.

As for the 64 bios flash, it's value is really dependent on the work profile of your application/game.  For example in the mining scenario, ethereum responds well to higher bandwidth, meaning higher clocks, which require more voltage and relaxed timings (which happens to be exactly what the bios changes.)  Other coins/algorithms may respond better to lower latency, which means tighter timings possibly requiring lower clocks (and possibly less voltage,) making the bios update less useful.

I believe games in general like the higher bandwidth, so I would think the flash would be helpful, but it's probably a more delicate balance between latency and bandwidth than many mining scenarios.

EDIT: Also, in case it wasn’t already apparent, your higher mem clock (vs stock) will likely require higher core voltage for the same cclk, because the infinity fabric, which shares power with the core, runs at (roughly) the same speed as the memory.  So the increased memory voltage resulting from the bios flash isn’t the end of the story...

In case you're still looking for solutions, here is my actual current setup for ethash, using TRM (autotuned):

amdmemtweak settings for all 8 GPUs: --RAS 30 --RCDRD 14 --RCDWR 6 --RC 44 --RP 12 --REF 15600 --RRDL 4



Bottom right pane shows profiles of 2 GPUs.  First profile can generally be run at 800mv for 47.5MH/s, and is *slightly* more efficient, but not by much.  Second one is for one of the GPUs doing 50.7MH/s - the only thing you should have to change from this is the mclk.p3 voltage setting - i need anywhere between 806-837mv across 7 GPUs doing ~50.7MH/s. Both profiles are using cclk p1 / mclk p3 (although in windows you may need to use mclk.p2 @ 1028MHz for the more efficient profile, to take advantage of the lower socclk - i'm not certain.)

Note this is slightly different from what I mentioned earlier... I was using core p0 (850/800) before TRM - and possibly before amdmemtweak (which likely would have resulted in 44MH/s.)  With TRM + amdmemtweak, it appears you need to have core running ~1000MHz to take (nearly) full advantage of the mem bandwidth @ 1107+adjusted timings (and get to 50+MH/s), so I use core p1 @ 1000MHz + mem p3 @ 1107MHz.

Is there any update on 5700 mem timings?

guys what is the danger of keeping tREF to high? I have seen somewhere that the HBM temps might go critical with it to high, but I'm not mining with my vega56@64, only gaming. now during winter with room temps 20-23C I'm not going over 63C on my HBM during heavy load.
these are my latest settings that I managed to get stable under tests/benches. I've been playing with this for the whole weekend. anything more than 1050mhz on HBM freq I get artefacts and crashes, so I left it there and went tightening the timing.

https://postimg.cc/5XR6nhG0

I'm a little disappointed cos I expected more out of samsung HBM when flashing v64bios and going higher on the voltage. I barely get the same results in tests/benches as with default bios and OC/UV/tightening:

https://postimg.cc/qhdBF4Gk

the card is revision C3

thanks.

Well you can start using TeamRedminer for a start

with rx5700 on fly not work
i download vbios (gpuz)
via atiflash load tis bios to card - good
change strap, edit cs, and atiflash breck upload to gpu -

old ssid e408
new ssid e408
bios authentication signature mithmatched
error 0fl01

how repair bios with new straps?

Hello guys !

finally, I can't do it.. I'm going crazy, i'm giving up !..

Can't reach a right profil without "Incorrect ETH Shares" and same without tweak..

I don't understand how is it possible... I've got 6 Sapphire RX Vegas 64 Nitro+ and I cannot have a profil around 50-51 Mh/s without errors...

I've already try this :

Conf 1 :

GPU :

- P0 : 852 Mhz / 800 mV
- P1 : 1175 Mhz / 900 mV
- P2-7 : Disabled

Memory :

- P3 : 1100 MHz / 900 mV
- P0-2 : Disabled

-> Incorrect ETH Shares

Conf 2 BIS :

GPU :

- P0 : 852 Mhz / 800 mV
- P1 : 1075 Mhz / 850 mV
- P2-7 : Disabled

Memory :

- P3 : 1090 MHz / 900 mV
- P0-2 : Disabled

-> Incorrect ETH Shares

Conf 3 :

GPU :

STOCK

Memory :

STOCK

-> Crash then restart !

Conf 4 :

GPU :

- P0 : 852 Mhz / 800 mV
- P1-7 : Disabled

Memory :

- p3 : 1107 Mhz / 837 mV

-> Settings won't apply in Claymore (I've got 44 Mh/s)

WTF is that ? I don't understand what's wrong ...

My config file with Claymore :


If someone can help me to reach a good profil it very helpful or i'm gonna die haha

example.
I have an ETH.xml profile file
How do I run AMDMemoryTweak so that it applies this profile at startup?
I tried to run through the bat file.
like this
AMDMemoryTweak.exe --ETH.xml

does not work.

to be
AMDMemoryTweak.exe ETH.xml

does not work.

how to run correctly

Tell me please.

guys. have an answer to the question?
https://bitcointalksearch.org/topic/m.53244888

How to apply an automatically saved profile?

One of my rx 570 cards, unable to detect by AMD Flash, normally if you open this tool, it will detect that specs of your cards, let say if you want to flash your RX 570, it's says that it was RX 570, In my cards case the flashing tool does not detect it as RX 570, but a Polaris 10, But when I tried to flash it with the original MOD, it says it was successful, the problem is, when i put it to my desktop, there was an exclamation poin in the device, meaning there's an error instaaling the driver or detecting the card. Is my card brick?

support for rx 5700 series soon??

Hello friends.
thanks for your work.

please teach.
write.
how in AMD Memory Tweak to make the profile used at startup.
how to apply * .xml files
or 1002-687F.xmr (in them I change the settings for myself)

if you load these settings in manual mode, through the program window, everything works.

but how to make it load automatically when the AMD Memory Tweak program starts

Tell me please. In the manual I did not find the answer to this question.

Unfortunately I keep getting
: Failed to loan EIO.dll

I downloaded all dependencies and even tried previous versions but no change.

Any suggestions ?

Sorry, my mistake:) I read what you posted once more and you are apparently correct if what you are saying is that vega (just like polaris) has its last stage memory(mem controller?) voltage as the controlling voltage of the last stage of the core. 

Don't really know how to respond to that... Which part are you suggesting is incorrect.

Also, please keep in mind this is all based on my experience w/ 8 nitro 64s and both a ref 64 and flashed 56 over 2+ years.  On both win and linux.  Nothing i'm stating here is theoretical.

I'm confused here. As far as my understanding goes - HBM on Vegas doesn't work the way you describe, which is however correct for Polarises.

Not sure who said anything about changing mem package voltage. 

I said to set the 'mem P3 voltage' - which of course actually controls the core/soc line if it's higher than the current core states voltage setting (and it likely will be w/ core p0 at 800mv.)  Since the mem (and thus soc) speed is what is really controlling the voltage needs, given that the core clock is so low in this scenario, to me it makes sense to make the appropriate setting there, rather than at the core clock parameter. 

And you could likely use mem P0 instead, or rewrite your core states to have 850/800 at p7, but i've found it unnecessary - no stability problems in my experience.

why do you think that you are changing the voltage of the memory on vega?
it's 1.25V on vega56 and 1.356V on vega64 - actually the reason to flash v56 with v64 bios is to update the mem voltage to 1.356

P.S. also in my experience setting proper phases make GPUs more stable (maybe it has to do with actual electricity supply and/or smoother silicon performance)