Jammer

It's my turn Alpha, it's puff puff pass...

dinos22

guess i should have said turn off logging not error reporting

graham_h

Thank you gents

SLi_dog

alpha0ne

Here ya go m8, your chuff

eva2000

Coretemp v0.94 is out http://www.thecoolest.zerobrains.com/CoreTemp/

alpha0ne

Thanks George

SLi_dog

"The Coolest", creator of CoreTemp, has publicly released a beta version of CoreTemp which supposedly fixes the BSOD problem many users experience.

http://www.alcpu.com/CoreTemp/ - direct link

Now no-one has an excuse NOT to use CoreTemp 0.95 to show the direct DTS readings!!!


If you guys aren't aware, the "actual temperature" reported by Core temperature reporting applications is not the actual temperature that the CPU is running at. It is a best-guess based on a software written Tjunction value and the Digital Thermal Sensor's (DTS) approach to it's throttle point. This causes all sorts of problems when new CPUs are released.
Because of this the creator of CoreTemp, The Coolest, changed his application so it can be configure show the actual DTS values instead. This is far more accurate and reliable for measuring maximum operating thresholds when a CPU is overclocked.

You can configure CoreTemp to show the DTS as shown in the following image.




So, for a 24/7 "safe" overclock with a:

- Core2 dual core CPUs should be run no closer than 20C to the throttle point (0C)

- Core2 quad core CPUs have a higher throttle temperature and so should only be run no closer than 25C from the throttle point.

Note: By run no closer I mean the maximum Prime95/Orthos Small FFT load temps, run for a minimum of 10mins, in the hottest thermal environment the CPU is likely to operate in you should not get closer than 20C or 25C.

For a over-exagerated example, don't go setting your 24/7 overclock at 5am in the middle of winter and expect it to be safe all throughout a summer heatwave.


Learn to love the DTS readings guys as they are the most accurate way of gauging the thermal levels of your Core2 CPU.