WHEA-logger and ivy.a warning:P.

[Zanovar]

Are you guys comfortable getting these?,i can run various clocks and volts and feel that im stable and these damn thing pop up with a regularity,and i up the volts to get rid.just interested what others thought on the warning .just to add using offset and c3/c6 i will always get these errors.so using eist and c1 with offset i seem ok.(offset with turbo llc 1.356v 95/97c briefly during some tests).and yes that is hot.

 

[Phynaz]

Wut?

 

[Zanovar]

Wut?

When overclocking ivy bridge,ive notice i get errors.windows log/system/ WHEA-logger errors.sorry if i wasnt clearer.proc errors,are these important?would it blue screen before?(im not sure it does or would? before?).anyways.
anyone have a clue?certainly not me:S,coming from a 750:S

 

[inf64]

Your OC is not stable. You need to invest in better cooling or lapping or adding more Vcore. Adding more Vcore results in more heat,power and maybe can degrade the CPU a bit.
Is it all really worth a couple more hundred Mhz? Just run it at 4.5Ghz and I guarantee you won't see any difference in anything you throw at it.

 

[Zanovar]

Your OC is not stable. You need to invest in better cooling or lapping or adding more Vcore. Adding more Vcore results in more heat,power and maybe can degrade the CPU a bit.
Is it all really worth a couple more hundred Mhz? Just run it at 4.5Ghz and I guarantee you won't see any difference in anything you throw at it.

Erm *scratches head* my overclock is stable enough for me,did you read my post? WHEA-logger proc errors?,i dont get them anymore as i add more volts.what are these errors?,do you think they are important for overall stability?(IVY)

 

[inf64]

It was definitely something related to stability of your CPU at that clock speed. WHEA is windows hardware error event.

 

[Zanovar]

It was definitely something related to stability of your CPU at that clock speed. WHEA is windows hardware error event.

Ya i understand that mate,my point is my proc will be perfectly stable prime 4 hour various(enough for me im a gamer) and linx all day long.but will still give me these WHEA proc errors.anyways it doesnt matter i dont think sandy has these WHEA? proc errors was just curious.

Just to add my proc needs 1.45+ for 4.8,i think ill pass.

 

[2is]

Erm *scratches head* my overclock is stable enough for me,did you read my post? WHEA-logger proc errors?,i dont get them anymore as i add more volts.what are these errors?,do you think they are important for overall stability?(IVY)

Erm *scratches head* did you read his post? It's quite simple, if you're getting errors its not stable.

 

[Zanovar]

Erm *scratches head* did you read his post? It's quite simple, if you're getting errors its not stable.

ERm *coughs*,i gathered that,are you stupid?

 

[2is]

ERm *coughs*,i gathered that,are you stupid?

I'd actually be more concerned if someone of your nature thought otherwise. Don't bother trying to figure that one out.

 

[Zanovar]

I'd actually be more concerned if someone of your nature thought otherwise. Don't bother trying to figure that one out.

hows about you telling me waht those errors mean?,we both know there is something unstable,ill wait a lifetime for you ...

 

[2is]

http://msdn.microsoft.com/en-us/library/windows/hardware/gg463286.aspx

The initial implementation of WHEA focuses on platform hardware devices, including processor, memory, cache, and system interconnects such as PCI, PCI-X, and PCI Express. Peripheral device errors remain under the control of their respective device drivers.

Certainly sounds like something you wouldn't want consistently happening to me, even if you don't "notice" it's negative side effects.

These errors might be getting corrected, but your system having to spend extra time correcting errors means you're losing performance, not to mention, it will only be a matter of time before an uncorrectable error occurs and you get a BSOD, or worse yet, data corruption. So you're losing performance, system stability and potentially data.

Raise your voltage or lower your OC. This really shouldn't even be a question that needs to be asked if you acknowledge instability.

 

[Zanovar]

http://msdn.microsoft.com/en-us/library/windows/hardware/gg463286.aspx



Certainly sounds like something you wouldn't want consistently happening to me, even if you don't "notice" it's negative side effects.

These errors might be getting corrected, but your system having to spend extra time correcting errors means you're losing performance, not to mention, it will only be a matter of time before an uncorrectable error occurs and you get a BSOD, or worse yet, data corruption. So you're both losing performance, system stability and potentially data.

Raise your voltage or lower your OC. This really shouldn't even be a question that needs to be asked if you acknowledge instability.

I never did,just wanted to know what WHEA errors were,as ive never seen them before on sandy etc.erm cheers i guess.

 

[Rvenger]

Zanovar, I had the same WHEA issues as you with my Gigabyte Z77X-UD5H. I had one that would pop up once in a blue moon then all of the sudden I got a blue screen and an automatic restart to a corrupted harddrive to the point I had to reinstall windows. Not even a repair install would fix. This happened about a month ago with my 3770k. Somehow my once stable OC slowly degraded from high IVB temps.

 

[Zanovar]

Zanovar, I had the same WHEA issues as you with my Gigabyte Z77X-UD5H. I had one that would pop up once in a blue moon then all of the sudden I got a blue screen and an automatic restart to a corrupted harddrive to the point I had to reinstall windows. Not even a repair install would fix. This happened about a month ago with my 3770k. Somehow my once stable OC slowly degraded from high IVB temps.

Ya man 2is seems to understand it,mayebe he will cut/paste some more.*laughs*

you stable now rvenger?

 

[Rvenger]

Yes, I adjusted LLC to have less Vdroop and problem solved.

 

[Zanovar]

Yes, I adjusted LLC to have less Vdroop and problem solved.

just to add and i know this is in the wrong section but it has to be said this motherboards usb ports are wonky all of them and thats all bioses to date too.just a tip.(might of had a stinker dunno?)

 

[Goros]

If you aren't 24 hours prime95 x64 stable with 90% memory used on torture with error checking enabled, 24 hours memtest 86+, and 8 hours OCCT linpack avx with 90% memory used you aren't stable.

WHEA errors are hardware errors corrupting your data slowly. May never bsod, but if you get them, you aren't stable and eventually it will catch up.

 

[Idontcare]

Ya i understand that mate,my point is my proc will be perfectly stable prime 4 hour various(enough for me im a gamer) and linx all day long.but will still give me these WHEA proc errors.anyways it doesnt matter i dont think sandy has these WHEA? proc errors was just curious.

Just to add my proc needs 1.45+ for 4.8,i think ill pass.

Zanovar, stability test programs like LinX and Prime95 only test a small subset of the instructions that your CPU can process.

Saying you get no errors in those programs simply means your processor is stable when running the instructions requested by those programs. But other programs, like your OS, will request your CPU process computations using other instructions from the ISA.

Your CPU's ISA supports nearly 2000 instructions. No program in the public domain will stress test all of them. LinX and Prime95 test maybe 100 of them.

WHEA errors are errors that are happening for other instructions, it is basically your OS telling you the CPU is not stable, same as LinX telling you it isn't stable.

As far as why you should care...its called "silent data corruption" and you should care about that.

 

[Zanovar]

If you aren't 24 hours prime95 x64 stable with 90% memory used on torture with error checking enabled, 24 hours memtest 86+, and 8 hours OCCT linpack avx with 90% memory used you aren't stable.

WHEA errors are hardware errors corrupting your data slowly. May never bsod, but if you get them, you aren't stable and eventually it will catch up.

im curious why the long tests,what for?

 

[Zanovar]

Zanovar, stability test programs like LinX and Prime95 only test a small subset of the instructions that your CPU can process.

Saying you get no errors in those programs simply means your processor is stable when running the instructions requested by those programs. But other programs, like your OS, will request your CPU process computations using other instructions from the ISA.

Your CPU's ISA supports nearly 2000 instructions. No program in the public domain will stress test all of them. LinX and Prime95 test maybe 100 of them.

WHEA errors are errors that are happening for other instructions, it is basically your OS telling you the CPU is not stable, same as LinX telling you it isn't stable.

As far as why you should care...its called "silent data corruption" and you should care about that.

Lol IDC you have me paranoid now with that silent data corruption.

 

[Idontcare]

Lol IDC you have me paranoid now with that silent data corruption.

Imagine the day you go to set up a slideshow of your pr0n folder and instead you get greeted with this:

Photo data corruption; in this case, a result of a failed data recovery from a hard disk drive

D: Noooooooooooooooooooooooooo

 

[Zanovar]

Imagine the day you go to set up a slideshow of your pr0n folder and instead you get greeted with this:



D: Noooooooooooooooooooooooooo

hahahah

 

[Goros]

im curious why the long tests,what for?

Because they are random with what they run and drive your temps and volts differently depending on what they are doing.

You can run prime95 in 3-4 short 4 hour stints and get different tests each time and still not run all the possible tests. Same with the memtest86+ 4.20 program.

I've had prime95 fail 16hours in on one core. 24 hours is considered stable, 36-48 is gold standard (and you might test all the patterns by then).

 

[Zanovar]

Because they are random with what they run and drive your temps and volts differently depending on what they are doing.

You can run prime95 in 3-4 short 4 hour stints and get different tests each time and still not run all the possible tests. Same with the memtest86+ 4.20 program.

I've had prime95 fail 16hours in on one core. 24 hours is considered stable, 36-48 is gold standard (and you might test all the patterns by then).

as i said why the long tests?not having a go mate just wondering

nvm