Overclock.net › Forums › Intel › Intel CPUs › Passed prime, yet one whea error in event long.
New Posts  All Forums:Forum Nav:

Passed prime, yet one whea error in event long.

post #1 of 9
Thread Starter 
I'm trying to get my 3770K to 4.6ghz and, after a 6 and a half hour prime run (enough for me), it seemed fine. However when I checked event log I noted one single WHEA error.
Now, the problem is.. I'm not willing to bump the vcore any higher as I'm already running it at 1.272v (idle/load), and my temps on one core hit 87c during the prime run. Now the funny thing is, I am most likely more ''stable'' at 4.6 than I was at 4.5. While testing 4.5ghz about a year ago, I remember getting several WHEA errors which resulted in the prime app crashing. Yet, despite this, I was able to run my comp (including games) with zero issues for the entire period I was running that oc (right up to now).
So first of all, is it a big deal if I only got one of those errors? And given my past experience with them, is it likely that (as before), I won't even see the error again under normal use? I'd really rather not push things any further if I don't have to.
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
post #2 of 9
It is unlikely that there's actually any real instability going on. It could've been a cache miss or some other anomaly. If it passed 6 hours and you're using it for gaming and therefore nothing critically important (like rendering where a crash could be disastrous) then I'd say you're fine. thumb.gif
Heisenberg
(10 items)
 
