If you have an AMD CPU, you might want to turn on this feature in BIOS

I have ZERO stutters on my 9800X3d so i guess this is not a issue

My 14700K has stutters even in low end games though. Every game has "minor" stutters. Drivers me mad
 
Looks like it depends on the MOBO:

"Auto setting to either Enabled or Disabled will be heavily dependent on the motherboard manufacturers implementation of the UEFI.

For the record, I haven't had any issues with ASUS with a 7950X3D with a 5080 in my HTPC in regards to this. I have however had issues with ASUS implementation of AMP, needing to ensure I use the full AMP profile rather than ASUS 'tweaked' versions of it to remove any performance issues I've had."
 
so, how much you wanna bet that this does actually nothing in particular, but it's one of those cases where people play a game, have shader stutters, change a setting, and the stutters are gone the second time?
then they of course attribute the improvement to the setting they changed, even tho it's simply the case that the shaders are now compiled, which means the stutters would have been gone either way
 
Last edited:
Wouldnt always enabling c-states have the opposite effect? Doesnt that just kind of put your pc into a low power state when idle? It's for power saving. Wouldn't disabling it be the way to potentially reduce stutter and reduce potential latency, not enabling it? Though I suppose that may be case by case since completely disabling could cause overheating in some systems since it would always be working at max power.

Someone correct me if I'm talking crazy please.
 
Last edited:
Weird that this would be off by default, as it is a power saving thing. So enabling it would then have the system be able to power down cores that weren't needed, right? I may be thinking of this wrong, I'm no expert. Odd that having this off, meaning your cores would be getting full power all the time, would cause stuttering, you'd think if anything it would be the other way around.

Anyhoo, on my 7800X3D I don't notice any egregious stuttering but it's worth a shot just to see what would happen if I turned it on, thanks for the post Gonzito Gonzito
 
kevboard said:
so, how much you wanna bet that this does actually nothing in particular, but it's one of those cases where people play a game, have shader stutters, change a setting, and the stutters are gone the second time?
then they of course attribute the improvement to the setting they changed, even tho it's simply the case that the shaders are now compiled, which means the stutters would have been gone either way
Click to expand...

Wrong. I had consistent stuttering in every session playing Dune. Now I dont have. This is the reason why I have made this post
 
Gonzito said:
Wrong. I had consistent stuttering in every session playing Dune. Now I dont have. This is the reason why I have made this post
Click to expand...

well, that's weird. because afaik all that this setting does is letting your CPU go into a low power mode when it detects that its full power isn't needed. it essentially will power down cpu cores that it detected as idling.
so in theory, turning this off should improve performance, not the other way around.
 
Yeah, it took me some playing around with AMD MB and software to get all my PC build issues sorted; at the time, it was driving me crazy. Now works like a dream all round without a single care in the world.

Good of you to post this in case others are having issues or are not familiar with the pain of these growing pains.
 
kevboard said:
well, that's weird. because afaik all that this setting does is letting your CPU go into a low power mode when it detects that its full power isn't needed. it essentially will power down cpu cores that it detected as idling.
so in theory, turning this off should improve performance, not the other way around.
Click to expand...

Papito I dont know, I am not Bill Gates. All I can tell you is that my experience in Dune has improved and I have a 7800X3D.

You can try and see if its worth it, many users are reporting that it works. I think it's worth trying
 
kevboard said:
well, that's weird. because afaik all that this setting does is letting your CPU go into a low power mode when it detects that its full power isn't needed. it essentially will power down cpu cores that it detected as idling.
so in theory, turning this off should improve performance, not the other way around.
Click to expand...
it could be legit this time around
these new AMD CPUs are too damn tight. they really rely on all kinds of settings left at default for them to properly work. and if those defaults are changed or broken, maybe CPU scheduler behaves unexpectedly
i mean imagine, if you uninstall game bar (not that you should) you have a great chance to ruin the gaming performance of certain AMD CPUs because they rely on game bar to detect a game as a "game" to ensure the scheduler only assigns the game to a single CCD or something

it's all intertwined now. but this is not on AMD or game devs. c-states by default (auto) should've been enabled. probably bad BIOS
 
Last edited:
All this does is change power consumption on idle. Your CPU has to support it as well and has no relation to GPU performance.
 
Last edited:
kevboard said:
well, that's weird. because afaik all that this setting does is letting your CPU go into a low power mode when it detects that its full power isn't needed. it essentially will power down cpu cores that it detected as idling.
so in theory, turning this off should improve performance, not the other way around.
Click to expand...
True, and yet this is CoPilot's take:

Enabling deeper CPU C-states can at first glance sound like it would add latency and stutter—after all, cores have to "wake up" to C0 before doing work—but on high-core/high-thread chips it often does the opposite. Here's why you might see stutter go away once you turn C-states back on:

  1. Power-Budget & Turbo Behavior • Modern Intel/AMD CPUs share a limited power/thermal budget across all cores. If C-states are disabled, every core—and the uncore (memory controller, IO)—stays in a high-power state even when idle. That constant draw can push VRMs/VRMs into thermal or current-limit throttling, causing momentary voltage droops under load and introducing frame-time spikes when the GPU/CPU fight for power headroom. Enabling C-states lets idle cores drop out of the budget, freeing headroom for active threads and smoothing out those micro-voltage sags.
  2. Thermal Equilibrium & Package Temperature • High-thread counts generate more heat overall. With C-states off, you're simply dumping more watts into the package even during "downtime," raising sustained temps. Higher temps = tighter thermal control = more abrupt turbo cutbacks when you suddenly need all 16 cores. Letting unused cores sleep keeps the average die temp lower, so bursts of activity sustain higher clocks for longer.
  3. OS Scheduler & Idle-Loop Efficiency • Many OS kernels detect C-state support and adjust their idle-loop strategy accordingly. If C-states are disabled but the kernel thinks they're available, you can end up with a mis-matched idle policy that either spins too much (wasting power and introducing jitter) or parks threads inefficiently, causing wake-up latency right when a core switch is needed for your game's physics/audio workload.
  4. Uncore/Interconnect Noise • C-states don't just gate cores—they can throttle ring/interconnect/link speeds when idle. On big chips the uncore noise (latency/bandwidth variability) can actually decrease when C-states are allowed, because the interconnect PLLs stay locked at a stable, lower-power idle frequency instead of running flat-out or being forcibly held in a high-latency "wake up" oscillation.
  5. Vendor-Specific Behavior • Some BIOS or EC firmwares have bugs or omissions that mishandle turbo and C-state interplay. In certain 16-core+ motherboards, disabling C-states inadvertently disables proper per-core turbo override, effectively locking the CPU at a modest all-core clock and causing stutters under uneven load. Re-enabling C-states can "unlock" that per-core turbo stacking.
In short, while disabling C-states shouldn't theoretically change performance or stuttering in a perfect world[1], on real hardware it often does—by cleaning up power delivery, thermal headroom, OS idle behavior and turbo coordination.
 
crackajack said:
haha, a reddit post where already someone complained that it was linking to another reddit post which was a youtube video.

Click to expand...

NjSO.gif
 
You must log in or register to reply here.

Similar threads

Guys, you have to see this!
25
229
Liopleurodon replied
AMD Ryzen 9 9950X3D CPU Review Thread
2
61
4K
winjer replied
My 14th gen Intel CPU has degraded, time to switch to AMD i guess
Community Hardware  2
55
830
manfestival replied
Former FFXI players, you may want to consider logging on
2
68
714
Pejo replied
Cities: Skylines now has a subscription base to access DLC if you don't want to buy it
10
66
Spukc replied
Top Bottom