CPU temperature sensor freezes on MSI X870E Tomahawk WIFI

I

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:
Sort by date Sort by votes
michelelaurell152d02d4 said:
Yes, it’s a direct connection from the PSU to the CPU EPS. No extensions and no daisy-chaining.
Click to expand...
Sorry I didn't see you already clarified that 😅 Have you tried doing the test with 1 stick of RAM in different slots to see if that yields anything? Also, just after I locked the CPU EPS cable in I reseated my RAM then did a CMOS reset just if you wanted to try and replicate the same steps.

Also, discharge any current with the power button and unplug it for a bit before doing that.

Are you using the official Corsair EPS cable?
 
Last edited:
Upvote 0 Downvote
I’ve just run another test; the issue showed up after 8 minutes. It’s completely random. This is the photo inside the case.
 

Attachments

  • IMG_1220 copia.jpg
    IMG_1220 copia.jpg
    874 KB · Views: 93
Upvote 0 Downvote
michelelaurell152d02d4 said:
I’ve just run another test; the issue showed up after 8 minutes. It’s completely random. This is the photo inside the case.
Click to expand...
I enabled FCH Spectrum Spread and I got 0w and frozen cpu again but before I did this I hadn't had the 0w thing occur for a few days but I also was changing PCIE devices. I'm dropping to BIOS 7E51v1A1A, apparently it's the most stable because ever since I upgraded to the newest BIOS build I had different problems arise.

All this was on the Jan 2026 BIOS.

Could FCH Spectrum Spread possibly have an affect?
 
Last edited:
Upvote 0 Downvote
anthony.angio152b02d7 said:
I enabled FCH Spectrum Spread and I got 0w and frozen cpu again but before I did this I hadn't had the 0w thing occur for a few days but I also was changing PCIE devices. I'm dropping to BIOS 7E51v1A1A, apparently it's the most stable because ever since I upgraded to the newest BIOS build I had different problems arise.

All this was on the Jan 2026 BIOS.

Could FCH Spectrum Spread possibly have an affect?
Click to expand...
Go back to the previous settings and do the test again.
 
Upvote 0 Downvote
It seems that there are “lucky” reboots where the bug does not occur, and others where it shows up after just a few minutes. For this reason, it’s better to split the test into multiple runs. In any case, this bug is absolutely fixable via software (BIOS or drivers), because it’s just an incorrect sensor reading. It does not cause system crashes and it resets after a reboot. They can easily fix it in code and make it reset automatically without requiring a PC reboot.
 
Upvote 0 Downvote
michelelaurell152d02d4 said:
It seems that there are “lucky” reboots where the bug does not occur, and others where it shows up after just a few minutes. For this reason, it’s better to split the test into multiple runs. In any case, this bug is absolutely fixable via software (BIOS or drivers), because it’s just an incorrect sensor reading. It does not cause system crashes and it resets after a reboot. They can easily fix it in code and make it reset automatically without requiring a PC reboot.
Click to expand...
I'll let you know at 30 mins if it drops to 0w.
 

Attachments

  • 20260204_150556.jpg
    20260204_150556.jpg
    1.2 MB · Views: 81
Upvote 0 Downvote
michelelaurell152d02d4 said:
It seems that there are “lucky” reboots where the bug does not occur, and others where it shows up after just a few minutes. For this reason, it’s better to split the test into multiple runs. In any case, this bug is absolutely fixable via software (BIOS or drivers), because it’s just an incorrect sensor reading. It does not cause system crashes and it resets after a reboot. They can easily fix it in code and make it reset automatically without requiring a PC reboot.
Click to expand...
The latest Jan BIOS messes my PC up badly but this one seems good so far 7E51v1A1A. 15 mins in and all good.
 
Upvote 0 Downvote
You must log in or register to reply.
Back
Top