Overclock.net › Forums › Intel › Intel CPUs › Help final stability on i5-3570k - WHEA LOGGER
New Posts  All Forums:Forum Nav:

Help final stability on i5-3570k - WHEA LOGGER

post #1 of 14
Thread Starter 
Hi guys,

Looking to finalize the overclock on my i5-3570k and rid of its intermittent WHEA-LOGGER error (hourly occurance - hard to know when/why its triggered).
Sorry for not yet having my own build filled out in my signature but I'll just fill it out here quick.

Specs:
i5-3570k 4.5Ghz(EVGA Superclock cooler)
gigabyte z77-d3h
G.Skill Ripjaws X 1866 1.5v (F3-14900CL9D-8GBXL)
GTX 570
BFG 650W PSU
Win 7 SP1 64bit

The Overclock:
Using offset voltage overclock. Dynamic vcore is at +50mV (so the Power on Voltage [1.265v] is effectively ~1.32v on load)
Realistically the vcore is dropped to ~1.308v on load from my vdroop llc setting.
CPU has always stable with vcore over 1.29v on load on fixed voltage (never crashing from benching).

BIOS settings:
3DPOWER
  • pwm phase control: exm perf
  • vcore voltage response: fast
  • vcore llc: medium
  • vcore current protection: extreme
MEMORY
  • 1866 9-10-9-28 1.5v
CPU FEATURES
  • thermal monitor disabled
  • C1e disabled
  • PLL overvoltage enabled
  • BCLK 100.00
  • core clock 45
  • CPU PLL 1.65v
  • CPU Vtt 1.06v

Please give me some recommendations on what I can try setup next to test from your own experiences or share your builds stable configuration.

Thanks, excited to learn more...
Warning: Spoiler! (Click to show)

Edited by twixa - 11/27/12 at 9:40pm
post #2 of 14
Thread Starter 
To continue on this thread, whether I receive any other comments or not I'll keep this up to date on what I find. (Found enough loose end information when trying to search for conclusions on the issue).

Swapped C1e enabled and C3/C6 disabled (yielded immediate results)
Settings now:
VOLTAGE
  • dvid: +0.04v (power on: 1.265v)
3DPOWER
  • pwm phase control: exm perf
  • vcore voltage response: fast
  • vcore llc: medium
  • vcore current protection: extreme
MEMORY
  • timings speed: 1866 9-10-9-28 1.5v
CPU FEATURES
  • thermal monitor disabled
  • C1e enabled
  • EIST enabled
  • C6/C3 disabled
  • PLL overvoltage enabled
  • BCLK 100.00
  • core clock 45
  • CPU PLL 1.65v
  • CPU Vtt 1.06v

Aside from much more tedious setup for offset overclock for my i5-3570k, I'm very happy with overclock so far. Runs much cooler on idle (DVID downclocks to 0.09V), runs cooler on load (less reliant on straining LLC settings).

Will quickly update on effects of longer term operation (if WHEA-LOGGER persists) and if these BIOS settings are keepers.
post #3 of 14
4646mhz

C1e enabled and C3/C6 disabled (c3/c6 are the deeper sleep states)
my settings now:
VOLTAGE
offset: +0.045v (VID: 1.260v), 1.305V vcore
3DPOWER
pwm phase control: auto
vcore voltage response: auto
vcore llc: Turbo
vcore current protection: auto
MEMORY
timings speed: 1600 9-10-9-24 1.55v
CPU FEATURES
thermal monitor auto
C1e enabled
EIST enabled
C6/C3 disabled
PLL overvoltage auto
BCLK 101.00
core clock 46
CPU PLL 1.8v
CPU Vtt auto

not much you have to change, i tried them all,
and noticed auto on most settings works ok for me most of the times
vcore llc should be on Turbo tho, gives you a bit vdroop,
seems to work the best, could be you whea errors comes from that,
now you prolly have to much vdroop smile.gif
blck set by hand to 100 is good,
if your using the XMP profile for your ram, you might want to reset
that to auto for now, and use multi only , set by hand, mine is 16x,
xmp profile can mess up oc's too..

its ok to lower cpu pll, i dont need to lower it anymore for temps,
my oc is stable too like this so..
if whea's are still there after you changed vcore llc to Turbo,
up offset by 0.005V, or more if they are still there after testing
BamBam
(17 items)
 
Pebbles
(14 items)
 
 
CPUMotherboardGraphicsRAM
amd 8350 my kids rig :) Gigabyte 990fxa-ud3 Gigabyte 7970 windforce Corsair Vengeance CMZ8GX3M2A1600C9 
Hard DriveHard DriveCoolingOS
500gb OZC vertex 4  Scythe Mugen 3 rev b windows 8.1 
MonitorKeyboardPowerCase
acer 23 inch logitech G510 XFX ProSeries 750W XXX Edition Cooler Master CM 690 II 
MouseAudio
dell  Logitech X-530 
  hide details  
Reply
BamBam
(17 items)
 
Pebbles
(14 items)
 
 
CPUMotherboardGraphicsRAM
amd 8350 my kids rig :) Gigabyte 990fxa-ud3 Gigabyte 7970 windforce Corsair Vengeance CMZ8GX3M2A1600C9 
Hard DriveHard DriveCoolingOS
500gb OZC vertex 4  Scythe Mugen 3 rev b windows 8.1 
MonitorKeyboardPowerCase
acer 23 inch logitech G510 XFX ProSeries 750W XXX Edition Cooler Master CM 690 II 
MouseAudio
dell  Logitech X-530 
  hide details  
Reply
post #4 of 14
Thread Starter 
Quote:
Originally Posted by VonDutch View Post

4646mhz
C1e enabled and C3/C6 disabled (c3/c6 are the deeper sleep states) ...
Thanks for the recommendations. I'll keep those in mind the next time I get on my computer.
I like those settings, seems pretty solid.

Some quick questions though regarding your choices:

Why BCLK 101? (I vaguely remember it being recommended for the Gigabyte Z77 series mobos)
With your turbo LLC, where does your vcore sit on load? (I recall mine behaving differently, no vdroop at that setting)
Edited by twixa - 11/28/12 at 5:59am
post #5 of 14
Quote:
Originally Posted by twixa View Post

Thanks for the recommendations. I'll keep those in mind the next time I get on my computer.
I like those settings, seems pretty solid.
Some quick questions though regarding your choices:
Why BCLK 101? (I vaguely remember it being recommended for the Gigabyte Z77 series mobos)
With your turbo LLC, where does your vcore sit on load? (I recall mine behaving differently, no vdroop at that setting)

i wanted 102 blck, cant hurt other components on the mobo,
but it seems i cant get any higher then 101.40-101.50, so left it at 101,
its not really recommended, ivy doesnt need blck oc,
for me, it feels just a bit snappier, blck oc's everything on the mobo,
setting it to high can harm components on the long run, that i know, i personally wouldnt go above 103,
and sometimes ssd's dont like higher blck..

Turbo gives you a slight vdroop, extreme is no vdroop
i quote sin's guide,
"You will also want to set LLC which is under the 3D power menu, the LLC should be set to Turbo for a slight droop,
or Extreme for no droop at all.
The LLC on these boards is rock solid, what you set is what you get, and nothing other than that."
somewhere else he says,
"Load Line Calibration: This setting can be increased in intensity which will decrease the standard Vdroop setting for the voltages,
the CPU VCore LLC is the most important, and if you are OCing on air you should set Turbo and if on LN2 you should set Extreme."
end quote,

hes using a gigabyte mobo too in his guide,
http://www.overclock.net/t/1247413/ivy-bridge-overclocking-guide-with-ln2-guide-at-the-end
but you prolly read it already ..lol, i did like 100 times hehe..


Vcore for 4646mhz sits at 1.305V, VID is 1.260V, offset 0.045V

Edited by VonDutch - 11/28/12 at 6:36am
BamBam
(17 items)
 
Pebbles
(14 items)
 
 
CPUMotherboardGraphicsRAM
amd 8350 my kids rig :) Gigabyte 990fxa-ud3 Gigabyte 7970 windforce Corsair Vengeance CMZ8GX3M2A1600C9 
Hard DriveHard DriveCoolingOS
500gb OZC vertex 4  Scythe Mugen 3 rev b windows 8.1 
MonitorKeyboardPowerCase
acer 23 inch logitech G510 XFX ProSeries 750W XXX Edition Cooler Master CM 690 II 
MouseAudio
dell  Logitech X-530 
  hide details  
Reply
BamBam
(17 items)
 
