MPG X870E CARBON WIFI Beta BIOS

Svet

Svet

🛠️ ⚙️⚒️
ADMIN
Joined
Nov 20, 2003
Messages
85,611
>>> E7E49AMSI.1A1E <<<

>>> E7E49AMSI.1A1H <<<

>>> E7E49AMSI.1A21 <<<

>>> E7E49AMSI.1A22 <<<

>>> E7E49AMSI.1A24 <<<

>>> E7E49AMSI.1A25 <<<

>>> E7E49AMSI.1A26 <<<

>>> E7E49AMSI.1A28 <<<

>>> E7E49AMSI.1A29 <<<

>>> E7E49AMSI.1A31 <<<

>>> E7E49AMSI.1A32 <<<

>>> E7E49AMSI.1A33 <<<

>>> E7E49AMSI.1A34 <<<

>>> E7E49AMSI.1A41 <<<

>>> E7E49AMSI.1A44 <<<

Notes:
  • * Unstable RAM OC
  • * Hang 0D when saving BIOS settings or doing M-Flash

>>> E7E49AMSI.1A62 <<<

>>> E7E49AMSI.1A65 <<<

>>> E7E49AMSI.1A66 <<<

>>> E7E49AMSI.1A93 <<<

>>> E7E49AMSI.1A99 <<<

.rar SHA-256: 0da3ebedfa9e1f53f3e3aa320c1fd32f770cae0b32f112fe87750f1f88031487
BIOS SHA-256: 07a227bb302e9eac43bca0e18a43cfe58e043302eebfb13b08c7b8653a8ad636




>>> E7E49AMSI.1AA1 <<<

.rar SHA-256: cf63c3ad59580532257612b108db651ec3341a517c22efb20127dd44c94d8ae1
BIOS SHA-256: 4BD52D73DE3112768E2C6C62CA85C423F0963359A4C4B1CFCFEF1C04294DE1D2

AGESA version:
Screenshot 2026-06-06 162546.jpg






>>> E7E49AMSI.1A9B <<<

.rar SHA-256: 9eae3f5df43c2696e64ef329c6fddc45ba2e40ec0b529a9c451fa3871b077bff
BIOS SHA-256: 2B34A9B25DDEC186AC2272334DC2666C80082B143468A4D9D470BE88AB2C4CB4

AGESA version:
1.jpg


With >>Forum UEFI Shell Flash Tool<< you can copy the hash of the BIOS file quickly for checking,
by loading the BIOS and click over BIOS-SHA256 on the bottom:
2.jpg
then in this topic do press CTRL+F to paste it to check if will match it.

Aside from this you can check AGESA version,
and / or let the tool prepare the USB key for flashing either by the tool by booting from USB key or by M-Flash.
While doing USB key preparation it will ensure the BIOS integrity on the USB key both checksum and SHA256.

>>> E7E49AMSI.1AA2 <<<

.rar SHA-256: 3e1eec8ecdd717f7b694f7a82e704d4fb7ef54ad4f357fe5e28de6b9de422473
BIOS SHA-256: B1172777823B553168B6B1A14C57CAF7E7B48C259EBC43586B39C2A9BC4C8542

AGESA version:
E7E49AMSI.1AA2_ver.jpg




Latest version: (from msi web page)
7E49v1AA3:
BIOS SHA-256: AF55A578CBDE8138906094F1CAD8C4C6A06639C4DAB23C0D7ACEA392326847AA
AGESA version:
Screenshot 2026-07-03 145909.jpg
 
Last edited:
Sort by date Sort by votes
vic123159d02e5 said:
I will try tonight, but I'm pretty sure I had no problem doing this on A25. OCCT is part of my benchmark tests to ensure system stability, along with AIDA, Cinebench R23, and Y-Cruncher. I run it almost every day, but since A30 gave me headaches with overclocking, even with R23, I haven’t run a full OCCT test on that BIOS yet.
Click to expand...
It looks like I may have found a workaround, but a proper fix is still needed from MSI side.

It seems that NZXT CAM is the culprit. However, I can’t go without it since I’m using a Kraken Elite 360 AIO, and all pump and fan control depends on CAM.

After uninstalling CAM, I haven’t encountered any FF, C5, or 0D errors so far.
But the downside is that my CPU starts overheating, since fan and pump control is disabled without CAM.

I know that ASUS managed to fix this issue in their BIOS somehow.

Also, worth noting: when I used this same AIO on a 9800X3D with an X870 Tomahawk running AGESA 1.2.0.2b, NZXT CAM never caused any problems.
I’ve reported the issue through the CAM feedback system, but I honestly don’t think they’ll release any fix for it.
:giljotiini:
 
