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

[anatolikostis]

See the generated strap:

Elpida:
777000000000000022AA1C10315A5436A0550F15B6191B0620550F117C041420CA8980A9000004C 00C09141734161D0B

it`s completely broken strap, I`d not use it at all.

Samsung:
777000000000000022CC1C10AD615C41C0590E152ED88D0840590E110B031420FA8900A00300000 008091922651C220D

\
the same trash 

[1714118751]

1714118751

[1714118751]

1714118751

[1714118751]

1714118751

[WhackOBill]

With the new XL version, I can only occasionally update the the values on the fly.  Most often not.  The added tools are nice to have though.  My system always fails to read the injected strap ... pops and error dialog box to that effect.

I still regret moving to Win10 1903 as I think that's what took away my ability to modify things real-time, while Claymore is running.

You probably need an option or button to revert out of test mode.  Obviously, you can flip into test mode if you don't detect it running but then there's no automated way back out in the XL Win tool.

Edit:

bcdedit /set TESTSIGNING OFF

just in case someone was looking for it.

I've tried to recreate your problem with the straps not injecting ..

Just to be clear here, you can only inject a strap at the selected frequency.

So if you're currently running your memory at 1900 Mh and you do a modification/strap injection for freq 2000, you're not going to notice any differences.
However, that doesn't mean that you should get those error messages.
It's the driver that fails to inject the strap.
Probably something to do with Claymore's driver

Button to turn test mode off has been added to latest release

As well as NAVI10 support 

Only Strap injection and Power Play support (read from vbios/registry and write to registry for now)

Latest version

Cheers!

Thanks.  I'm on Claymore 11.9 so I'm not using his newer strap injection version.  I'm only trying to mess with the REF at this point, but other timing regs also refuse to update.  I'll d/l the latest and keep at it ... see if I can find the common thread.

[xMindx163]

https://drive.google.com/open?id=1Gtteb5MIp6Ex1vHLuofiNBIfdKBFcXX6
Clay strap mod (Mind163). 36.4 (580 8GB Sams)

[WhackOBill]

Not sure I understand the reference to the file c:\windows\system32\drivers\AmdGpuTweak.sys on GitHub.  Where is this file and is it required?

[livada]

how close test mode?

every reset win go in test mode.

c:\windows\system32\drivers\AmdGpuTweak.sys not exist

[Iamtutut]

I always get a "NullReferenceException" window asking me to activate the test mode. I allow it, then reboot. My system is then running in test mode (indicated on the bottom right of the windows desktop). But when I launch the AMD.Memory.Tweak.XL, I get the same "NullReferenceException" window.

How can I solve this please ?

[WhackOBill]

how close test mode?

every reset win go in test mode.

c:\windows\system32\drivers\AmdGpuTweak.sys not exist

Look 10 messages back.  bcdedit /set TESTSIGNING OFF

[pstarSR]

https://drive.google.com/open?id=1Gtteb5MIp6Ex1vHLuofiNBIfdKBFcXX6
Clay strap mod (Mind163). 36.4 (580 8GB Sams)

Can we get the actual setting used to achieve this? Vega settings are posted like they are the new HOT instagram whore.

I ( and so does everyone else ) realize that bios mods/straps are available for the Rx series cards. so what, post settings so others can see what works and what doesnt.

so if you have settings for the rx-series cards post them. so others can see what changes are actually working vs guessing.


so far I have changed

tRFC setting down in 10's till 150 (from 219 WHEN MINING ) - stable
REF to 30 - stable

this gets me about 1kh more on an rx580 samsung memory 8gb ( MSI OC armor ) stock bios - for Turtlecoin algo ( CN/pico CN/trtl ) - 7khs @ 80watts ( 1150/2150 OC, undervolt -162 MSI AB )

[SulliJM1]

I gotta say, this tool is cool as hell.

Although, I'm having some trouble with it. Probably because I'm a noob.

I went ahead and downloaded it and installed it, manually with the terminal, running HiveOS, the VEGA supported version.

I'm running 6x 1070s, 1x 1070ti, and 4x Vega 64s.

The trouble I'm having is HiveOS kinda sucks at overclocking when it comes to AMD. Claymore isn't doing the job either; and my Linux illiteracy and lack of Google returns isn't helping.

I love how you can modify the hell out of the stuff with this tool, but I can't seem to get the GUI working so I can modify the DPM/Memstates (which, honestly, is all I'm tryna do). Is there a way to get the GUI working in HiveOS that I just don't know about? Or a command line? Or do I just suck at life?

[fr4nkthetank]

Thanks for the update, looking mighty fine.

[rednoW]

https://drive.google.com/open?id=1Gtteb5MIp6Ex1vHLuofiNBIfdKBFcXX6
Clay strap mod (Mind163). 36.4 (580 8GB Sams)

nice result but not reasonable ))

[livada]

how close test mode?

every reset win go in test mode.

c:\windows\system32\drivers\AmdGpuTweak.sys not exist

Look 10 messages back.  bcdedit /set TESTSIGNING OFF

thx

[lncm]

Great tool.

[Iamtutut]

I always get a "NullReferenceException" window asking me to activate the test mode. I allow it, then reboot. My system is then running in test mode (indicated on the bottom right of the windows desktop). But when I launch the AMD.Memory.Tweak.XL, I get the same "NullReferenceException" window.

How can I solve this please ?

Still get this issue, if anone can help please.

[eltech]

Can't wait to see linux version of XL tool !

[lncm]

Hi there.

