F5F Stay Refreshed Power Users Overclocking Gpu memory overclock stuck

Gpu memory overclock stuck

Gpu memory overclock stuck

L
louie018
Posting Freak
824
07-10-2016, 05:57 PM
#1
Yesterday I experimented with overclocking the GPU (not extreme) and adjusted the GPU clock from 1070 to 1120 MHz while changing the memory clock from 1550 to 1580 MHz. After that, I reset it back to default. My clock speed returned to normal, but the memory clock remains stuck at its current setting. The scale is fixed between 1580 and 2000 MHz, which I believe my card can't reach anyway.

I'm still seeking your assistance. I tried updating and reinstalling the drivers, but nothing worked. The drivers are the latest Crimson version (16.3), and the specifications are listed below.

Here is a screenshot:
http://i.snag.gy/x0wZi.jpg
L
louie018
07-10-2016, 05:57 PM #1

Yesterday I experimented with overclocking the GPU (not extreme) and adjusted the GPU clock from 1070 to 1120 MHz while changing the memory clock from 1550 to 1580 MHz. After that, I reset it back to default. My clock speed returned to normal, but the memory clock remains stuck at its current setting. The scale is fixed between 1580 and 2000 MHz, which I believe my card can't reach anyway.

I'm still seeking your assistance. I tried updating and reinstalling the drivers, but nothing worked. The drivers are the latest Crimson version (16.3), and the specifications are listed below.

Here is a screenshot:
http://i.snag.gy/x0wZi.jpg

F
Flashice
Member
172
07-10-2016, 07:18 PM
#2
I used the AMD cleanup tool, restarted the system, reinstalled the drivers, rebooted again and the problem disappeared.
F
Flashice
07-10-2016, 07:18 PM #2

I used the AMD cleanup tool, restarted the system, reinstalled the drivers, rebooted again and the problem disappeared.

T
121
07-11-2016, 12:19 AM
#3
I used the AMD cleanup tool, restarted the system, reinstalled the drivers, rebooted again and the problem disappeared.
T
the_true_benja
07-11-2016, 12:19 AM #3

I used the AMD cleanup tool, restarted the system, reinstalled the drivers, rebooted again and the problem disappeared.