cancel
Showing results for 
Search instead for 
Did you mean: 

Asus mobos - Ivy Bridge and WHEA-logger (Event 19) issues

WillyK
Level 10
Do you guys experience WHEA-logger issues with Ivy Bridge (i7-3770K) on the Asus mobos?
I’d like to share here a few thoughts about that and some testing I’ve done in this regard.

Ivy Bridge tends to generate a lot of “WHEA-logger Event ID 19” when OC is on the edge or unstable.
The general format is:
- A corrected hardware error has occurred.
- Reported by component: Processor Core
- Error Source: Corrected Machine Check
- Error Type: Internal parity error
- Processor ID: …

For Ivy Bridge owners it’s important to watch out for WHEA-logger events, even though Prime95 etc. may seemingly run Ok. Occasionally it may cause weird BSODs and other headaches so it’s not to ignore. Windows 8 is particularly sensitive to WHEA-logger events, and running WEI (WinSat) can help to detect instability related to this (it would typically crash around event 19).

The general advice about handling WHEA-logger issues is to bump the VCore… It works but it’ll raise the CPU temperatures etc. so it’s generally undesirable when everything else is Ok.

I discovered that bumping the VCCIO a little, e.g. to 1.075-1.100V (stock value is 1.050V), may help in getting rid of the WHEA-logger events, and it may even allow you to lessen the VCore without hurting the OC stability! (I’ve tested this on two different machines with Win7/Win8 and it has the same effect).

If you have any specific experiences with WHEA-logger issues please feel free to share.
456 Views
20 REPLIES 20

Myk SilentShadow wrote:
Any and all overclocking starts off the degradation process somewhat faster than when your CPU is at stock, but, it cannot be tracked, nor forecast how fast, or slow, your CPU will degrade. Just like the silicon lottery on having a good clocker with good high RAM clocks with a better than average IMC....the only time you'll know your CPU has degraded is when you need more volts to achieve the same OC you've had going for ages.


hmm, in that case, would you say temperatures alone can degrade CPUs? if so, how?

whether it took 2 years or 2 days, i've always thought current would be the main reason behind most dead chips that were overclocked (unless temperatures were extremely high 85C+ [for ivy bridge] for very long periods of time).
i7 3770k @ 4.7GHz w/ 1.26v (Cooler Master TPC 812)
Asus Maximus V Extreme
GTX 670 2GB SLI
Samsung (MV-3V4G3D/US) 8GB (2x4GB) DDR3-1600 CL11 @ 2400MHz CL10
Samsung 840 Pro 256GB SSD
Samsung HD103SJ 1TB HDD
Cooler Master V700

defter wrote:
hmm, in that case, would you say temperatures alone can degrade CPUs? if so, how?

whether it took 2 years or 2 days, i've always thought current would be the main reason behind most dead chips that were overclocked (unless temperatures were extremely high 85C+ [for ivy bridge] for very long periods of time).


You are correct. What kills or degrades a processor rapidly is heavy loads at elevated voltages, where the current becomes excessive. This is exacerbated at higher operating frequencies as the current drawn is proportional to operating frequency - higher operating frequency needs elevated voltage which is the potential for current to flow.

People are mistaken when they state only one or two of these contributors as the main factor. Voltage, current and temps can lead to degradation. However voltage and heat are not as significant as current.

i) Consider a CPU running at stock settings on a stock cooler at full load. If heat alone were an issue, the CPU would degrade rapidly.

ii) Consider an elevated voltage, and a light load. As the current being drawn is not high, we cannot say that voltage alone leads to or is the primary contributor to degradation. Even at high operating frequencies. Case in point for those that benchmark - we know that the "heavy load" benchmarks degrade a CPU faster than a light load benchmark. Why? Because more current is drawn.

iii) Consider the fact that the stock VID on these CPUs is variable - yet they all meet Intel's TDP. The variance in current draw between a high VID CPU and a low VID CPU is within a couple of watts most of the time. Hence the warranty offered on a high VID CPU versus a low VID one is the same.

The gap does widen as we increase the operating frequency as does the disparity in the level of voltage required between two such CPUs. Still, that change is not completely significant as quite often the CPUs will draw similar levels of current at a given frequency, regardless of how much voltage each of them needs to be stable (maybe 20W between the two samples at the kind of OCs we run on air and water).

The rest of this relationship is down to variables that fall outside my scope of education though I know enough to understand the elementary. Either way, not something I want to try and fudge my way through wrongly on a forum like a muppet.


We can say for certain that there is a relationship between required voltage and frequency - bearing in mind that the change is the amount of current that flows. Depending upon the temperature co-efficient of the substrate, heat can play a part in elevating the required current. I guess we need to understand that voltage is potential, while current is the name we give to flow of that potential. Also worth understanding that P=VA...

Of course, you could brick a CPU on purpose if you wanted; running it out of spec by grossly abusing any three of these contributors. However, as we're talking about the way we use these CPUs while overclocking (applying required voltages) - it's current we need to fear most.

-Raja

Hi there, I hope you don't mind me reviving this thread, it's just that I'm having problems with this error and I don't know how to proceed. It tends to show up whenever I'm playing a 3d game, especially if it's DirectX 11, and it just kills the process with no messages or warnings. My CPU is an i7 3770 (no K) and it looks like I have a slight increase in CPU Bus speed. I have no idea how did that happen, I'm not one for overclocking, that's why I didn't pick the 3770K in the first place. I have an Asus mobo, posting the rest of my setup here. I thought maybe the RAM was causing this, so I swapped it, to no avail.

Should I revert this Bus speed to the original values? I'm new to the process so I could use the help. It's really bugging me because I never touched a single OC config in this mobo ever, and this rig is little more than 1 1/2 years old. The rig in question is

Intel i7 3770 (the bus speed is around 103 MHz)
Asus P8z77-V deluxe mobo (bios version 1805)
2x 4GB DDR3 1600 MHz RAM, Corsair Vengeance (less than a month old, had this problem with the last one too)
Radeon Sapphire r9 series 270, Dual-X edition (also recent, had the same problem before this part)
Corsair CX600 PSU

HiVizMan
Level 40
This is a popular misconception that temp is the only factor.

Degredation starts the minute you power on any CPU. Overclocking will accelerate this. Now this is all relative. The degradation may take 5 or 10 years to be noticeable, or the same model CPU may have noticeable effect within three months. There is no hard and fast rule at all.

Temperature is the byproduct of voltage, you need voltage to make your CPU work, the more you overclock the more voltage is needed for that CPU to work. Heat and voltage kill, not one or the other. It does not matter just how cold you make your CPU either, if you put way to much voltage through your CPU it will die. Voltage is the killer.

For 96% of air and water overclockers there is little likelihood that in their normal lifetime of CPU usage they will have a CPU degrade on them. I would suggest that those folks that stress a CPU for days on end will most proberbly have accelerated wear and tear or if you prefer degradation.

So really it is a much ado about nothing. Just be sensible and do not push 2.2 volts through your CPU while on a stock cooler. 😄 😄
To help us help you - please provide as much information about your system and the problem as possible.

hehe sounds pretty good by me ^_^
i7 3770k @ 4.7GHz w/ 1.26v (Cooler Master TPC 812)
Asus Maximus V Extreme
GTX 670 2GB SLI
Samsung (MV-3V4G3D/US) 8GB (2x4GB) DDR3-1600 CL11 @ 2400MHz CL10
Samsung 840 Pro 256GB SSD
Samsung HD103SJ 1TB HDD
Cooler Master V700

i had MVE running 5ghz 24/7 @ + 0.33V offset mode for almost a year with no whea errors or any other issue .
that board died .
on my replacement MVE board , i can no longer run at the same settings without geting whea errors from time to time .
i played with all the voltages related to cpu + digi control , no help . only if i up the voltage to + 0.36 offset + llc at extreme (vcore goes as high as 1.6V) i can run on 5ghz without whea errors.

note that i dont get those whea errors on regular basis. only if i run solidworks renders i get this .
solidworks probably uses some different cpu commands then games or other software , and is very sensitive to whea.
i also use other high cpu demand software like adobe premier/lightroom , and no whea errors with those

HiVizMan
Level 40
Solid works really stress memory too by the way.
To help us help you - please provide as much information about your system and the problem as possible.

meankeys
Level 13
Raja - So with good sub ambit cooling what is the max voltage you would ever push through a i7 3770K with your CPLL set on high?
I am trying to get to 5300 + MHz I tried up to 1.855v with good temps but no go. am I wasting my time with this chip. I would hate to see it go pop and ruin my socket (I am running RealBench)
ty

Raja
Level 13
If it's not doing 5300 at the high voltages you have tried, you are indeed wasting your time.

meankeys
Level 13
Thank you Raja
what is the highest voltage you have ever heard someone pushing through these processors? Like I hear these world records 7 GHz on LN2
just curious.
ty