Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
There is not - He is not measuring the temp at the TDiode!

Lou

I think we need to ask for a screenshot to be posted from his iStat results. He sent this to me over the weekend, and the temperatures on CPU A and CPU B looked high compared to the results on my 2009 DP Mac Pro.

JD575 - Could you post your iStat results here for review?
 
Somebody tell the OP to install a copy of Bresink's Hardware Monitor and ignore anything else . The CPU Core temps reported by that program should be T junction sensor figures . Those are the important ones since they are the hottest sensors in the processor . Those and the heatsink temps are the ones we need to look at .
 
There is not - He is not measuring the temp at the TDiode!

Lou

I stand corrected - I looked at the image OP sent to me yesterday and I agree with you. The Core 0 Relative to ProcHot temperatures for both CPU A & B seem high, but the Tdiode temperatures are both very close to the temperatures of the heatsinks - I attached his image here ( comments ? ):
 

Attachments

  • Screen Shot 2015-01-25 at 3.55.13 PM.png
    Screen Shot 2015-01-25 at 3.55.13 PM.png
    247.3 KB · Views: 160
I stand corrected - I looked at the image OP sent to me yesterday and I agree with you. The Core 0 Relative to ProcHot temperatures for both CPU A & B seem high, but the Tdiode temperatures are both very close to the temperatures of the heatsinks - I attached his image here ( comments ? ):

Problem solved.

That "Core 0 Relative to ProcHot" is NOT the core temperature, but "how far away from processor hot". That means, the low the better. His machine is completely normal, both CPU run at normal temperature.
 
Problem solved.

That "Core 0 Relative to ProcHot" is NOT the core temperature, but "how far away from processor hot". That means, the low the better. His machine is completely normal, both CPU run at normal temperature.

Thank you for taking a look at this - I'll be waiting for OP to respond now.

Lou, if you are using the same Xeon processors - would you be willing to post your temperatures for comparison?
 
I am running a w3690, can't make a direct comparison, but please take a look of this post.

https://forums.macrumors.com/showthread.php?p=20632668#post20632668

Also, OP can run some simple software to load up just one core, then he will realise that temp relative to ProcHot will DROP when the real core temp rise.
 
Thank You

Sorry I don't post fast enough. I got diagnosed with Strep today. I am just worn out. Yes its very contagious for first 24 hours after starting antibiotics. But no worries you cannot get it through the net. :D

With everyone's knowledge coming together on this, it appears that I am okay. I learned something about these readings which I am grateful for those who chimed in. This is my first Mac and so I got a little bit of a learning curve.

I ran some light programs and I attached another iStat shot. They appear normal the core does go down with use.

Without sounding like the Academy Awards-thanks Machines, Box185, flowrider, and h9826790.

Flowrider, ditto box185's request. Can you post your temps since we have the same CPUs.

I will stress test soon and post again. At the suggestion of box185, I will use Geekbench.
 

Attachments

  • Screen Shot 2015-01-26 at 5.57.33 PM.png
    Screen Shot 2015-01-26 at 5.57.33 PM.png
    93.4 KB · Views: 123
^^^^Attached per your request.

Edit - Added shot from this morning - running cooler.

First shot this AM
Second shot yesterday PM

Lou
 

Attachments

  • Temps.jpg
    Temps.jpg
    18.4 KB · Views: 274
  • Temps1.jpg
    Temps1.jpg
    44.3 KB · Views: 91
Last edited:
Your first Mac is , incidentally, the most difficult Apple professional desktop Mac to upgrade the processors in . You did well and the shots you took really helped . Please let us know now what the CPU T junction temps are at idle and load just to make certain we're out of the woods .
 
Follow-up

I ran some Geekbench tests and I definitely noticed the Core 0 temps come down quite a bit and my Tdiode rise. One shot is idle and the other one is during a Geekbench benchmark test.

The Geekbench stress test really put it through its paces without any errors, but it made the CPU rise to 170 before I shut down the test. The fans did not increase speed over my manually set speeds, but my iStat did not turn red either.

Off subject a little, the Geekbench benchmark test was a little disappointing since I noticed other scores are in the 22000 range. I believe it might be the memory configuration. Two channel vs three.
 