Please help me here. Great, awesome tool, makes my vegas do 2050 H/min @ 1200 core / 940 memory.
However, I can't change memory settings with CLI, only GUI version.
Making a bat file and giving permission to run as administrator to WinAMDTweak.exe does nothing to memory timings, running from an administrator command prompt gives something about a missing or can't open EIO.DLL file.

GUI does work, just more tedious to load values and apply to 2 cards but I'm setting the clocks and voltages with this too, so no problem.

Cards are MSI Airboost and Sapphire Pulse.

This is the config file for both:

Code:

<?xml version="1.0"?>

-<values maxtemp="85" tdplimit="0" zerorpm="False" timing="0" rfc="248" ckestag="2" wrdata="1" rdlat="14" wrlat="4" rddata="16" cke="6" cpded="2" xp="6" stag="7" rfcpb="128" cksrx="8" cksre="8" pd="6" xsmrs="6" xs="216" mod="12" mrd="8" ref="15600" rdwr="17" wrrd="1" wrwrscl="3" wrwrsc="1" wrwrsd="2" wrwrdd="3" rdrdscl="3" rdrdsc="1" rdrdsd="2" rdrddd="3" rrefd="7" wr="13" wtrl="7" wtrs="3" cwl="6" faw="14" rtp="5" rrdl="3" rrds="3" rppb="12" rpab="12" rcpb="44" rcab="44" rcdwr="5" rcdrd="12" ras="28" cl="17">


-<mem>

<p0 vddc="800" clock="167" enabled="0"/>

<p1 vddc="800" clock="500" enabled="0"/>

<p2 vddc="900" clock="700" enabled="0"/>

<p3 vddc="825" clock="940" enabled="1"/>

</mem>


-<core>

<p0 vddc="800" clock="852" enabled="1"/>

<p1 vddc="800" clock="991" enabled="1"/>

<p2 vddc="800" clock="1138" enabled="1"/>

<p3 vddc="825" clock="1202" enabled="1"/>

<p4 vddc="825" clock="1202" enabled="1"/>

<p5 vddc="825" clock="1202" enabled="1"/>

<p6 vddc="825" clock="1202" enabled="1"/>

<p7 vddc="825" clock="1202" enabled="1"/>

</core>


-<fan>

<p0 fan="31" temp="30"/>

<p1 fan="42" temp="44"/>

<p2 fan="70" temp="55"/>

<p3 fan="100" temp="70"/>

<p4 fan="100" temp="72"/>

</fan>

</values>

One card runs superb with 825 mv Vcore. However, the Sapphire card doesn't get lower than 950 mv and I can't figure out why.



Tried drivers 19.7.1, 19.8.1, 18.6.1. Same thing.

Tried a custom PPT but then this card refused to do more than 500 Mhz memory.

The Vcore seems to be locked to Vmem in some way. If I set 1000 mv in P4 memory setting, the core gets to 1000 mv also, and then it doesn't get lower unless you reboot.

I really can't figure out this crazyness in Vega's voltage/speed control. Please help.

[clousian]

I'm running a batch of 8Gb 470/480/570/580. All running at REF 30 now and getting an average of 150 - 200h/s extra a card on CN-Conceal. These are all non-bios modded. Extra H/s bonus for setting tRFC (155) & tRC (69) across all. All around 1750 - 1800h/s a card. Haven't started playing with the straps yet. Hope this helps someone starting out.

[Iamtutut]

I always get a "NullReferenceException" window asking me to activate the test mode. I allow it, then reboot. My system is then running in test mode (indicated on the bottom right of the windows desktop). But when I launch the AMD.Memory.Tweak.XL, I get the same "NullReferenceException" window.

How can I solve this please ?

Still get this issue, if anyone can help please.

Am I the only one to have this issue ?

[miuchins]

Update:

Decided to release a Winblows supported version.

I've tested it on 2 systems with Latest adrenaline version (one with a Vega gpu, the other with a 570) and confirmed working.

Check OP for link.


Please post results here. That's all i'm asking

Cheers guys!

@Eliovp, once again thanks for your efforts here getting it onto windows. Much easier for traditional Vega Users with PPTs and Overclocking tools to really test the limits of your tool!

For my part, I'm getting pretty decent results on ETH; Reference Powercolor Vega 64 on latest Adrenalin 19.3.3 drivers.
Thanks to Windward for getting me started on values for parameters.

https://i.imgur.com/6bedvOO.jpg

Given the generosity of Eliovp in even making this tool available, I'm not gonna be the guy that takes and doesn't give back.

For those curious, here's what I put in a batch script after I honed in on parameters.

(PATH to folder where MemTweak is stored)\WinAMDTweak.exe --CL 16 --RAS 30 --RCDRD 14 --RCDWR 14 --RC 44 --RP 14s --RRDS 3 --RRDL 5 --RTP 5 --FAW 20 --CWL 7 --WTRS 4 --WTRL 9 --WR 16 --WRRD 1 --RDWR 19 --REF 17550 --MRD 8 --MOD 15 --PD 8 --CKSRE 10 --CKSRX 10 --RFC 244

Run before starting the miner. For some reason, injecting the timings when mining would crash the miner if FAW>17, but FAW>17 is okay if injected prior. Also, RC<44 led to incorrect shares being found. No guarantees of stability... I was simply looking for accepted shares w/o rejects in short runs. I need to read up as well on compatible RAM timings... lower RC seems to drive HR the most.

Happy to answer any Q's; also, memclock was 1107 and was using PhoenixMiner4.2c
                 

Thanks for Your share,
picture for my setting for 2 Vega64 ,
https://www.flickr.com/photos/92036598@N05/48551912691/in/dateposted-public/

46Mh/s for each card

[fr4nkthetank]

dumb question but any workaround to having the full window when working on 640x480