bf 1 - fx 8350 gtx 970 low fps problem

selbesoglu

Commendable
Jan 6, 2017
4
0
1,510
0
Hello everyone,

I am experiencing 30-40 fps on Battlefield 1 for ultra settings(1080p-%42 resolution scale- vsycn on-dx12 on) with the pc specs below:

FX 8350 (4.0 ghz - stock speed)
Asus gtx 970
Kingston hyper ddr3 2x4gb - 1600 mhz CL9(dual channel)
Asus M5A99FX PRO R2.0
WD black 1 TB 7200 rpm

I have used "Afterburner" to detect fps drop and bottleneck existence. GPU-CPU usage level is quite normal and also ram usage is about 6000 MB. I couldn't understand reason of the low fps. However I am suspicious of Ram CLK and Speed. In order to prove it, I have overclocked the ram speed 1600 Mhz to 1760 Mhz with same CLK and fps has improved a little bit. Either I will buy new ram such as 1866 Mhz CLK9 4x4 gb or I will wait for a new patch or sth else I don't know.

Any help would be appreciated. Best regards
 

ZaneDragon

Respectable
Jan 4, 2017
286
0
1,960
60
What about VRAM usage? Maybe that's the problem...
And when all the VRAM is used, the PC starts writing it on normal RAM and that slows the game down while you have ddr3 with low freq (ddr4 has 2133 and above).
 

selbesoglu

Commendable
Jan 6, 2017
4
0
1,510
0
I forgot to write other details. Nvidia driver version is 376.33 and maximum performance is chosen. Bios is updated and there is no heating problem.
 
D

Deleted member 217926

Guest
Also, although your 8350 will support slightly faster RAM it won't make any difference in gaming. The only game I know of that improves with faster RAM is Fallout 4.

If anything you would benefit from an SSD. It won't improve FPS but it will help noticeably with load times and level transitions.
 

selbesoglu

Commendable
Jan 6, 2017
4
0
1,510
0
I have also tried your suggestion changing to dx11 and fps becomes lower compared to dx12. Before december patch, it was vice versa and CPU usage has been optimized. SSD will not much affect to the situation. At the beginning of the multiplayer game(64 player), it causes lagging for a short time because of loading of the map.
 

ASK THE COMMUNITY