MPG X870E CARBON WIFI Beta BIOS

Svet

🛠️ ⚙️⚒️
ADMIN
Joined
Nov 20, 2003
Messages
85,768
>>> 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)
7E49v1AA6:
BIOS SHA-256: 2AB2300AFF619FF690301FCCDBC615330A0DA9D80573D51627632968FD40FBF8
AGESA version:
Screenshot 2026-08-22 164345.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:
Thanks for posting the updates. This fixed the broken Per CCD core ratio overclocking. The core ratios are running at the multipliers set now and not 43.00 on all cores.
Hi @Svet just wanted to report a random bug I see with this 1A22 BIOS. Sometimes the UEFI display output during POST and in the BIOS is corrupted. Rebooting usually straightens it out. The scaling and wallpaper in the BIOS gets all messed up and text is fuzzy/blurry when it occurs and it remains until reaching the Windows desktop. Here is a screenshot example.

MSI_Advanced DRAM Co_[2025-01-03-08-24-52].jpg
 
Hi salute @Svet here @Tatili from Romania, please note from Here another Severe MSI thread, which is not kinda Severe one Tomahawk ~jokeing~jokeing
Pls can you open another clean MSIx870 Tomahawk thread for us, which wanna keep it kinda crystal clear for more needed further infos and stuff ...
Thx in advance, ciao grazie 🙏
 
Last edited:
With BIOS version 1A22 I get I/O errors on the 5GB network card if I disable the onboard sound card and it makes a mess with my PBO settings. Example: one of the cores runs with CO -11 with the sound card disabled and if I activate the sound card I have to raise the CO to +1 to be stable.
 
That sound like quite a mess @RobsonByte and it's weird that those would affect the CO values. I can't think of a good reason those should be related electrically. If I had to take a wild guess it is something they goofed up in the firmware itself.
 
That sound like quite a mess @RobsonByte and it's weird that those would affect the CO values. I can't think of a good reason those should be related electrically. If I had to take a wild guess it is something they goofed up in the firmware itself.
For me, every day that passes it becomes clearer that it is a BIOS programming problem. Because in version 1A23 many people are having problems that did not exist before. In my case it was the worst version I have ever tested, because the Motherboard became totally unstable to the point of freezing regardless of the settings I make, there is nothing that makes it stable, usable.
 
Sorry to hear you're having issues like that as well as others that are. I returned the X870E Carbon for a refund and an X870E Taichi before the Carbon. Both had design defect issues. The Carbon's issues all seem to be firmware bugs. The Taichi issues were illogical allocation of PCIe lanes that limited functionality and higher memory latency.

I am using an X670E Gene until I am able to acquire an X870E Apex.
 
Sorry to hear you're having issues like that as well as others that are. I returned the X870E Carbon for a refund and an X870E Taichi before the Carbon. Both had design defect issues. The Carbon's issues all seem to be firmware bugs. The Taichi issues were illogical allocation of PCIe lanes that limited functionality and higher memory latency.

I am using an X670E Gene until I am able to acquire an X870E Apex.
Apex is a good option, but today I saw news about PCI problems: it's literally breaking GPUs. The world of technology is living in dark days.
 
Apex is a good option, but today I saw news about PCI problems: it's literally breaking GPUs. The world of technology is living in dark days.
Thanks for saying something. I have not seen that so I will have to look for it. The Apex is still under development so hopefully it will be resolved before they go into production.
 
Last edited:
Apex is a good option, but today I saw news about PCI problems: it's literally breaking GPUs. The world of technology is living in dark days.
Thanks for saying something. I have not seen that so I will have to look for it. The Apex is still under development so hopefully it will be resolved before they go into production.
Is this what you are referring to, or something more catastrophic?
https://videocardz.com/newz/asus-pc...-may-scratch-your-gpu-first-rtx-5090-affectedhttps://www.techpowerup.com/331578/...icting-physical-damage-on-gpu-pcie-interfaceshttps://www.tomshardware.com/pc-com...-reportedly-damaging-some-gpu-pcie-connectors
 
Yeah, that's definitely not ideal. I wouldn't call it "breaking" GPUs but, best case scenario, causing physical damage like that is undesirable and unaesthetic. If a person took their GPU in and out of the slot on a frequent basis it could hurt the resale value of the GPU or void its warranty with the GPU manufacturer having it all scratched up like that. What would be humorous is if the motherboard and GPU are both made by ASUS and they end up having to foot the bill for replacing both. I'd still buy the Apex though. My 4090s will be out of warranty long before any surface scratches on the PCB ever matter. It's good that the contact fingers are not being affected by that ridiculous retention mechanism the clowns at ASUS decided to make. Things like that are truly worthy of severe punitive legal action. It's sad how all of the big names in tech act first, think later and just don't care. I'm starting to grow numb to how we are getting screwed over at every turn. AMD, Intel, NVIDIA, ASUS, MSI, Gigabyte, ASRock... all of them. All shady and greed-driven self-centered entities that ultimately don't really care about the quality of their products, the people that make them or the people that purchase them. The joke is on us for thinking anything different.
 
Last edited:
Back
Top