Your graphics card sitting at 50–70% while a game runs badly is one of the most-asked questions in PC gaming, and the first answer offered is almost always “CPU bottleneck”. Sometimes it is. More often it is something duller and easier to fix.
Here are the causes, roughly in the order they turn out to be responsible. Work down the list; the first four take under a minute each.
1. Something is capping your frame rate
By far the most common, and the least interesting. If a frame cap is active, the card deliberately idles once it has hit the target. That is the system doing what you told it to.
Check all of these, because they stack and people forget the ones they set months ago:
- V-Sync, in the game and in the driver control panel — the driver setting overrides the game’s.
- A frame limiter in the game’s own settings, often listed as “Max FPS”.
- Your monitor’s refresh rate. If it is 60 Hz and you are getting exactly 60 fps, there is your answer.
- Battery or power settings on a laptop, which can impose a cap you never set.
- Low Latency or Radeon Chill modes, both of which can hold frames back.
The tell: the frame rate is pinned at a round number — 60, 120, 144 — and barely varies. Real performance limits produce a frame rate that wanders. A cap produces a flat line.
2. You are reading it at the wrong moment
Menus, loading screens, cutscenes and paused games all run differently from play. So does standing still in a corner. Utilisation during actual movement through a busy scene is the only reading worth taking, and it needs watching for a minute rather than glancing at once.
3. The game is running on the wrong graphics processor
This one mostly affects laptops, and it is responsible for an enormous amount of confusion. A laptop with a discrete graphics card also has one built into the processor, and Windows does not always pick the right one. The game runs on the integrated chip, which struggles, while the discrete card sits idle and reports low usage because it genuinely is doing nothing.
On Windows: Settings, System, Display, Graphics, find the game, set it to High performance. Then check it is actually plugged in — many laptops will not use the discrete card on battery regardless of what you have configured.
Desktops are not immune. A monitor plugged into the motherboard’s video output rather than the graphics card produces a similar mess.
4. Memory is not running at its rated speed
XMP and EXPO are off by default on a great many motherboards. Memory sold as 6000 MT/s runs at 4800 or lower until you enable the profile, and in processor-limited scenes that is a real loss — this is the single most common free performance left on the table in a self-built PC.
Open Task Manager, Performance, Memory, and look at the Speed figure. If it is well below what you paid for, the fix is one setting in the BIOS.
5. The processor genuinely is the limit
Now we get to the actual bottleneck, and it is worth confirming rather than assuming. The test: drop the resolution to the lowest the game offers. If the frame rate barely moves, the card was never the constraint and the processor is setting the pace. If it jumps, the card was working hard after all and something else explains your reading.
Note that total CPU usage can look low while this is happening. Games load a few threads heavily and leave the rest idle, so a processor can be completely saturated on the one core that matters while Task Manager reports 35%. Look at per-core usage, not the total — the diagnosis guide covers this in more detail.
6. The game itself is the limit
Some games cannot use your hardware no matter what you do. Older titles built around single-threaded engines, strategy games deep into a long campaign, simulation-heavy titles with large worlds — all of them can hit an internal ceiling with hardware to spare on both sides.
The tell is that the frame rate is similar on wildly different hardware. If people with far better machines report similar numbers in that specific game, you have found the engine’s limit, not yours. Nothing you buy will change it.
7. Something is wrong rather than merely unbalanced
Rarer, but worth ruling out if nothing above fits:
- Thermal or power throttling. Check whether clocks drop after a few minutes of play. A card that starts at 2600 MHz and settles at 1900 is overheating or power-limited.
- A bad driver install, particularly after a GPU swap. Clean reinstall.
- PCIe link running at reduced speed, visible in GPU-Z. Usually a seating or BIOS issue.
- Background software holding a core — overlays, capture tools, browser tabs doing real work.
- A failing or slow drive causing stalls that look like low utilisation while the game waits on data.
When low usage is not worth fixing
If your frame rate is comfortably above your monitor’s refresh rate, low GPU usage is a non-event. The card has spare capacity because you do not need it. That is a healthy build, not a broken one — a capped 240 fps on a 144 Hz monitor is the system being efficient.
Low utilisation only matters when the frame rate is also lower than you want. Those are two separate observations, and a lot of worry comes from treating the first as a problem on its own.
The order to work through it
- Turn off every frame cap and V-Sync, and check your monitor’s refresh rate.
- Measure during play, for a minute, in a demanding scene.
- On a laptop: plug it in, force high performance.
- Enable XMP or EXPO if memory is running slow.
- Drop the resolution. If the frame rate does not move, it is the processor.
- Compare against others running the same game before buying anything.
If you get to step five and the processor really is the constraint, the upgrade advisor will estimate what the smallest useful change buys you — including the cases where the honest answer is that nothing available is worth the money.