• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

GUP Help

Soldato
Joined
5 Nov 2014
Posts
9,243
AMD 390 GPU Help

I bought a 390 in the black Friday sales.

got it and installed fine with no issues at all.

I have noticed in CSGO that my fps is all over the place going as long as 130 mark.

I installed MSI after burner and can see the core speed is going up and down like a yoyo!

ranges from 500mhz to 880mhz but never reaches its factory clock of 1040mhz.

I tested in minecraft as well (only 2 games I have installed atm) and this sat around 500mhz.

to make sure everything was ok I ran fire strike on the 3D mark demo and this reached 1040mhz and didn't drop at all.

does anyone know why this would happen in csgo and minecraft but not fire strike?

I have tested on W10 and 8.1, done a clean install of windows as well.

thanks a lot!
 
Last edited:
cheers for the replies guys.

i am running the latest AMD drivers, i have done a clean OS install and tested on windows 10 and windows 8.1 which both showed the same issue.

when i ran fire strike from the 3d Mark demo software on steam i reach the 1040mhz core clock speed without any issues and doesnt drop at all

i tried to increase the power limit +10% and this made no difference.
 
Last edited:
forgot to add for testing i put back in my old GPU which is a Radeon HD 5830 1GB and this sites on a usage of 95%+ all the time and no dips and core clock sits at 800mhz which is the max core speed on that card
 
anyone else have any other suggestions?

cant see why firestrike works fine without having to change any power options but CSGO and minecraft both dont seem to get the full potential out of the card
 
Core clock bouncing up and down like a yoyo is a known problem with the Crismsons, loads of people are getting it (including me), best to roll back to the previous drivers, 15.11.1s, until AMD fix it. :)

thank you guys

i will give that a try, my old GPU (AMD as well) dont even use crismsons drivers its that old lol
 
Back
Top Bottom