Tom Clancy's The Division FPS Drops CPU Spikes to 100%

Saruhi

Reputable
Mar 4, 2014
19
0
4,510
Hello, i have been plagued with this problem since beta and have done/bought many things in an attempt at fixing my issue. the issue that i am having is where i am usually getting a solid 56-60fps for 10 or so minutes then it suddenly drops to 20-30fps and my cpu spikes to 90-100%.

Solutions ive tried
- Bought new RAM
- Reinstalled CPU
- Bought a new Graphics Card
- Reinstalled Windows and Graphics Drivers
- Cleaned Radiator

This issue seems to only occur when playing Tom Clancy's The Division so i am not sure if this is just because the game is new and has bugs. but i thought i would see if anyone else is having these issues or has a fix.

My Specs
- Windows 10 Pro 64-bit
- AMD FX-9370
- 16GB RAM DDR3
- Gigabyte 990FXA-UD3
- Nvidia GeForce GTX 970
- 232GB Samsung SSD 850 Evo

p.s I also run the game on a 2560x1080 resolution if that affects it in someway.

Thanks,
Kyle
 


Idle
GPU 60c | 1050MHz
CPU 30-40c | 4420MHZ

While problem is occuring
GPU 70c | 1253MHz
CPU 50-55c | 4448MHz
 
OK, the description sounds like throttling, but the temps and clocks don't (this would also have been cleared by everything that you have done.

How much Vram are you using?

I'd therefore suggest that something else is consuming (probably CPU) resource for a period of time, but a clean installation of windows should have resolved that.

Are you on the high performance power profile?

Can you watch processes (on another screen) to see if anything jumps ahead of the game?
I hope you don't mind me asking, but this is a legitimate copy of windows? My thought is that if not the version you have could have some payload that you are not aware of.
Does it get better if you carry on playing?
Are those clocks and temps whilst in game, or tabbing out?
 


playing it at the moment in windowed mode seems to of fixed the issue.

i couldn't see anything jump ahead of the game process.
 


after playing it for a few hours i found it didn't really fix it but didn't happen as often as it did in fullscreen.
😛