Pebbles
(14 items)
 
 
CPUMotherboardGraphicsRAM
amd 8350 my kids rig :) Gigabyte 990fxa-ud3 Gigabyte 7970 windforce Corsair Vengeance CMZ8GX3M2A1600C9 
Hard DriveHard DriveCoolingOS
500gb OZC vertex 4  Scythe Mugen 3 rev b windows 8.1 
MonitorKeyboardPowerCase
acer 23 inch logitech G510 XFX ProSeries 750W XXX Edition Cooler Master CM 690 II 
MouseAudio
dell  Logitech X-530 
  hide details  
Reply
post #6 of 14
Thread Starter 
Quote:
Originally Posted by VonDutch View Post

i wanted 102 blck, cant hurt other components on the mobo,
but it seems i cant get any higher then 101.40-101.50, so left it at 101, ...
I may just join you with that BCLK jump, makes sense and should not cause havoc.

Now I do feel a bit confused on the vdroop situation... As in your screenshot on load shows expected final vcore of (1.305v OFFSET + VID = EFFECTIVE VCORE)(0.045v + 1.260v = 1.305v)
I interpreted it as, when reaching high load situations, your cpu vcore will peak (for me 1.308v) and then droop down some (~12mV). So my high load situations read my vcore as 1.296v after droop. (OFFSET + VID - VDROOP = EFFECTIVE VCORE) (0.040v + 1.265 - 0.012v = 1.296v) I found mixed interpretations on what LLC to use for a moderate overclocking, can't really follow Sin's guide to a T (I mean he's dealing with liquid nitrogen to facilitate very high overclocks).

Sorry for keeping the interrogation going, but it's nice to know these things.
post #7 of 14
Quote:
Originally Posted by twixa View Post

I may just join you with that BCLK jump, makes sense and should not cause havoc.
Now I do feel a bit confused on the vdroop situation... As in your screenshot on load shows expected final vcore of (1.305v OFFSET + VID = EFFECTIVE VCORE)(0.045v + 1.260v = 1.305v)
I interpreted it as, when reaching high load situations, your cpu vcore will peak (for me 1.308v) and then droop down some (~12mV). So my high load situations read my vcore as 1.296v after droop. (OFFSET + VID - VDROOP = EFFECTIVE VCORE) (0.040v + 1.265 - 0.012v = 1.296v) I found mixed interpretations on what LLC to use for a moderate overclocking, can't really follow Sin's guide to a T (I mean he's dealing with liquid nitrogen to facilitate very high overclocks).
Sorry for keeping the interrogation going, but it's nice to know these things.

After reading your post, im more confused then you are ...lol biggrin.gif

this helped me alot to understand more about vdroop etc,
and i like pic's, they tell me more then 1000 words ..lol

i quote
"drooping" the load voltage as a function of supply current allows the VRM to effectively limit the maximum positive peak overshoot voltage (experienced during a heavy to light load transient) to a value below the maximum allowable CPU voltage. This resulting control system ensures the processor supply voltage, regardless of CPU load, never violates a specified limit. The following figure should help to illustrate these concepts.

As intended, Voffset and Vdroop ensure that the supply voltage never exceeds CPU VID

The CPU VID setting establishes the absolute maximum allowable processor supply voltage experienced during transient conditions and is not the target idle voltage. We hope this statement draws attention to this important distinction, as many believe the opposite to be true - a mistake all too commonly made. Together, Vdroop and Voffset ensure that the peak CPU supply voltage seen during heavy to light loading changes remains well below the established maximum. If you determine that 1.17V, as in the case above, is not sufficient for maintaining CPU stability under load, simply increasing the CPU VID does correct the problem. Let's now examine how the system responds if we remove Voffset.

Voltage oscillations while leaving heavy load can cause problems with no Voffset

s we can see, the system exceeds maximum allowable processor voltage whenever any heavy to light load transient is significant enough to warrant one or more voltage excursions above the CPU VID value. Even worse, this all happens without the user's knowledge. Again, removing Voffset completely undermines the purpose of the VID setting - which establishes the maximum CPU voltage, not the target value.
end quote,
http://www.anandtech.com/show/2404/5

i do read alot, but learned most about my mobo and processor by trial and error ..lol
mine can run 4.8ghz max. 24/7 without problem, 1.420V vcore, no blck tho biggrin.gif
BamBam
(17 items)
 
Pebbles
(14 items)
 
 
CPUMotherboardGraphicsRAM
amd 8350 my kids rig :) Gigabyte 990fxa-ud3 Gigabyte 7970 windforce Corsair Vengeance CMZ8GX3M2A1600C9 
Hard DriveHard DriveCoolingOS
500gb OZC vertex 4  Scythe Mugen 3 rev b windows 8.1 
MonitorKeyboardPowerCase
acer 23 inch logitech G510 XFX ProSeries 750W XXX Edition Cooler Master CM 690 II 
MouseAudio
dell  Logitech X-530 
  hide details  
Reply
BamBam
(17 items)
 
Pebbles
(14 items)
 
 
CPUMotherboardGraphicsRAM
amd 8350 my kids rig :) Gigabyte 990fxa-ud3 Gigabyte 7970 windforce Corsair Vengeance CMZ8GX3M2A1600C9 
Hard DriveHard DriveCoolingOS
500gb OZC vertex 4  Scythe Mugen 3 rev b windows 8.1 
MonitorKeyboardPowerCase
acer 23 inch logitech G510 XFX ProSeries 750W XXX Edition Cooler Master CM 690 II 
MouseAudio
dell  Logitech X-530 
  hide details  
