Low GPU usage in games: why it happens and how to fix it
A graphics card sitting at 50–70% while a game runs slower than you want is waiting for something. The card itself is usually fine: a frame rate cap, the processor or a setting is holding it back, and most of the causes cost nothing to fix.
Updated 26 September 2026
First: is it actually a problem?
Low usage is only a problem when the frame rate is lower than you want. If a game already runs at your monitor’s refresh rate, or at a limit you set, the card has nothing more to do and its usage falls. That is normal, and it keeps the card cooler and quieter. Light games, such as most competitive shooters, can also run faster than any processor can feed a fast card.
The rest of this guide is for the other case: a frame rate below what you would like, with the graphics card well short of the 95–100% it shows when it is the part setting the pace. Check the causes in this order; the first ones are the most common and the quickest.
1. Look for a frame rate cap
If the frame rate sits flat on a round number — 30, 60, 120, 144 — something is almost certainly capping it:
- V-Sync, in the game or the graphics driver, holds the frame rate at the monitor’s refresh rate.
- A frame rate limit in the game’s own settings, in NVIDIA Control Panel (Max Frame Rate) or in AMD Software (Radeon Chill).
- The monitor’s refresh rate. A monitor left at 60 Hz shows at most 60 frames a second, however fast the card is.
- Battery saving on a laptop, which can cap games at 30 or 60 frames a second until the laptop is plugged in.
Turn the caps off one at a time and watch whether the frame rate and the usage rise. A cap you chose on purpose is fine to keep; it is only a problem when you did not know it was there.
2. Check whether the processor is the limit
With no cap, the most common reason is that the processor cannot prepare frames as fast as the graphics card can draw them, so the card finishes early and waits. The signs:
- One or two processor threads close to 100%, even though total CPU usage looks modest. In Task Manager, choose Performance → CPU, right-click the graph and choose Change graph to → Logical processors.
- Lowering the resolution barely changes the frame rate.
This happens most with a fast graphics card and an older processor, at 1080p, and in games that lean on the processor: strategy, simulation and large multiplayer battles. The bottleneck calculator shows how likely it is for your pair of parts, and CPU or GPU bottleneck explains how to tell for certain.
One consolation: while the processor is the limit, the graphics card has capacity to spare. Raising the resolution or the graphics settings costs little or nothing, so you may as well use it.
3. Let the processor run at full speed
Before deciding the processor is too slow, make sure nothing is holding it back. Each of these makes a processor look slower than it is:
- Memory running below its rated speed, because XMP or EXPO was never switched on in the firmware.
- Memory in single channel: one stick, or two in the wrong slots.
- The power plan. In Windows 11, open Settings → System → Power & battery and set Power mode to Best performance. Plug a laptop in.
- Background programs. With the game running, open Task Manager’s Processes tab and sort by CPU. Browsers playing video, recording software, and game launchers updating in the background are the usual ones.
- Heat. A processor that gets too hot slows itself down; a stress test shows whether yours does.
4. Make sure the game is running on the graphics card
On a desktop, the monitor has to be plugged into the graphics card’s ports, lower down the back of the case, not the motherboard’s. Plugged into the motherboard, the game may run on the processor’s own graphics, or have every frame copied across to it — either way it is slower, and the graphics card may sit nearly idle.
On a laptop with two graphics chips, Windows sometimes runs a game on the weaker one. Open Settings → System → Display → Graphics, find the game (or add it), choose High performance and save. NVIDIA Control Panel and AMD Software have the same choice per program.
5. Drivers and the game itself
- Update the graphics driver from NVIDIA, AMD or Intel. After a new driver or a game update, the first minutes of play can stutter and dip while the game prepares its shaders again; that settles by itself.
- Hardware-accelerated GPU scheduling takes a little work off the processor, and on recent NVIDIA cards frame generation needs it. How to check it.
- Some games cannot use a modern card fully. Older games that run most of their work on one thread, and some that are simply poorly optimised, leave any graphics card waiting at any setting. Search for the game’s name with “low GPU usage” before spending money: if everyone sees it, it is the game.
High usage but still slow?
The opposite problem looks different. If the card shows 95–100% but performs below what it should, it is working flat out at less than full speed: overheating, a power limit lowered by an overclocking tool or a quiet profile, or a card running on fewer PCIe lanes than it supports, for example because it sits in the wrong slot. Reset any tuning tool to its defaults, clean the card’s fans, and check which slot it is in.
How Bottleneck checks this
Bottleneck’s scan looks for the causes on this page that Windows can see: a monitor plugged into the motherboard or running below its best refresh rate, memory below its rated speed or in single channel, a restrictive power plan or turbo boost switched off, programs using the processor in the background, a graphics card on fewer PCIe lanes than it supports or below its default power limit, and hardware-accelerated GPU scheduling switched off.
Measuring a game answers the main question directly. With Bottleneck open, start the game and press Ctrl+Shift+F11, play for a few minutes and press it again: Bottleneck records, for every frame, whether the processor or the graphics card held it back. Which part held the game back, and the average frame rate, are free. Pro adds the slowest-frame figures, stutter and before-and-after comparisons.