i5 6600k 100% CPU usage
Specs:
- i5 6600K @4.4GHz
- EVGA GTX 1070 (slightly overclocked with MSI afterburner)
- 16GB DDR4 RAM 2133MHz (XMP overclocked to 2666MHz)
- BF1 is on a 240GB SSD
- 1440P 144HZ Gsync monitor
I've played BF1 a decent amount since beta, but I have gotten more and more annoyed at a certain performance issue I'm having. I am seemingly not alone with this problem but I CANNOT find the fix for the problem. I eventually quit the game about 130h of playtime after release because of these insane issues, and now I have returned for the new DLC.
My i5 6600k CPU is struggling with this game A LOT, I sometimes have 98-100% CPU usage constantly usually in 64 man operations but sometimes even when there's not that many players. This gives me varying FPS that goes that dips down to as low as 40 but almost never goes over 80 fps. What graphics option I have in-game makes no difference in the CPU usage and thus I still stutter and frame drop beyond belief.
My GPU is usually about 80-90% usage, but in the past BOTH the CPU and GPU was at 99-100% usage so I don't know what the deal is. My friend who has an i5 gets no issues at all. In the beta BF1 ran exceptionally well with my CPU, no problems at all
I have tried a lot of fixes but nothing seems to work, at least in the long run...
- About a month ago I thought I found the fix, I tried closing battle.net (apparently can cause issues) and I also changed the nvidia PhysX setting to be on my GPU instead of CPU, and I believed it worked for a few days. But then the issue seemed to be back again for no reason.
- Just yesterday I believed I found the fix again, I have had my headphones "enhanced" with more bass etc, and when I turned off all sound effects on my headphones my game was fine with something like 80-99% GPU and 80-90% CPU, the game ran well for a whole operation and I was very happy.
- But today when I played the same operation again, my CPU was completely broken again. 100% constant CPU usage and GPU was about 80% with the same good ol' 40-75 fps.
INSANELY frustrating that I haven't changed a thing, no additional programs or anything in the background compared to yesterday and yet it didn't work.
Later today, it was fine again in the same map and area. It was about 80% once more, why? I have no idea.
Other:
- My CPU and GPU temperatures are fine
- V-sync is off, on doesn't help.
Things I have tried:
- Downclocking and defaulting my BIOS, it makes no difference
- Disabling superfetch service
- Having no background programs, I never do anymore, except maybe discord if I play with someone (doesn't seem to affect CPU)
- Limiting FPS, I thought it worked in the past but it doesn't always work out anymore. I have limited fps to 88 in user.cfg, having much more is more harsh on the CPU. (PS I WILL NOT limit fps to 60 even though it very much helps the CPU, I did not get a 144hz monitor to play at 60hz, I can't do it.
- PhysX to GPU
- Lowering graphics
- Unplugging second monitor
- DDU, clean reinstallation of graphical drivers
- Unparked CPUs
- Multiple commands in the user.cfg file in the BF1 folder, the only one that seems to do much is renderdevice.renderaheadlimit. If I have it on "1" it gets really bad in-game, I have it on 2, seems to work best.
- Turning off special effects on output sound.
- Setting maximum pre-rendered frames in nvidia control panel to different things, no effect.
- XBOX DVR off
- OneDrive off
- Not using MSI afterburner
- Hoping for an optimization update
- And probably some other things I forgot.
NEW:
- Origin in-game off
- Timebroker service Off
- Command prompt sfc /scannow (found a few issues actually)
- CCleaner, registry fix etc
- Clean DDU install then I ONLY installed GPU drivers, not HD audio or anything else.
I have considered buying an i7 but that is A LOT of money only for fixing one single game. I'd rather wait and pray that an update fixes everything.
Edit: I just thought that some might just say "100% is normal" well maybe it is, but I WITHOUT ANY DOUBT have problems ONLY when my CPU goes up to that constant 100%. (edit: Sometimes that's the case...)
