Yes, I know. That why I want to find out the truth, because I may be affected as well (touch wood, by 4,1 still stable so far). And I really appreciated that you share your experience (which I don't have), but it's so hard to me to follow your logic, and how to achieve this conclusion.
Well, read all I wrote again.
I'm all about thinking logical, they call me McGuyver because I usually find a fix.
That often means going where others didn't go, thinking outside the box, because of what you state too..."how can this be logical...so I will ignore it!"
What could you possibly loose by trying it yourself? Or you don't trust yourself fixing something without an iFixit guide?
Also, please study what's T-case max, and please tell me how to observe that in real world.
Let me tell you that when you ran 2 or 3 different Apps to check what's going on with your Mac, you should have noticed they all use their own language.
You tell me what the T-diode is!?
Its like the temp of the NB, I look at the IOH diode, no clue what it means...but I know its the NB.
As I said, my W3690's T-case max is 68 (directly from
Intel as well). Please tell me why my W3690 can run at 82C T-diode (with screenshot as prove) without shutdown, or even thermal throttling (by using the command "
pmset -g thermlog" in terminal)
Correct.
Again, we are fed with numbers...without really knowing what the diodes do/mean.
So tells me there is a difference between that T-diode and the actual core temperature of the CPU.
What you see in the screenshot is like a minute before it crashed...also the crash reporter told me it was a CPU failure....funny btw,...the Mac automatically rebooted within 10 seconds....go figure.
If we blindly recommend the other re-paste the NB with no valid reason behind, that's not helping the others, but may by creating problems.
I totally 100% disagree!
What problem could you create!!
You can **** up the procedure,.. you will have to detach the motherboard from the tray...leave the cpu's in the socket please and use some tape to make sure they don't fall out during the procedure!
Why??? You can very easily bent the pins of the socket.
So again,...I think that it should become a standard procedure when upgrading a MP....only something to gain.
In fact, pastrychef just bring up a good pint. If you ever fix that problem on a 5,1 as well. Then you can eliminate the "re-seat" theory, because the clip on the 5,1 make you no need to re-seat the CPU when re-paste the NB.
You have zero experience with this procedure, so what makes you think you can have an educated opinion about this!!
[doublepost=1463660757][/doublepost]Sorry for my poor English. So, do you mean
Hey man, Dutch is my native tongue!
1) You have a Mac Pro suffer from crash. (Mac Pro A)
2) You take the tray out, and then put in in another Mac Pro. (Mac Pro B)
3) The Mac Pro B now suffer from crash.
4) So you can sure it's somewhere in the CPU tray cause the trouble?
MP 1 crashes,
I take tray of MP 2 and use in MP 1...crash.
I take tray of MP 1 and stick in MP2...crash
We try MP2 with tray that belongs in it...crash
Anyway, I sometimes run Handbrake 24/7 on my 4,1 for a week. That's 100% stress for >100 hours. I am sure that's long enough to crash the machine if time / loading is the trigger. And many users here use that Mac Pro for proving heavy duty as well. That's why we want / need the Mac Pro.
Thanks for the tip, I should have figured that out myself!
It was kind of a shock to me, to see that thse guys run an App that is OpenGL (cinema 4D) but they wanted a GTX980...but when I was there I learned they cannot use GPU support in Cinema 4D (I don't know why) and were rendering 100% on the CPU's.
Besides that, I agree that the sensors may be wrong in some situations. And I have absolutely no idea where it is.
Me neither! Plus we don't really know what these 'diodes' are.
BTW using the same logical approach I managed to find a problem with another 4.1 octo,...a sensor gave a zero reading (forgot which one)... I had the guy bring me the processor tray. When I tested it in my MP I found out I did have a reading on that sensor, so the problem had to be in the backplane board (and it was)
[/QUOTE]