Redemption
(18 items)
 
 
CPUGraphicsRAMHard Drive
Intel Core 2 Extreme @ 2.8GHz (upgrade) Intel GMA 950 2 x 2 DDR2 667MHz (upgrade) 120GB Mushkin ECO2 
Optical DriveOSMonitorPower
Replaced with 42 W/hr aux battery Mint 17.3 1280x800 Dell 65w Dell Adapter 
CaseOther
Latitude D630 Chassis Intel 7260-802.11ac 2x2 
CPUMotherboardGraphicsRAM
Not telling AsRock something Pixel Pusher 2 x 8 GB AMD Radeon RAM @ 1600mhz (All the VM's) 
Hard DriveHard DriveHard DriveOptical Drive
Crucial M4 128GB (8 second boot) Western Digital RE4 1TB Western Digital RE4 2TB Pioneer Blu-Ray Reader/Writer 
CoolingOSMonitorKeyboard
Cooler Master Hyper 212 Evo Windows 8.1 Pro x64 Dell U2713HM IBM Model M (CLICKY!!) 
PowerCaseMouseAudio
Antec HCG-900 NZXT Source 210 (it was cheap) Logitech G502 Schiit Modi 
AudioAudio
Sennheiser HD 598 M-Audio AV40's 
CPUMotherboardGraphicsRAM
Intel Core i5-4200U Microsoft BGA1168 Intel HD 4400 8 GB LPDDR3 Dual Channel @ 1600mhz 
Hard DriveOSMonitorKeyboard
SK Hynix 256GB SSD Windows 8.1 Professional 1920 x 1080p IPS Display Microsoft Touch Cover 2 
Power
48w PSU 
  hide details  
Reply
Heisenberg
(10 items)
 
Redemption
(18 items)
 
 
CPUGraphicsRAMHard Drive
Intel Core 2 Extreme @ 2.8GHz (upgrade) Intel GMA 950 2 x 2 DDR2 667MHz (upgrade) 120GB Mushkin ECO2 
Optical DriveOSMonitorPower
Replaced with 42 W/hr aux battery Mint 17.3 1280x800 Dell 65w Dell Adapter 
CaseOther
Latitude D630 Chassis Intel 7260-802.11ac 2x2 
CPUMotherboardGraphicsRAM
Not telling AsRock something Pixel Pusher 2 x 8 GB AMD Radeon RAM @ 1600mhz (All the VM's) 
Hard DriveHard DriveHard DriveOptical Drive
Crucial M4 128GB (8 second boot) Western Digital RE4 1TB Western Digital RE4 2TB Pioneer Blu-Ray Reader/Writer 
CoolingOSMonitorKeyboard
Cooler Master Hyper 212 Evo Windows 8.1 Pro x64 Dell U2713HM IBM Model M (CLICKY!!) 
PowerCaseMouseAudio
Antec HCG-900 NZXT Source 210 (it was cheap) Logitech G502 Schiit Modi 
AudioAudio
Sennheiser HD 598 M-Audio AV40's 
CPUMotherboardGraphicsRAM
Intel Core i5-4200U Microsoft BGA1168 Intel HD 4400 8 GB LPDDR3 Dual Channel @ 1600mhz 
Hard DriveOSMonitorKeyboard
SK Hynix 256GB SSD Windows 8.1 Professional 1920 x 1080p IPS Display Microsoft Touch Cover 2 
Power
48w PSU 
  hide details  
Reply
post #3 of 9
Thread Starter 
Quote:
Originally Posted by coachmark2 View Post

It is unlikely that there's actually any real instability going on. It could've been a cache miss or some other anomaly. If it passed 6 hours and you're using it for gaming and therefore nothing critically important (like rendering where a crash could be disastrous) then I'd say you're fine. thumb.gif
That's what I needed to know, thanks!

Finally, I just have one other concern regarding the vcore and LLC. In order to pass the prime blend, I needed to increase Load Line Calibration from High up to ''Ultra High'' (75%). This stabilized my vcore at an almost static 1.272v. Is it safe to have LLC so high? I read that it can put stress on the VRMs.
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
post #4 of 9
it does put added stress because on ultra high the vcore goes up at load not down, just raise up your offset voltage and lower LLC back to high or 50% and your problem is solved
post #5 of 9
Thread Starter 
Quote:
Originally Posted by enigma7820 View Post

it does put added stress because on ultra high the vcore goes up at load not down, just raise up your offset voltage and lower LLC back to high or 50% and your problem is solved
Ok that would make sense, but what if the vcore does not go up at all during load? In my case, it remains at 1.272v whether it's at idle or load. Even during prime. And although it did fluctuate at times, it was only a brief decrease - down to 1.264v. The vcore does not go past what I set it to (1.272v).

So, keeping this in mind, is there still a danger? Particularly to any component other than the cpu?
Edited by Tideman - 3/16/13 at 8:41am
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
post #6 of 9
Thread Starter 
Sorry to bump, but can someone answer the above for me please? Basically I will be running 1.272v through this chip 24/7, with LLC at Ultra High. I want to be sure that what I have been doing is safe, with no risk of degradation to any components. Is the above voltage too much for constant use? Can LLC in itself cause any harm? If it helps, my cpu rarely exceeds 28C idle at these settings.
Thanks.
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
post #7 of 9
Technically, there is always degradation when you run voltage through electronics. Nothing lasts forever. You are safe with what you are doing, but no one can promise no degradation. The bigger issue, at the lower end of the overvoltage, which I would put 1.272 at, is heat. As you know these chips get hot, thanks to some stupidity by Intel. Your temps are fine though, so no worries. As was mentioned already, you should back down from Ultra to High, and bump the vcore to get it back to 1.272. If you get a lot of crashes or WHEAS, increase the offset a little until it is stable. If getting it stable gets the heat where you don't want it to go (upper 90s in my book), get better cooling, or delid, or back the OC down. Heat will be the issue here, not voltage. I'm at 4.8, delidded on a water loop, offset +.15 for a vcore of 1.423. Not worried about it for 24/7 as my temps don't go above 70 on Prime and it went 12 hrs no WHEAS.
post #8 of 9
Thread Starter 
Quote:
Originally Posted by tzvia View Post

Technically, there is always degradation when you run voltage through electronics. Nothing lasts forever. You are safe with what you are doing, but no one can promise no degradation. The bigger issue, at the lower end of the overvoltage, which I would put 1.272 at, is heat. As you know these chips get hot, thanks to some stupidity by Intel. Your temps are fine though, so no worries. As was mentioned already, you should back down from Ultra to High, and bump the vcore to get it back to 1.272. If you get a lot of crashes or WHEAS, increase the offset a little until it is stable. If getting it stable gets the heat where you don't want it to go (upper 90s in my book), get better cooling, or delid, or back the OC down. Heat will be the issue here, not voltage. I'm at 4.8, delidded on a water loop, offset +.15 for a vcore of 1.423. Not worried about it for 24/7 as my temps don't go above 70 on Prime and it went 12 hrs no WHEAS.
Thanks for responding. LLC is starting to worry me now. I get this very brief, what I would describe as, ''capacitor squeal'' when booting into windows. It doesn't occur at any other time, but all I know is it started happening right after running the new OC. What do you make of this?
And the problem with the LLC on my board is, if I drop it to High, the idle voltage will actually end up higher than my load voltage. Not the other way around. So in my case, with the 4.6 OC, I would have to set my vcore at 1.29-1.30v idle, just so that I get 1.27v load. I'm aware you mentioned using an offset, but this means I will have to idle way down at 1.6ghz right? I remember attempting an offset before and it was very unstable.
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
post #9 of 9
Thread Starter 
Right I played about an hour of Crysis 3 and hwinfo64 reports that my vcore remained at 1.272v throughout. The cores hit a maximum of only 64C.

The vcore seems rock solid, it doesn't budge. I'm inclined to leave everything as it is.
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
Dog hair magnet
(13 items)
 
  
CPUMotherboardGraphicsGraphics
5930K @ 4.6GHz 1.28v Asus Rampage V Extreme Nvidia TITAN X (Pascal) Nvidia TITAN X (Pascal) 
RAMHard DriveHard DriveCooling
16GB Ripjaws 4 DDR4 3200  Samsung 850 pro 256GB Samsung 850 EVO 1TB Corsair H110i GTX 
OSMonitorMonitorPower
Windows 10 Pro 64bit Acer Predator XB321HK Dell U2715H Corsair AX1200i 
Case
Corsair Obsidian 750d 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › Passed prime, yet one whea error in event long.