Thanks for the explanation.
I wonder if AMD have done something on their end to block 3rd party tools from making changes to overclocks etc. as iirc, using these tools in the background has been what's causing so many issues with the new relive drivers... and the last 2 drivers have been working great on my 290, originally had to revert back to 16.11.5 due to crashes, poor performance etc.
I wonder if AMD have done something on their end to block 3rd party tools from making changes to overclocks etc. as iirc, using these tools in the background has been what's causing so many issues with the new relive drivers... and the last 2 drivers have been working great on my 290, originally had to revert back to 16.11.5 due to crashes, poor performance etc.