Last edited:
Upvote 0 Downvote
Has anyone tried the new beta bios A31 yet? It looks like it just came out in the last day. Are there any notes for it (sorry, I'm new here)?
 
Upvote 0 Downvote
Alyred said:
With your 5090 and running on A25, do you need to do anything special to get optimal performance out of the card? I finally scored a 5080 (I'll get a 5090 once stock gets a bit more normalized or I get lucky in a vendor ticket draw) but thinking of staying on A25 for the time being (and just tweaking my memory for that).
How did you test your FCLK speed? Just looking at ZenTimings, or do you have a more conclusive way to check/benchmark it? I'll probably bump my testbench machine up to A31 to give it a shot, though A29 is working fairly stable for me on that one.
Click to expand...
Not really. I do overclock it with Afterburner, though. One of the few problems I’ve never had with that board is the PCIe lane not running at 5.0. I don’t use Ryzen Master since I found it doing weird things, sometimes it couldn’t even boot with looser timings than my manual overclock. I use HWInfo to check my FCLK speed and SMUDebugTool_v1.38 to test CO on the fly. I also use BIOS version A25, as it might not be the most bug-free, but in my opinion, it’s the fastest for benchmarking in the 2xx series of BIOS. (Except A21 , but it’s a mess in almost every other aspect.)
 
Upvote 0 Downvote
pogdmm said:
It looks like I may have found a workaround, but a proper fix is still needed from MSI side.

It seems that NZXT CAM is the culprit. However, I can’t go without it since I’m using a Kraken Elite 360 AIO, and all pump and fan control depends on CAM.

After uninstalling CAM, I haven’t encountered any FF, C5, or 0D errors so far.
But the downside is that my CPU starts overheating, since fan and pump control is disabled without CAM.

I know that ASUS managed to fix this issue in their BIOS somehow.

Also, worth noting: when I used this same AIO on a 9800X3D with an X870 Tomahawk running AGESA 1.2.0.2b, NZXT CAM never caused any problems.
I’ve reported the issue through the CAM feedback system, but I honestly don’t think they’ll release any fix for it.
:giljotiini:
Click to expand...
Really strange behavior. I tested it on my system but couldn’t reproduce the problem. I’m using the Lian Li Galahad Performance II AIO, so I don’t use NZXT CAM. Good luck getting MSI to fix this, you’ll need it, I’m afraid
 
Upvote 1 Downvote
vic123159d02e5 said:
Not really. I do overclock it with Afterburner, though. One of the few problems I’ve never had with that board is the PCIe lane not running at 5.0. I don’t use Ryzen Master since I found it doing weird things, sometimes it couldn’t even boot with looser timings than my manual overclock. I use HWInfo to check my FCLK speed and SMUDebugTool_v1.38 to test CO on the fly. I also use BIOS version A25, as it might not be the most bug-free, but in my opinion, it’s the fastest for benchmarking in the 2xx series of BIOS. (Except A21 , but it’s a mess in almost every other aspect.)
Click to expand...
All right, thanks. I'm going to pop in my card and stick with A25 for now, just gotta get to my somewhat-restricted power supply area to plug in the 12vHPWR cable. There's enough room to get it in straight but not a lot of room for hands/maneuvering/other power cables being plugged in. We'll see how the rest of the BIOS operates with the upgrade and adjusted memory timings, going to relax a few settings for my RAM and see how it impacts overall performance.
I'll upgrade my test machine to A31 over the next few days and see how well the same A29 settings for memory and CPU CO dial in. Otherwise, I'm in agreement - A25 seems to be a better BIOS revision overall. It would be nice if MSI would post some better changelogs for their BIOSes though. And would address some of the significant performance issues, like the M2 slots STILL not performing as well as A21's (I think it was A21 that still gave full speed on the M2's, but it's been so many revisions now...)
 
Upvote 0 Downvote
sgmwright said:
not yet, I'm just seeing it. Let me know your experience, I'll try it tomorrow
Click to expand...
I installed A31 hoping it would fix my C5–AB issue together with CAM.

But honestly, it feels like A30 with just the SATA fix.
Didn’t notice any changes in M.2 speeds, and overall things seem relatively stable.
 
Upvote 0 Downvote
Alyred said:
думаю, что именно A21 все еще обеспечивал полную скорость на M2, но с тех пор прошло уже столько обновлений...
Click to expand...
Most likely, they changed the M.2 lane priority to PCIe_1 with the release of the RTX 5xxx series and the related compatibility issues.

But that’s just my guess.
 
Upvote 0 Downvote
Install and memory re-config went ok, though took like 5 minutes to retrain the RAM once reset. Things seem to be running smoothly otherwise on A25. Still at -25 CO all core but we'll see how stability goes tonight.
 
Upvote 0 Downvote
RobsonByte said:
For me the A31 version shows the OA code during the boot and remains in this same code. I press the Power button, turn off the computer and turn it back. This way the boot happens normally.
Click to expand...
Unfortunately, this is now a "normal" situation. MSI hasn't been able to solve it since x570. It gets stuck at 00 and 0A, it boots again when you turn the system off and on, but when you try to restart it in Windows, it gets stuck again. loop :(
 
Upvote 1 Downvote
Anaksagoras said:
Unfortunately, this is now a "normal" situation. MSI hasn't been able to solve it since x570. It gets stuck at 00 and 0A, it boots again when you turn the system off and on, but when you try to restart it in Windows, it gets stuck again. loop :(
Click to expand...
Are you saying that this issue hasn’t been resolved for over 4 years?
😐
 
Upvote 0 Downvote
Anaksagoras said:
Unfortunately, this is now a "normal" situation. MSI hasn't been able to solve it since x570. It gets stuck at 00 and 0A, it boots again when you turn the system off and on, but when you try to restart it in Windows, it gets stuck again. loop :(
Click to expand...
According to the last change, BIOS A31 corrects only "HDD SATA shutdown when restarting", so I conclude that this benefit costs a regression, changing something that was working and was not corrected for 4 years.
 
Upvote 0 Downvote
pogdmm said:
Are you saying that this issue hasn’t been resolved for over 4 years?
😐
Click to expand...
Unfortunately, it is. Problems I have experienced personally. In my previous messages, I stated that I had the same problems with my x570 and x670e Carbon Wifi motherboard and the same problems with the motherboard I am currently using. If you search on the internet, you can see that the same problems have been experienced for years and have not been resolved. If you ask why you continued to buy if you are experiencing the same problems, I do not have a clear answer, I think it is like Stockholm syndrome. :)

 
Last edited:
Upvote 1 Downvote
Anaksagoras said:
Unfortunately, it is. Problems I have experienced personally. In my previous messages, I stated that I had the same problems with my x570 and x670e Carbon Wifi motherboard and the same problems with the motherboard I am currently using. If you search on the internet, you can see that the same problems have been experienced for years and have not been resolved. If you ask why you continued to buy if you are experiencing the same problems, I do not have a clear answer, I think it is like Stockholm syndrome. :)
Click to expand...
I bought MSI without knowing this problem, but even before I knew, I tried to buy from another brand, but where I live there is no other X870 motherboards and I was out of money. Who buys a brand full of unresolved problems? Stockholm syndrome can really explain, but the cases of people who don't know about the problems. They need to know ...
 