Attachments

  • Idle.png
    Idle.png
    86.3 KB · Views: 94
  • During Geekbench Test.png
    During Geekbench Test.png
    81 KB · Views: 95
  • Screen Shot 2015-01-28 at 6.35.01 PM.png
    Screen Shot 2015-01-28 at 6.35.01 PM.png
    217.2 KB · Views: 96
I ran some Geekbench tests and I definitely noticed the Core 0 temps come down quite a bit and my Tdiode rise. One shot is idle and the other one is during a Geekbench benchmark test.

The Geekbench stress test really put it through its paces without any errors, but it made the CPU rise to 170 before I shut down the test. The fans did not increase speed over my manually set speeds, but my iStat did not turn red either.

Off subject a little, the Geekbench benchmark test was a little disappointing since I noticed other scores are in the 22000 range. I believe it might be the memory configuration. Two channel vs three.

Figures look cool enough . I'll assume Tdiode means Tcase . I'd prefer Tjunction numbers . Chips should run for an hour at load for a meaningful figure . Your temps came down because your heatsinks are properly attached . Those rotational cylinders on the standoffs were not all flush with the cpu tray pcb before . seems they are now. memory configs and other components only alter score about 5-10 percent . GB is a CPU benchmark , pretty pure one .
 
Thanks Machines. I am not too sure what Tdiode stands for but Wiki had this to say
All modern Intel CPUs have on-chip thermal diodes. As they are right there in the middle it provides most relevant CPU temperature readings. The silicon diodes have temperature dependency of -2mV per degree celsius. Thus we can determine the junction temperature by passing a current through the diode and then measuring voltage developed across it. In addition to processors, the same technology is widely used in dedicated temperature sensor IC's.

I ran the GB stress test for an hour and it never got pass 176F with errors. I agree the heart sinks are working great.

As I make some more modifications, I will run the GB benchmarks again.
 
Figures look cool enough . I'll assume Tdiode means Tcase .

...memory configs and other components only alter score about 5-10 percent . GB is a CPU benchmark , pretty pure one .

Tcase is NOT Tdiode. There is no practical way to measure Tcase for a general cMP user, And Tcase can be 10 degrees (or more) lower than Tdiode. Anyway, My W3690 has a Tcase max 68C, and it can easily run into 86C (Tdiode) without any problem (with the stock fan control, it keep the CPU Tdiode temperature at around 85C under full load). For X5690, it's another 10C buffer (78C Tcase max), so I will say nothing to worry about.

GB score depends on other factors, e.g. how many process running in the background. So, even though after a clean install, may be the spot light index can make the score inaccurate to compare with other machine. For me, as long as it make sense, then everything is OK, no need to achieve the max score. I did play around with the power management system plist files which can lead to my CPU only able to run in 50% performance, that's when GB can tell me the problem. If about 90% of the max score, nothing to worry about. Anyway, in my own test, the memory config will contribute about 5% differences (16600 for 3x8G RAM vs 15800 for 4x8G).

For your info, when stressing the CPU, pay attention to the CPU current, it should stay at least around 80A. If not, that means the stress method is not good enough. You should see something like this:

Screen Shot 2015-01-29 at 16.18.50.jpgScreen Shot 2015-01-28 at 23.11.43 copy.jpg

In my own observation, GB stress can't really keep the CPU at 100% all the way, it fluctuate. I always run OpenCL_NBody_Simulation (switch to CPU multi-core) to assist the stress, then you will see the CPU stay at true 100% (0% idle all the way, load average well above your CPU count, current stay above 81A). Keep this config for 15min, then the temperature and fan speed reading should be stabilised.
 
  • Like
Reactions: yukdave
Tcase is NOT Tdiode. There is no practical way to measure Tcase for a general cMP user, And Tcase can be 10 degrees (or more) lower than Tdiode.

This is why I don't like using iStats for temp sensor reporting - they do not carefully define their sensors . Is the Tdiode then an average of all the Tjunction sensors inside the chip ?

Bresink's program gives me very clear Tjunction figures for all the processor cores and also CPU heatsink figures as well.

