Low CPU and GPU Usage but Low FPS Diagnostic

Low CPU and GPU Usage but Low FPS?

Low CPU and GPU usage but low FPS can make an expensive PC feel defective even when both major components are capable. That pattern does not prove both parts are weak. It usually means the next frame is waiting for a cap, one busy thread, memory, storage, temperature, power, software, the wrong graphics path, or the game engine itself.

Start the 3-Minute Check Run the Bottleneck Calculator

No registry tweak pack No fake FPS promise No automatic hardware blame Same-scene evidence first

Direct answer

Low CPU and GPU Usage but Low FPS Usually Means the Frame Is Waiting Somewhere Else

Low CPU and GPU usage but low FPS does not automatically mean a broken graphics card or an obvious CPU bottleneck. Total CPU usage can hide one heavily loaded game thread. Low GPU usage and low FPS can appear because the graphics card is waiting for that thread, an active frame cap, synchronization, memory, storage, shader work, a power or thermal restriction, the wrong GPU, or a game-engine ceiling.

The fastest diagnosis for low CPU and GPU usage but low FPS is to repeat one problem scene, remove intentional caps, compare frame time with per-core CPU activity and GPU behavior, then change one graphics variable. If lowering rendering load reduces GPU usage but does not improve FPS, the graphics card was probably not the active ceiling in that scene. This is also why a game can show the same FPS on Low and Ultra settings.

Evidence-gated hardware checks

Parts to Consider Only When the Matching Cause Is Proven

Low CPU and GPU usage but low FPS is not a reason to buy all five products below. Each option belongs to one specific diagnosis: memory configuration or capacity, storage and asset streaming, sustained CPU thermal throttling, or a confirmed power-supply requirement.

Before opening Amazon Name the waiting state Use the 3-minute capture and repeat the same scene first.

No-purchase path

Do Not Buy Hardware When a Cap, Wrong GPU, Driver, Game Patch, Background App, or Engine Limit Explains the Problem

The strongest result can be permission to keep the PC you already own. Fix the free cause, repeat the original scene, and spend money only when the same hardware limit remains.

Run the diagnostic before shopping

Memory path · DDR4 Matched 32GB kit

Corsair Vengeance LPX 32GB DDR4-3200 CL16

2 × 16GB desktop UDIMM · CMK32GX4M2E3200C16

Consider it when: A DDR4 desktop has one memory module, insufficient capacity, an unsuitable mixed kit, or repeatable memory pressure that matches low CPU and GPU usage but low FPS.
Check first: DDR4 motherboard support, CPU memory support, recommended paired slots, existing modules, BIOS compatibility, cooler clearance, and whether 32GB solves the measured workload.
Skip it when: The PC already has a stable matched 32GB or larger DDR4 configuration and memory is not the waiting state. Do not mix kits casually.

View This Exact DDR4 Kit on Amazon Check current listing, seller, and availability

Memory path · DDR5 Matched 32GB kit

Crucial Pro 32GB DDR5-6000 Kit

2 × 16GB desktop UDIMM · CP2K16G60C48U5 · CL48 listing

Consider it when: A compatible DDR5 desktop needs a matched two-module kit because capacity, channel layout, or memory behavior is proven to be restricting frame delivery.
Check first: DDR5 motherboard support, CPU memory-controller support, motherboard QVL where available, paired slots, supported profile, BIOS version, and stability at the selected speed.
Skip it when: The system uses DDR4, laptop SO-DIMMs, already has a suitable stable DDR5 kit, or low GPU utilization in games does not correlate with memory pressure.

View This Exact DDR5 Kit on Amazon Check current listing, seller, and availability

Storage path 2TB NVMe SSD

WD_BLACK SN850X 2TB NVMe SSD

M.2 2280 · WDS200T2X0E · Without heatsink listing