Reply
post #8 of 14
Thread Starter 
So based on that little summary you sent (which has been a good help in understanding this) I think I have the idea right.

I believe, since those diagrams were made without including the effects C1e or C3/C6 states I believe I am correct on my assumptions on the affects of my settings 'vdroop'.
Thanks for the resources...

I'm falling a bit off-track on the threads purpose but YOLO (sorry).

I'll keep up to date on stability testing.
post #9 of 14
when i read this about the C-states, i decided to disable C3/C6 only,

"C1E Halt: while similar reduces Clock speed by adjusting the multiplier (Core clock to system bus ratio) and to some degree VID. (voltage) this is a more common occurrence with light use
or on today case of Multicore shutting down a core or 2.

C3, C6. This is a deeper sleep with a complete core(s) shut down (Gate off) and no voltage/Data at all. harder to recover from quickly, previous data is cached elsewhere and needs to be re-cached in L3 memory
to re initialize full muliticore, multithread use. Part of Core parking
http://download.intel.com/design/pro...=tech_tb+paper "

looks like C1 can have a bit influence on vid, says to some degree..
but enough , i shut it now.. off track ..lol

gl with your oc tweaking thumb.gif
BamBam
(17 items)
 
Pebbles
(14 items)
 
 
CPUMotherboardGraphicsRAM
amd 8350 my kids rig :) Gigabyte 990fxa-ud3 Gigabyte 7970 windforce Corsair Vengeance CMZ8GX3M2A1600C9 
Hard DriveHard DriveCoolingOS
500gb OZC vertex 4  Scythe Mugen 3 rev b windows 8.1 
MonitorKeyboardPowerCase
acer 23 inch logitech G510 XFX ProSeries 750W XXX Edition Cooler Master CM 690 II 
MouseAudio
dell  Logitech X-530 
  hide details  
Reply
BamBam
(17 items)
 
Pebbles
(14 items)
 
 
CPUMotherboardGraphicsRAM
amd 8350 my kids rig :) Gigabyte 990fxa-ud3 Gigabyte 7970 windforce Corsair Vengeance CMZ8GX3M2A1600C9 
Hard DriveHard DriveCoolingOS
500gb OZC vertex 4  Scythe Mugen 3 rev b windows 8.1 
MonitorKeyboardPowerCase
acer 23 inch logitech G510 XFX ProSeries 750W XXX Edition Cooler Master CM 690 II 
MouseAudio
dell  Logitech X-530 
  hide details  
Reply
post #10 of 14
Quote:
Originally Posted by twixa View Post

Hi guys,

Looking to finalize the overclock on my i5-3570k and rid of its intermittent WHEA-LOGGER error (hourly occurance - hard to know when/why its triggered).
Sorry for not yet having my own build filled out in my signature but I'll just fill it out here quick.

Specs:
i5-3570k 4.5Ghz(EVGA Superclock cooler)
gigabyte z77-d3h
G.Skill Ripjaws X 1866 1.5v (F3-14900CL9D-8GBXL)
GTX 570
BFG 650W PSU
Win 7 SP1 64bit

The Overclock:
Using offset voltage overclock. Dynamic vcore is at +50mV (so the Power on Voltage [1.265v] is effectively ~1.32v on load)
Realistically the vcore is dropped to ~1.308v on load from my vdroop llc setting.
CPU has always stable with vcore over 1.29v on load on fixed voltage (never crashing from benching).

BIOS settings:
3DPOWER
  • pwm phase control: exm perf
  • vcore voltage response: fast
  • vcore llc: medium
  • vcore current protection: extreme
