the i5-4690k does not allow overclocking
the i5-4690k does not allow overclocking
Well, it seems Linux isn't working well with this setup. Running Windows in VirtualBox appears to hide key details from HWiNFO32. I'm missing the Overclocking information entirely, and it doesn't show up at all inside VirtualBox. Next, I might install Windows directly, which will take some time. After that, I can try HWiNFO again for a clearer list. I could also use RB or test the AI Suite to see if it helps. Please wait while I attempt to fix my Linux installation and get Windows running...
Now that things are clearer after further testing, I had to acquire an extra SSD and perform an isolated installation to safeguard my Linux images. Once the usual troubleshooting was done, I adjusted the BIOS settings back to default and opened HWiNFO32. Everything seemed normal:
[Operating Points]
CPU LFM (Minimum): 800.0 MHz = 8 x 100.0 MHz
CPU HFM (Maximum): 3500.0 MHz = 35 x 100.0 MHz
CPU Turbo: 3900.0 MHz = 39 x 100.0 MHz [Unlocked]
CPU Current: 3597.8 MHz = 36 x 99.9 MHz @ 1.0024 V
Uncore Maximum: 3900.0 MHz = 39.00 x 100.0 MHz
Uncore Current: 3497.9 MHz = 35.00 x 99.9 MHz
The previously observed "locked" issue disappeared, and I now understand it stemmed from VirtualBox managing the CPU allocation for the VM. A simple BIOS reset to 42 multipliers and a voltage adjustment of 1.25v, followed by another HWiNFO32 scan, resolved it:
[Operating Points]
CPU LFM (Minimum): 800.0 MHz = 8 x 100.0 MHz
CPU HFM (Maximum): 3500.0 MHz = 35 x 100.0 MHz
CPU Turbo: 4200.0 MHz = 42 x 100.0 MHz [Unlocked]
CPU Current: 3699.9 MHz = 37 x 100.0 MHz @ 1.0270 V
Uncore Maximum: 3900.0 MHz = 39.00 x 100.0 MHz
Uncore Current: 3899.9 MHz = 39.00 x 100.0 MHz
This was the first time I encountered a value outside 3500, which pointed me to the OS being the cause, as everything behaved correctly under Windows 7. I’ve since learned that CPU frequency scaling in Linux is highly regulated and depends on the processor type. Many monitoring tools only display rated speeds rather than actual performance.
I added overclocking utilities from Intel and extra probes/sensors, which now confirmed a stable 4200 MHz under stress. I also discovered methods to adjust the frequency scaling governor for needs like performance or power efficiency, allowing me to customize steps during scaling—such as changing the top step from 3500 to 4200.
Thank you very much for your assistance—your guidance was exactly what I needed to fine-tune the settings and improve daily speed.