MPG X870E CARBON WIFI Beta BIOS

Svet

Svet

Well-known member
Administrator
Joined
Nov 20, 2003
Messages
84,976
>>> 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 <<<
 
Last edited by a moderator:
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
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.
 
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
Back
Top