I can use:
Sapphire Trixx v5.2.1
or
Sapphire Trixx v6.5.0
to overclock the HBM memory frequency on AMD Fiji GPUs with AMD Crimson ReLive Driver 16.12.2
(https://www.amd.com/en/support/kb/release-notes/rn-rad-win-16-12-2 )
Here is an example of using Sapphire Trixx v5.2.1 to set a +10% memory frequency overclock (550MHz) on R9 Fury X using the AMD 16.12.2 Driver.
The AMD Radeon Crimson ReLive 16.12.2 Driver Global Wattman plots the HBM memory frequency and it also registers the increased memory overclock from 500 to 550 MHz.
The applied memory overclock using the above driver is also shown in GPUz as shown here:
If I attempt to use Sapphire Trixx v5.2.1 to Sapphire Trixx v6.5.0 versions to overclock the HBM on AMD Fiji GPU using any Driver later than 16.12.2 up to the first version of Adrenalin 2019 I see the following behavior when I apply the HBM Memory Overclock using Sapphire Trixx:
Once the HBM memory overclock is applied using Sapphire Trixx the main GPU clock is downlocked to 300MHz and is stuck there.
The 3DMark Performance is completely wrecked, and very low FPS performance and scores are seen.
I have been looking at the newever versions of Sapphire Trixx as well (TRIXX_installer_7_0_1).
It no longer supports any overclocking features on R9 Fury X - in this example the 550MHz HBM overclock was applied using Sapphire Trixx v5.2.1.
Here is a quick look at the latest version:
This version of Sapphire Trixx uses Trix Boost to create custom downscaled resolutions in Windows and then "upscaling" - for example stretching a 3296x1854 to full 4K. There is also an option to apply Radeon Image Sharpening from the Trixx interface if the AMD GPU supports it.
One problem I have found is using these custome resolutions means the Radeon Overlay will not work.
I will give details about that in another thread.
Although it looks like the 550MHz HBM overclock is applied, according to GPUz and Sapphire Trixx, the AMD driver is clearly not actually applying that overclock to HBM. Multiple 3DMark benchmark runs demonstrate no performance benefit at all with this "applied HBM Overclock" on Adrenalin 2019 Drvers. Although the GPU clock is no longer deliberatly downcloked to 300MHz it looks like HBM overclocking is still locked down since benchmark results are almost identical.
Still no explanation why this was ever done.
I see no problems with any of my Fiji GPUs if I use Sapphire Trixx to overclock the HBM on the 16.12.2 driver.
I file an AMD Reporting form pointing to this thread next.
Then I contact Sapphire Support.
AMD Reporting form filed and pointing to this thread:
