Here's my system, for starters—
Dell Inspiron 5737
core I7-4500U 1.8 GHz
Radeon HD8870M dGPU (detected by Windows as R9 M200X)
Intel HD4400 integrated GPU
8GB DDR3
The problem started a few months ago, whereby, at some points when playing, the screen would start to stutter with lower FPS than usual, while using the 20.4.2 Catalyst software.
After a small interval during which the card resumed behaving normally, I kept getting lower FPS in games more quickly and for a longer time.
While exploring this issue with GPU-Z, I've noticed that the GPU clock speed gets stuck at 400 MHz, and the memory clock speed gets stuck at 300 MHz, with no way to change it by loading games or by using FurMark. This happens when after using the GPU for a short time (~20 seconds) and when the GPU temperature is about 64 degrees Celsius. While the clock speed is at 400/300 MHz, the GPU cannot be used at it's maximum speed. After this “low clock-speed” state occurs, after a while when not using the GPU (~5 minutes), the clock speed changes to an even lower speed 300/150 Mhz, and the GPU can once again be used at its normal usage level of 775/1000 MHz, and the cycle with the frozen clock speed happens again.
I've had periods where my GPU could be used by games until it reached 92 degrees C, without it changing the clock speed. Curiously, more recently, if I leave the game open and do not interact with it, I get 775/1000 Mhz normal speed. As soon as I interact with a game object—and in multiple games for that matter—the GPU almost certainly, with a few exceptions, changes to 400/300 Mhz.
The following solutions have been tried:
Nothing has had any effect.
With this dGPU, I don't have access to power usage indicators or to the “PerfCap Reason” indicator.
What advice can you give me regarding this issue, since I think it's rather unlikely that the GPU is “terminally broken” because I could get it to heat up to 92 degrees without it shutting down, only until I interacted with the games in question (e.g. moved the mouse over a button or opened an in-game menu).
It seems to be a software issue, but I've ran out of ideas on how to deal with the problem.
Thanks!