F5F Stay Refreshed Power Users Overclocking Does the core ratio overclocking not functioning correctly?

Does the core ratio overclocking not functioning correctly?

Does the core ratio overclocking not functioning correctly?

N
naTe_coRe_1084
Senior Member
254
06-03-2016, 01:43 PM
#1
I watched the tutorial on per core ratio overclocking:
https://youtu.be/9iEwHxcOvss
CPU: i5 4690k, motherboard: Asus z97-A
I discovered my first core could reach 4.8 GHz, the second around 4.6, and the others up to 4.5.
My current settings were:
1-core ratio limit 48
2-core ratio limit 46
3-core ratio limit 45
4-core ratio limit 45
VCORE 1.33v
Input voltage 2v
Uncore 35 min/max
I expect these settings to stay stable, but I experienced a BSOD during startup due to low voltage. My thought is that applying the 48 multiplier to one of the weaker cores might be causing the issue. Any suggestions on how to resolve this?
N
naTe_coRe_1084
06-03-2016, 01:43 PM #1

I watched the tutorial on per core ratio overclocking:
https://youtu.be/9iEwHxcOvss
CPU: i5 4690k, motherboard: Asus z97-A
I discovered my first core could reach 4.8 GHz, the second around 4.6, and the others up to 4.5.
My current settings were:
1-core ratio limit 48
2-core ratio limit 46
3-core ratio limit 45
4-core ratio limit 45
VCORE 1.33v
Input voltage 2v
Uncore 35 min/max
I expect these settings to stay stable, but I experienced a BSOD during startup due to low voltage. My thought is that applying the 48 multiplier to one of the weaker cores might be causing the issue. Any suggestions on how to resolve this?

I
IamRikyPT
Member
129
06-03-2016, 05:56 PM
#2
He recommends introducing separate clock configurations for every core just before the 12-minute mark. The X-core usage cap restricts the clocks based on the number of cores engaged, not individual core speeds. This approach prevents overclocking each core individually.
I
IamRikyPT
06-03-2016, 05:56 PM #2

He recommends introducing separate clock configurations for every core just before the 12-minute mark. The X-core usage cap restricts the clocks based on the number of cores engaged, not individual core speeds. This approach prevents overclocking each core individually.

T
TiTansio11
Member
189
06-03-2016, 06:52 PM
#3
He recommends introducing separate clock configurations for every core just before the 12-minute mark. The X-core usage cap restricts the clocks based on the number of cores engaged, not individual core speeds. This approach prevents overclocking each core individually.
T
TiTansio11
06-03-2016, 06:52 PM #3

He recommends introducing separate clock configurations for every core just before the 12-minute mark. The X-core usage cap restricts the clocks based on the number of cores engaged, not individual core speeds. This approach prevents overclocking each core individually.

S
SwagZor
Junior Member
42
06-05-2016, 09:01 AM
#4
Yeah, I was thinking about that too. Maybe it was OS stability? Or perhaps he didn't crash while recording the video.
S
SwagZor
06-05-2016, 09:01 AM #4

Yeah, I was thinking about that too. Maybe it was OS stability? Or perhaps he didn't crash while recording the video.