Issues with MAG X870 Tomahawk

R

reaktiiv15be02f1

New member
Joined
Feb 6, 2026
Messages
12
Cheers,

  • I just recently upgraded my rig with Tomahawk, 9850X3D and Kingston DDR5. After clean installation of the operating system and starting to use the new hardware, I have faced some issues that I never had before. The issues are:

1) The PC won't completely turn off when I shut it down. The monitors go black but lights stay on on the GPU and case fans.

2) During desktop use, my CPU temps are around 45 C which is ok. When gaming, the temps have been on average around 65 C, which is also ok. However, after I stop gaming and return to desktop, the gaming temps remain for as long as I shut down the PC. For example, if I quit the game to desktop and leave the pc on idle, the temperature won't drop but is still around 65 degrees, no matter how long I give the PC time to "cool down".

3) On couple of occasions, the CPU temps have remained at solid 45 C no matter what I have done - desktop or intensive gaming. I have checked the temperature on the onboard LCD display and using HWMonitor, and it is probably correct as on these occasions the fans have not increased their RPM like they usually do under load.

So far what I have tried to do is:
1. Disable fast startup in Windows - no effect.
2. Enable and disable ErP ready mode - no effect.
3. Updated BIOS and chipset drivers to latest - effortless installation but no effect on the problems.

What should I do? Is this just a driver/software related problem, or is there a chance the hardware is faulty?

Thanks.
 
Sort by date Sort by votes
michelelaurell152d02d4 said:
The bug only happens when the CPU is at 100% for a prolonged period. In normal usage it almost never occurs. I personally don’t experience the issue for weeks unless I put the PC under heavy stress with intensive processing (I’m a developer). If you don’t run the stress test properly and across multiple reboots, you might never encounter it.
Click to expand...
I know? Nothing new here, i been testing this for more than 2 months, the cpu doesnt need to be at 100%, sometimes anything above 50% is enough to make sensors stuck and the system will fail to turn off properly.

20 minutes on AVX512 is enough to replicate the issue consistently, and i tested it for 48 hours straight on another x870 tomahawk. 0 issues. ( many also did this, if you follow the links on this topic you will see it )
 
Upvote 0 Downvote
Running any cpu for hours and hours at 100% is never a good thing. In normal usage this shouldn't happen and if it does it's RMA time.
As for the bios versions, they improved alot with memory compatibility and some other stability issues.
Temperature sensors randomly failing points to a hardware component issue. There are many components on a motherboard so it isn't far-fetched to imagine one or more are faulty.
As for the people suffering from this, they weren't stressing their system to the max, it just randomly happens to them. You start troubleshooting with stresstest and benchmarks, not the other way around.
 
Upvote -1 Downvote
rafaelg.mott159402e2 said:
I know? Nothing new here, i been testing this for more than 2 months, the cpu doesnt need to be at 100%, sometimes anything above 50% is enough to make sensors stuck and the system will fail to turn off properly.

20 minutes on AVX512 is enough to replicate the issue consistently, and i tested it for 48 hours straight on another x870 tomahawk. 0 issues. ( many also did this, if you follow the links on this topic you will see it )
Click to expand...
48 hours are useless.
You need to run several 30-minute stress tests and shut down the PC after each attempt.
 
Upvote -1 Downvote
michelelaurell152d02d4 said:
48 hours are useless.
You need to run several 30-minute stress tests and shut down the PC after each attempt.
Click to expand...
You missed my point lmao

15 minutes are enough to make my sensors stuck and power package drop to 0w

I did 48 straight on ANOTHER BOARD to prove that it was not a bios issue, its a hardware one, temps never got stucked and the power package never dropped to zero :)
 
Upvote -1 Downvote
rafaelg.mott159402e2 said:
You missed my point lmao

15 minutes are enough to make my sensors stuck and power package drop to 0w

I did 48 straight on ANOTHER BOARD to prove that it was not a bios issue, its a hardware one, temps never got stucked and the power package never dropped to zero :)
Click to expand...
You have to reboot and do another stress test. If you are in the "good" boot it never happens, you can do the stress test for days straight with no issue.
 
Upvote 0 Downvote
michelelaurell152d02d4 said:
You have to reboot and do another stress test. If you are in the "good" boot it never happens, you can do the stress test for days straight with no issue.
Click to expand...

That doesnt exist lmao. There is no such thing as "good boot"

All it needs is a cpu load for some time, for real, search the topic, there are link 6 links to another topics with multiple feedbacks about this, it will consistently happen.
 
Upvote -1 Downvote
 
Upvote -1 Downvote
 
