No, nothing like this at all. I always try to minimize running background programs, especially while gaming.
I've already have the latest.
Some games have stutters/unexplainable drops, and I always try to do everything to avoid it. One of my fear is (maybe absolutely nonsense) that when the CPU is return from a deeper C-State to C0 it may cause microstutter in games.
View attachment 134267
These are my settings in BIOS, everything at default. Should I set long and short duration to a higher value, than 91W?
I have found that section you're talking about (click on Sensors and scroll down). But what should I see? These informations tell me nothing :/
Game stutters are quite the complex and annoying issue. The causes can be very diverse, ranging from the rather common and easily fixable Standby Cache problem in later Windows 10 builds, to reports that CFG (Control Flow Guard in Windows Defender) causes some of the problems, to engines that are basically defective (Batman Arkham Knight for example, the game famously stutters quite heavily especially when driving, Digital Foundry has a video on it), to engines that are very demanding on hardware (AC Odyssey can be hardcore on the CPU especially in populated areas, the 8700K can spike to 100% with ease with just a 1070ti @1080p Ultra), to games that were released quite unoptimized and with features that are not working well (Metro Exodus comes to mind; i was never able to make it run without stutters, even though I can maintain 90-100 fps in most areas at Ultra settings; some have blamed Hairworks and PhysX, and while turning them off alleviates the issue a bit, it never fully goes away).
At the same time, there are games that run nearly flawlessly. Strange Brigade, for example, is a great showcase of what Vulkan can achieve. Overwatch is a great example of esports optimization. DOOM 2016 runs beautifully.
To complicate things further, all depends on your particular setup. At one point, I started experiencing periodic frame drops each minute, with regularity. It drove me mad for a day or two. Then I discovered a new Windows theme set the desktop wallpaper to change every minute - and each change was accompanied by an ingame frametime spike. It's that easy to break a game engine.
So your stuttering might, or might not be related to the CPU, but I would suspect it is not. Also, inside a game, the CPU should pretty much be stuck at its boost clocks, with rare exceptions like a cutscene. You should make a habit from monitoring and logging your game sessions. MSI AB/RTSS and HWinfo64 and indispensable tools.
Now, for the BIOS settings.
Before you do anything, run a torture test and see if you cap at 91W. Package Power should be visible in HWinfo. Even if you remove/increase the power caps in BIOS, it will likely not change your gaming experience, as you will not reach 91W when gaming on the 4 core CPU at default settings. Most games will hover around 30-50W, with rare spikes into the 60-80W range. The power cap will only get rid of power throttling under stresstesting, basically.
As for that section in HWinfo, it says a lot of things. It shows you what is the limiting factor for the CPU clocks. On my image, you can see Max Turbo Limit and Turbo Attenuation as "Yes". That is basically saying that the CPU is idling and not boosting to max multiplier, and also that it respects a turbo bin set in BIOS. If I would start a stress test, it would boost to 4.3GHz and the Turbo Attenuation will be on No, but Max Turbo Limit will still be there as the CPU will be restricted by the all core 43x multi which is the default setting. If I cap the Powers to 95W, I would get power throttling, which would result in the RING/IA: Package-Level RAPL settings switching to Yes. IA are the cores, Ring is the uncore, and GT is the iGPU.
TLDR: your stuttering will probably be difficult to troubleshoot, and probably you should open a separate topic for that, and the CPU should not have cores going into power saving C states while inside games. There is a C-State residency section in HWinfo64 to monitor that too, seems to go from C7 to C3 to C0 for me, C7 is idling, and C0 is triggered when I launch a stresstest. Not all games result in significant usage of the C0 state for me. Trine 4 barely uses the CPU, but AC Odyssey is quite stressful.
You'll have to kind of discover all these things through testing and monitoring.
