CPU temperature sensor freezes on MSI X870E Tomahawk WIFI

ilya.mfw12e402b7

New member
Joined
Jul 4, 2025
Messages
6
Hi, I'm another owner of a motherboard with a stuck sensor

I will not write the details, as everything has already been described on this forum and Reddit:
https://forum-en.msi.com/index.php?threads/msi-x870e-tomahawk-cpu-temp-sensor-gets-stuck.413221/https://forum-en.msi.com/index.php?...k-properly-when-the-temperature-rises.411247/https://forum-en.msi.com/index.php?threads/9950x3d-sensors-stuck-mag-x870e-tomahawk-wifi.413098/https://www.reddit.com/r/MSI_Gaming/comments/1hejqx3/mag_x870_tomahawk_wifi_lan_issues_fix/https://www.reddit.com/r/AMDHelp/comments/1kt1mat/ryzen_9950x3d_sensors_stuck_under_load/
System:
MSI X870E TOMAHAWK WIFI
AMD 9950x3D
Arctic Liquid Freezer III 420
PCCooler YS1200
GeForce RTX 5070 Ti

If you have solved the problem with the sensor, please share the solution in this topic
 
Last edited:
No, with your settings I had values similar to yours, but the bug still occurred. Now I'm trying more aggressive settings. In one hour of testing it hasn't happened yet, but I need to run more tests.
I worked in 3D Max for over 3 hours, rendering again. The temperature didn't rise above 65°C.
There was no problem with the temperature. If the problem goes away in the next two days, I'll change

Curve Optimizer = All Cores
Sign = Negative
Value = -5 may be -10
 
Last edited:
2 hours of stress test and no issue. I’ve never experienced such a long period of time without the bug. I’ll keep testing, I wouldn’t want it to be just luck, but maybe the key really is setting the PPT, TDC, and EDC values. But I didn’t set them manually one by one, I just selected the 200W value (the highest) from the BIOS list.
 
2 hours of stress test and no issue. I’ve never experienced such a long period of time without the bug. I’ll keep testing, I wouldn’t want it to be just luck, but maybe the key really is setting the PPT, TDC, and EDC values. But I didn’t set them manually one by one, I just selected the 200W value (the highest) from the BIOS list.
Could you send me your PPT, TDC, and EDC values and result of test?
 
Could you send me your PPT, TDC, and EDC values and result of test?
image0.jpg
image1.jpg
image2.jpg

1774509741169.png
 
Ok, the bug just occurred right now. So at the moment there is no solution.
Don't want to use my settings? Maybe your settings are too aggressive?
I see your temperature during the test is 87.5, power is 205, and the frequency is 4.7 GHz.
Here's what I have set:
PPT = 180W
TDC = 110A
EDC = 150A
Global C-State Control = Disabled
Power Supply Idle Control = Typical Current Idle
I left the rest of the settings as default.
With these settings, the AIDA 64 test showed 100% CPU load, a frequency of 5.17 GHz, a temperature of 67C, and a power of 147.6W

If we use different settings, the experiment cannot be called correct.
 
Don't want to use my settings? Maybe your settings are too aggressive?
I see your temperature during the test is 87.5, power is 205, and the frequency is 4.7 GHz.
Here's what I have set:
PPT = 180W
TDC = 110A
EDC = 150A
Global C-State Control = Disabled
Power Supply Idle Control = Typical Current Idle
I left the rest of the settings as default.
With these settings, the AIDA 64 test showed 100% CPU load, a frequency of 5.17 GHz, a temperature of 67C, and a power of 147.6W

If we use different settings, the experiment cannot be called correct.
Already tested, the bug is still there.
 
4 months dealing with this and I finally got tired and bought a x870 aorus elite, been on extensive contact with the support, they even sent me 2 custom bios but nothing solved it, so I will rma this, I give up

1000175291.jpg
 