Upvote 0 Downvote
Anaksagoras said:
Unfortunately, this is now a "normal" situation. MSI hasn't been able to solve it since x570. It gets stuck at 00 and 0A, it boots again when you turn the system off and on, but when you try to restart it in Windows, it gets stuck again. loop :(
Click to expand...
One of the threads I was reading on that specified that the RAM's "power down mode" (under advanced memory timings/settings) needs to be enabled in BIOS to avoid this and cause Windows restarts to be more stable. I've had Power-down mode on "automatic" for a while and haven't seen this issue recur. To hopefully eliminate this as a possibility, what does everyone have this setting at?
Seeing my first "PCIe Speed regression" crop up on my A25+5080 installation. Since my resume from sleep this morning, it's been stuck at PCIe v4, even with the render test going.
1743447067561.png
 
Upvote 0 Downvote
This board has a mind of its own. I use Power Down Mode disable and after updating to BIOS version a31 the OA error started appearing on boot, but in the same way that the error started on its own, now it has stopped appearing.
 
Upvote 0 Downvote
RobsonByte said:
This board has a mind of its own. I use Power Down Mode disable and after updating to BIOS version a31 the OA error started appearing on boot, but in the same way that the error started on its own, now it has stopped appearing.
Click to expand...
Definitely so.

After another resume, it went back to PCIe 5.0, then down to 4.0 again after another sleep/resume, then when I tried sleeping and resuming again, the entire board crashed and rebooted while resuming the desktop. I'm not sure these new issues are due to the older BIOS or with the nVidia drivers being flaky with the 50 series...
 
Upvote 0 Downvote
Back
Top