F5F Stay Refreshed Power Users Overclocking The CPU multiplier remains fixed at x39

The CPU multiplier remains fixed at x39

The CPU multiplier remains fixed at x39

K
Killa_Dx
Senior Member
645
03-16-2016, 01:52 AM
#1
Hi All,
I'm working on overclocking my i7 6700K and CPU-Z reports:
Core Speed: 3900.00 MHz
Multiplier: x 39 (8 - 45)
Bus Speed: 100.00 MHz
Updated BIOS OC profile to XMP, kept CPU BCLK at 100 and cores at 45 for 4.5 OC. Still stuck at x39 with no change in core speed from 3900, even after stress tests. Also tried enabling both SpeedStep and Turbo, plus disabling them, but nothing worked. Any advice would be great. Thanks.
K
Killa_Dx
03-16-2016, 01:52 AM #1

Hi All,
I'm working on overclocking my i7 6700K and CPU-Z reports:
Core Speed: 3900.00 MHz
Multiplier: x 39 (8 - 45)
Bus Speed: 100.00 MHz
Updated BIOS OC profile to XMP, kept CPU BCLK at 100 and cores at 45 for 4.5 OC. Still stuck at x39 with no change in core speed from 3900, even after stress tests. Also tried enabling both SpeedStep and Turbo, plus disabling them, but nothing worked. Any advice would be great. Thanks.

J
JebThePleb
Posting Freak
898
03-16-2016, 02:25 AM
#2
I'm just a quick question—what is your Windows power plan?
J
JebThePleb
03-16-2016, 02:25 AM #2

I'm just a quick question—what is your Windows power plan?

X
XxGrenidierXx
Posting Freak
813
03-16-2016, 03:44 AM
#3
I'm just a quick question—what is your Windows power plan?
X
XxGrenidierXx
03-16-2016, 03:44 AM #3

I'm just a quick question—what is your Windows power plan?

A
Andreasx345
Member
178
03-26-2016, 08:01 AM
#4
The solution to my problem is confirmed. My 'Maximum Processor State' was incorrectly set to 99, but after adjusting it to 100, everything functions correctly.
A
Andreasx345
03-26-2016, 08:01 AM #4

The solution to my problem is confirmed. My 'Maximum Processor State' was incorrectly set to 99, but after adjusting it to 100, everything functions correctly.

F
FreeZi_78
Junior Member
10
03-26-2016, 09:15 AM
#5
It's curious that the right setting wasn't the cause. I assumed you'd activated Power Saving mode. But it seems the issue was resolved. Happy to assist.
F
FreeZi_78
03-26-2016, 09:15 AM #5

It's curious that the right setting wasn't the cause. I assumed you'd activated Power Saving mode. But it seems the issue was resolved. Happy to assist.