0
1
I have a Xeon E5430 in a socket 775 board. Most of the apps are getting the CPU temperature wrong. Only aida64 is okay, the others think the CPU temperature is about 20°C higher than the reality. I guess Windows or the motherboard or whatever throttles the CPU thinks that too, since when the CPU hits the T case on the wrongly working program, it starts to be throttled and the applications sometimes crash because of this. So for example when I play with battlefield 4, I got a crash in every 2-3 hours, because the CPU reaches the 49°C and the T case is 67°C. This is very annoying. Is there a solution to change the temperature and verify that I am right about this?
1I'd post an answer if I could find something specific to back me up but Throttling is in hardware - there's literally an on processor sensor that does these things I thought. – Journeyman Geek – 2017-02-11T00:16:55.623
What makes you think the tcase for the E5430 is that low? – Ramhound – 2017-02-11T04:14:01.450
@Ramhound https://ark.intel.com/products/33081/Intel-Xeon-Processor-E5430-12M-Cache-2_66-GHz-1333-MHz-FSB
– inf3rno – 2017-02-11T08:51:23.280I found that the Tjmax is 100°C by default on the hwinfo, and it is 85°C on this CPU. If I set it to 85°C it shows correct temp data. I guess the mobo has the 100°C tjmax too, that's why the cpu starts throttling around 49°C. – inf3rno – 2017-02-11T08:52:41.113
it starts to be throttled and the applications sometimes crash because of this
. Uhm what? No, that should not happen. Slow down during throttling: yes. Crash? Nope nope nope nope. That crash is from a different reason. – Hennes – 2017-02-11T10:44:24.047@Hennes I have a 3 hours hwinfo log and the crash happened the same time as it started to throttle. I found out that the BIOS does not have proper microcode for this Xeon CPU. I'll mod the BIOS maybe that solves the stability issues. – inf3rno – 2017-02-11T11:33:04.473
Well, in that is is not due to the throttling itself but because it went into a valid and perfectly working state which the motherboard firmware (in your case BIOS) did not expect. – Hennes – 2017-02-11T19:15:19.193