CPU Bottleneck: How to Check It and Fix It

Short answer: a CPU bottleneck means your processor is the slower half of the pair. The graphics card finishes a frame, then sits idle waiting for the next batch of instructions. You can confirm it in about five minutes: if the GPU stays well under 95% usage in a demanding game, and your frame rate barely moves when you drop the resolution, the CPU is holding you back. Most of the fixes are free.

Last reviewed 26 October 2026.

I’m Mubashar, and I run this site and its calculator. I come from web development and SEO, not from a hardware review lab, so I won’t throw benchmark charts at you. What follows are checks you can repeat on your own PC in a few minutes, and the order I’d try fixes in before spending anything.

Timeline: the CPU prepares each frame, and the GPU sits idle between drawsOne frame, two stagesCPUPreparePrepareGPUDrawidleDrawGPU idle between draws = frame rate lost to the CPU
How a CPU bottleneck works: the processor prepares each frame, and the graphics card waits for it.

Why the GPU ends up waiting

Every frame takes two trips. The CPU goes first: it runs the game logic, works out where everything is, and packages up the drawing instructions. Then the GPU takes that package and paints the picture. Frame rate is set by whichever trip is slower.

Picture a very fast printer fed by someone who is slow at loading paper. The printer is not the problem, and buying a faster printer changes nothing. That is a CPU bottleneck. Say you pair an older six-core processor with a current high-end graphics card: in a busy open-world game the card may spend a good part of every frame doing nothing.

Two points before you panic. Some limit always exists, because two parts are never perfectly matched. And when the GPU is the limit instead, that is usually what you want, since it means the expensive part is working flat out. A bottleneck matters when the gap is big enough that you can feel it or when you are paying for performance you cannot use.

How to tell if it really is the CPU

Start with an overlay that shows GPU usage and per-thread CPU usage while you play. Your GPU software has one built in, or you can use MSI Afterburner with RivaTuner. Task Manager works too: open Performance, then right-click the CPU graph and choose to show logical processors.

Now play the part of the game that hurts. Not the menu, not an empty map. A crowded city, a big fight, a late-game base. Then run one simple experiment: lower the resolution and watch what happens.

What you seeWhat it usually means
GPU at 95% or more, CPU has roomGPU is the limit. Normal and fine.
GPU well below 95%, one or two threads near 100%, frame rate unchanged at lower resolutionCPU is the limit.
Both look relaxed but FPS sits at a round number (60, 144)A frame cap or V-Sync. Check your settings first.
Both low and the game hitchesLook at memory, storage, drivers and temperatures.
Flowchart: if GPU usage is under 95 percent, lower the resolution; if frame rate barely moves the CPU is the limitOverlay on, demanding gameGPU usage under ~95%?NoYesGPU-limitednormal, healthyLower resolutionone stepFPS jumpsNo changeGPU-limitedresolution was the limitCPU-limitedthe CPU is the cap
The five-minute test: GPU usage first, then a resolution drop.

If the frame rate jumps when you lower the resolution and the GPU is pinned, you were GPU limited. If it stays put, you are looking at the CPU, the memory, or a cap.

The usage number almost everyone misreads

The headline CPU percentage in Task Manager is an average across every thread. A game that leans hard on one thread and ignores the rest can cap your frame rate while the total says 6%. On a CPU with 16 threads, one thread at 100% is 6.25% overall. That is why “my CPU is only at 30%, so it can’t be the problem” is such a common wrong conclusion.

The reverse question comes up too: is 40% CPU with 96% GPU a bottleneck? No. A GPU at 96% is the limiting part, which is the healthy case for gaming.

Problems that only look like a CPU bottleneck

  • A frame limiter. V-Sync, an in-game cap or a driver cap holds usage down on purpose.
  • Heat. A hot CPU slows itself down. Check temperatures and clean the filters and cooler before blaming the chip.
  • Memory set up badly. One stick, or two sticks in the wrong slots, or XMP/EXPO switched off.
  • Background apps. Browsers, overlays, capture tools, launchers.
  • Too little VRAM. When textures spill out of video memory the game stutters in a way that mimics a CPU limit.
  • Shader compiling on first launch. It goes away on the second run.