You have to be careful with Intel, since they don't like reporting the Tjunction specs of their processors . They give Tcase .

When I build , I use the publically reported Tcase figure as my maximum permitted actual Tjunction figure, because I am very conservative . I build rendering machines that are at load continously and they must operate for a long time .
 
Bresink's program gives me very clear Tjunction figures for all the processor cores and also CPU heatsink figures as well.

Where? I have Bresink's running right now on my 2009 Pro (the full non-lite version) and I can't find that as an option in the sensors list. What am I missing to see Tjunction figures?
 
Thanks h9826790. I will take a look at the load in my next stress test. Maybe even run OpenCL_NBody_Simulation.

5% is about how far I am off so my memory configuration could be holding me back, but I am not to concern. I agree, I am over 90% there.

JD
 
Where? I have Bresink's running right now on my 2009 Pro (the full non-lite version) and I can't find that as an option in the sensors list. What am I missing to see Tjunction figures?

Run Bresink's HM 4.99 , click Window , click "show history windows" , on the Power sensors windows check the box that says "colors / extreme values" Sensors are all there , if Marcel added them .
 
Run Bresink's HM 4.99 , click Window , click "show history windows" , on the Power sensors windows check the box that says "colors / extreme values" Sensors are all there , if Marcel added them .

I'm running 4.99 and I've done what you mention, but no sign of any Tjunction listings. Why would they be on the "Power Sensors" window anyway - I thought we were talking temps.

----------

I'm running 4.99 and I've done what you mention, but no sign of any Tjunction listings. Why would they be on the "Power Sensors" window anyway - I thought we were talking temps.

And yes, I *did* check the "Colors/Extreme Values" box on the "Temperature Sensors" window as well - thinking perhaps thats what you really meant for me to do. ;) No difference there though - I get CPU A/B Diode temps and CPU A/B Heatsink temps - no different that what I see reported by iStat, or MacsFanControl
 
I'm running 4.99 and I've done what you mention, but no sign of any Tjunction listings. Why would they be on the "Power Sensors" window anyway - I thought we were talking temps.

----------



And yes, I *did* check the "Colors/Extreme Values" box on the "Temperature Sensors" window as well - thinking perhaps thats what you really meant for me to do. ;) No difference there though - I get CPU A/B Diode temps and CPU A/B Heatsink temps - no different that what I see reported by iStat, or MacsFanControl

Oops , my bad . I was talking with someone for a long time about power consumption and crossed my wires , it seems ! If the sensor does not appear , it's because Bresink hasn't put it in your particular system configuration . I just checked my own system - a 6 Core 2.8 GHz 2009 Yosemite - and all HM shows is only one T diode and one Heatsink sensor . If I boot into my 3.46 GHz 12 Core 2009 with Mavericks , it displays every Core's Tjunction and both heatsinks . I think he has to optimize the code and it might relate to what OS X the utility is installed on . What OS do you have installed ? Maybe you could have a scratch disk with an earlier OS X on it just to install the utility . I think all my in house diagnostic drives have 10.9.5 Mavericks on them . HM works great with them . Good luck !
 
If I boot into my 3.46 GHz 12 Core 2009 with Mavericks , it displays every Core's Tjunction and both heatsinks . I think he has to optimize the code and it might relate to what OS X the utility is installed on . What OS do you have installed ? Maybe you could have a scratch disk with an earlier OS X on it just to install the utility . I think all my in house diagnostic drives have 10.9.5 Mavericks on them . HM works great with them . Good luck !

It must be running on Mavericks then that makes the difference - this is also on a 12 Core 2009 3.46Ghz Pro, although its running Yosemite. I've got a bootable Mavericks 10.9.5 on a USB stick here somewhere - I'll try installing Hardware Monitor on that and see.
 
It must be running on Mavericks then that makes the difference - this is also on a 12 Core 2009 3.46Ghz Pro, although its running Yosemite. I've got a bootable Mavericks 10.9.5 on a USB stick here somewhere - I'll try installing Hardware Monitor on that and see.

If that does not work, go to Bresinks's website and download the last version that does not support Yosemite . I have older versions of HM on my in house diagnostic mavericks drives
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.