There are numerous reports of the on chip sensors getting stuck at fixed values. Most CPUs have one sensor stuck at idle but when overclocking with additional core voltage and MHz under full load they start to work OK. If the core temperatures don't change when TaskManager goes from 0% to 100% and back to 0% load then the on chip sensor is stuck. At 50C that isn't much of a problem other than it's annoying. Intel calibrates these sensors to operate accurately at 100C +/- 20C so I'd be very surprised to hear about a stuck sensor at higher values near the throttling point.
How do you know that CPU-z is wrong and how do you know that your actual vcore is 1.15 volts? What you set in the bios and the VID of your chip may or may not have anything to do with the voltage that your CPU ends up getting. I've found that CPU-z is very accurate, especially on the older P965 chipset. VID is like a suggested voltage for a CPU but some motherboards may decide to ignore that value and set the voltage to what it thinks is best.And i have a problem with my DFI DARK (965). CPU vCore is set on auto and the VID = 1.125. But the actual vcore is 1.15 and i can not set a lower value. Besides that cpu-z is reading totally wrong (1.232).
I don't know about the DFI board but I know on my Asus P5B Dlx (965) that setting vcore to AUTO can be dangerous when overclocking. AUTO sounds nice and safe but I've seen 1.60 volts at idle when vcore was set to AUTO in the bios. That kind of voltage might damage or degrade a new 45nm CPU.




Reply With Quote
Bookmarks