MEMORY
  • 1866 9-10-9-28 1.5v
CPU FEATURES
  • thermal monitor disabled
  • C1e disabled
  • PLL overvoltage enabled
  • BCLK 100.00
  • core clock 45
  • CPU PLL 1.65v
  • CPU Vtt 1.06v

Please give me some recommendations on what I can try setup next to test from your own experiences or share your builds stable configuration.

Thanks, excited to learn more...
Warning: Spoiler! (Click to show)

Have all C-States enabled bud. Are you able to pass 24 hours of Prime95 without any errors?

How about when using a custom set of 90% of your ram with 1792 set for both min and max? Does that pass 24 hours?
If you are able to fold for week straight, then by my standards, you are stable. Ignore the WHEA errors. Although if they continue, try giving your CPU a small bump in voltage (one notch). It may even be possible that your PLL is too low causing problems. Try just setting it to 1.725 and see if the errors go away.
 
Gsvlip Dudyrm
(15 items)
 
Oda'maksv
(9 items)
 
CPUMotherboardGraphicsRAM
3770k @ 4.5 1.312 load Zotac Z77 ITX Wifi GTX 1070 Gaming 2126/2249 w/ Hybrid cooler TridentX 16GB 2400MHz 
Hard DriveHard DriveCoolingCooling
Samsung 850 Pro 1TB Seagate 2TB H105 EVGA Hybrid GPU cooler 
OSMonitorKeyboardPower
Windows 10 Asus MG279Q - 24" 144Hz 1080p Filco Majestic II w/ Cherry Reds Seasonic X 760W 
CaseMouseMouse PadAudio
Bitfelix Prodigy Logitech G400 Razer Goliath AKG A701 
AudioAudio
JDS Labs Objective 2 JDS Labs ODAC 
CPUMotherboardGraphicsRAM
Core i5 750 3.99 (190x21) 1.376v Load ASUS P7P55d-E Pro GTX 670 FTW <- Poor overclocker :( 8GB (4x2GB) G.Skill DDR3 1600 
Hard DriveHard DriveOptical DriveOS
Samsung 830 Evo 128GB 2x 2TB  Some DVD drive OSX 10.10.4 
MonitorPowerCaseMouse
Asus 1080P Crap TX 750 HAF 922 G400s 
Mouse PadOther
Apple Keyboard Xbox One controler 
CPURAMHard DriveHard Drive
C2D 2,26GHz under volted @ .978v 8GB  Crucial M4 64GB SSD 500GB Scorpio Black 
OSMonitorKeyboardMouse
OS X 10.0 1280x800 Built-in Trackpad 
Audio
Built-in 
  hide details  
Reply
 
Gsvlip Dudyrm
(15 items)
 
Oda'maksv
(9 items)
 
CPUMotherboardGraphicsRAM
3770k @ 4.5 1.312 load Zotac Z77 ITX Wifi GTX 1070 Gaming 2126/2249 w/ Hybrid cooler TridentX 16GB 2400MHz 
Hard DriveHard DriveCoolingCooling
Samsung 850 Pro 1TB Seagate 2TB H105 EVGA Hybrid GPU cooler 
OSMonitorKeyboardPower
Windows 10 Asus MG279Q - 24" 144Hz 1080p Filco Majestic II w/ Cherry Reds Seasonic X 760W 
CaseMouseMouse PadAudio
Bitfelix Prodigy Logitech G400 Razer Goliath AKG A701 
AudioAudio
JDS Labs Objective 2 JDS Labs ODAC 
CPUMotherboardGraphicsRAM
Core i5 750 3.99 (190x21) 1.376v Load ASUS P7P55d-E Pro GTX 670 FTW <- Poor overclocker :( 8GB (4x2GB) G.Skill DDR3 1600 
Hard DriveHard DriveOptical DriveOS
Samsung 830 Evo 128GB 2x 2TB  Some DVD drive OSX 10.10.4 
MonitorPowerCaseMouse
Asus 1080P Crap TX 750 HAF 922 G400s 
Mouse PadOther
Apple Keyboard Xbox One controler 
CPURAMHard DriveHard Drive
C2D 2,26GHz under volted @ .978v 8GB  Crucial M4 64GB SSD 500GB Scorpio Black 
OSMonitorKeyboardMouse
OS X 10.0 1280x800 Built-in Trackpad 
Audio
Built-in 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › Help final stability on i5-3570k - WHEA LOGGER