Jump to content
Sign in to follow this  
The Coolest

"Core Temp" - monitor temps on K8s and Core/2 CPUs (updated

Recommended Posts

That is actually quite odd, I don't see any reason for this:confused:
Different refresh intervals?

 

The new version appears to have switched the cores arround, and it no longer shows me TcaseMax or TDP... not that it matters. I love this utility, Thanks. :)

Share this post


Link to post
Share on other sites

Well there were some changes, check the "Change log" link on the website.

The cores in the NB are organized in a reversed order to Windows, that's why Core Temp used to report temperatures increasing on Core #x while you were loading Core #y and vise versa, this has been fixed in this version.

Share this post


Link to post
Share on other sites

I think it's pretty well known that I am sucker for any temperature monitoring program :)

Kudos to all the fine work done by TheCoolest and the others.

And many thanks to TheCoolest for posting his latest update at DFI-Street.

What's new in CoreTemp for those that didn't read it before downloading v0.93

Version 0.93 - 19th October, 2006

- Change: Remove 49C/35W TCM/TDP (AMD only).

- Change: Reverse core numbers (AMD only).

- Change: Start numbering from CPU/Core #0.

- Change: "TCaseMax" label to "Tjunction" for Core 2 series.

 

- Fix: Temperature overflow, would show "4294967296C° (?)".

- Fix: A new "CPU is overheating" message appearing with each temp read.

- Fix: Wrong VID (not VCore) reported in the 1.0xxV range on Core 2 series.

 

- Add: Detection of CPU "C* State" (C0/C1/C2/C3, Intel only).

- Add: Toggle logging On/Off.

- Add: Select interval for reading temps.

- Add: Select interval for logging.

- Add: Disable CPU overheat warning.

 

Some thoughts/observations:

I used MBM5 with the DFI NF4 config file

http://www.dfi-street.com/forum/showthread...8&highlight=mbm

Everest Ultimate 3.50.761 (Beta)

http://www.lavalys.com/downloads/everestultimate350.exe

CoreTemp v0.93

http://www.thecoolest.zerobrains.com/CoreTemp/

The latest Central Brain Identifier (CBID)

http://cbid.amdclub.ru/files/cbid82b.zip

I then changed MBM5 and Everest so they would read at 1 sec intervals like CoreTemp. (Fastest Response)

I ran Prime95 and SuperPi on both cores for a while and after everything got good and hot I ran Prime95 on just one Core.

Just so it would be easier to see the difference between Temperature readings of the two cores.

The displayed temperatures seemed to very similar between programs and I've tried to color code some of the results.

 

coretempxl8.th.jpg

 

More details and comparisons in the CoreTemp main threads at XS.

Intel Thread and Results

http://www.xtremesystems.org/forums/showth...hlight=CoreTemp

AMD Thread and Results

http://www.xtremesystems.org/forums/showth...hlight=CoreTemp

Lolento posted some interesting thoughts starting at post #280 of the AMD.

 

Reading all the threads it's pretty easy to go into a Mobius loop as people obtain various results and either praise or criticize one program or the other.

The important thing to remember is that CPU Temp is usually referring to the outboard Thermal Diode while Core Temp is using the on die Temperature Sensor.

Both measurements offer valid results for comparison between other users results (although not between each other).

Two different methods reading from two different sources by different programs.

 

CPU temps can vary widely depending on Heat Sink used, ambient temperature, processor used, application of TIM and correct mounting of the HSF.

While these factors should not affect Core Temps some users have reported that they do.

So use the program that you are most comfortable with and if comparing, make sure you are looking and comparing the same thing.

But it is at best "naive" to say that one program is "better" than the other.

 

links to other Thermal Analysis Programs

Intel Thermal Analysis Tool (TAT)

http://www.techpowerup.com/downloads/392

Speedfan v4.31 by Alfredo Milani Comparetti

http://www.almico.com/speedfan.php

NextSensor by Vitaliy Jungle

http://www.almico.com/speedfan.php

SmartGuardian (from www.dfi.com.tw)

http://us.dfi.com.tw/Upload/Driver/ITE_SG_050123.zip

Share this post


Link to post
Share on other sites

During testing with Everest and prime95 that the Everest core labels are wrong.

 

Physical CPU 0 displays as Core #2 and physical CPU1 displays as Core #1.

 

It's not a really big deal but you should be aware of the discrepancy.

 

Does it really matter?

 

Well, I decided to investigate and here's what I found.

 

If you choose CPU0 in prime95 it uses the left hand CPU window in Windows Task Manager. During this test, the temp on Everest Core#2 went up.

 

I restarted prime95 on CPU1 and the right hand CPU window in Windows Task Manager went to 100% but Everest showed the temp on Core#1

 

So, if you believe the display in Windows Task Manager and the code in prime95, then you have to believe that the Core display in Everest is wrong.

 

I think it has something to do with reading the data from the on-board sensor versus directly addressing the data coming from the processor.

 

Talk amongst yourselves.

Share this post


Link to post
Share on other sites

 

That will be added in the next release :)

 

During testing with Everest and prime95 that the Everest core labels are wrong.

 

Physical CPU 0 displays as Core #2 and physical CPU1 displays as Core #1.

 

It's not a really big deal but you should be aware of the discrepancy.

 

Does it really matter?

 

Well, I decided to investigate and here's what I found.

 

If you choose CPU0 in prime95 it uses the left hand CPU window in Windows Task Manager. During this test, the temp on Everest Core#2 went up.

 

I restarted prime95 on CPU1 and the right hand CPU window in Windows Task Manager went to 100% but Everest showed the temp on Core#1

 

So, if you believe the display in Windows Task Manager and the code in prime95, then you have to believe that the Core display in Everest is wrong.

 

I think it has something to do with reading the data from the on-board sensor versus directly addressing the data coming from the processor.

 

Talk amongst yourselves.

 

Yes, you're correct.

The only reason you see reversed core numbers in Core Temp to other programs is to fix this issue you described above ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×