It's true. What happens with the Distance to TJ Max data is that it is stored in a 7 bit variable which gives it a range from 0 to 127.
As the CPU core temperature increases the Distance to TJMax decreases to zero. If it gets hotter than this then the data wraps around and starts counting down again from 127.
The version of RealTemp in the screen shot was using TJMax = 95C so it looks like this:
Distance - Tempeature
2 - 93C
1 - 94C
0 - 95C
127 - 96C
126 - 97C
125 - 98C
124 - 99C
123 - 100C
122 - 101C
121 - 102C
120 - 103C
119 - 104C
118 - 105C
I've always been pretty proud of RealTemp for being the only program to realize that the data wraps around and is still quite usable. Looks like another loose heatsink to me.
Most software uses the standard formula:
Reported Temperature = TJMax - DTS
When the DTS data wraps around and goes to 127 they use the same formula and start reporting negative numbers. I'd rather see the correct temperature than -42C. The CPU in the picture is thermal throttling which is what you'd expect to be going on at these temperatures.
Venturer: You have to trim some fat when trying to do some meaningful testing. That huge list of processes only represents half of what's going on. 129 processes running is too many. Task Manager shows 7% CPU usage and in your listed tasks it only shows 2% so whoever else is logged on to your computer is contributing the other 5%.
There is no way you can get your computer to idle down if there is that many tasks running on it. There's file sharing programs running in the background and you could have other users downloading from your computer during your tests.
Edit: Here's a first class program for turning off start up items while testing or permanently:
Autoruns
http://technet.microsoft.com/en-us/s.../bb963902.aspx





Reply With Quote

Bookmarks