Real Temp - New temp program for Intel Core processors

I heard that NDA is lifted on Monday, so we should hopefully get some screenshots after then.

EDIT: Page 100!

Thanks for your work unclewebb. :)

:rocker: :worship: :worship: :worship: :worship: :worship: :rocker:

Congratulations on 100 pages of excellent information people. And great job webb. Cheers.

Quote:

---

Originally Posted by Ol'Baditude

Congratulations on 100 pages of excellent information people. And great job webb. Cheers.

---

Ditto!!!

Thanks for the thumbs up guys. Stuff like that gets me motivated.

I've been doing some background work recently and tonight I started programming a more advanced sensor test. I've got the general layout done and have started hooking it up. This test will take about 10 minutes but I'm making it very user friendly and I think it will give users a much better look at exactly what their sensors are up to. It goes well beyond the present Sensor Test and it should be much easier to find sticking sensors with it.

Here's a preview:

http://img208.imageshack.us/img208/8...sortestao5.png

My present backdrop should be titled, "Wishful thinking." :)

that's GREAT uncle! :up: can't wait to get my hands on v2.84 :D

That look AWESOME!!! Looking forward to it.

Thanks Uncle for all the effort you have put itno this, IMO there is nothing better out there. :up:

Thanks to burebista for sending along this screen shot.

http://img89.imageshack.us/img89/6682/tjmaxcy1.png

Model Specific Register (MSR) 0x1A2 is where TjMax is hiding in Core i7. Thanks Intel.
This might significantly reduce the million and one posts about, "What is TjMax?"

In the picture, 64 hex translates to 100 decimal so it looks like TjMax=100C for the early Core i7.
You can use any program that lets you read MSR data to check your Core i7 or you can use the MSR Tool

at least the new Core i7s don't seem to have stuck sensors

Looking good, can't wait!

Quote:

---

Originally Posted by emoners

at least the new Core i7s don't seem to have stuck sensors

---

That makes them boring :p:

I always love seeing those flat line in all 4 core temps on a quad, mine looks like 63-63-59-59 on load =(

I just completed my first CPU Cool Down Test. It takes just over 10 minutes and is about as exciting as watching paint dry but I think it will give users some useful information about how their sensors are working. I'm sure Intel is going to be real happy with this test. :D

This test uses Prime95 small FFTs for consistency. I was running 4GHz at 1.40 volts with my Tuniq on low speed to create a nice temperature spread from full load to idle.

During testing I noticed that when using the Clock Modulation feature that as a CPU throttled down, my Kill-a-Watt meter would show less and less power consumption. In theory, every step down in power consumption should translate into a lower core temperature. A person should see the Distance to TJMax increase at each and every step going down in the chart.

Here's how my test looks on my E8400 that doesn't have sticking sensor issues at normal room temperatures:

http://img91.imageshack.us/img91/5126/cooldowngr4.png

I think a processor with sticking sensors when running this test is going to get about half way through it when it will be very obvious that the sensor has stopped moving. If the power decreases to the CPU and the CPU keeps reporting the same Distance to TJMax then that is going to be an easy way to see that one of your temperature sensors is stuck.

Hopefully within the next 24 hours I'll have a version ready for download.
Anyone out there with some stuck sensors that need testing? :up:

Quote:

---

Originally Posted by unclewebb

I think a processor with sticking sensors when running this test is going to get about half way through it when it will be very obvious that the sensor has stopped moving. If the power decreases to the CPU and the CPU keeps reporting the same Distance to TJMax then that is going to be an easy way to see that one of your temperature sensors is stuck.

---

hi uncle,
do we have to look at dts temps and check "manually" if the sensor stopped moving, or are you considering to let realtemp check if dts movement stopped? would be nice to let realtemp itself check if the sensor stopped moving and pop up an error msg and probably even stop the cool down test if this happens ...

Quote:

---

Originally Posted by unclewebb

I'll have a version ready for download.

---

link pls

Quote:

---

Originally Posted by Factotum

link pls

---

Hopefully within the next 24 hours I'll have a version ready for download.

that's what he said at the time of posting

We`re looking forward to get it.

fgw: The first thing I need to do after releasing this new test is to get a lot of feedback from users that have CPUs with good sensors. Most 65nm and the new Core i7 seem to rarely get stuck. I'll also need to see what this new test reports on 45nm CPUs with known stuck sensors.

It might not be until the 25% mark that a sensor first sticks and then I would still have to run a couple of more rounds after that to confirm it. Sensors also tend to stick at slightly different values so after the first sensor gets stuck the test would still need to be run further to see what the other sensor or sensors are up to.

This test isn't designed to be run everyday so stopping it at the 8 or 9 minute mark instead of letting it run for the full 10 isn't going to save a user a lot of time. This test was designed more for when you first get a new chip so that you can get to know your sensors reasonably quickly and see if you have any duds or not. It should also provide a thorough baseline that you can compare to later.

There is a wide range of CPUs with large differences in temperatures from idle to full load depending on cooling, core voltage, etc. That makes it difficult to create a simple formula to interpret this data and pop up an accurate message that says, "ERROR!, Your sensors are junk."

To begin with, I'm going to let users interpret their own data. Maybe I'll get more feedback that way.

Edit: 12 more hours. :)

Here's a second test with the same CPU as before at closer to default settings with SpeedStep / C1E enabled. With Prime95 running, it was at 3000 MHz and 1.200 volts and dropped to 2000 MHz and 1.192 volts when RealTemp stopped Prime95 at the 0.0% level.

http://img223.imageshack.us/img223/5...wntest2sm9.png

The final Idle level is when the CPU Clock Modulation feature is turned off. Power consumption at the wall drops again and the CPU cools down one final step.

When not overclocking and testing at default values, the data continues to look pretty clear. Based on this test I can conclude that both sensors are well balanced and don't exhibit any sticking issues at a Distance to TjMax of 66 or less.

A few more hours and it will be ready for release. :)

At first I thought your temps were going up as CPU load was dropping. :eek:

Note to self: read the labels.

you rule :)

unclewebb
Comon, mate? Where are you :D

Based on the MSR tool's reading, what is my TJ max for the Merom T7100, Unclewebb?:shrug:

Since that's a mobile chip, you can just look it up on the processorfinder. It's 100C according to the thermal spec. If only Intel was as clear about desktop chips. Of course, in the case of a known Tj Max (like for mobile chips), you could just add the temperature to the "Distance to Tj Max" together ;)