The reason Intel went to digital on chip thermal sensors was to get away from the inaccuracy of temperature readings from the on board diodes. I know the CPU temp reading on my P5B can vary by 10C depending on if I re-boot or resume from stand by mode. CPU temp readings can also change from one bios version to the next and from one board to the next.Originally Posted by Zucker2k
The on chip DTS is consistent and individually calibrated. CoreTemp and SpeedFan are the only two programs that are reading this data correctly from the chip in real time. I've tested various other programs, including TAT, that take the raw data and averages it and does other sorts of bastardizations to it.
Running CoreTemp and subtracting 10C off of the displayed readings should be giving everyone some very accurate core temperatures so why bother screwing around with anything else?
My E8400 survived the heat baking. I think I'll make something close to this my 24/7 setting and see if it degrades any.
I was planning to EBay off my E6400 Conroe core but it's built like a tank compared to these new fragile 45nm chips so I'm keeping it. If Penryn can't reliably run 4.0 GHz then might as well dump it. All this worrying about degrading chips is taking the fun out of overclocking.
Edit: Almost forgot. When experimenting with my chip I noticed that when Orthos fails it is always Core0 that dies first. For me this is also the core that has a temperature sensor that gets stuck at 67C away from the throttling point. That is far enough away that it won't cause a problem for me but I was just wondering if anyone else with a stuck sensor has noticed Orthos crapping out on the same core? I think stuck sensors could be a warning sign of a second rate chip that is more likely to degrade and fail even if the core voltage never goes over 1.40 volts.
Reply With Quote
Bookmarks