Is 100% CPU or GPU usage bad?

Published 2026-09-02 · Updated 2026-09-02 · By the PCPartGuide team

Short answer: 100% GPU usage while gaming is healthy: it means the graphics card is the limiter, which is what you paid for. 100% CPU usage across all cores during a game usually means the CPU is holding the GPU back, or something else is running. Neither number is harmful as long as temperatures and clocks are normal.

100% GPU usage in a game is the goal

A graphics card at 100% is doing exactly what you bought it for: drawing frames as fast as it can. Usage measures how busy the chip is, not stress or damage. A GPU is designed to run flat out for years, and its fans, power limit and clock controller exist to make that safe.

When the GPU sits at 97 to 100% during play, the card is the limiter and everything upstream of it is keeping up. That is the normal, healthy state for a gaming PC unless the frame rate is below your target. The question is not why usage is so high, but whether the frame rate is enough.

If it is not, you have a GPU-bound system that needs lower settings or a faster card. Dropping shadows, volumetric effects and ray tracing frees the most GPU time; upscaling from a lower internal resolution frees even more. The Ryzen 5 5600 and RTX 4060 pair is a typical build that shows 100% GPU usage in almost everything, because the card gives out well before the processor; upgrade CPU or GPU first? helps you decide what to change.

When 100% GPU usage is a problem

There are three cases where a pinned GPU means something is wrong.

100% on the desktop. With no game running, GPU usage should idle near zero. If it sits high, a browser tab, a crypto-miner, a stuck driver process or a wallpaper engine is burning it, and Task Manager's Processes tab sorted by the GPU column shows which.

100% with a frame rate that makes no sense. If a card that should manage triple digits at 1080p is pinned at 100% while delivering 40 fps, look for a runaway setting such as supersampling or a resolution scale above 100%, or a card stuck at low clocks. Temperatures and clocks, covered below, separate the two.

100% with stutter. Usage is an average over a sampling window, so a GPU can read 100% while the frametime graph spikes. That points at VRAM running out, shader compilation or storage streaming rather than raw GPU horsepower; an 8GB card such as the RTX 4060 at Ultra textures in a demanding game shows exactly this pattern.

CPU usage: the number that lies

CPU usage is where most people get misled, because Task Manager shows one averaged figure. Games are rarely spread evenly across cores. Most engines have a main thread and a render thread that do the bulk of the work, and if one of those is saturated, the game cannot go faster no matter how idle the other cores are.

On a 16-thread processor, a single thread pinned at 100% shows up as about 6% total CPU usage. Task Manager will say the CPU is barely working while the game is completely CPU-bound. You need a per-core view, which Task Manager offers under Performance, CPU, right-click on the graph, Change graph to, Logical processors.

The reverse pattern is the one that should worry you. All cores at 100% during a game means either the game genuinely needs more processor than you have, which is rare outside heavy simulation and strategy titles, or something else is running. Shader compilation on first launch, a Windows update, an antivirus scan or a browser with fifty tabs all look like this, so check the Processes tab with the game minimized.

A processor with few threads makes both patterns worse. Quad-core chips and older six-core chips without much cache hit the main-thread wall sooner and leave less room for background work. If an older CPU is pinned in every modern game, compare it with a drop-in successor on its CPU page, such as the Ryzen 5 3600 against a Ryzen 7 5700X3D.

How to read an overlay

Free overlays such as MSI Afterburner with RivaTuner Statistics Server, or Intel's PresentMon, put the numbers that matter on top of the game. Watch these counters, in this order:

• GPU usage, or GPU Busy in PresentMon. Near 100% means GPU-bound. Well below 90% with the frame rate uncapped means something upstream, usually the CPU, is the limiter. GPU Busy is the better counter because it measures how long the GPU spent on each frame versus how long the whole frame took.
• Per-core CPU usage. One or two threads near 100% with the rest idle is the classic CPU-bound signature. The single averaged number hides it.
• Frametime graph. A flat line is a smooth game. Spikes are stutters, and their timing tells you the cause: regular spikes while turning or entering new areas point to asset streaming or RAM, random spikes point to shader compilation or background tasks.
• 1% low frame rate. The average of the slowest 1% of frames. A big gap between the average and the 1% low means the game feels worse than the average suggests, and that gap is usually CPU or memory, not GPU.
• Clocks and temperatures for both parts, so you can rule out throttling.

A five-step bottleneck test

