AnsweredAssumed Answered

Bad Framerate Drops with Crimson Drivers; Fury X

Question asked by endereverend on Dec 18, 2015
Latest reply on Dec 19, 2015 by silentgame



I got myself a Fury X;


All my games ran buttery smooth with the catalyst drivers; even though the card showed high activity and got pretty warm.


Then i installed the Crimson drivers; Many of my games ran marginally worse, or began having framerate drops;


Fallout 4, for example runs buttery smooth 60+ FPS (except in crowded large open areas, stays above 50 more or less always) on ultra settings with the latest Catalyst Beta driver.

With the Crimson driver, the game fluctuates wildly over and under 60FPS, and even drops below 30, suddenly in certain areas (Fixed areas, even indoors, areas that should be really low cost)


These drops are 100% replicable; As a drop occurs, the activity LEDs on the Fury also drop significantly.


Fallout is not an exception, this happens in many of my games, under varying circumstances.


GPU activity and framerates drop hand in hand, seemingly for no reason.


Looking at the symptoms i'd assume there is something wrong with the Framerate targeting control.

I have tried setting it to 60, 100, off ... globally and/or on a per game basis.

Frustratingly all of this does exactly nothing to alleviate the issue.

Same for any and all other settings in the AMD settings, and or Fallout 4 settings;


The Fury X stubbornly refuses to produce acceptable, stable framerates with the crimson drivers, all the while seemingly just idling around on it's lazy behind.


I've tried the latest crimson drivers; same results.


I've downgraded back to the latest Catalyst Beta, my card runs a bit hotter (all within acceptable range) but actually does it's job.

Though i can't access the settings, with the dreaded "Catalyst Control Center cannot be started. There are currently no settings that can be configured using AMD CatalystControl Center." message.


Is this a know issue?

It doesn't seem to be listed as such.

It seems to be a global issue, not game specific.

Can i count on this being fixed in a future crimson update?


Or should i try something else in the meantime?


I'm on WIN10 64bit