Should you disable C-States for gaming?

10 September 2026, updated 18 September 2026 · ~4 min read

"Should I disable C-States?" Short answer: on any CPU built in roughly the last decade, no. Disabling C-states doesn't meaningfully lower latency in normal gaming, and on documented real systems it's actively stopped the CPU from boosting properly — leaving you with more heat, more power draw, and equal or worse real-world performance. Here's why, the narrow case where it genuinely applies, and what to optimize instead for a real gain. For what actually does boost FPS on Windows 10 and 11, see our full FPS guide, and for the wider picture on registry-level tweaks like this one, see our Windows 11 registry tweaks guide.

This guide is one part of our full PC optimization checklist for gaming. To properly optimize a PC for gaming, you need to work through every real lever once: optimize background processes, optimize GPU driver settings, optimize CPU and device affinity, optimize RAM and storage, optimize your network, and optimize your display settings, each in the order that actually moves the needle on a real PC, not six separate half-remembered tips picked at random. Whichever topic brought you to this specific guide, the full PC optimization checklist is the fastest, most reliable way to optimize the rest of your PC too.

What C-States actually are

A CPU doesn't run every core flat out all the time. When a core has nothing to do, it drops into a low-power idle state — a "C-state." C1 is a light doze; deeper states (C3, C6, and beyond) progressively shut more of the core down to save power and heat. The instant work arrives, the core wakes back up.

"Disabling C-states" means forcing every core to stay fully powered at all times, even while doing nothing.

The "lower latency" claim

The usual argument for turning them off: waking a sleeping core takes time, so a core that never sleeps responds instantly.

That was a real concern fifteen-plus years ago. On modern hardware it mostly isn't. C-state exit latency is measured in microseconds — millionths of a second, typically under 1µs for a light C1 doze, up to roughly 50-150µs (plus a cache-cold-reload penalty on top) for a deep C6 wake. For scale, one frame at 60 FPS is about 16,600 microseconds; at 144 FPS it's about 6,900. Even the deepest case is a small fraction of a single frame, well below what's perceptible in normal gaming. The one narrow exception, covered below, is real-time work sensitive to scheduling jitter at a much finer grain than frame time.

Where disabling them actively backfires

This is the part most "gaming tweaks" lists leave out. On documented real systems, C-states aren't just harmless — they've been shown required for the CPU to reach its rated speed:

• Intel (documented example, not a universal rule): one measured, reported case on an i5-6600, a non-K chip on a non-Z board — disabling C-states in BIOS dropped its boost clock from 3.86GHz to 3.56GHz. That's a real, reproducible-on-that-system effect, not the flat "stuck at base clock" some tweak lists claim — and we can't point to Intel's own documentation establishing the exact mechanism behind it, so treat this as "it happened on this system, worth checking on yours," not a rule for every non-K Intel CPU.
• AMD Ryzen (documented example, mechanism not publicly confirmed): controlled testing on a Ryzen 7000 part found disabling Global C-State Control capped boost at 5.5GHz, a real, measured effect AMD's own board partners refer to as a "C-State Boost Limiter." What we won't do is assert a specific internal mechanism for it — the source measures the effect, not why it happens, so we're reporting exactly that and no more. Worth naming what this isn't, since it gets confused often: it's not "clock stretching," a real but separate AMD safety mechanism (a voltage-droop protection that fires under sustained heavy load regardless of your C-state setting) — a different, unrelated cause some guides misattribute this to.

On any system where the boost-cap effect above applies, the net result is higher idle temperature, higher power draw, and equal or lower performance — a straight downgrade. Since the exact prevalence across all Intel/AMD hardware isn't documented, the safe default is to assume it could apply to yours and check, rather than assume it doesn't.

When it might genuinely help

Narrow cases exist:

• Very old CPUs with slow P-state / C-state transitions, where wake-up really was slow enough to matter.
• Specialised real-time workloads — some pro-audio / DAW setups, certain measurement rigs — that are sensitive to any scheduling jitter and run on a machine dedicated to that one job, with cooling to match.

If you're gaming on hardware from the last several years, neither applies to you.

How to check and change it yourself

It's a power-plan setting. From an elevated Command Prompt:

powercfg /setacvalueindex scheme_current sub_processor IDLEDISABLE 1
powercfg /setactive scheme_current

IDLEDISABLE 1 turns C-states off; 0 restores them (the Windows default). No reboot needed.

Worth knowing this is specifically the Windows power-plan switch, not the same thing as turning C-States on or off in BIOS via the "Global C-State Control" (or similarly named) toggle some motherboards expose — they're two separate switches controlling the same underlying behaviour at different layers, not one setting with two names. Changing one doesn't automatically change the other.

In Wayne's GoldCore this is one of the tweaks we rate Risky and deliberately keep out of every preset — including the no-ceiling Esports preset — for exactly the reasons above. It's still available if you have a specific, tested reason to want it, with the full explanation attached, but nothing applies it to your system on your behalf.

Core Parking: a different setting, often confused with this one

Core Parking and C-states get mixed up constantly, but they're separate mechanisms. C-states are a per-core, microsecond-scale idle state a core drops into between individual instructions. Core Parking is a much coarser, whole-core decision Windows' own power plan makes to stop scheduling new threads onto a core entirely for a longer stretch, to consolidate load onto fewer active cores and let the rest drop to a deeper sleep state. Disabling Core Parking (a separate power-plan setting) is the one of the two worth testing on a desktop gaming PC; disabling C-states, as covered above, generally isn't.

Bottom line

"Disable C-states for lower latency" is one of the most repeated pieces of PC gaming advice that stopped being true over a decade ago. On modern hardware it does nothing useful and often does real harm. Leave them on. If you want measurable gains, put the effort into the things that actually move frame times — timer resolution, GPU driver settings, background process load — and confirm them with an honest before/after FPS test rather than folklore.

For the full picture, see our guide to reducing input lag on Windows 11 — the mouse, timer, CPU, GPU, network, and display fixes that actually move the needle.