Just wanted to make a post about broken package c states. I kinda found out, that at least for my case, they seem to be 99% related to the Intel iGPU (driver). I had a good talk with @unclewebb about this, and he also had issues with his Intel iGPU on his desktop, and noticed, when playing around with the Intel GPU tool and toggle back and forth power settings, or disable the iGPU in device manager,the 0% package c states got resolved. This actually let me think, that my random broken package c states were also related to the Intel iGPU driver. I have actually random igfx crashes, which is the Intel GPU driver on my laptop, maybe happening 2-5 times per months or more. I just noticed by accident, that when it happened last time, it caused a 0% package c state for me, until Windows reboot. So I have the theory now, whenever or at least with high chance (cant proof so far it happens always), Windows 10 restarts the GPU driver after it crashed, it causes the c states to break. Either this is a bug with the Intel driver, or Windows 10 that it doesnt reset the driver 100% correctly when it reloads it. This actually all got to me, after I reported a bug I found a months ago in Chrome and reported it to the Chromium team. Actually I knew this bug existed over 1-2 years now, but I was always too lazy so far to report it. Here is the bug ticket: https://bugs.chromium.org/p/chromium/issues/detail?id=1107403 Turned out, there is a bug in mostly every Intel iGPU gen6(or so I think starting from Broadwell) > <=gen9.5 which seem to be related to using swap chain for video decoding. Just read the bug ticket if youre interested in it. As I see it, it doesnt happen just in Chrome but every app which uses a swap chain for decoding, maybe even Windows 10 itself, and the driver doesnt seem to be stable when you push it with high memory change. You can actually fix this with a simple workaround for Chrome by starting Chrome with "--disable-features=DirectCompositionUseNV12DecodeSwapChain" and then check in chrome://gpu that it is disabled . Everyone using a laptop and having a <=UHD630 and using Chrome or Edge should do this until the workaround of disabling the swap chain gets live. I dont think that is true. What is reported is correct. As I see it, there is nearly no difference between c8 and c10 in idle when laptop is on, at least for me. Either 80% c8 or 30% c10 are kinda identical, for power drain. Also for me, C10 just works with laptop powered on, when I remove the power cable and am on battery. @unclewebb implemented a handy new feature in latest TS to debug c8 and c10 usage during modern standby and it will show the time it was in c8 and c10 for the last modern standby sleep.