F5F Stay Refreshed Power Users Overclocking Operating smoothly at the x37 ratio even after being pushed to x43

Operating smoothly at the x37 ratio even after being pushed to x43

Operating smoothly at the x37 ratio even after being pushed to x43

T
ThatMiningGuy
Senior Member
Find
704
10-16-2016, 11:37 AM
#1
Hi everyone! I have an I5-4690k, and an Asrock pro4 H97 motherboard.
Before I start off, yes, I am aware that the H97 chipset cannot overclock in the bios. But there is an Asrock tuning utility app which lets you overclock. I used the "auto" feature (or something like that) and it set it to x43 for the ratio and x39 for the cache ratio. Basically, on CPU-Z, it displays that it is running at x37, and in parenthesis "(x8-x43)". I've played high-demanding games while watching and it always remains at x37. I disabled SpeedStep in the bios, but no change. Task manager says its running at 3.5GHz (stock speed).
I know the H97 chipset doesn't overclock thru the BIOS, but is that the reason I run at the stock ratio (x37) even when CPU-Z says it can go up to x43 (which I overclocked to)?
Any help is appreciated!
Reply
Reply
T
ThatMiningGuy
10-16-2016, 11:37 AM #1

Hi everyone! I have an I5-4690k, and an Asrock pro4 H97 motherboard.
Before I start off, yes, I am aware that the H97 chipset cannot overclock in the bios. But there is an Asrock tuning utility app which lets you overclock. I used the "auto" feature (or something like that) and it set it to x43 for the ratio and x39 for the cache ratio. Basically, on CPU-Z, it displays that it is running at x37, and in parenthesis "(x8-x43)". I've played high-demanding games while watching and it always remains at x37. I disabled SpeedStep in the bios, but no change. Task manager says its running at 3.5GHz (stock speed).
I know the H97 chipset doesn't overclock thru the BIOS, but is that the reason I run at the stock ratio (x37) even when CPU-Z says it can go up to x43 (which I overclocked to)?
Any help is appreciated!

Reply
Reply
C
Camshi356
Junior Member
Find
45
10-26-2016, 05:42 PM
#2
Yes, that is why. Have you updated the board's BIOS to the latest? Some manufacturers have found a way to get around Intel's limitation with a BIOS fix. But it sounds like you are stuck at x37 until you get a new board.
Reply
Reply
C
Camshi356
10-26-2016, 05:42 PM #2

Yes, that is why. Have you updated the board's BIOS to the latest? Some manufacturers have found a way to get around Intel's limitation with a BIOS fix. But it sounds like you are stuck at x37 until you get a new board.

Reply
Reply
P
Polin_
Junior Member
Find
14
10-26-2016, 11:26 PM
#3
Yes, that is why. Have you updated the board's BIOS to the latest? Some manufacturers have found a way to get around Intel's limitation with a BIOS fix. But it sounds like you are stuck at x37 until you get a new board.
Reply
Reply
P
Polin_
10-26-2016, 11:26 PM #3

Yes, that is why. Have you updated the board's BIOS to the latest? Some manufacturers have found a way to get around Intel's limitation with a BIOS fix. But it sounds like you are stuck at x37 until you get a new board.

Reply
Reply
T
Trentqn
Member
Find
150
11-07-2016, 11:35 AM
#4
Yes, that's the reason. Have you made sure the board's BIOS is updated to the latest version? Some makers have discovered a workaround for Intel's restriction using a BIOS patch. It seems you're still stuck at x37 until a replacement board arrives.

Ah, good to hear. The problem was likely with the chipset or a setting I overlooked. The BIOS update should be applied. Apparently, the BIOS-overclocking option was present in earlier versions but removed after Windows 10 was released. I've been told that updating the BIOS might conflict with Windows 10, so I'll have to wait for a new board.

Thanks for the advice!
Reply
Reply
T
Trentqn
11-07-2016, 11:35 AM #4

Yes, that's the reason. Have you made sure the board's BIOS is updated to the latest version? Some makers have discovered a workaround for Intel's restriction using a BIOS patch. It seems you're still stuck at x37 until a replacement board arrives.

Ah, good to hear. The problem was likely with the chipset or a setting I overlooked. The BIOS update should be applied. Apparently, the BIOS-overclocking option was present in earlier versions but removed after Windows 10 was released. I've been told that updating the BIOS might conflict with Windows 10, so I'll have to wait for a new board.

Thanks for the advice!

Reply
Reply