Consider it when: Disk activity, insufficient free space, asset streaming, decompression, loading, or drive health repeatedly matches frame-time spikes.
Check first: M.2 NVMe support, available 2280 slot, PCIe generation, motherboard heatsink, current drive health, backup, cloning, and operating-system migration requirements.
Skip it when: The problem is a steady CPU or GPU ceiling with no storage evidence. A faster SSD is not a universal cure for low average FPS.

View This 2TB NVMe SSD on Amazon Check current listing, seller, and availability

Cooling path Dual-tower air cooler

Thermalright Phantom Spirit 120 SE Black

Seven heat pipes · Dual 120mm PWM fans · Desktop CPU cooler

Consider it when: CPU clocks or sustained frame delivery fall as temperature rises, and mounting, fan, pump, dust, airflow, and firmware causes have been checked.
Check first: CPU socket, included mounting hardware, case cooler-height clearance, motherboard components, RAM clearance, CPU power, and your current cooler problem.
Skip it when: The CPU maintains expected clocks and the performance issue does not worsen after warm-up. One high temperature screenshot is not enough.

View This CPU Cooler on Amazon Check current listing, seller, and availability

Power path 850W ATX 3.1 PSU

Corsair RM850e 850W, 2025 Model

Fully modular · ATX 3.1 · PCIe 5.1 · Native 12V-2×6 cable

Consider it when: The current PSU is unsuitable, unstable, damaged, missing the required connector, or inadequate for a verified CPU, GPU, or complete-system upgrade.
Check first: Complete system power needs, GPU and CPU guidance, connector type, case compatibility, regional input power, warranty, and the exact cable plan.
Skip it when: The existing quality PSU is correctly sized and stable. A PSU does not normally create a predictable bottleneck percentage or automatic FPS gain.

View This 850W PSU on Amazon Check current listing, seller, and availability

CPU or GPU path Separate decision lab

Confirmed the Major Component Is the Limit?

Use the dedicated Upgrade Decision Lab for exact CPU and GPU product paths, complete platform cost, compatibility checks, and the no-purchase option.

Compare CPU and GPU Upgrade Paths Open the verified product decision section

Do this before changing settings

The 3-Minute Evidence Capture

You do not need a laboratory to diagnose low CPU and GPU usage but low FPS. You need one repeatable scene and a small set of signals that explain what is waiting.

01
Choose one scene that shows the problem
Use the same save, route, benchmark pass, match location, or workload segment. Avoid menus, loading screens, cutscenes, and a random screenshot taken after the problem has already passed.
02
Write down the complete target
Record resolution, refresh rate, frame cap, V-Sync state, graphics preset, ray tracing, upscaling, frame generation, game mode, and whether streaming or recording is active.
03
Capture frame time and the parts that can delay it
Watch frame time, average FPS, 1% lows where available, GPU utilization or GPU busy time, important CPU cores, clocks, temperatures, RAM use, VRAM use, and background activity.
Open Intel PresentMon
04
Change one graphics variable
Lower output resolution or one demanding rendering option, then repeat the identical scene. Do not change the frame cap, crowd density, simulation, upscaler, and several visual settings at the same time.

FPS improves clearly Rendering load was part of the ceiling

Continue with the GPU-side checks and verify VRAM, clocks, temperature, power, and settings response.

Run the GPU-side checks

FPS barely changes The GPU was probably waiting

Check important CPU threads, caps, memory, storage, engine behavior, power, and background work.

Run the CPU-side checks

The result is inconsistent Stutter or another system limit may be involved

Use a longer capture and match each spike to temperature, clock, RAM, VRAM, disk, shader, or software activity.

Open the 53-point verification lab

The utilization trap

Why Low CPU and GPU Usage but Low FPS Can Hide One Busy Game Thread

Low CPU and GPU usage but low FPS often confuses people because total CPU usage averages work across all cores and threads. A game may depend heavily on one main thread, one render thread, simulation work, asset preparation, or a small set of important cores while the remaining cores have spare capacity. The total percentage can therefore look comfortable even when the next frame cannot be prepared any faster.

