Should You Disable C-States for Gaming? (Honest Answer)

Published

On this page

Disabling CPU C-states is one of the most-repeated “gaming BIOS tweaks,” but it’s also one of the most misunderstood. The honest answer for most gamers is leave them on Auto — and on many modern CPUs, disabling them can actually cost you performance. This guide explains what C-states do, when turning them off genuinely helps, and how to test it properly instead of cargo-culting a setting.

Should You Disable C-States for Gaming? (Honest Answer)

What C-states actually do

C-states are CPU idle power states. When a core has nothing to do, it steps down through progressively deeper sleep states to save power and heat:

  • C0 — active, executing instructions
  • C1 / C1E — halted, clocks and voltage reduced (light sleep)
  • C2–C10 — progressively deeper sleep; more of the core powers down, wake latency rises

The deeper the state, the more power saved but the longer it takes to wake back to C0. The theory behind disabling them: if cores never sleep, they never pay that wake-up latency, so response is more consistent.

In practice, the wake latency on modern chips is measured in microseconds, and Windows plus the CPU’s own governors handle transitions well. For the vast majority of systems, you will never feel it in a game.

When disabling C-states can help

There are real, narrow cases where it’s worth testing:

  • You’ve run LatencyMon and see DPC/ISR latency spikes that line up with cores dropping to idle.
  • You get micro-stutter or brief hitches during light-load moments (menus, lulls in a match) that smooth out under sustained load.
  • You’re chasing the last few percent of frame-time consistency on a competitive setup and have already done the higher-impact fixes.

If none of those describe you, disabling C-states is very unlikely to change anything you can perceive.

The catch: it can lower your boost clocks

This is the part most “disable C-states” guides skip. Modern CPUs — especially AMD Ryzen and recent Intel chips — raise single-core boost by keeping other cores in deep sleep to stay inside their power and thermal budget. Force every core awake by disabling C-states and the chip may:

  • boost lower on the active cores
  • run hotter at idle and under load
  • draw more power for no gaming benefit

In lightly-threaded games that lean on one or two fast cores, that can mean fewer FPS, not more. So this is a genuine trade-off, not a free win.

How to change C-states in the BIOS

The exact wording varies by motherboard:

  1. Reboot and enter the BIOS/UEFI (Del or F2 on most boards).
  2. Look under Advanced → CPU Configuration or the AI Tweaker / OC menu.
  3. Find CPU C-states, Global C-state Control (AMD), C-States Control, or Package C State Limit (Intel).
  4. Set it to Disabled to force cores awake, or leave Auto/Enabled for default behavior.
  5. Save and exit.

To disable only the deepest states while keeping light idle, some boards let you set a Package C State Limit to C1 or C2 instead of fully off — a milder change worth trying first.

Test it — don’t assume it

Treat this like any other tweak: measure before and after, change one thing at a time.

  1. Benchmark a repeatable scenario and record your 1% lows and average FPS — see Testing PC Components Using Benchmarking Tools.
  2. Optionally run LatencyMon idle and in-game to check DPC latency.
  3. Change the C-state setting, reboot, and run the exact same test.
  4. Keep the setting only if your 1% lows or latency genuinely improved. If FPS dropped or nothing changed, set it back to Auto.

Fixes that beat C-states for input lag

Before touching C-states, these move the needle far more on latency and smoothness:

Bottom line: leave C-states on Auto unless you’ve measured a real idle-transition problem. On modern CPUs the wake latency is tiny and disabling them can lower your boost clocks — so if you try it, benchmark your 1% lows and keep the change only if it actually helped. The bigger latency wins are timer resolution, Reflex/Anti-Lag, and a clean FPS cap.

Frequently asked questions

Should I disable C-states for gaming?

For most people, no — leave them on Auto. C-states let idle CPU cores drop into low-power sleep, and modern Windows plus the CPU wake them fast enough that you won't feel it. Only consider disabling them if you measure real DPC latency spikes or micro-stutter that tracks with cores idling. On many Ryzen and Intel chips, disabling C-states also lowers peak single-core boost, so you can lose FPS by turning them off.

Does disabling C-states reduce input lag?

It can shave a tiny amount of wake-from-idle latency because cores never go to sleep, but the effect is very small and usually invisible in-game. Real input-lag wins come from a fine timer resolution, NVIDIA Reflex or Anti-Lag, an FPS cap below your refresh rate, and disabling MPO or fixing DPC latency. Try those first — they matter far more than C-states.

Will disabling C-states hurt my CPU boost clocks?

It can. Many modern CPUs raise single-core boost by keeping other cores in deep sleep to stay within thermal and power limits. If you force every core awake by disabling C-states, the chip may boost lower and run hotter, which can cost you FPS in lightly-threaded games. This is why disabling C-states is not a guaranteed win and should be tested, not assumed.

What is C1E and should I turn it off?

C1E (Enhanced Halt) is a light idle state that drops core voltage and clock when the CPU is briefly idle. It's the mildest C-state and rarely causes gaming problems, so leaving it enabled is fine for almost everyone. Disabling C1E specifically is only worth trying if you've confirmed idle-transition stutter with LatencyMon and want to isolate the cause.

Is it safe to disable C-states in the BIOS?

Yes, it's safe — C-states are a power-saving feature, not a stability one, so turning them off won't damage anything. The trade-offs are higher idle power draw, more heat, and possibly lower boost clocks. It's fully reversible: set the C-state option back to Auto in the BIOS and reboot to restore the default behavior.