Serious frame problems

[Freddyfish775]

Hi, i am currently using a sapphire r9 280x, not OC

 

when i'm playing bf4 however, i only get 40 frames max when in battle, and it doenst matter what resolution i play at. 

 

Until last week, everything was fine, i got 60+ frames when playing on high. 

 

I have reinstalled drivers, did a clean sweep using specific tools, however, no avail.

 

when i monitor my cpu usage its at 100 % and my gpu is at max 40% now; this was not the case last week.

 

 

Can someone please help me?

 

specs:

resolution: 1080p - 900p - 720p -no difference

cpu i5 760 all unparked cores

8 gig ram

r9 280x

840 evo 250gig

 

temperature ingame: max 50 after two and a half hours of playing

cpu temps very normal (round 60 with stock cooler)

 

[Mixzzz]

Have you got another PC to test the GPU? Im not really sure what could cause this...

[Freddyfish775]

i gave my gpu to a friend of mine who runs a i5 750 and it runs just fine on his rig; im clueless

[Mixzzz]

i gave my gpu to a friend of mine who runs a i5 750 and it runs just fine on his rig; im clueless

Hmm... Either its CPU bottleneck(shouldnt be) or theres a problem in BF4 or in drivers/windows... Try reinstalling the game. Does any other game act the same or its a problem only with BF4?

[Peacefulwarrior]

Are you running beta drivers? Are you also running Mantle API if you are using beta drivers for bf4? Do you notice low frame rates in other games as well or just Bf4, and I assume this is with multiplayer and not SP? Last thing is that 64 player servers and large maps can bring most gpus to its knees along with the cpu such as the i5 750 that is a possible bottleneck.

[Freddyfish775]

I found a 'fix' online regarding reinstalling dx files from within the bf4 installer folder, this helped out quite a bit and i tried to up my settings a bit to reduce possible bottleneck. I did not have issues on other titles. i also oc'ed my cpu a bit (to 3.6 ghz). now i get round 80 fps with dips to around 50, which is very playable. not sure what the real cause was however...

 

edit: i was running 13.12 whql release drivers; thought it hadsomething to do with the beta drivers so i cleaned them and reinstalled 13.12