MSI MAG Tomahawk X870/X870E Owners Thread

Only changed the mobo going from an x570 to an x870e, same fan configuration and my pc is way quieter than it was previously.

Perhaps MSI have a lower fan curve than Gigabyte out of the box.
 
Last edited:
Mine boots in around 25 seconds.

Specs:

Ryzen 7 9800X3D
X870E Tomahawk
32GB DDR5 6000MHz CL30

I am running bios version E7E59AMSI.2A20 (27th Dec) according to the bios.
 
There is currently a bug (latest BIOS of Jan 2025), which is becoming widespread atm when using the M2.1 slot for PCIe 5.0 and 4.0 NVME storage devices were Windows 11 will randomly report the transfer speed of these NVME's to 1.0 x4 and sometimes 3.0 x4 when checked via CrystalDiskInfo.

Also, doing benchmark tests when this occurs, the read and write speeds are not up to spec either (lower numbers). It's completely random for when this occurs, as personally myself, didn't encounter it after numerous reboots, full shutdown's, etc, but eventually it was triggered and showed up, so can easily be missed if not checking the transfer speeds once the OS is booted.

The current temporary workaround is to move it down a slot to M2.2 and enable X4 in the BIOS, since M2.2 shares bandwidth with USB 4.0 ports, so enabling X4 to the M2.2 will disable the USB 4.0 ports. There is an ongoing thread on the MSI forum regarding this and user posts on reddit too, so anybody who has this MOBO, please check your NVME in M2.1 with CrystalDiskInfo (transfer speed) and you may have to do several reboots for it to show lower numbers like 1.0, so please keep that in mind and raise a support ticket with MSI, so they can escalate this to the DEV team to fix. https://account.msi.com/services/tickets

More information is here:



 
Last edited:
Forgot to mention too, USB hubs connected seem to trigger this more, yet results may still vary to the user. I had more success with a 4 port USB hub connected to the USB 3.0 port on the MB with a SD card reader and a USB pen drive plugged into it.
 
There is another bug too where the ethernet port lights go dead and the transfer rate either stops or gets stuck at 100MB. I just had this yesterday, I thought the port had died, and only a clear CMOS fixed it. No idea if it will happen again or not... but hope the info helps someone! :)
 
Oh dear.

Not noticed any issues (touch wood) with mine thankfully.

The board only launched in Dec 2024 so it's very new still.
I would still check though, as I thought mine was okay until after around 10 reboots in a row and then it showed 1.0 x4 in the CrystalDiskInfo screen transfer row. The more users confirm it, the faster a new update can be done, as it's quite a serious bug imo, even though you can workaround it for now.
Oh dear.

Not noticed any issues (touch wood) with mine thankfully.

The board only launched in Dec 2024 so it's very new still.
Interesting, I had something similar after I plugged in the Wifi/BT addon, as the LED on the Ethernet port was not on. Windows then detected no ethernet connected when in fact it was, and as a result, I unplugged the Wifi/BT addon and reset my network. Luckily, the ethernet port then started working again after a reboot, but very weird though.
 
There is another bug too where the ethernet port lights go dead and the transfer rate either stops or gets stuck at 100MB. I just had this yesterday, I thought the port had died, and only a clear CMOS fixed it. No idea if it will happen again or not... but hope the info helps someone! :)
Thank you, that info does/will help! Have just installed the board in the last few days and had the speed at 100Mbps, assumed it was my SFP+ RJ45 transceiver not negotiating the rate properly but this gives me something else to check. I will try with a switch with RJ45 ports and see what happens before messing around too much.
 
Thank you, that info does/will help! Have just installed the board in the last few days and had the speed at 100Mbps, assumed it was my SFP+ RJ45 transceiver not negotiating the rate properly but this gives me something else to check. I will try with a switch with RJ45 ports and see what happens before messing around too much.
It just happened a second time yesterday, seems to ocurr when it loses connection a few times (I have been installing and playing around with a new SFP+ router during a 10GB fibre upgrade). CMOS fixed it again and as long as you save your bios settings in a profile (I will do this today) then its easy to restore after a CMOS reset.

I hope MSI fix it via a BIOS upgrade soon though!
 
Last edited:
I've noticed an issue with the NIC. I raised a ticket with MSI but they don't want to acknowledge any issue.

Maybe it is similar to what is being described here and elsewhere.

My issue is that the NIC stops detecting a physical link under certain circumstances.
Once the issue is triggered, the only remedy is to remove power from the board. This will bring the link back 100% of the time.

The trigger is "swapping the cable". but it is intermittent. Maybe related to time? not sure.
I accidentally found the remedy when disconnecting the ATX power to take a photo of the serial number for the steam code claim. It miraculously came back to life after being disconnected for 3 days!
Since then, if just disconnected at the PSU when it happens.

Maybe this is useful to others having the issue (or similar ones).

I'm wondering if it would be better to swap out for something else....


Question to other owners:
When you connect the NIC to a switch and shutdown Windows, does the switch still show a link on the switch port?

I am seeing that the onboard NIC no longer has a link light when shutdown, but the switch maintains a low speed link (FE) even though there is no WoL enabled etc....
 
I've noticed an issue with the NIC. I raised a ticket with MSI but they don't want to acknowledge any issue.

Maybe it is similar to what is being described here and elsewhere.

My issue is that the NIC stops detecting a physical link under certain circumstances.
Once the issue is triggered, the only remedy is to remove power from the board. This will bring the link back 100% of the time.

The trigger is "swapping the cable". but it is intermittent. Maybe related to time? not sure.
I accidentally found the remedy when disconnecting the ATX power to take a photo of the serial number for the steam code claim. It miraculously came back to life after being disconnected for 3 days!
Since then, if just disconnected at the PSU when it happens.

Maybe this is useful to others having the issue (or similar ones).

I'm wondering if it would be better to swap out for something else....


Question to other owners:
When you connect the NIC to a switch and shutdown Windows, does the switch still show a link on the switch port?

I am seeing that the onboard NIC no longer has a link light when shutdown, but the switch maintains a low speed link (FE) even though there is no WoL enabled etc....
Thats literally the problem that we wrote above. :D
 
Thats literally the problem that we wrote above. :D

Sure, but I haven't seen anyone removing power to fix the issue. Or trigger the issue by connecting a different cable.
Clearing the CMOS is a bit drastic IMO so it would be good if others experiencing the problem can simply remove power to get around it....?

Anyway,
I am interested to know if your switch still detects a link when windows is shutdown?
 
Back
Top Bottom