Fixes, from free to expensive

Three steps from free fixes to hardware upgrades, in order of cost1Ten minutes, no moneyFree2Move the work onto the GPUFree3When it has to be hardwareCosts money
Work down the list in this order, and stop as soon as the problem is gone.

Ten minutes, no money

Close what you don’t need and trim the startup list. Update the GPU driver, the chipset driver and the motherboard BIOS. Check that your memory runs in dual channel and that XMP or EXPO is on, because memory speed matters more to a CPU-limited game than most people expect. Make sure the power plan is not throttling you: Balanced is usually fine once the chipset driver is installed, but if the CPU never boosts, try High performance. Clean the cooler.

Move the work onto the GPU

This is the counterintuitive one. If the GPU has spare capacity, give it more to do. Raise the resolution, the render scale, texture quality or anti-aliasing. The frame rate stays about the same, but the picture looks better, so the CPU limit stops costing you anything visible.

Do the opposite for CPU-heavy settings. Crowd and traffic density, view distance, physics and object detail all lean on the processor, and in many games so does ray tracing. Turning those down gives the CPU room. Capping the frame rate a little below what the CPU can sustain also smooths frame times. And if you use DLSS, FSR or XeSS, remember upscaling lowers the internal resolution, which shifts load back towards the CPU.

When it has to be hardware

If the free changes do not close the gap, the cure is a faster CPU. The cheapest route is a processor that fits your existing motherboard socket, so you keep the board and memory. Chips with a large cache, such as AMD’s X3D models, tend to help most in CPU-limited games. On an older platform you may need a new board and memory too, so price the whole job before you commit.

You can sanity-check a plan in the PC upgrade calculator, or see how a new pairing balances in the bottleneck calculator. Treat those percentages as estimates, not measurements; this page explains what they can and cannot tell you.

Check your own pairing. Pick your CPU and GPU and see your bottleneck percentage, with upgrade suggestions, in a few seconds. No sign-up needed.

Open the bottleneck calculator

Do you need to fix it at all?

Often not. At 1440p or 4K the GPU is already the limit in most games. If you reach the refresh rate of your monitor you are done. And some games are capped by their own engine, so no hardware changes the result. Fix a CPU bottleneck when you can feel it, in stutter or a frame rate that will not rise, not because a percentage on a website looked scary.

CPU bottleneck versus GPU bottleneck

They are two sides of the same measurement. When the CPU is slower you get the problems above. When the graphics card is slower you get a GPU bottleneck, which in gaming is the normal outcome. To see what a change might do to your frame rate before you buy, try the FPS calculator.

Frequently asked questions

What is a CPU bottleneck?

A CPU bottleneck is when the processor cannot prepare frames as fast as the graphics card can draw them. The GPU waits, so frame rate is limited by the CPU and the graphics card runs below its full capability.

How do I know if my CPU is bottlenecking my GPU?

Play a demanding scene with an overlay showing GPU usage and per-thread CPU usage. If GPU usage stays well below about 95% while one or two CPU threads sit near 100%, and the frame rate does not rise when you lower the resolution, the CPU is the limit.

Is 40% CPU usage with 96% GPU usage a bottleneck?

No. A GPU at around 96% is the limiting part, which is the healthy situation for gaming. Low overall CPU usage is normal because games rarely spread work evenly across every thread.

Is a 5% bottleneck okay?

Yes. A small percentage from a calculator is within the margin of error and does not translate into a noticeable loss. Focus on large imbalances and on what you actually see in your own games.

Can RAM cause a CPU bottleneck?

Memory can hold back a CPU, especially in CPU-limited games. Check that two sticks run in dual channel and that XMP or EXPO is enabled in the BIOS.

Will a new GPU fix a CPU bottleneck?

No. In a CPU-limited game a faster graphics card changes little. You need to ease the load on the CPU, improve memory, or upgrade the processor.