May I suggest looking into de-lidding. There are a lot of folks that have found that the thermal compound connecting the die to the ihs (can) is very very badly applied. If you are game, there are vids on utub on de-lidding, you then just clean and re-apply thermal compound to the die and stick the can back on and proceed as usual. Certainly consider this if your cores show significantly different temperatures from one another.
If I'd built an Ivy Bridge system, I would've felt compelled to do that. Some people had really good results over a short-term of reporting with Liquid Ultra or similar indium-gallium-based thermal compounds. Others who used regular replacement TIM material seemed to show short-term regression to the thermal equivalent of the INTEL paste. There were worries that the Liquid Ultra or Indigo Xtreme TIM might cause damage to the processor as Intel might have anticipated with their soldering process, but I never heard anything (anyone else?)
FalseChristian said:
I've been running an 'old' i5 2500K at 4.5GHz using 1.325v for years without 1 problem. Any thing under 1.4v is fine with a good after-market CPU cooler.
Well, the issue is the lithography -- the closeness or "packing" of circuits -- and electromigration from over-volting. I think my old Q6600 system was volted to near 1.38V -- fixed for an overclock. At that time, Intel published a "safe range" and a wider "operable range," and the upper bound of the safe range was about 1.375 -- if I recollect properly. The lithography (I think . . ) was something like 45nm. Then Sandy Bridge came along, with a 32nm lithography; collective wisdom said 1.35V. It should only be lower -- maybe 1.30 or 1.32V -- for Ivy @ 22nm -- and don't quote me!
But things have also changed since OC'ing Yorkies, Kentsfields and earlier processors. You can over-clock with precision while leaving EIST, C1E etc enabled. So -- unless you're "Folding" or running marathon benchmarks, the processor is not going to sustain the higher voltages for very long, and the residual risk is then simply in the load-to-idle transition spikes -- so brief that the monitoring software won't even register them.