Originally Posted by bluezone
Sorry BT I have to retract what I said earlier. When I first received My Nano there was about a 350-400 point advantage in FS scores with tuning Per DPM. That was with old drivers. With current drivers there is not a significant difference in scores. Temps are 1-2C lower though than using offset voltage.
I believe current drivers are actually completely broken in regards to memory overclocks. I tried my R9 290 with 16.8.2 and the memory overclocks don't work there, either.
I seem to be the only person that has actually noticed this, so I am going to file a report with AMD.
EDIT: In case you aren't up to date with my saga: memory clocks don't work with the RX 470 or RX 480 with 16.8.1 or 16.8.2, from my experience.
With the RX 470 I was unable to use a driver older than 16.8.1, so I came to suspect a faulty card, but then the card started messing up pretty bad anyway, so I RMA'd it and bought an RX 480 - with 16.7.2 I can overclock the memory fine, but there are other bugs. 16.8.2 has other problems (cursor corruption, for starters), but doesn't crash my games.
It looks that whoever fixed the memory overclocking range in the driver actually broke it.
To check, all you have to do is see if the screen flickers when you set the memory clocks - they should. If not, then the memory clock is not actually being engaged, despite all utilities saying otherwise. You should be able to set any memory clock you want and GPU-z will say you did it, but you will get no memory errors nor any improvement in speed.
Created a thread: http://www.overclock.net/t/1609366/amd-16-8-1-16-8-2-memory-clocks-not-workingEdited by looncraz - 8/21/16 at 6:17am