FPS Dropping in CS2 and Valorant: Why It Falls Mid-Match

There is an important difference between having low FPS and having FPS drop. Low FPS shows a small number all the time. Dropping FPS shows 300 in the menu, 300 at the start of the round, and a nosedive to 120 exactly when the fight starts.

This guide is about the second case. And it is almost never a hardware shortage — the same PC was delivering fine seconds earlier.

First: identify when it drops

The moment of the drop is the biggest clue there is. Find your pattern:

• Drops in the first few minutes then stabilises — shader compilation
• Drops when a lot is happening — smoke, grenades, several enemies — scene load
• Drops after twenty or thirty minutes and never recovers — temperature
• Drops at random moments unrelated to the game — a background process
• Drops ever since you updated something — driver or game update

Each has a different fix, which is why generic advice rarely works.

Shader compilation

A classic symptom, often mistaken for a fault: the first matches after updating the game or driver stutter a lot, then it improves on its own.

The game has to prepare visual effects the first time it encounters them. While doing that, it stutters. Once done, it is cached and stops.

How to recognise it: stutter in the first few minutes, fades over time, returns after every update. Not a fault, needs no fix — just patience for the first matches.

What breaks that process: clearing the shader cache often, and "cleaner" programs that do it without telling you.

Temperature

The most common cause of a drop that does not recover.

CPU and GPU have a ceiling. On reaching it they reduce their own frequency to protect themselves. The result is FPS that starts fine and worsens through the session.

How to recognise it: the first matches are good, the third is bad, and restarting the PC helps temporarily. That pattern is practically a signature of a thermal problem.

Common causes: dried-out thermal paste, a dusty cooler, a case with no airflow, a laptop with blocked vents.

Background processes

This explains the drops that seem to have no reason.

Both CS2 and Valorant lean heavily on one primary CPU core. When another program decides to use that same core — antivirus running a scan, a store client downloading, a browser processing a heavy tab — FPS drops for as long as that lasts.

How to recognise it: the drop has no relationship to what is happening in game. You can be standing still facing a wall and still drop.

Power plan

Underrated and very common.

In power-saving mode, Windows holds back CPU frequency to save energy. In a competitive game that shows up as drops at peak moments — exactly when you need it.

On a laptop the effect is larger still, because the manufacturer's profiles and the plugged-in versus battery difference stack on top.

Per-game specifics

CS2

CS2 is heavier than CS:GO was, and many people still compare against the old expectation. Smoke and grenades genuinely cost performance — a drop during smoke is expected behaviour, not a fault.

If your drop happens exactly at those moments and the rest of the match is stable, you are within the game's normal behaviour. The path there is raising your baseline FPS, not hunting a fault.

Valorant

Valorant is light. Precisely because of that, a drop in Valorant is more suspicious: if a game that runs on modest machines is dropping on yours, something is getting in the way.

In that case, suspect temperature, power plan and background processes rather than a hardware shortage.

A useful signal: dropping in both games means the problem is the system. Dropping only in CS2 means it is the game's load.

The routine

1. Note when it drops — the main clue
2. Rule out shaders — play a few matches after updating before concluding anything
3. Monitor temperature through a long session
4. High-performance power plan
5. Close background software — browsers and updaters especially
6. Compare the two games — both means system, one means the game

Notice that no step involves buying a part. In-match drops are almost never solved with new hardware, because the same hardware was delivering fine seconds earlier.