Help Please

[cojkeee_11]

I have been triying to fix this for 2 weeks and nothing...I have got new (used) mobo and ram and has finnaly happy that i will be able to play some games but ofc no.The problem is my gpu.When i try to play some really gpu intensive games (rise of tomb raider nfs the run etc),I get big fps spike in first couple of seconds (60-70fps) and than it drops into the 20s.I tried running them on max and lowest(even resolution) and same thing.Its like gpu is trying for couple of seconds and nothing.I looked into msi afterburner graphs and immediately i saw that the gpu clock was the problem,after restart and boot in to the game it spikes into 100mhz or 1150 mhz and drops and goes bettwen 300 mhz and 400mhz and never goes up(while fps is the same 15-25).I tried uninstalling gpu drivers at least 10 times ,used DDU and it stays the same.Any help would be great,thanks.

[faziten]

2 minutes ago, cojkeee_11 said:

I have been triying to fix this for 2 weeks and nothing...I have got new (used) mobo and ram and has finnaly happy that i will be able to play some games but ofc no.The problem is my gpu.When i try to play some really gpu intensive games (rise of tomb raider nfs the run etc),I get big fps spike in first couple of seconds (60-70fps) and than it drops into the 20s.I tried running them on max and lowest(even resolution) and same thing.Its like gpu is trying for couple of seconds and nothing.I looked into msi afterburner graphs and immediately i saw that the gpu clock was the problem,after restart and boot in to the game it spikes into 100mhz or 1150 mhz and drops and goes bettwen 300 mhz and 400mhz and never goes up(while fps is the same 15-25).I tried uninstalling gpu drivers at least 10 times ,used DDU and it stays the same.Any help would be great,thanks.

complete info in brand and model of every component in your rig would be nice to help debugging. Driver version and game ofc. 

Posting a GPUz sensor tab screenshot while gaming is helpfull too (the vcap reason usually reveals what is the culprit). 

 

The GPU is somewhat stuck at minimum clock, judging by those clocks it's either an old Nvidia architecture or an AMD card. 

What ever the case may be, go into driver control panel and set the global profile of the card to maximum level of performance and test again. 

[cojkeee_11]

20 minutes ago, faziten said:

complete info in brand and model of every component in your rig would be nice to help debugging. Driver version and game ofc. 

Posting a GPUz sensor tab screenshot while gaming is helpfull too (the vcap reason usually reveals what is the culprit). 

 

The GPU is somewhat stuck at minimum clock, judging by those clocks it's either an old Nvidia architecture or an AMD card. 

What ever the case may be, go into driver control panel and set the global profile of the card to maximum level of performance and test again. 

Cpu:amd phenom x4 II 840 @ 3.6ghz

Gpu:Msi radeon r7 250 1gb OC

Mobo:ga 790xta ud4

HDD:320gb samsung

Ram:hynix 2x4gb

Psu:Frontier 500w

 

Driver:radeon-software-crimson-relive-16.12.2

any game game that i run(not game speciffic)

[cojkeee_11]

You can clearly see gpu clock spike,after restart and than i started furmark

[faziten]

15 minutes ago, cojkeee_11 said:

You can clearly see gpu clock spike,after restart and than i started furmark

you could attempt a motherboard BIOS update since it all started with the new Motherboard. 

But first:

1) i'd try to force the GPU at constant max settings through catalyst control panel. Activate overdrive and try a very slight OC (like +10mhz) to see if it goes into 3d mode. Test again.

2) Set windows energy profile to maximum performance. Test again.

3) Open event viewer on windows and see System events if there's any warning or failure reported within this two weeks. (helps debugging).

[cojkeee_11]

Already done all of that,exept bios,and about event viewer uhmm,i dont use it ofter can u explain what im looking for?

[cojkeee_11]

24 minutes ago, faziten said:

you could attempt a motherboard BIOS update since it all started with the new Motherboard. 

But first:

1) i'd try to force the GPU at constant max settings through catalyst control panel. Activate overdrive and try a very slight OC (like +10mhz) to see if it goes into 3d mode. Test again.

2) Set windows energy profile to maximum performance. Test again.

3) Open event viewer on windows and see System events if there's any warning or failure reported within this two weeks. (helps debugging).

