No, IVB throttles at 105°C, stays there and works fine. Tested on my i5-3550 with stock cooler, IBT and non-optimal thermal environment. Didn't run it for hours though, just a few IBT runs. But as this is within specs, no need to worry....would it be permanently damaged?
So you're saying it still functions? Amazing.
You will not have damaged the cpu in the sense that it will still perform as it was originally intended, i.e at stock. That said, heat is one of the factors that degrades cpus over time so you might have knocked a hair off it's maximum OC frequency. I really wouldn't worry about it though.
...would it be permanently damaged?
^ this.
If you run a cpu at 110C for 12hours it probably wouldnt be funktional.
^ wrong.
The stuff the chip is made of, starts to melt around those temps (I believe).
Also even if its just a tiny bit, its not just "knocking hairs breaths of max oc ing potential off".
Minor damages results in error calculations occureing more often (even perfectly fine CPUs have them), but a CPU thats been damaged is bound to have more.
IVB throttles at 105°C until the temps go down again. The system doesn't shut down (i5-3550 on Asrock Z77 Pro4).Based on earlier C2D chips I've had, the system just shuts down when it reaches TJMax. With newer chips, it should also do the same, not just throttle. For example, if your using the stock push pin cooler, the pins can pop out if they're not absolutely secured. When it reaches 105c its likely something like that is the cause, and it should shut down rather than throttle.
12/20/12 14:45:55 3890.13 103 101 98 95 99.0
12/20/12 14:46:00 3860.13 105 99 96 95 99.8
12/20/12 14:46:05 3890.13 103 101 97 96 99.4
12/20/12 14:46:10 3850.13 104 101 98 95 99.4
12/20/12 14:46:15 3820.13 102 98 95 94 99.6
12/20/12 14:46:20 3830.13 105 103 97 95 99.6
12/20/12 14:46:25 3840.13 104 101 97 96 99.9
12/20/12 14:46:30 3820.13 104 102 98 95 99.8
12/20/12 14:46:35 3850.13 105 101 98 96 99.6
12/20/12 14:46:40 3820.13 103 101 97 95 99.8
12/20/12 14:46:45 3760.12 104 101 97 95 99.8
12/20/12 14:46:50 3820.13 103 102 95 95 98.4
But this should never happen in real-life, even with a disconnected HSF. The CPU will just throttle to a crawl; Intel has had this down pat since the P4. If you put the system into an oven, OTOH...It actually shuts down at 135C, should the throttle fail to lower the temperature. But the mobo might do it sooner.
It actually shuts down at 135C, should the throttle fail to lower the temperature. But the mobo might do it sooner.
Quote: You will not have damaged the cpu in the sense that it will still perform as it was originally intended, i.e at stock. That said, heat is one of the factors that degrades cpus over time so you might have knocked a hair off it's maximum OC frequency. I really wouldn't worry about it though.
^ wrong. The stuff the chip is made of, starts to melt around those temps (I believe). Also even if its just a tiny bit, its not just "knocking hairs breaths of max oc ing potential off". Minor damages results in error calculations occureing more often (even perfectly fine CPUs have them), but a CPU thats been damaged is bound to have more.
My E2160 doesn't shut down, overclocked to 3.2 it only throttles when the temps reach around the 88-90c mark.Based on earlier C2D chips I've had, the system just shuts down when it reaches TJMax.
Its not an issue for the CPU since it was allowed to throttle as needed.Idc? What's your take? I'm guessing not much different than what's already been posted.
I see. I had a Pentium 4 running in the 90c range with the same heat sink issue. It wasnt until I looked inside and noticed the fault. I was surprised it was still running though. Some boards/bioses have different fail-safe systems in place.An e6400 I had with Intel stock cooler shut down when one of its pins popped out (bumped my knee hard on the case). This is the main reason I think it has the 'Thermtrip', to protect against such events or improper cooler installation. In normal usage (fan intact) if it overheats, throttling should occur.