in task W10 manager I can see the actual frequency. For an old i3-3220 i can see how it goes down to ~1.5 GHz (3.3 Ghz max) when idle or not doing much (just some 8-15% load). so that saves energy and cooling load.
but my i3-6100 only goes down to about 3.5 GHz, no matter how low the load (3.66 GHz max).
Is there something wrong, or is that how they are? When not much load, I'd prefer it to throttle back to save energy and cooling. I couldn't find specs on what the lower limit is (I realize most enthusiast reviews care more about max frequencies
my board is an ASRock H170M Pro 4. the UEFI settings didn't have soemthing obvious to enable throttling back.
Just to clarify, i don't want to underclock or undervolt. I just want the CPU to through its full range of clockspeeds depending on load. when i have full load, I want my fullclock speed. Just not 99% of the time.
but my i3-6100 only goes down to about 3.5 GHz, no matter how low the load (3.66 GHz max).
Is there something wrong, or is that how they are? When not much load, I'd prefer it to throttle back to save energy and cooling. I couldn't find specs on what the lower limit is (I realize most enthusiast reviews care more about max frequencies
my board is an ASRock H170M Pro 4. the UEFI settings didn't have soemthing obvious to enable throttling back.
Just to clarify, i don't want to underclock or undervolt. I just want the CPU to through its full range of clockspeeds depending on load. when i have full load, I want my fullclock speed. Just not 99% of the time.
Facebook
Twitter