Problems · Under load
How do I know if my GPU is the bottleneck?
Lower the resolution or the graphics settings and watch the frame rate. If it rises a lot, the graphics card was the limit. If it barely moves, the processor, memory or the game engine is holding it back instead. That two-minute check is more reliable than any bottleneck calculator.
A graphics card being the limit is not a fault. In most games at high settings the GPU is supposed to be the busiest part. It only matters when the frame rate is lower than you want, and then the fixes are settings, cooling, or a faster card.
First, notice when it happens
The causes, ranked
1. Settings and resolution beyond what the card can draw
most commonHow to confirm it
Frame rate rises substantially when you lower resolution, shadows, or anti-aliasing.
The fix
Reduce the heaviest settings first: shadow quality, ray tracing, and resolution scaling usually cost the most frame rate for the least visible difference.
2. The card slowing itself as it heats up
commonHow to confirm it
Frame rate starts fine and falls after several minutes; fans are loud; performance recovers after a pause.
The fix
Improve airflow, clean the cooler, and on a laptop use a hard surface. This restores performance you already paid for.
3. A laptop GPU running at a low power limit
commonHow to confirm it
A laptop with a named GPU performs far below desktop versions of the same card, or much worse on battery.
The fix
Plug in, choose the manufacturer's performance mode, and check the card's rated wattage, which varies widely between laptops sharing one GPU name.
4. The card is genuinely too slow for the game
occasionalHow to confirm it
Frame rate stays low even at reduced settings, and the card is well below the game's recommended requirement.
The fix
Upscaling such as DLSS, FSR or XeSS can help substantially. Beyond that, a faster card is the fix.
When the limit moves during a session
A bottleneck is not always a fixed property of the machine. A graphics card that is the limit in the first minutes of a game can stay the limit at a lower frame rate later, if it reduces its own speed as it warms or meets a power limit. The resolution check still works, but run it twice: once cold and once after twenty minutes of play. If the frame rate falls between the two with nothing else changed, the question is no longer which part is slower, but which part is losing speed.
That second question is what a sustained test answers. The SystemCheck run records graphics throughput over the whole stage and shows whether it holds or falls; the deep run repeats the graphics pass and runs processor and graphics together, which is closer to how a game loads a laptop where both share one cooler.
Measure it instead of guessing
SystemCheck measures the GPU and CPU separately and together. The GPU stage reports frame rate at a fixed 1600 by 900 and whether it held; a Deep run adds a combined load that shows how much each part gives up when both are busy, and a soft-shadow stage that shows what one expensive setting costs your card.
What software cannot tell you here
- Which part limits a specific game. That depends on the engine and your settings, so check it in the game with the resolution test.
- GPU utilisation in real time. Browsers do not expose it; use the vendor overlay while playing.
Asked, in people’s own words
- Is a GPU bottleneck bad?
- Usually not. At high settings the graphics card is meant to be the limit, which means the rest of the system is keeping up. It is only a problem when the resulting frame rate is lower than you want.
- Can a GPU bottleneck damage your PC?
- No. Being the busiest part is the card's normal working state, and it is protected against heat and power problems regardless of which part is the limit.
- Does a GPU bottleneck cause stuttering?
- Steady low frame rate is typical of a GPU limit. Irregular stutter more often comes from the processor, memory, shader compilation or storage, so look there if frame rate is decent but uneven.
- Why does my GPU usage show below 100% if it is the bottleneck?
- Usage counters average over time and can read below full while the card is still the limit for most frames. Equally, a card can sit below full because the processor cannot prepare frames fast enough. The resolution check settles it more reliably than the usage number.