MPG X870E CARBON WIFI Beta BIOS

Svet

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:
Sort by date Sort by votes
sheni_re154702d9 said:
(Nice way to work around the censorship 😁)
I come from ASUS and for comparison I am tracking the BIOS page of one of their premium (but not the most expensive) mobos. I am surprised how consistent they are with their releases (they had a BIOS with 1.3.0.1b a month ago and they released a new one with PatchA this week). I think that MSI can do better in this regards.
On the positive side, 1AA2 is quite stable so far and I even increased my overclock a tiny bit. I had no experience with test BIOSes (which are closer to alpha status maybe?) so far and I am really pleasantly surprised by it.
Click to expand...
They've been a bit further along than Alphas. They've largely worked but have had some definite bugs, though unsure if that was due to vibecoding parts of it at times or if the hardware in some of the boards (carbon wifi?) is just particularly hard to work with.
But I do agree... 1AA2 has been exceptionally stable and performant so far, though I haven't had time the last week to really put it through some burn-in paces as I had planned. Hopefully this upcoming week.
 
Upvote 0 Downvote
Hello good morning Svet, could you please notify msi to update the lan, wifi and bluetooth drivers of this motherboard since they have been stopped since 2025 that is more than a year, and also the amd chipset is stopped at 7.12 which is old for months and now we are already at 8.05 thank you very much for your time and thank you again that you release here at least the newest bios for this motherboard.... One last favour msi is working on a new VBIOS for the rtx 5080 msi Gaming trio oc do you know something maybe? Thanks again
 
Upvote 0 Downvote
gutashkam159902e0 said:
Hello good morning Svet, could you please notify msi to update the lan, wifi and bluetooth drivers of this motherboard since they have been stopped since 2025 that is more than a year, and also the amd chipset is stopped at 7.12 which is old for months and now we are already at 8.05 thank you very much for your time and thank you again that you release here at least the newest bios for this motherboard.... One last favour msi is working on a new VBIOS for the rtx 5080 msi Gaming trio oc do you know something maybe? Thanks again
Click to expand...
I think they are updating the actual files, but not updating the dates listed.
 
Upvote 0 Downvote
gutashkam159902e0 said:
Hello good morning Svet, could you please notify msi to update the lan, wifi and bluetooth drivers of this motherboard since they have been stopped since 2025 that is more than a year, and also the amd chipset is stopped at 7.12 which is old for months and now we are already at 8.05 thank you very much for your time and thank you again that you release here at least the newest bios for this motherboard.... One last favour msi is working on a new VBIOS for the rtx 5080 msi Gaming trio oc do you know something maybe? Thanks again
Click to expand...
While MSI should update what they can get (since they can often get them before we can, or in the case of audio, they're the only ones that get them) you can download the AMD and Realtek LAN drivers directly from the company websites. The qualcomm drivers are a bit tougher since there was so many problems with the Qualcomm drivers and chipsets for so long.
I was able to get somewhat newer Qualcomm drivers from one of the other motherboard manufacturers that have been working well.
 
Upvote 0 Downvote
Just updated to 1.AA3 with AGESA 1.3.0.1b Patch A. Put back all my usual settings (CO -30 to all cores, VSOC 1.25V, VDDIO 1.25V, global C-states enabled) and it works flawlessly.
Honestly, this feels like the fastest and most responsive BIOS yet. OS performance is instant and smooth as butter. Also disabled IOMMU since I don't use virtual machines, and everything booted right up with perfect signal integrity. Highly recommend this build!
 

Attachments

  • ZenTimings_Screenshot_29712348.2187111.png
    ZenTimings_Screenshot_29712348.2187111.png
    44.7 KB · Views: 111
Last edited:
Upvote 0 Downvote
Vendex_AMD said:
Just updated to 1.AA3 with AGESA 1.3.0.1b Patch A. Put back all my usual settings (CO -30 to all cores, VSOC 1.25V, VDDIO 1.25V, global C-states enabled) and it works flawlessly.
Honestly, this feels like the fastest and most responsive BIOS yet. OS performance is instant and smooth as butter. Also disabled IOMMU since I don't use virtual machines, and everything booted right up with perfect signal integrity. Highly recommend this build!
Click to expand...
Hello. How and where do I adjust these settings: VSOC 1.25V, VDDIO 1.25V, and Global C-states enabled? And how do I disable IOMMU?
 
Upvote 0 Downvote
kekolopez55154a02d1 said:
Hello. How and where do I adjust these settings: VSOC 1.25V, VDDIO 1.25V, and Global C-states enabled? And how do I disable IOMMU?
Click to expand...
Make sure to press F7 first to switch to Advanced mode. Here is the exact path for each setting on the X870E carbon:

1. VSOC and VDDIO voltages:
  • Go to the main OC section on the left and scroll down to the voltages.
  • Look for CPU VDDIO voltage and CPU NB/SoC voltage.
  • Change them from Auto to 1.250V (or 1.200V for VSOC, which is plenty for 6000MHz).
2. Global C-states:
  • Go to OC -> Advanced CPU configuration -> AMD CBS -> CPU common options.
  • Find global C-state control and switch it to enabled.
3. Disabling IOMMU:
  • Go to OC -> Advanced DRAM configuration.
  • Scroll all the way down to AMD CBS -> NBIO common options (right below the turn around timings).
  • Find IOMMU and change it from compatible mode to disabled.
Hit F10 to save and exit when you are done
:)
 