4 months dealing with this and I finally got tired and bought a x870 aorus elite, been on extensive contact with the support, they even sent me 2 custom bios but nothing solved it, so I will rma this, I give up
I previously shared my settings, and I haven't had any issues with temperature or power drops for several days now.
I'm currently continuing to optimize the system at the processor core level.
 
I previously shared my settings, and I haven't had any issues with temperature or power drops for several days now.
I'm currently continuing to optimize the system at the processor core level.
U just don't get it do you?

It's not a matter of optimize, they are literally working with their engineers to fix an issue on the smu on telemetry level

This has nothing to do with optimize the system lol
 
U just don't get it do you?

It's not a matter of optimize, they are literally working with their engineers to fix an issue on the smu on telemetry level

This has nothing to do with optimize the system lol
I will not claim that my decision is right or wrong. I made the settings and got the result. I ask anyone interested to check it for information.If my settings help anyone, I'll be happy. If not, I'd love to hear feedback on how their system works.
 
I will not claim that my decision is right or wrong. I made the settings and got the result. I ask anyone interested to check it for information.If my settings help anyone, I'll be happy. If not, I'd love to hear feedback on how their system works.

Oh my god...

You are mixing two completely different things and thats exactly where your reasoning falls apart.

What you are describing is a workaround, not a fix. If changing some settings “solves” it, all you actually did was change the conditions so the issue doesnt trigger as easily. That doesnt mean it’s gone, it just means you are no longer hitting the edge case.

The behavior being discussed here is very specific. Sensors freeze or return invalid values, telemetry becomes inconsistent between different tools, power readings drop to zero, and yet the system itself remains fully stable. That points to a telemetry or smu communication issue, not something related to system tuning or optimization.

If this were really about optimization, you would expect instability, crashes, or hardware errors. None of that happens. The system keeps running normally, only the monitoring layer breaks. That alone already separates this from any kind of tuning problem.

On top of that, this behavior has been reproduced multiple times under controlled conditions, including long uptime and specific software triggers, and multiple users with the same motherboard report identical symptoms. That’s not random configuration, that’s a pattern.

In my case, I’ve also been working directly with msi support and tested multiple custom bios builds provided by their engineering team. These are not public releases, and even with those modified versions the behavior changed but did not disappear, which further confirms this is not a configuration issue but something deeper at the firmware/telemetry level.

So no, this has nothing to do with optimizing the system. You just havent triggered the issue under your current setup, which is not the same thing as it being fixed.
 
Oh my god...

You are mixing two completely different things and thats exactly where your reasoning falls apart.

What you are describing is a workaround, not a fix. If changing some settings “solves” it, all you actually did was change the conditions so the issue doesnt trigger as easily. That doesnt mean it’s gone, it just means you are no longer hitting the edge case.

The behavior being discussed here is very specific. Sensors freeze or return invalid values, telemetry becomes inconsistent between different tools, power readings drop to zero, and yet the system itself remains fully stable. That points to a telemetry or smu communication issue, not something related to system tuning or optimization.

If this were really about optimization, you would expect instability, crashes, or hardware errors. None of that happens. The system keeps running normally, only the monitoring layer breaks. That alone already separates this from any kind of tuning problem.

On top of that, this behavior has been reproduced multiple times under controlled conditions, including long uptime and specific software triggers, and multiple users with the same motherboard report identical symptoms. That’s not random configuration, that’s a pattern.

In my case, I’ve also been working directly with msi support and tested multiple custom bios builds provided by their engineering team. These are not public releases, and even with those modified versions the behavior changed but did not disappear, which further confirms this is not a configuration issue but something deeper at the firmware/telemetry level.

So no, this has nothing to do with optimizing the system. You just havent triggered the issue under your current setup, which is not the same thing as it being fixed.
I understand you. But I don't suggest that I have solved the problem of SMU level.
I use the tools that are available to me. And if after setting up the system I get a result I'm happy with, why shouldn't I use it?
 
Back
Top