BonzaiDuck
Lifer
Seems that there's this history over the last several years, per confusions about which processor has which TJunction spec, whether SW programmers for RealTemp, CoreTemp and the like have correctly observed the proper spec or use it correctly, etc. etc.
After updating my BIOS to version 0606, I note that the single "CPU" temperature reported by ASU Monitor is about 10C below what it had been before the BIOS update. I could never be sure if programs like HWMonitor, reporting something called "Package" temperature, weren't in fact providing a value for the "T-CASE" referenced by the Intel thermal spec. More puzzling, both the ASUS and other monitoring software were reporting "Package" (or "CPU" temperature) as equal or slightly greater than the highest of the four (i7-2600K) core temperature values.
Has anyone noticed the same thing? I'm wondering if the ASUS software (as well as HWMonitor) had mis-reported what was intended to be "TCASE," and this new temperature reported after the BIOS upgrade represents ASUS' attempt to correct it.
If it's any indicator of TCASE, I can probably over-clock my Sandy Bridge another 100 Mhz -- at least . . . . If I thought it worthwhile to do so . . . .
After updating my BIOS to version 0606, I note that the single "CPU" temperature reported by ASU Monitor is about 10C below what it had been before the BIOS update. I could never be sure if programs like HWMonitor, reporting something called "Package" temperature, weren't in fact providing a value for the "T-CASE" referenced by the Intel thermal spec. More puzzling, both the ASUS and other monitoring software were reporting "Package" (or "CPU" temperature) as equal or slightly greater than the highest of the four (i7-2600K) core temperature values.
Has anyone noticed the same thing? I'm wondering if the ASUS software (as well as HWMonitor) had mis-reported what was intended to be "TCASE," and this new temperature reported after the BIOS upgrade represents ASUS' attempt to correct it.
If it's any indicator of TCASE, I can probably over-clock my Sandy Bridge another 100 Mhz -- at least . . . . If I thought it worthwhile to do so . . . .