Background apps that quietly steal frames
A recorder, a browser, or a store client can spend the frame time you wanted for the game. What to check.
A game can lose frames to software that is not the game. Recorders, browsers, launchers, chat clients, and RGB suites all assume they are allowed a little of the machine. A little each, across a dozen processes, is a missing fight. You do not need a sterile operating system. You need to know which guests are expensive and how to ask them to wait until the match is over.
The usual thieves
A browser with many tabs, especially ones playing video, spends processor time and memory. A launcher that is updating another game will hit the disk and the network. An overlay that draws a frame counter and a clip button is usually cheap, and a stack of three overlays is not. Cloud backup that decides your screenshots folder is due for upload will saturate a disk at the worst moment. None of these look like a graphics setting. How to tell a CPU limit from a GPU limit helps you see the processor busy with work that is not the scene. If GPU use is modest and the frame rate is poor, a background guest belongs on the suspect list.
Overlays and recorders
Clipping software that keeps a rolling buffer is writing video even when you never press save. That is a real cost. Hardware-accelerated capture can be gentle, and a software capture of the whole desktop can be rude. Turn the buffer off if you are not actually saving clips. Instant-replay features are the feature people forget they enabled in a different game's client. One client open for the game you are playing is reasonable. Four clients, all injecting an overlay, are a hobby you did not mean to start. Disable overlays in the ones you are not using tonight.
Updaters, scans, and the disk
Windows and store updaters, shader caches being built by a different title, and an antivirus scan of a newly installed game all prefer idle time and do not always get it. If a hitch lines up with the drive light staying on, look at what is reading. How to Benchmark Your Own Games Properly assumes a quiet machine. A benchmark taken during a backup is a benchmark of the backup. Pause large sync tools before a session you care about. You can let them run overnight. They do not need to share the boss.
A short isolation test
Close the browser, quit extra launchers, and disable overlays you do not need. Play the same spot. If the frame rate or the smoothness returns, add things back one at a time until the cost reappears. That one guest is the thief. Leaving everything closed forever is unnecessary if only one tool was expensive. Write down the culprit, because next month a reinstall will enable it again with a friendly checkbox. A second monitor full of animated chat is also a guest. It can stay if the test says it is cheap.
What is worth leaving open
Voice chat you are using, the game's own launcher, and a single monitoring overlay are fair. A controlled machine is not an empty one. The aim is a frame time that belongs to the game. When the game is done, let the updaters work. A PC that is allowed to finish its chores between sessions behaves better than a PC that is asked to chore and render in the same second.
Frequently asked questions
Does a frame counter cause stutter? One light overlay rarely does. Several injectors, each drawing its own counter, can. Keep a single tool you understand.
Will game mode fix background apps? It can nudge priorities. It will not stop a backup from reading the disk. Pause the heavy task. Do not expect a toggle to uninstall it.
Should I close everything in the system tray? Close what the isolation test implicated. A tray icon is not guilt. A tray icon that is encoding video in the background is.