MPG X870E CARBON WIFI Beta BIOS

Svet

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





>>> E7E49AMSI.1AA4 <<<

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

AGESA version:
agesa.jpg
 
Last edited:
I flashed this A42, should I be concerned?
If your system is functioning as expected, it is best to leave it as is; mine is working well, so I intend to do the same. I have noticed one issue in my case: if I do not unplug the USB hub with numerous USB devices connected and perform a CMOS clear, the system gets stuck on boot with the error code P01. Typically, when I perform a new BIOS flash, I ensure that everything except the necessary keyboard and mouse is unplugged. I have a significant number of devices connected via USB, including an external 20Gbps M.2 SSD.
 
I flashed it too, but I think there was a problem and it was removed from the site.
Not uncommon for MSI to behave this way they have done it in the past, which demonstrates how little respect they have for their customers. There was not a single note or explanation provided about why this happened or what should be done for those who upgraded from the official site. My guess is that they received negative feedback and, not wanting to be held accountable, simply removed it from the official page.
 
Would be nice with some more transparent communication in terms of these BIOS releases. It's weird they are released with zero commentary about what they actually do, have changed or what to even test for (the entire point of a beta?) and they also decide to pull them with not a single word.
 
I see why if you can't use overclock the ram when I was doing testing last night bios rev 40 ram use at 8000 works and passed all test I throw at it but on 42 would not ever post .
 
In my previous messages, I already mentioned that the A42 BIOS is broken. It’s almost funny — but true — it feels like MSI is using us as lab rats, or maybe their engineers have left the company and switched to farming instead. :) :) :)
One word sums up each launch = fiasco.
 
If your system is functioning as expected, it is best to leave it as is; mine is working well, so I intend to do the same. I have noticed one issue in my case: if I do not unplug the USB hub with numerous USB devices connected and perform a CMOS clear, the system gets stuck on boot with the error code P01. Typically, when I perform a new BIOS flash, I ensure that everything except the necessary keyboard and mouse is unplugged. I have a significant number of devices connected via USB, including an external 20Gbps M.2 SSD.
I'm having a couple of small issues with the A42 BIOS:
  1. 1 - PBO and Curve Optimizer: can't hold 10x scalar, +200 MHz boost, and -20 anymore. Even with -15, the system sometimes freezes — so for now, I’ve just enabled XMP and left it at that.
    2 - USB 2.0 with the Lian Li hub (Edge):
    is acting up. It’s interfering with two fans — their LCD screens keep freezing whenever I try to upload a GIF, and they constantly reset or go crazy.
 
I'm having a couple of small issues with the A42 BIOS:
  1. 1 - PBO and Curve Optimizer: can't hold 10x scalar, +200 MHz boost, and -20 anymore. Even with -15, the system sometimes freezes — so for now, I’ve just enabled XMP and left it at that.
    2 - USB 2.0 with the Lian Li hub (Edge):
    is acting up. It’s interfering with two fans — their LCD screens keep freezing whenever I try to upload a GIF, and they constantly reset or go crazy.
Interestingly, I, on the other hand, have no issues with PBO -30 + scalar 10X +200 boost and no USB ghosting on the same BIOS. What I don't understand is the inconsistency with the same board. However, there must be something fishy with this BIOS, which is why they pulled it from the download page.
 
Interestingly, I, on the other hand, have no issues with PBO -30 + scalar 10X +200 boost and no USB ghosting on the same BIOS. What I don't understand is the inconsistency with the same board. However, there must be something fishy with this BIOS, which is why they pulled it from the download page.
All cores CO -30? What processor do you have?
 
Last edited:
I'm using an A42, and maybe I just got lucky. I enabled PBO with +200, -30, temperature limit at 75°C, running 6000C28 RAM with 96GB. So far it's running normally, and it passes the R23 test.
 
Back
Top