Gpu stuck at max memory clock!

[Houndz]

Essentially my 390 sapphire's memory clock would be stuck at max (1500mhz) even at idle, whilst my core clock stays at ~300-400mhz. 

 

This started happening after I repasted my gpu with MX4. 

 

Any ideas? I noticed that dust got on the ram's thermal pads, but im not sure that affects anything. 

[Houndz]

Btw i have done the following:

- fully uninstalled radeon drivers, then reinstalled at latest version

- reinstalled at an older version of radeon drivers (17.7.2)

- changed my monitor from 144hz to 60hz

- i even opened my gpu again to check anything wrong, seems fine from what i saw. 

 

 

ALSO, SYSTEM SPECS:

R7 1700 at 3.8ghz

3000mhz 16gb ram

r9 390 8gb sapphire

1x 1080p LG ips monitor

1x 1440p 144hz ips Pixio monitor

 

[Houndz]

After further testing. When I unplug my 144hz 1440p monitor from my pc, the memory clock would to down to 150mhz, then back up to 1500mhz, then down again. 

 

ANY HELP PLEASE?

 

 

[Analog]

Reinstalling the graphics driver doesn't always make a difference as there are always files left over scattered throughout the system. I would check in the driver itself if there is a high-performance option there that got checked somehow. I haven't had an AMD card in quite some time, but there should be something of that sort. Another thing to check is if you accidentally pressed the dual-BIOS button of that card. It has a legacy and UEFI mode. Could be something with that. 

[Houndz]

11 hours ago, Analog said:

Reinstalling the graphics driver doesn't always make a difference as there are always files left over scattered throughout the system. I would check in the driver itself if there is a high-performance option there that got checked somehow. I haven't had an AMD card in quite some time, but there should be something of that sort. Another thing to check is if you accidentally pressed the dual-BIOS button of that card. It has a legacy and UEFI mode. Could be something with that. 

Yo, thanks for the reply. The dual bios has been left in UEFI mode since I installed the gpu. Ill give legacy a try.

[Houndz]

Putting it in legacy mode didnt fix the problem, any other thoughts?

[Analog]

No idea mate. The last thing left is a fresh Windows install. 

[Princess Luna]

Did you DDU in safe mode before installing new drivers?

[Houndz]

On 11/8/2017 at 10:28 PM, Princess Cadence said:

Did you DDU in safe mode before installing new drivers?

Yep, I used DDU in safe mode. I think the AMD drivers 17.7.2 and up are giving me problems, Ive seen in other forums where people are having a similar problem, hope they fix it soon.

[MedievalMatt]

6 minutes ago, Houndz said:

Yep, I used DDU in safe mode. I think the AMD drivers 17.7.2 and up are giving me problems, Ive seen in other forums where people are having a similar problem, hope they fix it soon.

does a PC restart work?

 

I used to have this happen after playing TF2, the only fix was a restart of the PC?

[ryann0213]

On 11/10/2017 at 9:46 AM, MedievalMatt said:

does a PC restart work?

 

I used to have this happen after playing TF2, the only fix was a restart of the PC?

I have a Asus Rog Strix 1070TI, my gpu max at 8000 mhz. the only fix i know is to restart the pc. how did you fix yours? TY

[MedievalMatt]

10 hours ago, ryann0213 said:

I have a Asus Rog Strix 1070TI, my gpu max at 8000 mhz. the only fix i know is to restart the pc. how did you fix yours? TY

I didnt, its a bug with the game.  When you close it it doesnt release something in GPU memory fully, so the clocks stay high.  It wont hurt anything.  its just annoying if you pay attention to it.