Upvote 0 Downvote
Vendex_AMD said:
Just updated to 1.AA3 with AGESA 1.3.0.1b Patch A. Put back all my usual settings (CO -30 to all cores, VSOC 1.25V, VDDIO 1.25V, global C-states enabled) and it works flawlessly.
Honestly, this feels like the fastest and most responsive BIOS yet. OS performance is instant and smooth as butter. Also disabled IOMMU since I don't use virtual machines, and everything booted right up with perfect signal integrity. Highly recommend this build!
Click to expand...
Agreed. Combined with the newest Windows preview update, everything feels way quicker than A95. I'm running 6000 MT/S right now because my 8000 OC kept memory training every boot, but going to try it again on this bios and see what happens. I've read that you can use lower voltages with this AGESA so hopefully that helps stabilize it.
 
Upvote 0 Downvote
sticks435 said:
Agreed. Combined with the newest Windows preview update, everything feels way quicker than A95. I'm running 6000 MT/S right now because my 8000 OC kept memory training every boot, but going to try it again on this bios and see what happens. I've read that you can use lower voltages with this AGESA so hopefully that helps stabilize it.
Click to expand...
If your 8000 MT/s profile keeps training on every boot, the motherboard is probably failing the quick boot checks and retraining for safety. On this new AGESA, you can definitely stabilize it with lower voltages, but you also need to force the training values to stick.

Try these settings in BIOS:
  1. Go to OC -> Advanced DRAM configuration -> find Memory context restore and set it to enabled (instead of auto).
  2. Right below it, make sure Power down enable is also set to enabled. (Normally for 6000 MT/s I keep Power down disabled for lower latency, but for 8000 MT/s with MCR turned on, keeping Power down enabled is pretty much mandatory to avoid blue screens).
For the voltages on AGESA 1.3.0.1b, you can usually drop VSoC to around 1.25V - 1.28V even for 8000 MT/s, which keeps the memory controller cooler and much more stable. Give it a shot!
 
Upvote 0 Downvote
Vendex_AMD said:
If your 8000 MT/s profile keeps training on every boot, the motherboard is probably failing the quick boot checks and retraining for safety. On this new AGESA, you can definitely stabilize it with lower voltages, but you also need to force the training values to stick.

Try these settings in BIOS:
  1. Go to OC -> Advanced DRAM configuration -> find Memory context restore and set it to enabled (instead of auto).
  2. Right below it, make sure Power down enable is also set to enabled. (Normally for 6000 MT/s I keep Power down disabled for lower latency, but for 8000 MT/s with MCR turned on, keeping Power down enabled is pretty much mandatory to avoid blue screens).
For the voltages on AGESA 1.3.0.1b, you can usually drop VSoC to around 1.25V - 1.28V even for 8000 MT/s, which keeps the memory controller cooler and much more stable. Give it a shot!
Click to expand...
My Kingston Fury Renegade 8000 LE CL36 runs smoothly and doesn't require retraining on every boot. All my usual tuning settings are working, and it seems that MSI has polished the BIOS for the X870E Carbon WiFi. Although I personally hold a grudge against MSI due to various support issues and unfriendly customer service, I have to admit my system is running better than ever.
 
Upvote 0 Downvote
Vendex_AMD said:
If your 8000 MT/s profile keeps training on every boot, the motherboard is probably failing the quick boot checks and retraining for safety. On this new AGESA, you can definitely stabilize it with lower voltages, but you also need to force the training values to stick.

Try these settings in BIOS:
  1. Go to OC -> Advanced DRAM configuration -> find Memory context restore and set it to enabled (instead of auto).
  2. Right below it, make sure Power down enable is also set to enabled. (Normally for 6000 MT/s I keep Power down disabled for lower latency, but for 8000 MT/s with MCR turned on, keeping Power down enabled is pretty much mandatory to avoid blue screens).
For the voltages on AGESA 1.3.0.1b, you can usually drop VSoC to around 1.25V - 1.28V even for 8000 MT/s, which keeps the memory controller cooler and much more stable. Give it a shot!
Click to expand...
I had MCR forced Enabled without Power Down mode for a day or so before I updated to 1AA3 and didn't get any blue screens. I was also running 1.11 VSOC since I was running in 2:1 mode. I'm going to try and exact same settings I had before with MCR set to Auto again and see what happens first.
 
Upvote 0 Downvote
sticks435 said:
I had MCR forced Enabled without Power Down mode for a day or so before I updated to 1AA3 and didn't get any blue screens. I was also running 1.11 VSOC since I was running in 2:1 mode. I'm going to try and exact same settings I had before with MCR set to Auto again and see what happens first.
Click to expand...
people running VSOC on 1.11 on 8000MT/s and wonder why the system is unstable or BSOD ? this is way below spec and I wouldn't run this voltage even on a 6000MT/s kit let alone 8000.
 
Upvote 0 Downvote
You must log in or register to reply.
Back
Top