should global c-state be "enabled" instead of auto on am5 x3d processors?

[squallypo]

hello there, i recently came across this thread over reddit https://www.reddit.com/r/pcmasterrace/comments/1igmb6f/am5_cpu_stutter_fix/?share_id=cLCtMOD36Doud0T...
in which this guy affirms that having global c-state on "auto" on the motherboard for am5 processors its pretty much having it as "off or disabled"
where you should instead be setting it as "enabled" for it to reduce or eliminate any performance issues that your computer may be having with micro stuttering related.

is this accurate? what does global c-state even do anyways?

im on ryzen 7800x3d, x670e aorus pro motherboard, and at the moment its set on auto but if what he says its true, then i should set it to enable ?
ive noticed a few micro stuttering in dead by daylight, cyberpunk 2077.

thanks for your time.

 

[R-T-B]

c-states are a power saving option. Honestly, disabling them should not be causing stutter.

 

[squallypo]

c-states are a power saving option. Honestly, disabling them should not be causing stutter.

yeah i wish i knew more of the topic but i really dont, i just found interesting how this could be causing a micro stuttering issue.
so setting it on, makes the general pc performance lower?

Update on Ryzen 7000 C-State Boost Limiter - SkatterBencher

AGESA 1003 re-introduces Precision Boost C-State Boost Limiter which prevents boosting to over 5.5 GHz when more than 4 cores are active

skatterbencher.com

i also found this article, speaks a bit of c-states and how it should be "enabled" as well.

 

[ShrimpBrime]

Auto = Enabled. Should be no change between them.

Disabled will run the cores at their rated speeds without throttling when in lower power states.

 

[squallypo]

Auto = Enabled. Should be no change between them.

Disabled will run the cores at their rated speeds without throttling when in lower power states.

is there a reason why he claims that auto = disabled ?

 

[R-T-B]

so setting it on, makes the general pc performance lower?

Not really, no. Disabling it just make it use more power at idle for no reason twiddling its thunbs. But it shouldn't hurt anything either.

is there a reason why he claims that auto = disabled ?

I'm skeptical of that as well, unless its like a one board or brand firmware glitch.

Disabled will run the cores at their rated speeds without throttling when in lower power states.

Actually clock control is a seperate thing. This is more of a "can I sleep/turn off a core short-term when I have literally nothing to do?" setting.

 

[squallypo]

Not really, no. Disabling it just make it use more power at idle for no reason twiddling its thunbs. But it shouldn't hurt anything either.


I'm skeptical of that as well, unless its like a one board or brand firmware glitch.


Actually clock control is a seperate thing. This is more of a "can I sleep/turn off a core short-term when I have literally nothing to do?" setting.

so to summarize:
auto should be fine just as enable should be fine, since auto should be = "enabled" pretty much
yeah i dont understand this person logic with auto = disabled really, he prolly has a glitchy firmware/bios from his motherboard but apparently other persons have been trying this and has worked out for them, i honestly cant say from personal experience as ive had it default which is auto, i did wanted to test this out because i wanted to know if this would help with the micro stuttering in dead by daylight, cyberpunk 2077.