Free tools Windows power users keep installed
One-click scans. No signup required.
The quickest test: monitor per-thread CPU activity, GPU usage, FPS, and frametime while repeating the same demanding scene. Then lower the resolution substantially. If FPS barely changes, one important CPU thread is heavily loaded, and the GPU is waiting, your game is probably CPU-limited. If lowering resolution produces a large FPS increase while the GPU remains near full load, the GPU is more likely the bottleneck.
Before buying hardware, rule out frame caps, V-Sync, thermal throttling, background tasks, incorrect GPU selection, memory pressure, shader compilation, storage streaming, and network lag.
As an Amazon Associate I earn from qualifying purchases.
What a CPU bottleneck actually means
Every rendered frame passes through several stages. The game simulates the world, processes AI, physics, animation, audio, networking and input; the CPU prepares rendering commands; the GPU renders the image; and the display presents it. The slowest stage sets the frame rate.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsA CPU bottleneck does not necessarily mean the processor is defective or that total CPU usage reaches 100%. A game may be limited by one main or render thread while other cores remain lightly used. Microsoft identifies CPU-side work such as draw submission and game systems as possible limits in Windows titles, while resolution, fill rate and pixel shading are more typical GPU-side workloads (Microsoft’s game-performance guidance).
#1 Best Overall
- The world’s fastest gaming processor, built on AMD ‘Zen5’ technology and Next Gen 3D V-Cache.
- 8 cores and 16 threads, delivering +~16% IPC uplift and great power efficiency
- 96MB L3 cache with better thermal performance vs. previous gen and allowing higher clock speeds, up to 5.2GHz
- Drop-in ready for proven Socket AM5 infrastructure
- Cooler not included
Think in frame times rather than utilization alone:
frame time in milliseconds = 1,000 ÷ FPS- 60 FPS requires about 16.7 ms per frame.
- 120 FPS requires about 8.3 ms.
- 144 FPS requires about 6.9 ms.
- 240 FPS requires about 4.2 ms.
If the CPU needs 20 ms to prepare a frame while the GPU needs only 8 ms to render it, the CPU is setting a theoretical ceiling near 50 FPS.
Symptoms that point to the CPU
These clues are useful together, but none proves a CPU bottleneck by itself:
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- GPU utilization stays well below its normal gaming load.
- FPS changes little when resolution is lowered.
- Performance falls in cities, large battles, crowded areas or simulation-heavy scenes.
- Average FPS may look acceptable while minimum or 1% low FPS is poor.
- One or a few logical processors show sustained high activity.
- A faster graphics card produces little improvement at the same settings.
- CPU frame time is higher than GPU frame time.
Do not use “GPU below 90%” as a verdict. A frame cap, V-Sync, loading, shader compilation, thermal problem, driver issue or storage delay can also leave the GPU underused.
First rule out simpler causes
Check these before diagnosing the processor:
- Frame limits: Check the game’s FPS limit, V-Sync and driver-level profiles. Also check Radeon Chill, NVIDIA application limits and any RivaTuner Statistics Server limit.
- Display settings: Confirm Windows is using the monitor’s intended refresh rate. A game locked to 60 FPS on a 60-Hz display may leave both CPU and GPU below full utilization normally.
- Power: Plug in a laptop and select an appropriate performance mode. Battery operation can impose severe CPU and GPU limits.
- GPU selection: Verify that the game uses the dedicated GPU rather than integrated graphics. Windows graphics preferences and the vendor control panel can both affect application selection; some games prioritize Windows’ setting.
- Temperatures and clocks: A CPU that loses clock speed as the system warms up may be throttling rather than simply being too slow.
- RAM and VRAM: Nearly full system memory can cause paging and stutter. Exhausted VRAM can disrupt texture streaming and frame pacing.
- Background work: Pause downloads and close unnecessary browsers, recording tools, antivirus scans and overlays for one test.
- Network symptoms: Rubber-banding, delayed hit registration and teleporting players indicate latency or packet loss, not necessarily low rendering performance.
MSI’s low-FPS troubleshooting guide also recommends checking cooling, dedicated-GPU assignment, storage, drivers, BIOS and network conditions.
Rank #2
- Legend perfected: Modern design with a matte "basalt black" finish in an optimized chassis with customizable AlienFX lighting zones, including the striking stadium lighting.
- Game changing graphics: Step into the future of gaming and creation with the NVIDIA GeForce RTX 5080 graphics, powered by NVIDIA Blackwell architecture.
- Marathon gaming unlocked: This high-performance technology ensures clean energy is consistently available, unleashing the top-level power of Intel Core Ultra 9 processor as you game, livestream, and multi-task for hours on end.
- 240mm heat exchanger: The 240mm heat exchanger, available on the optional CPU liquid cooling, heightens thermal resistance, ensuring temperatures stay consistently low during longer gaming sessions.
- Total command: Alienware Command Center software allows you to create and edit AlienFX lighting across the ecosystem, choose and monitor your performance mode across distinct power states, and create custom gaming profiles for your whole library.
Make the test repeatable
- Choose the same save, replay, benchmark, map, route or 30–60-second gameplay section.
- Record resolution, graphics preset, FPS limit, V-Sync, upscaling, dynamic resolution and frame-generation settings.
- Test the area where the slowdown actually occurs, not a menu, loading screen or cutscene.
- Close unnecessary applications, keeping only the monitoring software you need.
- Repeat the same scene after each meaningful change.
Utilization can fluctuate from moment to moment. A repeatable scene produces evidence instead of a misleading single reading.
Fast first pass with Windows Task Manager
- Press Ctrl + Shift + Esc.
- Open Performance and select CPU.
- Right-click the CPU graph.
- Choose Change graph to → Logical processors.
- Run the game and watch the graphs during the problem scene.
Also inspect CPU frequency, memory usage, GPU activity and the Processes tab for unexpected CPU-consuming software.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For example, one fully occupied thread on a 16-thread CPU may appear as only roughly 6–7% total CPU usage. The exact percentage varies with Windows’ accounting and the game’s thread behavior, but the conclusion is the same: total CPU percentage can hide a saturated game thread. Microsoft treats sustained CPU utilization above approximately 85% as a useful general warning indicator, not as a definitive gaming-bottleneck threshold (Microsoft Performance Monitor guidance).
Task Manager is a screening tool, not a complete frame-time analyzer. Different tools may disagree because they use different sampling and averaging methods; Intel documents this difference between instantaneous and rolling CPU readings (Intel’s explanation).
Use Xbox Game Bar without installing software
- Launch the game and press Win + G.
- Open the Performance widget.
- Enable the available CPU, GPU, memory and FPS graphs.
- Pin the widget if it must remain visible.
The exact layout varies by Windows version and installed components. Xbox Game Bar is useful for a quick check, but it may not expose detailed CPU/GPU frame times.
Rank #3
- Can deliver fast 100 plus FPS performance in the world's most popular games, discrete graphics card required
- 6 Cores and 12 processing threads, bundled with the AMD Wraith Stealth cooler
- 4.2 GHz Max Boost, unlocked for overclocking, 19 MB cache, DDR4-3200 support
- For the advanced Socket AM4 platform
Use an in-game overlay for better evidence
MSI Afterburner with RivaTuner Statistics Server can display the measurements most gamers need. Afterburner works with graphics cards from different manufacturers; monitoring does not require overclocking.
In Afterburner, open Settings → Monitoring, select each metric and enable Show in On-Screen Display. Set an OSD hotkey in the On-Screen Display tab. Useful fields include:
- FPS, frametime and 1% lows
- GPU usage, clock, temperature and power
- CPU total and per-core or per-thread usage
- CPU clock and temperature
- RAM and VRAM usage
Download Afterburner only from MSI or its authorized Guru3D distribution. Fake download sites exist. If an overlay causes crashes or fails to appear, test once with it disabled; overlays can conflict with anti-cheat systems, launchers and some rendering APIs.
The resolution-scaling test
Run the same scene at native resolution and then at a substantially lower resolution. Keep other settings unchanged where possible.
| Result | Likely meaning |
|---|---|
| FPS rises substantially and GPU remains busy | GPU limitation is likely. |
| FPS barely changes and a CPU thread is busy | CPU, engine or another non-GPU limitation is likely. |
| FPS rises but stutter remains | There may be both a GPU limit and a separate CPU, shader, streaming or memory problem. |
| FPS remains exactly 60, 120 or 144 | Check a cap, V-Sync or refresh-rate limit first. |
Dynamic resolution, upscaling and frame generation can make this test misleading, so record whether each is enabled. Lowering resolution reduces GPU work; it does not substantially reduce the game’s simulation, AI or draw-submission workload.
Rank #4
- Pure gaming performance with smooth 100+ FPS in the world's most popular games
- 6 Cores and 12 processing threads, based on AMD "Zen 5" architecture
- 5.4 GHz Max Boost, unlocked for overclocking, 38 MB cache, DDR5-5600 support
- For the state-of-the-art Socket AM5 platform, can support PCIe 5.0 on select motherboards
- Cooler not included
Compare CPU and GPU frame times
This is generally stronger evidence than utilization alone. If GPU frame time is higher, the GPU is normally limiting the frame. If CPU frame time is higher and the GPU is waiting, the CPU is normally limiting it. Examine spikes as well as averages.
PresentMon records CPU, GPU and display frame durations across supported DirectX, OpenGL and Vulkan workloads. Intel’s PresentMon interface provides overlay and capture-oriented workload data, including CPU/GPU balance information. NVIDIA FrameView can log average FPS, 1% lows, utilization, clocks, temperatures and frame-time-related metrics, and its documentation describes support across NVIDIA, AMD and Intel graphics hardware.
These tools are valuable for comparisons, but their definitions and capture paths are not identical. PresentMon documents limitations affecting some latency calculations, so treat results as diagnostic measurements rather than absolute laboratory truth.
How to read common patterns
| What you observe | What to investigate next |
|---|---|
| GPU near full load; lowering resolution raises FPS | GPU settings such as resolution, ray tracing, lighting, shadows and effects. |
| GPU underused; one CPU thread is busy; lower resolution changes little | CPU-heavy settings, clocks, temperatures, power mode and background tasks. |
| Total CPU usage is low; one logical processor is near full | Main-thread or engine limitation; inspect CPU frame time. |
| CPU and GPU are both below full load; FPS is fixed | In-game, driver, V-Sync or RTSS caps and monitor refresh rate. |
| High FPS but large frametime spikes | Shader compilation, asset streaming, storage, RAM/VRAM, drivers and overlays. |
| CPU clock drops with rising temperature and FPS loss | Cooling, fan curve, power limits, BIOS and laptop charging. |
| Normal rendering metrics but rubber-banding or delayed hits | Network latency, packet loss or server conditions. |
| Low laptop GPU usage on battery | Connect the charger and verify dedicated-GPU routing. |
| Camera movement changes FPS but resolution does not | Scene complexity, shader compilation or asset streaming; repeat in settled areas. |
Fixes for a confirmed CPU limit
- Set a sensible FPS cap. If the CPU cannot sustain the display’s maximum refresh rate, a stable lower cap can improve frame pacing and reduce unnecessary load.
- Lower CPU-heavy settings. Try view distance, object or model distance, crowd density, simulation quality, physics, foliage distance and world-streaming or population settings. Names differ by game.
- Close CPU-heavy background software. Check Task Manager rather than blindly installing a “game booster.”
- Restore normal clock behavior. Check temperature, effective clock, package power and thermal or power-limit indicators. A cooler, fan-curve change or correct laptop power mode may solve the problem without a CPU upgrade.
- Check memory. Confirm adequate capacity and that memory is not running in an unintended single-channel or reduced-speed configuration.
- Update selectively. Check BIOS, chipset drivers, GPU drivers and game patches when the problem is game-specific or began after an update. Keep a record so you can reverse a change that worsens the issue.
Textures and resolution are usually more directly tied to VRAM and GPU work. Lowering them may improve a GPU limit, but it often does little for a CPU-limited game.
When slow performance is not a CPU bottleneck
GPU limitation
High GPU usage, high GPU frame time and a substantial FPS increase after lowering resolution or ray tracing point toward the graphics card. A faster GPU is relevant only when measurements show that the GPU is limiting the target frame rate.
Best Value
- POWERHOUSE 8-CORE GAMING PERFORMANCE — Driven by the AMD Ryzen 7 8700F with 8 cores and 16 threads, boosting up to 5.0 GHz for smooth, responsive gameplay and the ability to handle AAA titles, streaming, and background tasks all at once
- NEXT-GEN BLACKWELL ARCHITECTURE — The NVIDIA GeForce RTX 5070 is powered by NVIDIA's cutting-edge Blackwell GPU architecture, delivering a massive generational leap in rasterization and ray tracing performance so you can experience your games the way they were meant to be played.
- Simplistic Design: Enjoy the latest generation of Windows 11 Home for your everyday needs. *MSI recommends Windows 11 Pro for business use.
- Cool While Gaming: In conjunction with an ARGB fan Air Cooler, the Codex R2 features four system cooling fans; three in the front and one in the rear to pull in cool air and push heat out of the PC.
- Turn on the Bright Lights: With the built-in RGB lighting, take your gaming experience to the next level by pressing the MSI LED button to cycle through lighting options. Customize lighting even further with MSI Center software.
Shader compilation
Brief hitches after launching a game, entering a new area or installing a driver can be shader-compilation stutter rather than a persistent CPU limit. Consistently low FPS suggests a sustained workload problem; recurring brief hitches suggest compilation or another streaming issue.
RAM, VRAM and storage streaming
Nearly full RAM can cause paging, while full VRAM can disrupt texture streaming. An SSD may improve loading or streaming behavior, but it does not automatically increase average FPS. Storage is a likely target only when your measurements show loading or streaming-related stalls.
Engine limits and game bugs
Some games are constrained by a main thread, a particular API path or an engine behavior that no graphics setting fully fixes. One busy thread does not prove that buying a new processor is the only solution; a patch, targeted setting change or frame cap may be more appropriate.
Should you upgrade the CPU?
Consider an upgrade only after a repeatable test shows that the CPU is the limiting stage while temperatures, clocks, power, memory and software are normal. Your target matters: a processor can be perfectly adequate for 60 FPS yet limit 144 or 240 FPS in a simulation-heavy game.
Before purchasing, write down:
- Current CPU, motherboard socket and BIOS support
- Memory generation, capacity and channel configuration
- Target resolution, refresh rate and FPS
- The affected games and scenes
- CPU and GPU frame times during the problem
- GPU utilization while the CPU limit occurs
- CPU temperature, effective clock and power behavior
- Total platform cost, including motherboard, memory or cooler if required
A faster CPU will not automatically improve every game. Conversely, replacing a GPU will not solve a CPU limit simply because the current graphics card is older. Diagnose the component that is actually setting the frame time.
Quick Recap
Screenshot checklist
- Repeat the same 30–60-second problem scene.
- Check caps, V-Sync, refresh rate, power mode and dedicated-GPU selection.
- Monitor FPS, frametime, GPU usage, CPU per-thread activity, clocks, temperatures, RAM and VRAM.
- Lower resolution without changing other variables.
- Compare CPU and GPU frame times if possible.
- Check for throttling, background tasks, shader compilation, streaming and network symptoms.
- Apply targeted settings changes before buying hardware.
- Upgrade only when measurements confirm a sustained CPU limit at your target FPS.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