Upvote -1 Downvote
rafaelg.mott159402e2 said:
You? I agree 😂😂
Click to expand...
  1. 1. We tested 3 different motherboards (2 after RMA replacement) and all of them have the problem.
  2. 2. If it were a hardware issue, the sensor should never work properly. Instead, there are sessions where it happens after just a few minutes and other sessions where it never happens, even after hours and hours under stress.
  3. 3. If it were a hardware problem, it shouldn’t be fixed with a simple reboot. This means that through code they could make the sensor reset itself (as if it were a reboot) when the issue occurs.
  4. 4. MSI does not control the AGESA part of the BIOS, so reporting the issue here is of little use.
In any case, we are on different positions. If version 1.3.0 doesn’t fix the problem either, then it will mean there is no hope of it being resolved. The number of reports is simply too high for this to be an isolated hardware issue.
 
Upvote -1 Downvote
michelelaurell152d02d4 said:
  1. 1. We tested 3 different motherboards (2 after RMA replacement) and all of them have the problem.
  2. 2. If it were a hardware issue, the sensor should never work properly. Instead, there are sessions where it happens after just a few minutes and other sessions where it never happens, even after hours and hours under stress.
  3. 3. If it were a hardware problem, it shouldn’t be fixed with a simple reboot. This means that through code they could make the sensor reset itself (as if it were a reboot) when the issue occurs.
  4. 4. MSI does not control the AGESA part of the BIOS, so reporting the issue here is of little use.
In any case, we are on different positions. If version 1.3.0 doesn’t fix the problem either, then it will mean there is no hope of it being resolved. The number of reports is simply too high for this to be an isolated hardware issue.
Click to expand...

Well, I tested it in 2 boards, and on one of them I can reproduce it on every boot regardless, it will always happen under stress

The fact is just one

This has been reported for more than a year already and nothing, are you really gonna wait for amd and msi get their [***CENSORED***] together ( IF this is something agesa related)

Yeah, nah, the fact that the first report about this has more than 1 year and they keep replying my tickets telling me that they dont know wtf is happening speak volumes
 
Upvote -1 Downvote
rafaelg.mott159402e2 said:
Well, I tested it in 2 boards, and on one of them I can reproduce it on every boot regardless, it will always happen under stress

The fact is just one

This has been reported for more than a year already and nothing, are you really gonna wait for amd and msi get their [***CENSORED***] together ( IF this is something agesa related)

Yeah, nah, the fact that the first report about this has more than 1 year and they keep replying my tickets telling me that they dont know wtf is happening speak volumes
Click to expand...
I know, it’s frustrating because this is a bug related to the AMD CPU and only the AMD AGESA part can fix it. That’s why MSI has no real control over it. They receive the BIOS code from AGESA and then customize it for their motherboard. Other manufacturers do the same, but unlike MSI, they are using more recent AGESA versions.
Unfortunately, we will never know 100% how things really stand, but before switching to another manufacturer, I want to give MSI one last chance.
 
Upvote 0 Downvote
michelelaurell152d02d4 said:
I know, it’s frustrating because this is a bug related to the AMD CPU and only the AMD AGESA part can fix it. That’s why MSI has no real control over it. They receive the BIOS code from AGESA and then customize it for their motherboard. Other manufacturers do the same, but unlike MSI, they are using more recent AGESA versions.
Unfortunately, we will never know 100% how things really stand, but before switching to another manufacturer, I want to give MSI one last chance.
Click to expand...

Well, as far i know only asrock is using beta agesa 1.3 so far, let's hope msi dont take too long to launch its own version and that somehow this manage to fix the issue

Because asrock having issues, now asus too, now this with msi....will be left with gb lol
 
Upvote 0 Downvote
michelelaurell152d02d4 said:
I know, it’s frustrating because this is a bug related to the AMD CPU and only the AMD AGESA part can fix it. That’s why MSI has no real control over it. They receive the BIOS code from AGESA and then customize it for their motherboard. Other manufacturers do the same, but unlike MSI, they are using more recent AGESA versions.
Unfortunately, we will never know 100% how things really stand, but before switching to another manufacturer, I want to give MSI one last chance.
Click to expand...

Actually i just checked and the X870E version already has it

7E59v2AA02026-01-3015.73 MB
  • Description:
    - AGESA PI pre-1.3.0.0 updated.- Enable the "BIOS UEFI/CSM Mode" option.
I will test it out, lets see if it will change anything
 
Upvote 0 Downvote
1770837457736.png
1770838607770.png

New 1.3 AGESA bios and like always, CPU Power Package want to 0 a little after 15mins

Hardware issue as expected
 
Last edited:
Upvote 0 Downvote
Back
Top