i just saw that i can only 'update' to a beta version or to down grade to older one, got f3 version of bios rn.

[faziten]

26 minutes ago, cojkeee_11 said:

Already done all of that,exept bios,and about event viewer uhmm,i dont use it ofter can u explain what im looking for?

 

And avoid Beta BIOSes. The only thing i'd rollback is the GPU driver try to get a pre "crimson" driver. 250 was launched in 2013 i believe so you've got a nice margin of drivers to dig, yes it's a pain in the rear, but it's better than not being able to game at all. 

[cojkeee_11]

25 minutes ago, faziten said:

 

And avoid Beta BIOSes. The only thing i'd rollback is the GPU driver try to get a pre "crimson" driver. 250 was launched in 2013 i believe so you've got a nice margin of drivers to dig, yes it's a pain in the rear, but it's better than not being able to game at all. 

i think i tried pre crimson drivers.I have my hd 5450 rn and its working no problem(getting the same fps in furmark with both -_-)

[cojkeee_11]

2 hours ago, faziten said:

 

And avoid Beta BIOSes. The only thing i'd rollback is the GPU driver try to get a pre "crimson" driver. 250 was launched in 2013 i believe so you've got a nice margin of drivers to dig, yes it's a pain in the rear, but it's better than not being able to game at all. 

Just tried crimson edition 15.11.1,everything is still the same...this is painfull

 

[faziten]

4 minutes ago, cojkeee_11 said:

Just tried crimson edition 15.11.1,everything is still the same...this is painfull

 

Crimson crap is still causing trouble... try the all mighty OMEGA drivers

 

http://support.amd.com/en-us/download/desktop/previous/detail?os=Windows 7 - 64&rev=14.12

 

if those can't fix the issue i'm out of ideas besides a bios update. 

 

btw: can you try the GPU in some friend pc ?

[cojkeee_11]

3 minutes ago, faziten said:

Crimson crap is still causing trouble... try the all mighty OMEGA drivers

 

http://support.amd.com/en-us/download/desktop/previous/detail?os=Windows 7 - 64&rev=14.12

 

if those can't fix the issue i'm out of ideas besides a bios update. 

 

btw: can you try the GPU in some friend pc ?

Probably,but in couple of days,2 or 3

[cojkeee_11]

I dont think you gave me display drives ,its amd control center,gaming evolved app,and catalyist install manager,and its not even working.

[cojkeee_11]

1 hour ago, faziten said:

Crimson crap is still causing trouble... try the all mighty OMEGA drivers

 

http://support.amd.com/en-us/download/desktop/previous/detail?os=Windows 7 - 64&rev=14.12

 

if those can't fix the issue i'm out of ideas besides a bios update. 

 

btw: can you try the GPU in some friend pc ?

managed to install them,still the same problem should i try bios update...or downgrade because there is only beta one that is newer?

[faziten]

1 minute ago, cojkeee_11 said:

managed to install them,still the same problem should i try bios update...or downgrade because there is only beta one that is newer?

neither is a good idea tbh. Hold your hope until you test it in someone else pc. If the problem persist it's obviously a driver issue or a faulty card (which i strongly believe is NOT the case). 

If the problem is not present on your friend's PC, then i'd recommend you to send a mail to AMD support and hope they have something to say about this. I googled a bit and seems to be a fairly common problem but none of the cases give a solid solving path. The thing ends itself after a few messing around with driver, OS and BIOSes. 

Is a friggin pain in the rear i know but it's the less regretable path. (bios downgrade/ beta bios may cause more trouble than they solve). 

[cojkeee_11]

2 minutes ago, faziten said:

neither is a good idea tbh. Hold your hope until you test it in someone else pc. If the problem persist it's obviously a driver issue or a faulty card (which i strongly believe is NOT the case). 

If the problem is not present on your friend's PC, then i'd recommend you to send a mail to AMD support and hope they have something to say about this. I googled a bit and seems to be a fairly common problem but none of the cases give a solid solving path. The thing ends itself after a few messing around with driver, OS and BIOSes. 

Is a friggin pain in the rear i know but it's the less regretable path. (bios downgrade/ beta bios may cause more trouble than they solve). 

Dude a lot thanks for help.I will take old mobo and try it there but on the same hdd,whitch could still cause the prob.oh well,thanks again