Change Task Manager from one total CPU graph to logical processors, then compare the busy cores with GPU behavior and frame time. Do not assume that one core touching a high value for a moment proves a permanent CPU limit. The pattern must repeat in the scene that matters.

See Microsoft’s core and logical-processor steps

Total CPU 31% Looks comfortable

1 2 3 4 5 6 7 8

One important thread can delay the frame while the total percentage stays low.

Match the symptom

Six Patterns That Narrow the Cause Quickly

Start with the low CPU and GPU usage but low FPS pattern you can reproduce. Do not apply every fix on the internet at once.

01 Exact ceiling

FPS Stops at 30, 60, 120, 144, 165, 240, or Another Exact Number

When low CPU and GPU usage but low FPS stops at an exact and stable ceiling, an intentional limit is often more likely than weak hardware. Check the in-game limiter, V-Sync, driver-level frame limit, RTSS or overlay limit, menu cap, monitor refresh setting, laptop battery feature, and any game-specific maximum.

Both CPU and GPU have headroom Frame time is regular The number repeats across scenes Lower settings do not break the ceiling

What this usually means: the PC may already be delivering the requested frame rate and is intentionally waiting. Low utilization is normal when no more frames are being requested.

02 Same FPS

Low and Ultra Settings Produce Almost the Same FPS

Low CPU and GPU usage but low FPS with nearly identical results on Low and Ultra usually means rendering is not the active ceiling. GPU utilization may fall on Low because the card finishes its reduced work sooner and waits longer for the next frame. This is a common reason the GPU is not fully utilized even though the game remains slow.

Compare the identical scene Keep the frame cap unchanged Check important CPU cores Record GPU busy and frame time

Likely directions: CPU thread limit, engine ceiling, cap, memory behavior, background process, or a workload setting that does not change with the graphics preset.

03 One game

Only One Game, Map, Server, or Patch Has the Problem

When low CPU and GPU usage but low FPS appears in only one game, the chance that both major components suddenly became defective is lower. Look for engine behavior, shader compilation, a patch regression, anti-cheat interaction, a damaged configuration file, mod conflict, server load, CPU-heavy simulation, or one unusually demanding area.

Test another game with similar load Check the developer’s known issues Verify game files Compare a clean configuration

Do not overreact to one title: a platform replacement should solve a repeated target problem, not one isolated patch unless that game is the reason the PC exists.

04 Every game

Every Game Is Slower Than Expected

Low CPU and GPU usage but low FPS across every game deserves broader checks: power mode, wrong GPU selection, display cable routing, memory channel and profile, thermal or power limits, clock speed, background capture, driver state, BIOS changes, storage health, and whether the hardware is running at the expected link and clock behavior.

Compare clocks with specifications Check RAM channel and speed Check power mode while plugged in Test a known repeatable benchmark

Review Microsoft’s Windows performance checks

05 Laptop path

Laptop, Handheld, or Multi-GPU System Uses the Wrong Performance Path

Low CPU and GPU usage but low FPS on a laptop or multi-GPU system can happen when the game runs on a power-saving GPU, passes frames through a different display path, or uses a quiet, battery, hybrid, or manufacturer performance mode. Test while connected to the correct power adapter, confirm the active GPU, and check the laptop maker’s performance or MUX settings.

Confirm the game uses the high-performance GPU Check the manufacturer’s power mode Test plugged in Confirm the display connection path

Open Windows graphics preference instructions

06 Sudden change

The Problem Started After a Game, Driver, Windows, BIOS, or Software Update

Low CPU and GPU usage but low FPS that begins suddenly should be treated as evidence. Record the date and what changed before replacing hardware. New drivers, shader-cache rebuilds, overlays, monitoring tools, firmware settings, game patches, background utilities, and Windows updates can alter behavior without changing the CPU or GPU.

Check update timing Use official driver sources Review changed settings Retest after shader work settles

Open NVIDIA’s official Game Ready driver page

Waiting-state library

Twelve Causes to Check in the Safest Order

Open only the causes that match your evidence. Low CPU and GPU usage but low FPS has several possible waiting states, and each panel explains what the symptom means, what to check, and what not to assume.

