1. Confirm what kind of drop you have
An FPS drop is not always the same problem as stutter. A long drop from 140 FPS to 70 FPS usually points toward sustained load, throttling or a scene that is harder to render. A very short hitch can happen even when the average FPS remains high.
- Reproduce the issue in the same map, area or workload.
- Watch CPU usage, GPU usage, temperatures and memory use while it happens.
- Note whether the game recovers immediately or stays slow for several seconds.
- Compare plugged-in power mode and battery mode on laptops.
2. Check for a GPU or CPU bottleneck
If GPU utilization stays close to its practical maximum and lowering resolution or graphics quality raises FPS substantially, the workload is likely GPU-limited. If GPU use falls while one or more CPU cores are saturated, the game can be CPU-limited instead.
Do not rely only on total CPU percentage. A game can be limited by one busy thread while overall CPU usage looks moderate.
3. Look for thermal or power throttling
Performance that starts strong and becomes worse after several minutes can be consistent with temperature or power limits. Check CPU and GPU temperatures, clock speeds and power behavior during the slowdown. Clear blocked vents and confirm fans are working before changing software settings.
4. Reduce background contention
Windows can be responsive while another application still competes for CPU time, disk access, memory or network bandwidth. Close unnecessary launchers, browser tabs, video encoders and large downloads before testing.
If the problem began recently, check Task Manager for a process that becomes active at the same time as the FPS drop. Avoid disabling security software as a generic optimization; if a specific process is causing load, investigate that process instead.
5. Check memory and storage pressure
If system memory is nearly full, Windows may need to move more data between RAM and storage. That can create pauses or inconsistent frame delivery. Make sure the system drive also has reasonable free space and that the game is not competing with a large background copy or update.
6. Treat driver changes as a controlled test
If the issue started immediately after a graphics-driver update, compare with a known stable driver for your hardware. If you update, reboot and test before changing anything else. Reinstalling a driver should be a troubleshooting step, not the first response to every performance problem.
7. Use settings that match the bottleneck
Lowering resolution mainly helps when the GPU is the limiting factor. CPU-heavy settings such as crowd density, simulation detail or view distance can matter more when the CPU is limiting frame production. This is why copying another player's settings can give very different results.
When hardware may be the limit
If the system is stable, temperatures are under control, background load is low and the same scenes consistently exceed the capability of the CPU or GPU, the remaining limit may simply be hardware performance. At that point, a frame-rate cap that the system can hold consistently can feel smoother than chasing a higher but unstable peak.