Weird GPU Bug

[007agentHP]

hello, my 280x that i have been running at 1500 Mhz  is having a weird bug. i wanted to see what kind of uniengine valley scores i got over stock. i start with stock, it normally went to its 1020 Mhz,  and stayed there. now when i overclocked it again, it was locked at 870 Mhz. even with a mild 1125 Mhz overclock, its still locked at 870 MJhz (pictures included)

any help would be appreciated. at idle its 500 Mhz and under load its 870

 

idle

 

load

 

 

any ways to solve this?

its not thermal throttling cause under load is at 51 C at stock and 76 C overclocked to 1500 MHZ

[Badger906]

its msi after burner. I get this with my 980ti.

sometimes it shows its only running at 800mhz while gaming. despite me getting no side effects from this.

[007agentHP]

its msi after burner. I get this with my 980ti.

sometimes it shows its only running at 800mhz while gaming. despite me getting no side effects from this.

i get side effects. lower FPS and uniengine score

[Chicken Chaser]

I have the same problem. I have a 280x and at load it caps at 870 Mhz when previously it would go to 1020 Mhz. I notice FPS drops in-game when previously there were none. I have tried updating to the newest AMD drivers 15.7.1 with the latest hotfixes and I used DDU to wipe clean the old drivers. Despite setting my core clocks at 1020 mhz, the readings were always 870 mhz. Would love for someone to take a look at our problem..

 

EDIT: I've discovered if I run the game without Google Chrome open, I get my expected 1020 Mhz Core Clock speed again. As soon as I open it and play something off YouTube, Core Clock drops to 870 Mhz. I'm going to see if I can disable GPU acceleration.

 

EDIT 2: You can disable it with these instructions. http://www.pcadvisor.co.uk/how-to/internet/how-turn-off-gpu-hardware-acceleration-in-google-chrome-3605455/

 

EDIT 3: I just tested and disabling GPU Hardware Acceleration in my browser has fixed the problem. While I'm in-game with Chrome open, I get my expected 1020 Mhz again. Yippee. You can look up how to do this for your browser if you don't use Chrome.

[Zhuocheng]

try a clean install of the drivers