MPG X870E CARBON WIFI Beta BIOS

Svet

Svet

🛠️ ⚙️⚒️
ADMIN
Joined
Nov 20, 2003
Messages
85,902
>>> 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



>>> 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



>>> E7E49AMSI.1AA4 <<<

.rar SHA-256: 501a027d7cc8d1016f0164a0e7ec5a5f1cf39a32c13ad90af2c70e3dc90bfce2
BIOS SHA-256: 2A98DA827D82FF800397AF901680995D5481DC7DE8D62BAB6890DB9119C472F7

AGESA version:
agesa.jpg



Latest version: (from msi web page)
7E49v1AA7:
BIOS SHA-256: 060DCBFB7B80454820B56418A55255BEF9E79686C6CF43D1522D015AA5B82CFE
AGESA version:
Screenshot 2026-09-23 003104.jpg





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

Aside from this you can check AGESA version of the BIOS File,
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 with the tool,
it will ensure the BIOS File's integrity on the USB key of both Checksum and SHA256.
This also will ensure your USB key used is not damaged or corrupted prior flashing
regardless of the flashing method.
_
 
Last edited:
Sort by date Sort by votes
dlomond said:
I had to go back to 64 my video card slot would downclock never had the problem before only way to fix it was to restart. did a bios flashback to 64. I did not remove any parts .
Click to expand...
Mine never did on earlier BIOSes either, but somewhere along the way (A29?) It started to do so and now does it occasionally ever since. Hopefully the rollback fixes it for you.
If not, try turning on spread Spectrum. That reduces the problem to 1 in 20 times or so.
 
Upvote 0 Downvote
Svet said:
They been taken down due to critical bug been found.
Click to expand...
Is it possible to know what serious error it is? Mainly for those of us on version 79, to know whether we should be concerned and change the BIOS. Thanks in advance, and happy holidays
 
Upvote 0 Downvote
dlomond said:
You have to stay on. It now .if you want to go back you have to bo bios flashback but that is at your own risk I know I did it and another user did it so it works.
Click to expand...
Just wanted to share that I successfully rolled back from beta BIOS version A79 to A70 without any issues. The process was smooth and everything is working fine now
 
Upvote 0 Downvote
DarkOmenX said:
the A75 was broken in a way , A79 works perfectly fine and the rest I didn't care to try whatever your issues are could be more to your setup then "bad bios"
Click to expand...
My hardware [ryzen 9800x3d, gpu rtx5080 asus, my dac smsl su9, creative SB AE9, Ram 128gb(4x32gb) Klevv crass V RGB 6400] with bios A79 error stuck at 00, after flash A79 and I cannot enter bios at all, stuck at 00.
 
Upvote 0 Downvote
jankmail15af02e1 said:
My hardware [ryzen 9800x3d, gpu rtx5080 asus, my dac smsl su9, creative SB AE9, Ram 128gb(4x32gb) Klevv crass V RGB 6400] with bios A79 error stuck at 00, after flash A79 and I cannot enter bios at all, stuck at 00.
Click to expand...
this is too many bios wrong in your case "Happy Birthday broken bios [A71,A75,A78,A79]" so which one you are running now? 79 works excellent on my system:
Carbon Wifi+9800X3d+48 GB Kingston Fury Renegade CL36 8000@8000 , RTX5090LiquidSOC, SB AE-5 Plus, 3 X M.2 SSD
 
Upvote 0 Downvote
DarkOmenX said:
this is too many bios wrong in your case "Happy Birthday broken bios [A71,A75,A78,A79]" so which one you are running now? 79 works excellent on my system:
Carbon Wifi+9800X3d+48 GB Kingston Fury Renegade CL36 8000@8000 , RTX5090LiquidSOC, SB AE-5 Plus, 3 X M.2 SSD
Click to expand...
If the reason they pulled A79 was due to the AMD Microcode needing patching, that looks like it's only going to effect 16 and 32 bit versions of random seed generators on Linux, which would likely have very limited impact in a Windows environment. So A79 can still be "broken" but not impact your system.
Unfortunately, there's never a good way to know exactly why it was pulled, just that Svet stated the reason it was pulled was because there was a critical bug found.
Hopefully it's true and the critical bug in A79 is limited to a configuration that isn't used too often.
 
Upvote 0 Downvote
Alyred said:
If the reason they pulled A79 was due to the AMD Microcode needing patching, that looks like it's only going to effect 16 and 32 bit versions of random seed generators on Linux, which would likely have very limited impact in a Windows environment. So A79 can still be "broken" but not impact your system.
Unfortunately, there's never a good way to know exactly why it was pulled, just that Svet stated the reason it was pulled was because there was a critical bug found.
Hopefully it's true and the critical bug in A79 is limited to a configuration that isn't used too often.
Click to expand...
They pulled 75, not 79; 79 came later from Svet, and 75 was quite buggy. I switched from 64 to 75, which was on the official download page, but ran into issues. I then switched back to 64, and once Svet introduced 79, I decided to update to it, and it works great now.
 
Upvote 0 Downvote
DarkOmenX said:
They pulled 75, not 79; 79 came later from Svet, and 75 was quite buggy. I switched from 64 to 75, which was on the official download page, but ran into issues. I then switched back to 64, and once Svet introduced 79, I decided to update to it, and it works great now.
Click to expand...
They pulled both 78 & 79, if you look just a few posts back
 
Upvote 0 Downvote
DarkOmenX said:
Svet obviously pulled them, but the first one on the official page was 75, which MSI removed. Svet can add and remove whatever he wants because these are not released on the official download page.
Click to expand...
Huh, strange. I'm not seeing A79 at the top of this forum post anymore, and the conversation from earlier was someone asking why 78/79 was removed. Are you seeing it elsewhere on MSI's sites as an officially working version?
The chatter in this forum was that it was likely taken down to the 16/32 bit RNG values being bad in Linux applications, though again, never verified by anyone connected to MSI.
 
Upvote 0 Downvote
I compared BIOS versions A64 and A79. With the exact same OC settings, A64 boots fine, but A79 just hangs on post code 15. I had to roll back to A64—seems like it’s the most stable build for now.
 
Upvote 0 Downvote
You must log in or register to reply.
Back
Top