SOLVED Ivy bridge 3570k still unstable 0.03v past 12 hour prime test stable

[JnV]

I'm using an ivy bridge 3570k in an asus sabertooth z77, I overclocked to 46x100 and it was stable under a 12 hour prime95 torture test at 1.290v (Quite a bit higher than everyone else, apparently I have a fairly low quality CPU)

I just had a system freeze at 1.32v - I've been upping it by 0.005v every time I got a freeze assuming prime just hadn't caught the instability.

Since I'm now well above the point of "Stability" I'm assuming either I missed a setting somewhere or it's something else entirely.

I still presume it's an overclocking issue because lowering the vcore back to 1.290v makes it usually freeze before ever hitting the log in screen while higher vcores last longer (But still fairly randomly crash) and going back to stock speed I don't see any crashes.

Edit: Just got it to boot at 1.29v but I doubt it will last long, could this be caused by "Droop"?

This is my first overclock so all I've tweaked is the multiplier, the vcore, and set the vcore to fixed.

PS: I'm on linux (No idea if that little tidbit will start a flame war but I'm hoping not - I just want to get my hardware stable)

Edit: I just realised I only benched small FFTs (prime torture test default) - Lets mark this closed, I'll leave a result once I get it blend stable

Edit: Yep - seems stable at 1.335v with "Ultra high" LLC so it's about 1.34v

 

[Archer0915]

I'm using an ivy bridge 3570k in an asus sabertooth z77, I overclocked to 46x100 and it was stable under a 12 hour prime95 torture test at 1.290v (Quite a bit higher than everyone else, apparently I have a fairly low quality CPU)

I just had a system freeze at 1.32v - I've been upping it by 0.005v every time I got a freeze assuming prime just hadn't caught the instability.

Since I'm now well above the point of "Stability" I'm assuming either I missed a setting somewhere or it's something else entirely.

I still presume it's an overclocking issue because lowering the vcore back to 1.290v makes it usually freeze before ever hitting the log in screen while higher vcores last longer (But still fairly randomly crash) and going back to stock speed I don't see any crashes.

This is my first overclock so all I've tweaked is the multiplier, the vcore, and set the vcore to fixed.

PS: I'm on linux (No idea if that little tidbit will start a flame war but I'm hoping not - I just want to get my hardware stable)

CPU cooler and temps please

 

[JnV]

Noctua NH-D14

In idle it can be anywhere from 40C to 18C depending on room temp and under load after 12 hours of prime it was maxing out at 70C

 

[Archer0915]

Noctua NH-D14

In idle it can be anywhere from 40C to 18C depending on room temp and under load after 12 hours of prime it was maxing out at 70C

Kay screen shots CPUz (mem and CPU tab) and core temp.

 

[JnV]

Well again, I'm on linux. So here's the same info from different sources:

*-cpu
description: CPU
product: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
vendor: Intel Corp.
physical id: 4
bus info: cpu@0
version: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
serial: To Be Filled By O.E.M.
slot: LGA1155
size: 1600MHz
capacity: 3800MHz
width: 64 bits
clock: 100MHz
capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms cpufreq

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 58
model name	: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz
stepping	: 9
microcode	: 0x10
cpu MHz		: 1600.000
cache size	: 6144 KB
physical id	: 0
siblings	: 4
core id		: 0
cpu cores	: 4
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms
bogomips	: 6800.28
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +38.0°C  (high = +85.0°C, crit = +105.0°C)
Core 0:         +38.0°C  (high = +85.0°C, crit = +105.0°C)
Core 1:         +29.0°C  (high = +85.0°C, crit = +105.0°C)
Core 2:         +30.0°C  (high = +85.0°C, crit = +105.0°C)
Core 3:         +27.0°C  (high = +85.0°C, crit = +105.0°C)

i7z while using prime confirms it's running at 4.6Ghz with 100mhz bclk, lm-sensors don't have ivy voltage settings yet

4 of these gzkill DDR3-1600 4g sticks stock speeds and timings

description: DIMM DDR3 Synchronous 1600 MHz (0.6 ns)
product: F3-12800CL9-4GBXL
vendor: Fujitsu
physical id: 0
serial: 00000000
slot: ChannelA-DIMM0
size: 4GiB
width: 64 bits
clock: 1600MHz (0.6ns)

Edit: Found where asus hid the load line calibration, brb (Hopefully at 1.290v)

Ultra high didn't work for very long at 1.290, trying ultra high 1.295 now

 

[djscrew]

did it crash during or when you stopped the torture test? if when you stopped it is becuase your LLC is too high.

 

[manu2b]

^+1

I don't know linux chair and its power saving features... But if it behaves like windows, you can do the following.

If you use offset, the vCore might be too low at idle and makes the rig crash: lower the LLC and increase offset to get a higher idle vCore.

 

[JnV]

It crashed after I stopped it, but LLC was at auto - Should I be lowering it to gain stability or raising it? I was under the impression you needed to raise it.

I'm not using offset, but fixed vcore.