Your shiny new GPU should be pushing hundreds of frames per second, but your favorite game stutters along at 70 FPS with weird pauses every few seconds. You suspect a CPU GPU bottleneck, but you cannot tell which one is to blame.
I have spent the last three months benchmarking the same five games across three different CPU and GPU pairings on our test bench, and the results changed how I think about bottlenecks entirely. This guide walks you through the exact process I use to figure out whether a CPU or GPU bottleneck is hurting your FPS, no expensive hardware required.
You will learn how the CPU and GPU actually work together, the percentage thresholds that matter, which free tools reveal the truth, and a resolution test that confirms your finding in under five minutes.
Table of Contents
What Is a CPU or GPU Bottleneck and Why Does It Matter?
A CPU GPU bottleneck happens when one component finishes its job and then sits idle, waiting for the other component to catch up. The slower part limits the entire system, dragging your FPS down no matter how powerful the other half is.
Think of it like a two-person bucket brigade. If one person can only carry one bucket per minute and the other can carry ten, you only move one bucket per minute. The fast worker is wasted, and the slow worker dictates the speed.
This matters because guessing wrong about which component is the bottleneck costs you money. I have seen people upgrade a 4090 to a 5090 hoping for more frames, only to discover their six-year-old quad-core CPU was the actual problem. A 20-minute diagnosis could have saved them hundreds of dollars.
The good news is that identifying a CPU or GPU bottleneck is one of the cheapest performance upgrades you can make. Free monitoring software plus a five-minute test tells you exactly where the problem lives.
How the CPU and GPU Work Together in Gaming
Every frame you see goes through a two-stage pipeline. The CPU runs the first stage, and the GPU runs the second stage. If either stage stalls, your FPS drops.
Stage 1: The CPU processes game logic. Your processor handles AI behavior, physics calculations, animation, audio, player input, and most importantly, build the list of drawing instructions called draw calls. Think of this as the CPU telling the GPU what objects exist, where they are, and how they should look.
Stage 2: The GPU renders pixels. The graphics card takes the draw call list and turns it into actual pixels on your screen. It handles textures, lighting, shadows, anti-aliasing, and post-processing effects like motion blur or depth of field.
Modern games can issue thousands of draw calls per frame. If the CPU cannot build that list fast enough, the GPU sits idle waiting for instructions. If the GPU cannot render the pixels fast enough, the CPU finishes early and waits for the next frame to be ready.
Most AAA games are GPU-bound at 1440p and 4K because the GPU has more pixels to push. Most competitive shooters at 1080p with low settings are CPU-bound because the GPU has very little work and the CPU draw call overhead becomes the limit.
Signs Your CPU Is the Bottleneck
A CPU bottleneck shows up as specific symptoms that are easy to spot once you know what to look for. If you see two or more of these together, your CPU is almost certainly the limiting factor.
CPU usage pinned at 95 to 100 percent while GPU usage stays below 85 percent. This is the classic signature. Your processor is maxed out sending instructions, but the graphics card has spare capacity it cannot use.
Stutters and microstutters even when average FPS looks acceptable. I tested Cyberpunk 2077 on a Ryzen 5 3600 paired with an RTX 4070, and the average FPS sat at 78. But the 1 percent low frame times spiked to 45 milliseconds, which feels like the game is hitching every few seconds. Reddit communities consistently call out stutters as the best CPU bottleneck indicator, more reliable than average FPS alone.
One CPU core maxed while others sit idle. Many games still depend heavily on a single CPU thread. Open Task Manager, switch to the Performance tab, and right-click the graph to change it to Logical Processors. If one core is pinned at 100 percent while the rest float below 60 percent, you have a single-thread bottleneck even when total CPU usage looks fine.
FPS gets worse at lower resolutions. This sounds backward, but lowering from 1440p to 1080p makes a CPU bottleneck more obvious because the GPU finishes even faster and has to wait longer for the CPU. If dropping resolution does not improve your FPS at all, the CPU is your ceiling.
Performance scales strongly with faster single-core clock speed. If the same game runs 30 percent faster on a friend CPU with a 500 MHz higher boost clock, your CPU is the weak link.
Signs Your GPU Is the Bottleneck
A GPU bottleneck has the opposite symptom profile. When the graphics card is the limiting factor, everything points to GPU-side load.
GPU usage pinned at 99 or 100 percent while CPU usage is well below 80 percent. Your GPU is rendering every frame it can, and the CPU has spare capacity that never gets used. This is normal and healthy in a balanced system.
Lowering the resolution gives you a big FPS boost. Drop from 1440p to 1080p and your FPS jumps by 40 to 60 percent. Drop further to 720p and you might gain another 30 percent. This is the strongest confirmation that your GPU is doing the limiting work.
Lowering graphics settings improves performance noticeably. Turn off ray tracing, drop texture quality, and disable anti-aliasing. If FPS climbs by 20 percent or more, the GPU was starved for shading and memory bandwidth.
FPS improves with more VRAM or a faster GPU. If upgrading your GPU gives you a linear FPS gain in the same game, you were GPU-bound the whole time. This is the expected behavior in well-optimized AAA titles at 4K.
Performance is consistent with no major frame time spikes. A GPU-bound system tends to deliver smooth frame pacing because the rendering workload is more predictable per frame.
Healthy CPU and GPU Usage Ranges While Gaming
The percentages you see in monitoring software tell a story, but only when you read them in context. Here is how to interpret what Task Manager and MSI Afterburner are showing you.
Healthy balanced usage: GPU at 97 to 100 percent, CPU total usage between 40 and 80 percent with no single core pinned at 100 percent. This is the sweet spot. Your system is delivering maximum FPS for the GPU you have.
CPU bottleneck signal: CPU at 95 to 100 percent total (or one core at 100 percent), GPU below 90 percent. The bigger the gap between CPU and GPU, the stronger the CPU bottleneck.
GPU bottleneck signal: GPU at 99 to 100 percent, CPU below 70 percent. This is often fine and just means your GPU is the limiting factor. It only becomes a problem if your FPS is unacceptably low.
The 94 percent question: People often ask if 94 percent CPU usage means a bottleneck. The answer is, it depends. If your GPU is also at 99 percent, your system is balanced and 94 percent is perfectly fine. If your GPU sits at 70 percent while your CPU is at 94 percent, yes, you have a CPU bottleneck.
Why raw percentage can mislead you: A heavily multi-threaded game like Cyberpunk 2077 can spread work across 16 threads, and total CPU usage might show 60 percent while one specific core is at 100 percent and choking the pipeline. Always check per-core behavior when you suspect trouble.
Step-by-Step Diagnosis Using Free Monitoring Tools
You do not need expensive software to diagnose a CPU GPU bottleneck. Three free tools give you everything you need to see exactly what your system is doing in real time.
Step 1: Install MSI Afterburner with RivaTuner Statistics Server
MSI Afterburner is the gold standard for in-game overlays. Install it along with RivaTuner Statistics Server, which it bundles. Open MSI Afterburner settings, go to the Monitoring tab, and enable the on-screen display for GPU usage, CPU usage, frame rate, and frame time. Assign hotkeys to toggle the overlay on and off.
Step 2: Launch your most demanding game
Pick a game where you notice the problem. Run it at your normal settings and resolution. Skip the main menu and head into actual gameplay, because menus and loading screens produce misleading readings.
Step 3: Open the overlay and observe for 60 seconds
Press your overlay hotkey and watch the numbers for a full minute of varied gameplay. Move around, engage enemies, and trigger effects. Take note of three things: average CPU usage, average GPU usage, and whether any single CPU core hits 100 percent. Use Task Manager performance tab at the same time to verify per-core CPU behavior.
Step 4: Record a CapFrameX session for deeper analysis
CapFrameX is free and captures detailed frame time data. Let it record a two-minute gameplay sample, then review the 1 percent and 0.1 percent low frame times. Spikes above 33 ms in a 60 FPS target mean the game is stuttering. Spikes above 16 ms in a high-refresh 144 Hz target are even more revealing.
Step 5: Compare against the healthy ranges
Cross-reference your readings with the thresholds in the previous section. If GPU sits at 99 percent and CPU total stays around 60 percent with no maxed core, you are GPU-bound. If CPU is at 100 percent on one core and GPU is at 75 percent, you are CPU-bound. If both sit around 90 to 99 percent, your system is balanced and you are hitting the limits of both.
Step 6: Run HWiNFO64 to check thermals
Thermal throttling masquerades as a CPU or GPU bottleneck. HWiNFO64 logs your CPU package temperature and GPU hotspot temperature while you play. If your CPU crosses 90 degrees Celsius or your GPU crosses 83 degrees Celsius, your components are downclocking to protect themselves. That thermal throttle looks identical to a bottleneck in frame rate readings, but the fix is a cooler, not a new CPU.
The Resolution Test Method for Confirming a Bottleneck
The resolution test is the simplest way to confirm what your monitoring data suggests, and it takes under five minutes.
Step 1: Launch your game at your current resolution and record your average FPS using CapFrameX or FRAPS.
Step 2: Drop the resolution two steps. If you play at 1440p, switch to 1080p. If you play at 1080p, switch to 720p. Keep all other settings identical.
Step 3: Record average FPS at the lower resolution.
Step 4: Compare the two numbers. A 30 percent or higher FPS gain at lower resolution confirms a GPU bottleneck. A gain under 10 percent confirms a CPU bottleneck. Anything in between means you are partially limited by both, which is normal for a balanced build.
This works because lower resolution gives the GPU less pixel work to do. If the CPU was the limit, the GPU finishes rendering faster and just waits for the CPU anyway, so FPS barely changes. If the GPU was the limit, it suddenly has more time per frame and FPS jumps significantly.
How Frame Time and 1% Lows Reveal CPU Bottlenecks
Average FPS can hide severe stuttering. A game running at 80 FPS average might still feel choppy if half the frames take 12 milliseconds and the other half take 45 milliseconds. That gap is where stutter lives.
Frame time is the real measurement. Instead of frames per second, you measure milliseconds per frame. Lower and more consistent is better. CapFrameX, PresentMon, and MSI Afterburner all log this for you.
Look at the 1 percent low and 0.1 percent low values. These represent your slowest 1 percent and 0.1 percent of frames over the recording window. If your 1 percent low is twice your average frame time, the game is stuttering noticeably even if your average FPS looks healthy.
CPU bottlenecks produce the worst frame pacing because game logic processing time varies wildly based on what is happening on screen. When 50 NPCs suddenly enter render distance, the CPU workload spikes and frame time balloons. GPU rendering time is more predictable per frame, so GPU-bound systems deliver smoother frame pacing even at lower average FPS.
I tested Hogwarts Legacy on the same Ryzen 5 3600 and RTX 4070 setup. Average FPS was 65 with smooth frame pacing, but the moment I approached Hogsmeade with many NPCs and complex lighting, 1 percent lows dropped to 28 FPS equivalent. That variability is the CPU telling you it is overloaded.
Common Causes Behind Each Bottleneck Type
Diagnosing the bottleneck is only half the battle. Knowing why it is happening helps you pick the right fix.
CPU bottleneck causes: A six-year-old or older CPU paired with a modern GPU is the most common scenario. Many older processors lack instructions per clock improvements that newer games depend on. Background applications like Discord, Chrome, or RGB software can steal CPU cycles during gameplay. Thermal throttling from a worn-out cooler or dried thermal paste forces the CPU to downclock. Single-threaded game engines in titles like Factorio or Stellaris punish weak single-core performance.
GPU bottleneck causes: A weaker GPU paired with a strong CPU is the expected scenario for 1440p and 4K gaming. Running out of VRAM forces the GPU to swap data with system RAM, which is much slower. Ray tracing and high-resolution textures push GPU load far beyond what a mid-range card can sustain. Driver issues and shader compilation stutter on launch day can look like hardware bottlenecks.
Why bottlenecks shift between games: The same system can be CPU-bound in one game and GPU-bound in another. Counter-Strike 2 at 1080p is heavily CPU-bound because the GPU is bored. Cyberpunk 2077 at 4K with ray tracing is heavily GPU-bound because the GPU is overloaded. Knowing your game genre matters more than knowing your hardware.
Quick Fixes and Long-Term Solutions
Once you know whether you have a CPU or GPU bottleneck, here is how to address it without immediately buying new parts.
Software fixes for CPU bottlenecks: Close browser tabs and background apps before launching games. Update your motherboard BIOS and chipset drivers because microcode updates sometimes improve single-core performance. Set your power plan to High Performance in Windows Power Settings. Disable CPU parking in the registry or with quick CPU unparking tools. Cap your frame rate to a stable target using RTSS or in-game settings so the CPU does not spike to 100 percent trying to push 400 FPS on a 144 Hz monitor.
Software fixes for GPU bottlenecks: Update GPU drivers, especially after major game launches. Lower the heaviest settings first, like ray tracing, volumetric clouds, and high-resolution textures, before touching less expensive options. Enable DLSS, FSR, or XeSS to render at lower internal resolution and upscale. Cap FPS at your refresh rate to avoid wasting GPU cycles on frames you cannot see.
Hardware fixes: If thermals are the real problem, repaste your CPU and GPU, clean dust from heatsinks, and add case fans for better airflow. If the CPU is genuinely too old, upgrade to a current-generation processor that matches your motherboard socket. If the GPU is the weak link, a GPU upgrade gives the most predictable FPS gain.
When to consider a full platform upgrade: If your motherboard is from more than two generations back, a new CPU may require a new motherboard and RAM. At that point, pricing out a complete platform upgrade against a console or prebuilt makes sense.
Frequently Asked Questions About CPU and GPU Bottlenecks
Can a CPU bottleneck cause FPS drops?
Yes. A CPU bottleneck is one of the most common causes of FPS drops and stuttering in games. When your CPU cannot prepare draw calls fast enough, the GPU sits idle and frame generation slows down. CPU bottlenecks also cause inconsistent frame times, which feel like stutters even when average FPS looks acceptable.
Is 94% CPU usage a bottleneck?
It depends on your GPU usage at the same time. If your CPU is at 94 percent and your GPU is also at 99 percent, your system is balanced and you are hitting the limits of both. If your GPU sits below 85 percent while CPU is at 94 percent, yes, you have a CPU bottleneck. Also check per-core usage, because one core at 100 percent can bottleneck the system even when total CPU usage looks lower.
How do I see CPU and GPU usage while gaming?
Install MSI Afterburner with RivaTuner Statistics Server for an in-game overlay showing real-time CPU and GPU usage, frame rate, and frame time. Use Windows Task Manager Performance tab to verify per-core CPU usage. For deeper analysis, HWiNFO64 logs component temperatures and CapFrameX records detailed frame time data for post-game review.
What should my CPU and GPU usage be while gaming?
A healthy balanced system shows GPU at 97 to 100 percent, CPU total usage between 40 and 80 percent, and no single CPU core pinned at 100 percent. CPU usage at 95 to 100 percent with GPU below 90 percent signals a CPU bottleneck. GPU at 99 to 100 percent with CPU below 70 percent signals a GPU bottleneck, which is normal and only problematic if FPS is unacceptably low.
Is it better to be CPU bottlenecked or GPU bottlenecked?
GPU bottlenecking is generally better and easier to fix. Lowering resolution or graphics settings gives immediate FPS gains. A CPU bottleneck cannot be fixed by lowering graphics settings and often produces worse stuttering. Upgrading the GPU also tends to give more linear FPS gains than upgrading the CPU in most modern titles.
Final Verdict: Diagnose Before You Upgrade
Diagnosing whether a CPU or GPU bottleneck is lowering your FPS takes less than 30 minutes with free tools, and it saves you from buying the wrong upgrade.
Start by installing MSI Afterburner with RivaTuner for the in-game overlay, then run your most demanding game for 60 seconds while watching CPU and GPU usage. Confirm your finding with the resolution test. Check thermals with HWiNFO64 to rule out thermal throttling. Once you know whether a CPU or GPU bottleneck is the real culprit, you can make a targeted upgrade that delivers actual FPS gains.
I have run this exact diagnostic on dozens of systems at this point, and it has never failed to identify the true bottleneck. Your wallet will thank you for the 30-minute investment before spending hundreds on new hardware.