AMD's half-broken porting of OCing API for older GCN cards to the latest API that results in erratic behavior with memory overclocking not only in Afterburner and other third-party tools but also Wattman which has also been confirmed by Unwinder.

I've been reading this story for a long time here. But it's a fact that in here I can OC with MSI AB, and it works, I can even make a video if you want..

AMD's half-broken porting of OCing API for older GCN cards to the latest API that results in erratic behavior with memory overclocking not only in Afterburner and other third-party tools but also Wattman which has also been confirmed by Unwinder.

Old good and traditional Overdrive 6 overclocking/monitoring/fan control API for 2x0/3x0 series cards have been totally locked for such hardware and now AMD try to port support for those old cards to new Overdrive 7 (aka OverdriveNext) API, which was previously supported by Polaris architecture only. So you'll absolutely need a software with OverdriveNext API support to get it working, old legacy software with Overdrive API support will simply stop working now due to lacking support of legacy Overdrive API... ...4.3.0 in official overclocking mode is already compatible with OverdriveNext API.

Even Unwinder himself posted in these forums AMD changed things in their ReLive drivers that closed AfterBurner OC options for AMD GPUs. I don't think you dare to say that you know his software better than him! :3eyes:

...4.3.0 in official overclocking mode is already compatible with OverdriveNext API.

@sammarbella, THEAST: Stop spreading this misinformation guys. MSI AB is working fine with ReLive Edition drivers on older cards - see Unwinders post above

I have a Sapphire R9 290 Tri-X with stock BIOS, Crimson ReLive 17.2.1 and MSI AB 4.3.0 and I have no issues with OC via MSI AB or clock fluctuation. What's your MSI AB settings?

As I posted above, these guys clearly missed a last part of post from Unwinder

That reply is from 4-5 months ago; his latest reply is here. If it is working for you, be happy; Unwinder himself already confirmed it doesn't work for many people and it is not going to work until AMD fixes their broken API for older cards.

Those who don't know something normally don't make ultimate statements telling where the fix is supposed to be without having even a basic understanding of the subject of discussion. And I explained what's going on a few times, but sadly one nice person from this thread seem to have personal issues and enjoy trolling on AB related topics during a few months and ignoring any requests to stop. So I'm forced to repeat the same over and over again. The facts are: - There is no any newer version of overclocking API available from AMD side, so updating overclocking tools absolutely won't make them "more compatible" with ReLive as they currently are. - OverdriveNext, the latest version of ADL overclocking API is almost half year old, it was introduced on Ellesmere/Baffin launch, so any overclocking tool with Polaris architecture support is already using the most recent version of AMD overclocking API during long period of time. So that's not something new, that must to be updated by third party developers, they are already using new overclocking implementation for months. What AMD did with ReLive was an attempt to provide unified overclocking API (and control panel) for older generations of cards, and that's their first attempt to rewrite overclocking API for 2xx/3xx and Fury series. Things gone wrong for 2xx/3xx and memory overclocking implementation is currently not working properly on some systems (depends of number of monitors and refresh rate AFAIK), even in Wattman itself. - The issue on affected 2xx/3xx systems can be easily replicated with any tool using OverdriveNext API to adjust memory clock. It cannot be fixed from application side, also applications cannot use the previous (and stable) version of Overdrive6 API because some developer from AMD got a "nice" idea to ignore backward compatibility and simply killed old Overdrive6 API in the driver for such cards. Utilities cannot fix issues existing in driver's overclocking API. That's the reason why it is not fixed in ANY utility yet and no utility developer promise you to provide a fix.

What are yours?Mine don't work obviously. You told it worked fine with your settings, show them please so i can fix mine. 🙂

In that case it affects the GCN 1.1 and GCN 1.2, but not the GCN 1.0, because GCN 1.0 is still using the ancient overdrive and not the Wattman (or AKA Overdrive NEXT) You might have problems Sammarbella and make sense since Unwinder say it, altough, THEAST wasn't suppose to have problems.. Anyway here it is the video: https://www.youtube.com/watch?v=7vcTc_hbmhE I used my Monero Mining tool in order to stress test the GPU, and the 500MHZ/1200MHZ idle is related to the recorder being, recording. The normal idle is 300/150MHZ The Bios are not tweaked or Modded, it is the stock Bios. Cheers

The issue on affected 2xx/3xx systems can be easily replicated with any tool using OverdriveNext API to adjust memory clock. It cannot be fixed from application side, also applications cannot use the previous (and stable) version of Overdrive6 API because some developer from AMD got a "nice" idea to ignore backward compatibility and simply killed old Overdrive6 API in the driver for such cards.