01 Frame cap, V-Sync, refresh-rate limit, or engine ceiling Exact or stable FPS ceiling

A limiter tells the CPU and GPU to stop producing frames beyond the requested rate. Low CPU and GPU usage but low FPS can therefore be intentional when the selected cap or synchronization target has been reached, even though both components remain below full utilization.

Check the in-game limiter and V-Sync.
Check driver and overlay frame limits.
Confirm the monitor is set to the intended refresh rate.
Check menu, cutscene, and game-engine caps separately.

02 One busy CPU thread hidden by low total CPU use GPU waits while total CPU looks comfortable

The main game thread, render submission, simulation, draw calls, decompression, or asset preparation can delay the next frame. Low CPU and GPU usage but low FPS can remain visible because total CPU usage across many cores hides that pressure while the graphics card waits.

Display logical processors instead of one total graph.
Compare busy cores with GPU drops and frame-time spikes.
Lower CPU-heavy settings such as crowds, simulation, view distance, or object density when the game exposes them.
Do not treat one brief core spike as a permanent bottleneck.

03 Memory channel, capacity, speed, profile, or stability Weak 1% lows, CPU-side slowdown, or stutter

Single-channel operation, an incorrect module layout, insufficient capacity, inactive XMP or EXPO, unstable memory tuning, or heavy background memory use can create low CPU and GPU usage but low FPS by reducing frame delivery and making the GPU wait.

Confirm the modules are in the motherboard’s recommended paired slots.
Check whether the system is operating in the expected channel mode.
Confirm actual memory speed and capacity.
Use XMP or EXPO only when the CPU, motherboard, and memory support it and the system remains stable.

Intel XMP information AMD EXPO information

04 Thermal throttling or restricted sustained clocks Performance falls after the PC warms up

A component can remain below full utilization because it cannot maintain expected frequency under heat, power, voltage, cooling, firmware, or laptop design limits.

Log temperature and clock speed from the start of the test.
Watch for falling clocks as temperature or power limits change.
Check dust, fan behavior, pump behavior, mounting, and case airflow.
Do not compare temperatures alone without clock and power behavior.

05 Power-saving mode, battery mode, quiet mode, or vendor profile Low clocks and low utilization across many games

Windows, a laptop control app, BIOS firmware, a handheld profile, or a GPU utility can favor lower power and quieter operation. The system may never request full performance.

Test while connected to the correct power adapter.
Check Windows power mode and the device maker’s performance profile.
Confirm CPU and GPU clocks rise under load.
Remember that higher-performance modes increase heat, fan noise, and power use.

See Microsoft’s Windows power-mode steps

06 Wrong GPU, wrong display path, or hybrid-graphics behavior Dedicated GPU remains unexpectedly idle

This is most relevant to laptops, mini PCs, systems with multiple GPUs, and desktops where display routing is unclear. Confirm the active adapter before changing hardware.

Check the GPU engine used by the game.
Set the app to the intended high-performance GPU when multiple GPUs exist.
Check the monitor cable and motherboard or graphics-card output.
Review the device maker’s hybrid, discrete, or MUX mode guidance.

07 Shader compilation, asset streaming, storage, or decompression Stutter during traversal, first runs, loading, or new effects

A storage or shader event can stall frame delivery while neither main component appears fully occupied. This is different from a steady CPU or GPU throughput limit.

Repeat the same route to see whether first-run stutter improves.
Watch disk activity and memory pressure during the spike.
Check free storage space and drive health.
Do not assume an SSD upgrade will fix a sustained frame-rate ceiling without storage evidence.

08 Background capture, browser, overlay, RGB, monitoring, or update activity The result changes after closing software

Background tools can use CPU time, memory, storage, GPU scheduling, overlays, encoder resources, or hooks. The impact can be small in one scene and obvious in another.

Record the active background applications before closing them.
Retest after closing nonessential capture, browser, launcher, RGB, and overlay tools.
Keep one monitoring method active so you can still compare the result.
Do not disable security services or random Windows services from an optimization pack.

