F5F Stay Refreshed Power Users Overclocking overclock works in bios but fails on desktop

overclock works in bios but fails on desktop

overclock works in bios but fails on desktop

B
Blureux
Posting Freak
797
12-18-2016, 04:24 AM
#1
I'm dealing with a strange issue and need assistance. My computer had a weird problem, so I tried increasing the clock speed for years, but it only saved the change. When I went to my desktop, it stayed at 4.3GHz instead of what I set before. I thought it was a dead battery and not saving properly, so I changed it out and it returned to the original setting. Now in the BIOS it shows 4.3GHz, but when I load into Windows and check, it's still at 3.7GHz. I own an i5 2500K with an ASUS motherboard, which failed and I replaced it with an ASRock Z75.
B
Blureux
12-18-2016, 04:24 AM #1

I'm dealing with a strange issue and need assistance. My computer had a weird problem, so I tried increasing the clock speed for years, but it only saved the change. When I went to my desktop, it stayed at 4.3GHz instead of what I set before. I thought it was a dead battery and not saving properly, so I changed it out and it returned to the original setting. Now in the BIOS it shows 4.3GHz, but when I load into Windows and check, it's still at 3.7GHz. I own an i5 2500K with an ASUS motherboard, which failed and I replaced it with an ASRock Z75.

M
MatthewW2005
Member
63
12-18-2016, 07:29 PM
#2
It's normal for Windows to show only a nominal frequency or the time of installation. Many programs can reveal what processes are active.
Also remember that during the update, power-saving features were left enabled, so the CPU operated at a reduced speed until it was fully loaded.
M
MatthewW2005
12-18-2016, 07:29 PM #2

It's normal for Windows to show only a nominal frequency or the time of installation. Many programs can reveal what processes are active.
Also remember that during the update, power-saving features were left enabled, so the CPU operated at a reduced speed until it was fully loaded.

T
TOMMYCRAFT05
Member
124
12-26-2016, 06:03 AM
#3
CountMike shared some insights about Windows reporting frequency. He mentioned that it's common for Windows to show just a nominal value or frequency at installation time, and there are many programs available to check what's actually running. He also noted that during the boot process, the CPU would run at a lower frequency until fully loaded, and he uses tools like hwmonitor and cpuz to verify this behavior. Additionally, he mentioned having power-saving features enabled on his system.
T
TOMMYCRAFT05
12-26-2016, 06:03 AM #3

CountMike shared some insights about Windows reporting frequency. He mentioned that it's common for Windows to show just a nominal value or frequency at installation time, and there are many programs available to check what's actually running. He also noted that during the boot process, the CPU would run at a lower frequency until fully loaded, and he uses tools like hwmonitor and cpuz to verify this behavior. Additionally, he mentioned having power-saving features enabled on his system.