1. Turn on GPU usage, per-core CPU usage, frametime and 1% low counters, then start the game at your normal settings with any frame cap and V-Sync turned off for the test.
2. Play a demanding scene for two or three minutes. Note the average frame rate and where GPU usage sits.
3. Lower the render resolution or resolution scale to about 50%. If the frame rate rises a lot, you were GPU-bound at the original settings; if it barely moves, the GPU was not the limiter.
4. Put the resolution back and lower the CPU-heavy settings: crowd density, draw distance, shadow quality, physics. If the frame rate rises now, the CPU is the limiter.
5. Compare what you saw with the estimate from the bottleneck calculator for your parts, game and resolution. If they disagree, your settings, RAM or background load are probably the difference; the methodology page explains what the estimate does and does not take into account.

100% disk usage: annoying, but not a frame-rate problem

Disk usage at 100% is usually a burst of legitimate work: a game loading, a shader cache compiling, a Windows update installing, Windows Search indexing, or an antivirus scan walking the drive. On a hard drive, 100% is easy to reach because the drive is slow, and the number only says the drive was busy for the whole sampling window.

It does not lower your frame rate once the game is loaded, with one exception: open-world games that stream assets from a mechanical hard drive can stutter and show texture pop-in while the drive catches up. The fix is to move the game to an SSD, not to buy a faster CPU or GPU.

If disk usage sits at 100% at idle for a long time and the whole PC is sluggish, check the drive's health with a SMART reader; a failing hard drive retrying bad sectors looks exactly like this. Also check that Windows Search, SysMain and any cloud sync client are not fighting over the drive.

Temperatures and clocks: when low usage is the warning sign

Throttling looks like the opposite of the "100% is bad" worry. A part that gets too hot or hits a power limit lowers its clock speed, and because it now finishes its work more slowly, usage and frame rate can drop together. Low frame rates with GPU usage that will not stay pinned, and no CPU thread saturated, are the signature.

Read the clocks alongside the usage. A GPU that should boost past its rated speed but sits hundreds of megahertz lower under load is throttling; GPU-Z's PerfCap Reason field says whether it is thermal, power or voltage. A CPU that drops well below its all-core boost while its package temperature sits at its limit is doing the same.

Some numbers that look alarming are by design. Many modern processors run at their rated temperature limit under sustained load and control clocks from there, and graphics cards routinely sit at 70 to 85 degrees Celsius with hotspot readings higher still. The problem is not a high temperature; it is a clock that falls and a frame rate that falls with it. Clean the dust filters and check that fan curves ramp before anything more drastic.

FAQ

Quick answers to the usage questions people ask most.

Is 100% GPU usage bad while gaming?

No. It means the graphics card is the part setting your frame rate, which is the normal state for a gaming PC, and a GPU is built to run at full load for years. It is only a problem when the frame rate is lower than it should be, or when the card sits at 100% on the desktop with nothing running.

Is 100% CPU usage bad while gaming?

Usually it is a symptom rather than damage. All cores at 100% means the game is CPU-bound or something else is running; one thread at 100% with a low total means the game's main thread is the limiter. Check the Processes tab for background load, then a per-core view, and pair that with GPU usage to decide which part is holding you back.

Why is my GPU usage low while gaming?

Because something upstream is limiting the frame rate: the CPU, the RAM feeding it, a frame cap, V-Sync or a power-saving mode. Turn off caps and V-Sync, check per-core CPU usage for a pinned thread, and confirm the game is using the dedicated card rather than integrated graphics. Low GPU usage with a low frame rate almost always points to a CPU bottleneck.

Is 100% disk usage bad?

Not for frame rate, and usually not at all. It is normal during loading, shader compilation, updates and indexing. Sustained 100% at idle with a sluggish PC suggests a failing hard drive or a stuck background service. Games installed on a hard drive can stutter while streaming assets, which moving them to an SSD fixes.

What GPU usage should I see with a CPU bottleneck?

Anything noticeably below the high 90s while the frame rate is uncapped, often 60 to 85% and bouncing around. Look at the pattern rather than the number: GPU usage that dips when the action gets busy, a CPU thread near 100%, and a frametime graph that gets rougher at the same moments. How to fix a CPU bottleneck covers what to do next.

References

• Intel PresentMon documentation (GPU Busy and frametime metrics)
• Gamers Nexus frametime and 1% low testing methodology
• Hardware Unboxed CPU and GPU benchmark videos
• TechPowerUp GPU reviews and GPU-Z documentation
• Microsoft documentation for Task Manager and Windows performance counters