Dig into BIOS tuning guides and you will eventually hit advice to disable CPU C-States for gaming. C-States are power-saving idle modes that let cores sleep to save energy and reduce heat. The theory behind disabling them is that waking a sleeping core adds latency, so keeping cores awake could smooth frametimes. But is it actually worth it on a modern CPU? The honest answer is nuanced.
What C-States Actually Do
When a core has nothing to do, it enters a C-State (C1, C3, C6, and deeper), progressively cutting power and voltage. Deeper states save more energy but take longer to wake from. On paper, that wake latency, measured in microseconds, could cause tiny hitches in latency-sensitive workloads. In practice, modern CPUs transition between states extremely fast.
The Case For and Against Disabling
| Factor | C-States Enabled | C-States Disabled |
|---|---|---|
| Idle power / heat | Lower | Higher |
| Wake latency | Microseconds | None |
| Boost clock behavior | Normal | Can reduce max boost |
| Frametime consistency | Excellent on modern CPUs | Marginal difference |
| Typical FPS gain | Baseline | 0-1% in most games |
The Modern Reality
On current Ryzen and Intel chips, disabling C-States rarely produces a measurable gaming benefit, and it can actually hurt. Many CPUs rely on cores dropping to idle states so that active cores can boost higher within power and thermal limits. Force every core awake and you may raise temperatures and package power enough to slightly lower peak boost clocks, a net wash or loss.
When Disabling Might Help
- Chasing the absolute lowest DPC latency for pro-level competitive play or audio work.
- Diagnosing a specific stutter suspected to come from deep sleep transitions.
- Certain overclocking scenarios where a fixed all-core state improves stability.
Even then, disabling only the deepest states (like C6) rather than all of them is usually the smarter, less costly move.
A Better Approach
Rather than blanket-disabling C-States, use the Windows “High Performance” or “Ultimate Performance” power plan, which raises the minimum processor state and keeps clocks high during gaming without fighting the CPU’s boost logic. This captures most of the responsiveness benefit while letting the silicon manage power intelligently. Reserve BIOS C-State changes for troubleshooting or advanced overclocking.
What the Data Usually Shows
Independent testing across many titles tends to reach the same conclusion: on modern platforms, toggling C-States moves average and 1% low frame rates by margins small enough to fall within run-to-run variance. The frametime graphs look essentially identical. Where reviewers do occasionally find a difference, it is often that leaving C-States enabled produces slightly better boost behavior, because the CPU can park idle cores and redirect that thermal and power budget to the cores actually running the game. That is the opposite of what the old advice assumes, which is why blanket disabling has fallen out of favor.
Tune the Real Bottleneck Instead
If you are hunting for smoother frametimes, your time is far better spent elsewhere: enable your memory’s XMP or EXPO profile, make sure the CPU is not thermally throttling under a good cooler, update chipset drivers, and use a high-performance power plan. Those changes deliver consistent, measurable gains. C-State tinkering belongs in the narrow world of latency professionals and overclockers chasing stability at fixed voltages. For a typical gaming build, leave the power-saving states on, fix the genuine bottlenecks, and you will get better results with less risk.
FAQ
Will disabling C-States boost my FPS?
Almost never meaningfully. On modern CPUs the typical gain is zero to one percent, and it can slightly reduce boost clocks by raising temperatures and power draw. For everyday gaming it is not a worthwhile tweak.
Do C-States cause stutter?
Very rarely on current hardware, because state transitions take microseconds. If you have genuine stutter, background software, drivers, shader compilation, and thermal throttling are far more likely causes and worth investigating first.
Bottom Line
Disabling CPU C-States is an old tweak that modern hardware has largely outgrown. The wake latency is negligible, and forcing cores awake can cut into the boost headroom that actually drives gaming performance. Use a high-performance Windows power plan instead, and leave C-States enabled unless you are doing serious latency tuning or overclocking, in which case disable only the deepest states and test carefully.
