I5-9600K is running at 1.9 GHz despite a base clock of 3.7 GHz.
I5-9600K is running at 1.9 GHz despite a base clock of 3.7 GHz.
angerous. I noticed a reading of 1.91 GHz, which caught me off guard. I wondered if the processor could actually underclock below its base frequency or if this was just an inaccurate measurement. This was unexpected since I hadn’t seen it drop below 4.6 GHz before.
TheMiniKins
04-21-2018, 11:45 AM #1I opened my task manager and checked the CPU clock while playing Eliteangerous. I noticed a reading of 1.91 GHz, which caught me off guard. I wondered if the processor could actually underclock below its base frequency or if this was just an inaccurate measurement. This was unexpected since I hadn’t seen it drop below 4.6 GHz before.
kungfutyla
04-24-2018, 06:13 AM #4When the CPU is idle or under light workloads, it lowers its clock speed automatically to conserve energy. Did you stop the game and then check Task Manager or monitor performance? Consider using MSI Afterburner and Rivatuner Statistic Server to track your CPU and GPU usage during gameplay, then share the results.
_KaikyRPG_
04-24-2018, 10:03 AM #5These CPUs slow down at idle, often dropping below the base frequency. They briefly pause—if they don’t then something’s amiss—and quickly jump back up to increase speed when under load. If you manually adjust the settings, you can turn off speedstep or similar features so it doesn’t happen. This helps with stability during testing of your ideal clock speed, but whether you do it matters for personal comfort and how your board handles fluctuating clocks and voltages after the stock levels.
DontQuestionM3
04-26-2018, 12:55 AM #6I followed hwinfo64's advice and each core matched the task manager's speed. @Void Master I didn't pause the game, which surprised me, but after checking, the CPU clock was about 4.3 during play and likely entered low performance mode when I closed the window. Thanks for the tips—I was just underclocking while not looking at the game window, something I hadn't noticed before. @Zando Bob, I didn’t turn off this feature when trying to overclock; I got stable at 5.15, but after a stress test it crashed.