XS INTEL CORE i7 STABLE OVERCLOCKING DATABASE

[unclewebb]

justin.kerr: RealTemp is using TJMax = 99C for your processor and so is Core Temp. To figure out the core temperature, software needs to know TJMax.

Reported Temperature = TJMax - Digital Thermal Sensor Reading

With Core i7, Intel writes TJMax information into each CPU so as long as software reads that information correctly, which RealTemp and Core Temp are able to do, there shouldn't be any issues. I'm not sure what HW Monitor is doing but it doesn't look like it's following the Intel documentation when it comes to reading TJMax which is screwing up the reported temperatures.

rge brings up another issue about Everest. For the longest time, it has only been reading two cores of a Core i7 and then copying that information and presenting it as the core temperature for all 4 cores. I don't know if that issue has been fixed yet.

When lightly loaded, a CPU can change core temperature instantaneously but when loaded running Prime95, Core Temp and RealTemp should be virtually the same.

RealTemp used to do that too when Core i7 first came out but rge's infinite testing helped me make sure that RealTemp works correctly on Core i7. Core Temp also works correctly though in certain situations it might not order the temperature data in the correct physical order but at least it is able to read all 4 cores and it uses the correct TJMax.

AC3421: Once you know what settings work for you at BCLK 200 MHz then going from 133 to 200 isn't a big deal but if you don't know what settings work then you might have to go up in more gradual steps.