09 Driver, game patch, Windows update, BIOS change, or configuration regression The problem began suddenly

A timing match is not proof, but it is a strong place to start. Check official release notes, known issues, reset settings, shader rebuild behavior, and whether the same issue appears outside one title.

Use official GPU and motherboard support pages.
Record the previous and current driver or BIOS version.
Avoid stacking several driver, BIOS, and registry changes before retesting.
Keep a rollback plan for firmware and configuration changes.

10 Upscaling, frame generation, dynamic resolution, or variable workload state Displayed FPS and utilization do not compare cleanly

Upscaling changes internal rendering load. Frame generation adds displayed frames after the underlying game frames. Dynamic resolution can change the workload during play. Record these states before comparing two runs.

Compare native with native or the same upscaling mode and quality level.
Keep frame generation consistently on or off.
Record dynamic-resolution targets.
Do not compare generated displayed FPS directly with a native run and call the difference a CPU or GPU fix.

11 Game-engine or server-side ceiling One title or mode refuses to scale

Some games are limited by their main thread, simulation, draw calls, server conditions, anti-cheat, world complexity, mods, or a fixed internal behavior. Stronger hardware may help only a little or only in certain scenes.

Compare another mode, map, save, or server.
Check whether the problem appears offline.
Review community and developer reports for the current patch.
Do not use another player’s uncontrolled screenshot as your performance baseline.

12 Monitoring mismatch or the wrong performance question The numbers look alarming but the target is already met

Low utilization is not a fault when the frame-rate target, frame time, image quality, temperature, noise, and responsiveness already meet the user’s goal. The PC does not need to keep both components at 100 percent.

Judge the real target, not an arbitrary utilization goal.
Use frame time and 1% lows alongside average FPS.
Compare the same scene and settings.
Upgrade only when a confirmed limit prevents something that matters.

The safe repair order

What to Do Next Without Making the Diagnosis Worse

Each change should answer one question. When diagnosing low CPU and GPU usage but low FPS, changing ten settings at once can hide what fixed the problem or which change created a new one. Low CPU and GPU usage but low FPS becomes useful evidence only when the same controlled scene produces the same pattern.

1
Confirm the target and remove intentional caps
Resolution, refresh rate, limiter, V-Sync, upscaling, frame generation, workload, and scene.
2
Check whether the problem affects one game or every game
This separates an application path from a system-wide path.
3
Capture frame time, per-core CPU activity, and GPU behavior
Do not rely on one total CPU percentage or one utilization screenshot.
4
Change one rendering variable
Use the same scene and cap to see whether the GPU workload changes the outcome.
5
Check clocks, temperature, power, memory, and storage
Match frame-time spikes to the system event that happened at the same moment.
6
Check software and update timing
Drivers, patches, overlays, capture tools, background tasks, firmware, and configuration.
7
Repeat the original scene
Keep the successful change separate so you know what mattered.
8
Use the upgrade path only when the same limit remains
Compare the complete platform cost and preserve the no-purchase option.

High-risk shortcuts

Do Not “Optimize” a PC by Removing the Evidence

Registry tweak packs

A copied registry file can change scheduling, services, power behavior, or security without proving the cause. It also makes rollback and support harder.

Disabling security or random services

Removing protections and background services may create risk without improving the limiting scene. Close known nonessential apps first and retest.

Overclocking before diagnosis

An unstable CPU, GPU, or memory tune can create stutter, driver resets, data corruption, and misleading results. Return to known-stable settings when troubleshooting.

Buying from one percentage

A utilization value or calculator estimate is not measured FPS loss. Hardware becomes the answer only when the same proven ceiling blocks the target that matters.

When hardware becomes a valid answer

Upgrade Only When the Waiting State Has a Name

A processor upgrade becomes reasonable only when low CPU and GPU usage but low FPS is repeatedly traced to important CPU threads, frame time, and GPU headroom, and memory, power, heat, caps, software, and the game engine have been checked.

