Playing with an i5 3570k, thoughts?

[wand3r3r]

i had no idea what a WHEA was until last week because of reading about it on AT. good to pay it forward.

go to your Event Viewer under Adminastrative Options, open up Warnings, then go to WHEA logger and double click it. on the right hand side pane a bunch of options appear under Actions - under actions go to "Attach Task to this Custom View"

Name your task, hit next. Then 'When an Event is Logged' is next, click next - then under Action select Display a Message. then finish.

voila. you get a little pop up box when a WHEA happens.

Do you have to have an actual existing Warning event for WHEA (and see it in the list of warnings)?

When looking at the warnings I didn't see any WHEA warnings nor an option anywhere. I also tried searching for WHEA in the warning event list to no avail.

 

[Vectronic]

... then under Action select Display a Message....

Windows 8 doesn't like this option, so people using that will have to be a bit more creative with their alerts (cmd.exe, bat files, point it to an application you have running that is single-instance with focus on initialize, etc)

 

[wand3r3r]

Do those WHEA errors exist in Windows 8?

Edit. Yep, I just found the first one. When oc'ing with too low of a voltage and it froze up whereupon it logged this error in the event viewer.

Just testing 4.7 GHz with 1.34v, temps are maxing at 78-82c after 10 minutes. I tried 1.29v but it crashed quickly so I just bumped it up quite a bit. On auto voltage it was hitting 90c but I notice the auto voltage was like 1.4v on the core.

 

[Vectronic]

Auto probably wasn't that far off, 4.7 with mine is about 1.38v. (don't know for sure since other than 4.5 I don't like odd multipliers, lol... 4.6 1.32, 4.8 1.44)

 

[coffeejunkee]

Do those WHEA errors exist in Windows 8?

Edit. Yep, I just found the first one. When oc'ing with too low of a voltage and it froze up whereupon it logged this error in the event viewer.

Just testing 4.7 GHz with 1.34v, temps are maxing at 78-82c after 10 minutes. I tried 1.29v but it crashed quickly so I just bumped it up quite a bit. On auto voltage it was hitting 90c but I notice the auto voltage was like 1.4v on the core.

They sure do. I think they exist in Vista as well, but never heard of them untill I started using Ivy. I wonder if you just get a bsod when using XP.

If you got a whea error and it froze up you're probably still a way from full stability. They also occur without you noticing anything, just the entry in event viewer.

I must say these cpu's are really easy to oc but testing for stability is another matter. My previous i5 750 was rock stable if it could do 20 runs Linx, my current 3570K not so much. I've tried pretty much every stress tester out there (Linx, Prime, OCCT, Intel XTU, Aida) but not a single one gave me satisfying results. In fact I now use BF: P4F as stress tester and it works much better. Had all my overclocks stable, until I tried playing and running a movie in mpc at the same time which caused some new whea errors to pop up. So I would recommend running many real life applications at the same time over using the traditional stress testers.

 

[Vectronic]

You'll usually (circumstances prevailing) get an error in Event Viewer with XP... however yes, the BSOD that usually accompanied it took priority.

I'd also agree that Ivy Bridge (I skipped Sandy) is frustrating compared to older processors. Older processors typically either worked, or didn't with a given configuration, Ivy is really picky, and often doing the opposite of what you would assume should work, is the right thing to do.

That said, there's a lot more to play with, and recently found a use for the "Long/Short Power Limits"... amusingly (or appropriately) enough, the wattage I set there equates to degrees celcius when running LinX, so I can "set" the temperature in the BIOS and then just play around to get the max out of it at that temperature.

Stress testing by itself is rather useless, you are generally just wasting processor time and energy... instead I start a stress test, and then just "forget" that it's running, and do whatever I would normally do. Find errors much quicker that way.

 

[MrSquished]

well it's been a couple of weeks at this OC and voltage tested with PRIME and linx - hours of bf3 gaming, lots of lightroom 4 heavy lifting/merging to HDR and tons of movie watching and general browsing with no WHEA messages or instability - and just got a WHEA error log message.

ugh.