F5F Stay Refreshed Hardware Desktop i7 8086k reaches 4.7ghz during testing after being overclocked to 5.2ghz

i7 8086k reaches 4.7ghz during testing after being overclocked to 5.2ghz

i7 8086k reaches 4.7ghz during testing after being overclocked to 5.2ghz

Pages (2): 1 2 Next
R
ReborntoKill
Posting Freak
821
11-20-2017, 08:23 AM
#1
i7 8086k reaches 4.7ghz during testing when overclocked to 5.2ghz. Why does this happen? When idle it maintains around 5200mhz, but under multicore tests it drops back to 4700mhz. Single-core runs stay steady at 5200mhz. It never behaved that way before—it stayed flat when running at 5400mhz the first time I had it. After a BIOS update and a CMOS reset, it can't return to stable 5400mhz. The main problem now is this instability at higher speeds. I need my full 5200mhz performance on a Z370 M Pro4 board with an ICE cooling setup (280mm front, 140mm rear, CPU and memory blocks in a tiny H17). Temperatures are around 50°C during Cinebench tests. GSKill Trident Z 4266MHz runs at 4133MHz (around 4133Hz), while my system is at 500GB NVMe SSD with WD Black 12GB. Any suggestions or help would be appreciated!
R
ReborntoKill
11-20-2017, 08:23 AM #1

i7 8086k reaches 4.7ghz during testing when overclocked to 5.2ghz. Why does this happen? When idle it maintains around 5200mhz, but under multicore tests it drops back to 4700mhz. Single-core runs stay steady at 5200mhz. It never behaved that way before—it stayed flat when running at 5400mhz the first time I had it. After a BIOS update and a CMOS reset, it can't return to stable 5400mhz. The main problem now is this instability at higher speeds. I need my full 5200mhz performance on a Z370 M Pro4 board with an ICE cooling setup (280mm front, 140mm rear, CPU and memory blocks in a tiny H17). Temperatures are around 50°C during Cinebench tests. GSKill Trident Z 4266MHz runs at 4133MHz (around 4133Hz), while my system is at 500GB NVMe SSD with WD Black 12GB. Any suggestions or help would be appreciated!

G
GodRaidYT
Member
76
11-20-2017, 08:32 AM
#2
Check if all cores run at 5.2GHz or limited to a few.
G
GodRaidYT
11-20-2017, 08:32 AM #2

Check if all cores run at 5.2GHz or limited to a few.

G
george24300
Junior Member
7
11-20-2017, 08:38 AM
#3
Adjust the AVX multiplier to 52.
G
george24300
11-20-2017, 08:38 AM #3

Adjust the AVX multiplier to 52.

C
CasperPromp
Member
64
11-22-2017, 05:16 AM
#4
That’s how it’s configured, right? The minimum cache ratio is indeed set to 52. The 4300MHz comes from somewhere else, I’m not sure what.
C
CasperPromp
11-22-2017, 05:16 AM #4

That’s how it’s configured, right? The minimum cache ratio is indeed set to 52. The 4300MHz comes from somewhere else, I’m not sure what.

A
alejandro351
Member
137
11-22-2017, 06:44 AM
#5
The note indicates the second screen shot setting uses auto mode, which will apply a default of 4.7GHz across all cores. The cache operates independently from CPU core overclocking, so avoid adjusting it now.
A
alejandro351
11-22-2017, 06:44 AM #5

The note indicates the second screen shot setting uses auto mode, which will apply a default of 4.7GHz across all cores. The cache operates independently from CPU core overclocking, so avoid adjusting it now.

R
Raulcarq1
Member
73
11-22-2017, 07:35 AM
#6
Sure, I've added 52 to the total.
R
Raulcarq1
11-22-2017, 07:35 AM #6

Sure, I've added 52 to the total.

M
My_life
Member
69
11-22-2017, 08:16 AM
#7
Only a limit of 31 allowed, but the lower value is preferable. I used 3 and the same result on Cinebench directly at version 4.7, then dropped to 4.35 during the second test phase with R23.
M
My_life
11-22-2017, 08:16 AM #7

Only a limit of 31 allowed, but the lower value is preferable. I used 3 and the same result on Cinebench directly at version 4.7, then dropped to 4.35 during the second test phase with R23.

U
UN_Zimmoww
Member
59
11-28-2017, 09:33 AM
#8
You may need to adjust your long and short turbo settings carefully. The Auto option can be confusing—use HWiNFO64 to check why throttling happens. Power limit restrictions are typical. Make sure the AVX Ratio Offset is at zero. Both turbo limits were set very high, so they won’t block peak performance.
U
UN_Zimmoww
11-28-2017, 09:33 AM #8

You may need to adjust your long and short turbo settings carefully. The Auto option can be confusing—use HWiNFO64 to check why throttling happens. Power limit restrictions are typical. Make sure the AVX Ratio Offset is at zero. Both turbo limits were set very high, so they won’t block peak performance.

X
XGigaPL
Member
172
12-19-2017, 08:45 PM
#9
You probably handled those tasks before, but you mentioned seeing numbers like 120 and 150—maybe the best you got was 150. It seems like the top one was around there. You might have used AVX around version 3, and it’s been a while since you worked with it that way. Feels like you’re starting over now.
X
XGigaPL
12-19-2017, 08:45 PM #9

You probably handled those tasks before, but you mentioned seeing numbers like 120 and 150—maybe the best you got was 150. It seems like the top one was around there. You might have used AVX around version 3, and it’s been a while since you worked with it that way. Feels like you’re starting over now.

I
iBroady
Junior Member
14
12-19-2017, 08:58 PM
#10
Renomad172 notes that 120 Watts causes significant performance caps during extended tests such as R23, and an AVX offset of 3 reduces CPU speed to 300 MHz. To achieve optimal performance, resolve these two problems.
I
iBroady
12-19-2017, 08:58 PM #10

Renomad172 notes that 120 Watts causes significant performance caps during extended tests such as R23, and an AVX offset of 3 reduces CPU speed to 300 MHz. To achieve optimal performance, resolve these two problems.

Pages (2): 1 2 Next