Hellbovine
Well-Known Member
In my optimized image guide I have a whole .reg file dedicated only to power plan settings. I spent a few months on just that topic, researching and thoroughly tearing apart the registry tree for power plans and learning it inside out. There are 142 total keys I think it is offhand, and I turned off as much of the obvious power savings as possible, core parking related stuff, etcetera. My power plan is more effective than the ultimate plan plus bitsum's plans combined, but I still get the spikes from Nvidia. I'm sure it will greatly help a lot of people that are worse off though, especially people suffering from ACPI issues if they try my reg file.
I think you are on the right track for sure though, there is still a specific avenue that I left on my todo list because it was too volatile and I needed to spend more time on it, and that's handling the "idle states" of Windows. So you can straight up disable idle states entirely, however there appears to be a bug in the task manager or performance counters or something because when you do this the CPU load goes up to 100% all the time, even when idling at the desktop, and it starts to act strange. There are quite a few CPU settings to experiment with (about half of those keys are CPU keys), but there's almost no documentation on them, and it will take months of testing to figure out what they all do.
I have noticed though, that even if your CPU/GPU are under a load, such as running a game, the CPU will constantly try to downclock and enter an idle state, and this is a factor in DPC issues. I just haven't yet figured out how to safely address this. I don't want to brick people's systems by peddling something I'm not confident in.
If you want to "see" what I mean, download the TimerBench tool from overclockers.net and run the test in fullscreen at your native resolution. Then in the results take a look at the CPU Load screen. You will probably see 2-3 dips, where the CPU downclocks for brief periods of time, but this is rather devastating in a game, and absolutely is a cause of DPC, stuttering, and lower framerates.
I think you are on the right track for sure though, there is still a specific avenue that I left on my todo list because it was too volatile and I needed to spend more time on it, and that's handling the "idle states" of Windows. So you can straight up disable idle states entirely, however there appears to be a bug in the task manager or performance counters or something because when you do this the CPU load goes up to 100% all the time, even when idling at the desktop, and it starts to act strange. There are quite a few CPU settings to experiment with (about half of those keys are CPU keys), but there's almost no documentation on them, and it will take months of testing to figure out what they all do.
I have noticed though, that even if your CPU/GPU are under a load, such as running a game, the CPU will constantly try to downclock and enter an idle state, and this is a factor in DPC issues. I just haven't yet figured out how to safely address this. I don't want to brick people's systems by peddling something I'm not confident in.
If you want to "see" what I mean, download the TimerBench tool from overclockers.net and run the test in fullscreen at your native resolution. Then in the results take a look at the CPU Load screen. You will probably see 2-3 dips, where the CPU downclocks for brief periods of time, but this is rather devastating in a game, and absolutely is a cause of DPC, stuttering, and lower framerates.
Last edited:
