Overclock.net › Forums › Intel › Intel CPUs › WHEA Error Alert Guide (or "How I got out of WHEAville")
New Posts  All Forums:Forum Nav:

WHEA Error Alert Guide (or "How I got out of WHEAville") - Page 9

post #81 of 136
Thread Starter 
I did note in my guide "I discovered how to do this while learning how to overclock my Intel Ivy Bridge CPU. I don't know if other CPU owners could benefit from this guide. If you do, please let me know." smile.gif
post #82 of 136

Yeah, but what I'm saying is it needs to be specifically stated that this only applies to Ivy Bridge.  That is, now that we know.

It's a computer!
(19 items)
 
  
CPUMotherboardGraphicsRAM
i5-2500K @ 4.5GHz (1.368-1.384V fixed voltage) ASUS P8P67 EVO B3 (UEFI ver. 1850) GTX 780 ASUS DirectCU II (1228 / 6300, 1.180V) G.SKILL Ripjaws X 8GB (2 x 4GB) 1866MHz, CL9 
Hard DriveHard DriveHard DriveOptical Drive
250 GB Samsung 840 EVO (C:\) 250 GB Samsung 840 EVO (D:\) 150 GB WD VelociRaptor Samsung SH-S243N 24x DVD Burner 
Optical DriveCoolingOSMonitor
Samsung SH-S203N 20X DVD Burner Thermaltake Frio Win 7 Home Premium x64 SP1 Retail AOC G2460PG (24" 1920 x 1080 144Hz G-SYNC) 
KeyboardPowerCaseMouse
Filco Majestouch 104-key Cherry MX Blues w/NKRO Corsair HX650 (Bronze, ordered on 12-12-2009) CM 690 Intellimouse Optical (1.1A) 1000Hz polling rate 
Mouse PadAudioAudio
Basic, but premium round X-Fi Titanium HD Klipsch ProMedia 2.1 (with 16 AWG Monster Cable... 
  hide details  
Reply
It's a computer!
(19 items)
 
  
CPUMotherboardGraphicsRAM
i5-2500K @ 4.5GHz (1.368-1.384V fixed voltage) ASUS P8P67 EVO B3 (UEFI ver. 1850) GTX 780 ASUS DirectCU II (1228 / 6300, 1.180V) G.SKILL Ripjaws X 8GB (2 x 4GB) 1866MHz, CL9 
Hard DriveHard DriveHard DriveOptical Drive
250 GB Samsung 840 EVO (C:\) 250 GB Samsung 840 EVO (D:\) 150 GB WD VelociRaptor Samsung SH-S243N 24x DVD Burner 
Optical DriveCoolingOSMonitor
Samsung SH-S203N 20X DVD Burner Thermaltake Frio Win 7 Home Premium x64 SP1 Retail AOC G2460PG (24" 1920 x 1080 144Hz G-SYNC) 
KeyboardPowerCaseMouse
Filco Majestouch 104-key Cherry MX Blues w/NKRO Corsair HX650 (Bronze, ordered on 12-12-2009) CM 690 Intellimouse Optical (1.1A) 1000Hz polling rate 
Mouse PadAudioAudio
Basic, but premium round X-Fi Titanium HD Klipsch ProMedia 2.1 (with 16 AWG Monster Cable... 
  hide details  
Reply
post #83 of 136
There is indisputably a direct correlation between the number of these party errors and the stability/reliability of the overclock.

It's easy to see, massively undervolt an overclock and watch the parity show up within seconds, keep increasing the voltages step by step and the errors will become less abundant and less frequent, to the point where it can take many hours of heavy load to generate one, maybe even weeks of just general use before one shows up.

Prime will pass just about anything if the machine doesn't crash. I've never had an error reported in prime even when event viewer was flooded with parity errors.

Do they matter...? who knows, I'm not an expert on the intricate workings of CPU's, but sure as hell a machine running stock won't have them unless there is something severely wrong.

I use parity errors to assess overclocks because they will almost always show up before any fatal signs of instability do. I stress test, but I see stress testing as a means to generate the errors.
post #84 of 136
Quote:
Originally Posted by TheDoctor46 View Post

Do they matter...? who knows, I'm not an expert on the intricate workings of CPU's, but sure as hell a machine running stock won't have them unless there is something severely wrong

They absolutely matter.
Its a failed process due to incorrect checksum on the result and thus the calculation process was started again from scratch while the rest of the queue waited.
post #85 of 136
This time around with my new 3770k (been overclocking for ages on Intel and AMD chips), when I read about WHEAs here, I thought, great idea, and setup a popup. I setup a Prime run and stopped it if I got a WHEA, upped the vcore or offset, and started again. Once I got 12 hours in, I threw in IBT for good measure, and if WHEA free, I then noted my settings in a spreadsheet and upped the multiplier and vcore and started over. Got a very stable OC considering the chip's limitation (did not get a 5ghz monster but 4.8 is fine).

Anything that causes an error that makes the CPU recalculate something that should have already been done, will slow it down. We had an issue at work on a new Win7 load, with a system account that did not have rights to start service 'Diagnostic Service Host' and would try to start it, fail, log the failure then try to start it again. I saw it and said "this is going to slow the computer". Ok, I'm the IT Security/Incident Response/Compliance (ITAR Audits are FUN!) person, not load architecture, but I know that having this loop over and over will slow the computer for no good reason and the load should not be deployed like this (I spent years doing field tech work (A+ cert) and am an MCSE/Security among other things). It's tying up CPU cycles and the hard drive logging errors. With a field tech, we were able to show on multiple assets that it affected the user experience at work and the AD/Patch admin was able to get a fix pushed and the amount of 'slow Windows 7 upgrade' tickets decreased.

WHEA errors mean something is wrong. I would not consider my OC to be stable if a Prime thread failed after some hours. I'm not about to accept that the CPU failed a calculation and had to do it again. How do I know that it will always be able to correct it?
Caseless
(17 items)
 
  
CPUMotherboardGraphicsRAM
Intel 3770k Asus Maximus V Extreme EVGA 780ti SC ASC G.Skill Trident X 2400 
Hard DriveHard DriveOptical DriveCooling
Muskin MSATA Segate 3tb 7200rpm 32gig cache 2x LG BD Burner XSPC Raystorm RX360kit 
OSMonitorKeyboardPower
Windows 7 Ultimate Samsung 46" 'SmartTV' 240hz Coolermaster CM Storm Corsair 1200i 
CaseMouseMouse PadAudio
Lowes 6ft 5 shelf metal rack with extra shelf. Corsair M65 Corsair metal pad. Logitech with subwoofer or home AV (Polk, Tandb... 
Other
Soundblaster SB-Z 
  hide details  
Reply
Caseless
(17 items)
 
  
CPUMotherboardGraphicsRAM
Intel 3770k Asus Maximus V Extreme EVGA 780ti SC ASC G.Skill Trident X 2400 
Hard DriveHard DriveOptical DriveCooling
Muskin MSATA Segate 3tb 7200rpm 32gig cache 2x LG BD Burner XSPC Raystorm RX360kit 
OSMonitorKeyboardPower
Windows 7 Ultimate Samsung 46" 'SmartTV' 240hz Coolermaster CM Storm Corsair 1200i 
CaseMouseMouse PadAudio
Lowes 6ft 5 shelf metal rack with extra shelf. Corsair M65 Corsair metal pad. Logitech with subwoofer or home AV (Polk, Tandb... 
Other
Soundblaster SB-Z 
  hide details  
Reply
post #86 of 136
whea errors are super important if you are looking for stability .
most stress testing software , like prime only good for testing max temps . for stability testing you need a software with heavy and accurate calculations .
for example , my 3770k was stable at 5g , 1.47V vcore .
no whea errors running prime for few hours and ibt (small fft , large fft , yada yada) .
no stability issues at all , no crashes , nothing for more then 2 weeks , including video encoding ,browsing , burning etc .
today , installed solidworks (cad software , needs accurate calculations) and during rendering (photoview360) the program crashed .
checked whea errors - tons of it lol .
to eliminate the errors and crashes , i had to up the vcore to 1.51V !!!
post #87 of 136
I stumbled upon this while searching and wondering why I've never seen any WHEA Errors on my 2500k after my overclock. I haven't been able to get any to show up on it at all in over 6 months time. From my experience it seems to hold true, along with others, that Ivy Bridge detects these while Sandy Bridge almost never does.

Recently I've been overclocking another PC with a 3770k at 4.6ghz (I'd go higher, but I'm not going to delid someone else's CPU) and while it's been quite easy to find instability, looking over WHEA Error logs has made the process much quicker. Testing for 5-10 minute increments with 90%+ ram is very helpful for that as well. Anyways, getting towards the tail end of testing down to the last voltage increment would appear to be perfectly stable. Never encountered any BSODs during this time, but WHEA errors would pop up periodically every 10 minutes or so while Prime95 was running. As soon as I went up 0.005v or 0.010v they would disappear.

I can't imagine WHEA errors as good considering almost every time a worker would display an error in prime these would as well. If I were to go any lower then it would be an endless sea of WHEA Errors. Though if I'm at the point where it BSODs for just booting up or even opening Prime95 I sometimes don't even get them. Like a lot of people have said in here, it's definitely something that complements the overclocking process for Ivy Bridge CPUs and I'm hoping Haswell and beyond detects these as well considering the time and hassle it has saved me.
post #88 of 136
Nice to come across a thread that actually provides some clarification if i should be worried about WHEA errors or not.
I just put together my first rig last year.

Struggling to get a decent overclock as i think i lost the CPU lottery...
Need approx 1.328 - 1.344v to achieve 4.4ghz stable... (varies under load with offset of .055)

Anyway nice to finally be a part of the forums smile.gif
post #89 of 136
My experience with this, trying to get a 4.3ghz target with my 3570K + 212 Evo:

- I set the offset so my vcore was 1.17 under load (I think the offset was +0.03). That passed 24 hours of Prime95 blend and hours of Intel Burn Test on maximum, but produced lots of WHEA errors in the logger. Playing Sleeping Dogs, Planetside 2 and Skyrim I got CTDs, every 20-40 minutes of playtime. Max temp around 69C under IBT.

- Increased the vcore to 1.18 and only got a few WHEA errors every 4-6 hours of stress testing. Got CTDs again from the games, this time after 2-3 hours. Max temps 72C IBT.

- Increased the vcore to 1.19. No WHEA errors. Games do not CTDs. Max temps 74C IBT.

So I would say that IBT or Prime95 on their own can't warrant stability, and a system with WHEA errors is most certainly not stable.

About the errors, if you read the actual description of the errors it says something like "parity error detected and corrected". If you don't know about it, a parity error usually happens when some bit is flipped (a 0 is changed to a 1 or a 1 to a 0), but an additional bit that stores the parity (if the number should be odd or even) catches the error and force a recalculation. This can happen naturally, for example if a cosmic ray, neutron or alpha particle hits the register where the numeric word is stored (seriously, this happens on average every 1000 to 10000 hours on a 10GB RAM machine, Google it) and it is the reason that parity checks exists but it is rare enough that if you consistently get WHEA errors when overclocking you can be sure that you need to increase the vCore. Also, some errors can't be detected, for example if the parity is not changed (the number changing from 2 to 20, for example) and these undetected errors are going to cause problems. Anybody saying that WHEA errors are unimportant deserves the corruption that he is eventually going to have on some important file.
Edited by juanjux - 3/6/13 at 5:57am
post #90 of 136
The WHEA errors this guy refers to, seems different than WHEA errors I heard referred elsewhere (custom->administrative events). I have no Kerneal-WHEA errors but I have tons of custom->administratrive events errors.
Build In Progress
(17 items)
 
   
CPUMotherboardGraphicsRAM
Haswell i7-4770K 4.8GHz@1.452v/1.97vRIN Gigabyte Z87X-UD3H Older Gigabyte 7950 (H60 Mod) 2x4GB Gskill 2400CL11 Hynix CFRs 
Hard DriveCoolingOSMonitor
Samsung 830 128gb Corsair H110 w/4x 140mm Yate Loon High Blues W7 x64 Ultimate Yarrgh Matey Dell U2312HM Matte IPS 1080p 
MonitorMonitorKeyboardPower
Sanyo DP19640 18.5" 768p KDS Rad-7xp 1024p CM Storm Quickfire Rapids Brown Rosewill Capstone 750 
CaseMouseMouse PadAudio
Bitfenix Shinobi Modded CM Storm Spawn Steelseries Diablo 3 2 set CD Speaker + Big Sub 
Other
Bitfenix Recon Fan Controller Moded 
CPUMotherboardGraphicsRAM
Delidded i7-3770K 5GHz@1.499 Gigabyte Z77X-UD5H 1.1 Sapphire Dual-X 7950 3L Boost 4x2GB Mushkin Ridgeback 2200mhz 8/11/8/27 1.75v... 
Hard DriveCoolingCoolingCooling
Intel X25-M 80GB SSD NH-D14 SE2011 Noctua 120/140/140 Fans 3 x Yate Loon Mediums (Petras) 2 x NZXT Havik 140mm Fans 
OSMonitorMonitorKeyboard
Hax'd W7 Ultimate 64-bit Sanyo DP19640 19'' KDS Radius Rad-7xp 17'' Ducky 1087 MX Brown 10keyless 
PowerCaseMouseMouse Pad
Rosewill Capstone 550w Modular NZXT Source 210 w/Modded Window Razer Deathadder 3.5G Steelseries Blizzcon D3 
AudioAudioOtherOther
Phillips FW-C250 2 Speaker Set w/3 CD Changer JBL Sub 6 Subwoofer NZXT Sleeved LED Strip 1m Blue NZXT Sentry 2 Fan Controller 
Other
Colonial Blue Paracord Sleeving 
CPUMotherboardGraphicsRAM
Phenom ii X4 955C2, $31, 5 broken pins, works! ... Biostar A770e3 6.3 Red&Black MSI GTX 460 768mb Twin Frozr II 2 x 2GB Kingston HyperX 1333 OC to 1348CL7@1.65v 
Hard DriveCoolingCoolingCooling
Intel X25-M G2 80GB SSD NH-D14 SE2011 6 x Case Fans (4 x YL-M, NZXT case fan, CM Hype... Jerryrigged Chipset-Northbridge 80mm HSF 
CoolingOSMonitorKeyboard
Jerryrigged VRM Heatsink (sawed off stock AM2 h... Hax'd W7 Ultimate 64bit Sanyo DP19640 19"1360x768 Ducky Cherry Browns 10keyless 
PowerCaseMouseMouse Pad
Antec Earthwatts 430D NZXT Gamma Steelseries Kinzu Optical Steelseries Blizzcon Diablo 3 
  hide details  
Reply
Build In Progress
(17 items)
 
   
CPUMotherboardGraphicsRAM
Haswell i7-4770K 4.8GHz@1.452v/1.97vRIN Gigabyte Z87X-UD3H Older Gigabyte 7950 (H60 Mod) 2x4GB Gskill 2400CL11 Hynix CFRs 
Hard DriveCoolingOSMonitor
Samsung 830 128gb Corsair H110 w/4x 140mm Yate Loon High Blues W7 x64 Ultimate Yarrgh Matey Dell U2312HM Matte IPS 1080p 
MonitorMonitorKeyboardPower
Sanyo DP19640 18.5" 768p KDS Rad-7xp 1024p CM Storm Quickfire Rapids Brown Rosewill Capstone 750 
CaseMouseMouse PadAudio
Bitfenix Shinobi Modded CM Storm Spawn Steelseries Diablo 3 2 set CD Speaker + Big Sub 
Other
Bitfenix Recon Fan Controller Moded 
CPUMotherboardGraphicsRAM
Delidded i7-3770K 5GHz@1.499 Gigabyte Z77X-UD5H 1.1 Sapphire Dual-X 7950 3L Boost 4x2GB Mushkin Ridgeback 2200mhz 8/11/8/27 1.75v... 
Hard DriveCoolingCoolingCooling
Intel X25-M 80GB SSD NH-D14 SE2011 Noctua 120/140/140 Fans 3 x Yate Loon Mediums (Petras) 2 x NZXT Havik 140mm Fans 
OSMonitorMonitorKeyboard
Hax'd W7 Ultimate 64-bit Sanyo DP19640 19'' KDS Radius Rad-7xp 17'' Ducky 1087 MX Brown 10keyless 
PowerCaseMouseMouse Pad
Rosewill Capstone 550w Modular NZXT Source 210 w/Modded Window Razer Deathadder 3.5G Steelseries Blizzcon D3 
AudioAudioOtherOther
Phillips FW-C250 2 Speaker Set w/3 CD Changer JBL Sub 6 Subwoofer NZXT Sleeved LED Strip 1m Blue NZXT Sentry 2 Fan Controller 
Other
Colonial Blue Paracord Sleeving 
CPUMotherboardGraphicsRAM
Phenom ii X4 955C2, $31, 5 broken pins, works! ... Biostar A770e3 6.3 Red&Black MSI GTX 460 768mb Twin Frozr II 2 x 2GB Kingston HyperX 1333 OC to 1348CL7@1.65v 
Hard DriveCoolingCoolingCooling
Intel X25-M G2 80GB SSD NH-D14 SE2011 6 x Case Fans (4 x YL-M, NZXT case fan, CM Hype... Jerryrigged Chipset-Northbridge 80mm HSF 
CoolingOSMonitorKeyboard
Jerryrigged VRM Heatsink (sawed off stock AM2 h... Hax'd W7 Ultimate 64bit Sanyo DP19640 19"1360x768 Ducky Cherry Browns 10keyless 
PowerCaseMouseMouse Pad
Antec Earthwatts 430D NZXT Gamma Steelseries Kinzu Optical Steelseries Blizzcon Diablo 3 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › WHEA Error Alert Guide (or "How I got out of WHEAville")