A graphics-card upgrade becomes reasonable when the GPU is the repeated rendering ceiling, the same scene responds to lower rendering load, VRAM and thermal behavior are understood, and the current card cannot meet the chosen resolution, frame rate, or image-quality target.

Decision lab Compare CPU and GPU upgrade paths Open the full cost and evidence comparison → Calculator Check the selected CPU, GPU, resolution, and FPS target Run the main BottleneckLab tool → Verification Confirm the result on the real PC Open the 53-point checklist →

Common questions

Low Usage and Low FPS FAQ

These answers stay conditional because games, laptops, drivers, caps, memory, cooling, and performance targets differ.

Why are both CPU and GPU usage low while gaming?

Low CPU and GPU usage but low FPS can come from an FPS cap, V-Sync, one busy CPU thread, memory, storage, shader work, temperature, power, background software, the wrong GPU, or a game-engine limit. Check frame time, important CPU cores, GPU behavior, clocks, and the same scene together.

Does low GPU usage mean a CPU bottleneck?

Not by itself. Low GPU usage can appear during a CPU-side limit, but also during a frame cap, menu, engine ceiling, shader compilation, storage stall, power-saving mode, wrong GPU selection, background process, or when the requested frame rate has already been reached.

Why is total CPU usage low if the CPU is the limit?

Total usage averages activity across all cores and threads. One or a few important game threads can delay the next frame while the remaining cores stay lightly used. Check logical processors and compare the busy threads with frame time and GPU drops.

Why do Low and Ultra settings give the same FPS?

Rendering may not be the active ceiling. Lower settings can reduce GPU utilization without increasing FPS when the CPU, game engine, frame cap, memory, background work, or another waiting state controls frame delivery.

Is low GPU usage bad if the game feels smooth?

No. If the selected frame rate, frame time, image quality, responsiveness, noise, and temperature meet the goal, the GPU does not need to remain near full utilization. Low use is a problem only when the real target is being missed.

Can RAM cause low GPU usage?

Yes. Single-channel operation, insufficient capacity, incorrect module placement, low default speed, inactive XMP or EXPO, unstable tuning, or heavy memory pressure can reduce CPU-side frame delivery and leave the GPU waiting.

Can a slow SSD cause both CPU and GPU usage to look low?

Storage and asset streaming can cause stalls during loading, traversal, decompression, or texture streaming. That is different from a steady rendering bottleneck. Match disk activity to the frame-time spike before replacing the drive.

Should I reinstall Windows to fix low utilization?

Not as the first step. A reinstall removes clues and costs time. First identify whether the problem is game-specific or system-wide, check caps, GPU selection, power mode, memory, clocks, temperatures, drivers, background apps, and update timing.

Should I upgrade the CPU or GPU when both usage numbers are low?

Neither upgrade is justified until the waiting state is identified. Use the same-scene test, remove false ceilings, check per-core CPU activity and GPU response, then compare the complete CPU and GPU upgrade paths.

Evidence and editorial limits

Sources Used for the Diagnostic Framework

This page combines official operating-system and hardware guidance with a symptom-first BottleneckLab process for low CPU and GPU usage but low FPS. It does not claim that every game, patch, laptop, CPU, GPU, storage device, cooler, power supply, or memory kit behaves the same.

Intel PresentMon for frame telemetry, GPU busy, and CPU-GPU balance context.
Microsoft processor-core guidance for viewing cores and logical processors in Task Manager.
Microsoft Windows graphics preferences for selecting a high-performance GPU on multi-GPU systems.
Microsoft Windows performance checks for power mode, background activity, storage, and resource monitoring.
Intel XMP and AMD EXPO for official memory-profile context and overclocking cautions.
BottleneckLab Editorial Methodology for estimate, evidence, recommendation, source, and correction rules.

Last materially reviewed: July 22, 2026. Game patches, Windows behavior, drivers, BIOS versions, laptop profiles, and hardware support can change after publication.