WARNING! The latest BIOS from 01/22/25 for the MSI X870 Tomahawk Wifi does not work!

C

cedric39o155e02d8

New member
Joined
Nov 17, 2024
Messages
9
Hello everyone,

Just to inform you, I tried updating the BIOS today (01/22/25) using the following link:
https://www.msi.com/Motherboard/MAG-X870-TOMAHAWK-WIFI/support

Version: 7E51v1A24

I updated the BIOS without any particular issues, but after the reboot, the PC kept restarting in a loop (without displaying anything on the screen!).

I tried clearing the CMOS = no result.

I also tried re-downloading the BIOS and using the button on the back of the motherboard = no result.

I started to panic a little, so I reverted to the BIOS version from 01/02/25 (7E51v1A2), reflashed it using the button on the back of the motherboard, and the PC booted up normally!

Has anyone else encountered this issue?
Thanks.
 
Last edited:
Sort by date Sort by votes
Same problem for me with version 7E51v1A24, I have a restart loop with my X870 tomahawk wifi.
CPU : AMD Ryzen 9 7900x
RAM : CORSAIR VENGEANCE DDR5 64GB 6000MHz CL30 AMD EXPO (CMK64GX5M2B6000Z30)
GC : Nvidia GTX 1070

In my case, I was able to restart a first time after the first restart loop by shutdown with power button the PC and restart next. But at the next start today, I was the same behavhiour, a restart loop (without access to the bios). The solution for me was to back to previous version of BIOS with bios flashback button on the motherboard.

I don't know if it's linked but I have the same RAM (except RGB but I think it's not important here) than aandmsantos09115ac02dd

I have also another issue when I update my BIOS but it's not linked to this version because I have already the problem in previous version. When I restart after the upgrade of BIOS, I have a black sreen and to recover my screen, the workaround is to unplug and replug the display port.
 
Upvote 0 Downvote
Updated my X870 Tomahawk to 7E51v1A24 today. As always I did a CMOS reset before flashing the new BIOS.
So far no problems but I had to install the new chipset driver from MSI support site to get rid of an 'unknown device' in the WIN11 device manager.

At the moment I'm stress testing with the help of AIDA64...
 
Upvote -1 Downvote
Build this board 2 days ago with 9800x3d, came with the original bios. Which caused tons of problems leading me to believe in a hardware error. After I was able to flash the December bios things got better but post still disabled my monitor 2 times. Flashed this bios yesterday, and it's snappier and seems more stable. No complaints except for post disabling my monitor now 4 times, showing the MSI boot screen 4 times too.
But today that's gone, post is now faster and doesn't disable my monitor. I'm starting to believe this board is busy learning after hardware/firmware refresh, in a rather slow pace. Give it a day and suddenly all is better.
Btw I used the USB port for flash on the back panel.
 
Upvote 1 Downvote
The only issue I have with the latest BIOS (A24) is that enabling Memory Context Restore will load EXPO timings from the RAM kit and ignoring my custom set timings, so disabling Memory Context Restore is the only way in this BIOS for me to save my custom RAM timings and make it work, very weird, it was working fine in previous builds.
 
Upvote 0 Downvote
Went ahead and upgraded to the latest firmware. Also installed the newest chipset driver and all is running well. Re-setup my PBO setting, EXPO and other BIOS settings. So far no issues, seems to run a little quicker as well.
1737694610876.png
 
Upvote 0 Downvote
tomfuegu152e02d3 said:
The same issue for me after BIOS update to 1A24 version. 1A1F beta is stable.
Click to expand...
No, 7E51v1A1F is one of the worst BIOS versions next to 7E51v1A24. The BIOS crashes reproducibly when numbers are entered.

Either 7E51v1A2 or 7E51v1A1A. These are, if you want to describe it in a very positive way, the best, but also not error-free versions.
 
Upvote 0 Downvote
blockjak0fe90273 said:
No, 7E51v1A1F is one of the worst BIOS versions next to 7E51v1A24. The BIOS crashes reproducibly when numbers are entered.

Either 7E51v1A2 or 7E51v1A1A. These are, if you want to describe it in a very positive way, the best, but also not error-free versions.
Click to expand...
Thanks, but for my use it's stable, I'll wait to update the BIOS to a couple of versions later to be sure it will be more polished.
 
Upvote 0 Downvote
I have the same behavior after the latest bios update. .. x870 tomahawk and 9800x3d.

I am so annoyed by MSI rn. Never had so much issues with a system. I won't buy one again anytime soon. Do they even test their releases or is it fire and hope for the best.. ?

Now my system is in a boot loop. After 16 minutes or so it booted in windows but after a restart it's in the boot loop again. I am sick of it. The Mainboard was bought in November.. still not useable.
 
Upvote 0 Downvote
They say they are testing it, but all the versions show that they can't have tested it at all. Otherwise you wouldn't notice bugs from/at customers so quickly.

You also have to remember that this is a beta. Only Asus and Asrock have BIOSes with the same AGESA, but both manufacturers have correctly labeled them as beta. MSI has simply released the version without this information. A few weeks ago, MSI simply removed the beta tag from all BIOS versions, although they did not yet have a stable version. Accordingly, few customers of other manufacturers are likely to have installed this version at all.
 
Upvote 1 Downvote
It's been the same for me, after several years with an AORUS Z690 PRO and previously with several high-end Asus motherboards, this is the first time a motherboard has given me this kind of problem, I even had the problem that the LAN card didn't seem to work at all, why is this happening, MSi?

I also have a 9800X3D and a RTX 4090.
 
Upvote 0 Downvote
Yesterday I experienced the reported boot looping + no post on my X870 Tomahawk after upgrading from to the latest 7E51v1A24 (from 7E51v1A2).
At the time of the flash I was able to enter the bios afterwards and re-do my system settings in bios, but after repowering the system hours later the issue occurred and I had to roll back to have it working again.
Read online someone else mention they got the board to post by unplugging any devices which incorporate or present themselves as a usb hub and/or devices like storage etc and got me thinking it might have to do with a few usb devices I had connected when the system had the issue.
Decided to try again but this time with "Legacy USB" disabled in bios and so far I haven't had any problems getting post bios even with all my usb devices connected again.
Could be an idea to try with only a keyboard and mouse connected, and turn off legacy usb in bios if they make it that far, but obviously this shouldn';t happen in the first place.
 
Upvote 1 Downvote
Back
Top