AMD Memory Tweak - Read/Modify Timings on the fly!

Hey all,

My first post here, thought i'd make it a good one ;-)

I have done a lot of debating with myself whether i would share this.
Well, i decided to do so and on top of that, open source it.

What is this?

Well, with this tool, you are able to change memory timings on the fly.
Yes, you read that correct, you can modify almost any value while the GPU is running.

Current support:
- AMD GPU's with GDDR5, HBM(Later) and HBM2 memory. (check code for more details)
- Linux only
- Windows supported

As of now, also a GUI version (Windows)
Can be found in the releases section on github.
Link: Github
Direct Link for latest GUI version: GUI
Direct Link for latest CLI version: CLI

Some shots:
GUI



CLI




Check Readme for some additional info such as command line parameters and how to build.



Enjoy and have fun tweaking!

 

cool stuff

 

Great Mod -> Thank YOU

More about Timings:
-> http://alexanderhuzar.angelfire.com/files/ram_timings.htm

==
I've tested and find out:
When i Put tCL 14 or less it reverts to last good value - tCL16
Working Values for tCL: 16,17,18 up to 24 all up to 18 are fast for Bandwidth & Latency (Great for Gaming)

So we can say that Driver falls back to last working Value when we exceeds Defaults.

 

I'd change the app's title to reflect that it's used to tweak -GPU- memory.
I was about to download it to tweak my DDR4 until I noticed.

 

Here is my Tweak for HBM2 (working without V change)
Just Tweaked some moare

Also good method to approach 1200HBM2 is to lossen some tCL *-* (first timings )
I think 1230-1250 is easy achievable now thanks to this MOD.
Thanks to the speed, VEGA 56/64 can do even better, closer to Vega 2 (without +1800MHz )

We need somebody to do some Tests with hefty 1200+ for HBM2.
Just enter Vega 2 Timings (first 4 rows)

Spoiler: My current settings

Note:
Tested in UE4 Vampyr (UE4 is sensitive to Mem OC)

Note 2:
Always set timings with same OC Profile (to avoid app. error, or hit reset)

 

Thanks to your tool, i can confirm that extending the max tuning level does actually work at least on polaris , and is not placebo, also confirms the reboot bug I observed when using the memory timing level setting ( ie if you set timing level 2 at 2000mhz, upon reboot it will apply 1750mhz level 2 timings to 2000 mhz)

 

Here is memory timings for Vega Mem OC:

Auto, T1 & T2

The difference is only in Timing 3 Values of MemTweaker.
4,6,5
3,5,5
2,4,5

Spoiler

Here is Stable so far....

Spoiler: My new Default

 

Glad you guys are having fun!

On a Vega, try to start from AMD's timing level 1, set FAW to 18 and push tREF higher.

Cheers!

 

I think that work done here is great. I would have had much more fun if I did not fine tune timings for my RX-580 for 2250MHz memory clock long time ago.
Took only few hundreds of vBIOS edits, flashes and tests.

With this, it would have been easy and quick. So, I am happy that you did release it. Say thanks to other guy who worked on it w/ you.
= = = =
And I hope that your work will be easily adapted to GDDR6. (Navi)

 

This looks like an amazing program, I can only imagine how useful this will be to people with relevant hardware to make use of it (slightly weeps for my Fury's HBM) - fine tuning on the fly before baking a new bios rom is a great feature!

 

Strong ATI Moding Scene is Back baby

 

Some benchmark stable settings:

UPD. Stable with Gaming, my new OC.

Spoiler

 

Looking to play around with this. Couple of questions.

Do you have to run both the OverdriveNtool and this at same time?
Which Timings are the ones to play around with?
What program is best for testing?

 

Anyone with the 580 tried playing with this? I would like to know how that went pls.

 

@Eliovp Thanks for doing this....I found it this morning elsewhere (a bitcoin forum)...but great to see you post it here. GREAT WORK. Been playing with the tool this morning on Vega 64 and it does rock the timings. Not had a chance to play around with on my RX 580s...but I have those already bios flashed with tight timings.

 

Im using as always: WattMann + OverdriveN & after restart -> Just apply Your saved Stable HBM2 OC (with Our new VRAM Tweaker).
Then im using only OverdriveN (for changing OC Profiles, not every game needs 1670MHz )

Note: For Vega 56/64 try my stable OC

Spoiler: Working Fine

 

No you do not have to run both.
There is really only so far about 5 main timings...SO FAR..I have only been testing this today. Seeing gains.

I apply my Softpowerplay table I created the VegaSoftPowertable Editor far more options then overdriventool to create the table.

Then I apply my Wattmann custom settings if needed. I saved the setting for ease.

Then I use this tool to start adjusting timings and see where it goes.

So far the only timings I have adjusted are tCL, tRCAB, tFaw, tREF*, and tRFC

*Note 1 tREF does not work the way we all generally think of timings...the larger the value the better the performance. Default on my vega64 is 3600...I am up to 14400 and still testing. The rest the lower you can get stable the better. I am seeing tRCAB my lowest value is 44 with my card.

For testing...use a variety of things that will fully test the loads...I used 3dmark, aida64 gpu test, realbench, farcry and a few others.

Also keep in mind...since this just adjusting the registries on the GPU itself, it does not save...so if you artifact, or lock-up...after a reboot you will be back to stock settings. Also if that happens..you have to go through the steps I mentions minus having to reenter the softpowerplay table registry.

And remember timings will also depend on how high you are trying to push the Vram speeds.

One nice thing about this...it would of saved me days and days of time tuning my RX 580. Since this is on the fly...I could test without actually creating new bios. I think I made about 300 to 400 RX 580 bios. If you already have a modified bios on these gpus with tight vram timing straps, you will not already get much performance. This is for Polaris GPU with a modified bios with tight vram timing straps.

Also you must apply the timings from the new tool on each restart at this time.

 

If you crash it does reset the timings that the new tool sets...so you also have to apply them again. But yeah also on restarts.

Also you can use the export file and import file in the tool to also have your overdriventool settings. Since it is fully integrated.

 

Guys please share Your screen (with Stable OC)
For everyone to profit

 

Vega 2 scores >990GB/s !
4x HBM2 is a Beast