MPG X870E CARBON WIFI Beta BIOS

[Svet]

Spoiler: Older Versions

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

---

>>> E7E49AMSI.1A9B <<<

.rar SHA-256: 9eae3f5df43c2696e64ef329c6fddc45ba2e40ec0b529a9c451fa3871b077bff
BIOS SHA-256: 2B34A9B25DDEC186AC2272334DC2666C80082B143468A4D9D470BE88AB2C4CB4

AGESA version:

---

>>> E7E49AMSI.1AA2 <<<

.rar SHA-256: 3e1eec8ecdd717f7b694f7a82e704d4fb7ef54ad4f357fe5e28de6b9de422473
BIOS SHA-256: B1172777823B553168B6B1A14C57CAF7E7B48C259EBC43586B39C2A9BC4C8542

AGESA version:

---

Latest version: (from msi web page)
7E49v1AA3:
BIOS SHA-256: AF55A578CBDE8138906094F1CAD8C4C6A06639C4DAB23C0D7ACEA392326847AA
AGESA version:

---

>>> E7E49AMSI.1AA4 <<<

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

AGESA version:

---

Latest version: (from msi web page)
7E49v1AA7:
BIOS SHA-256: 060DCBFB7B80454820B56418A55255BEF9E79686C6CF43D1522D015AA5B82CFE
AGESA version:

---

---

---

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:

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

---

 

[RobsonByte]

I did some initial tests.
In version 1A23 the symptoms were:
- restart with error 0d, after a few times clearing CMOS the boot worked;
- automatic shutdown when using Topaz AI software;
- Very high optimized curves to achieve stability;
- Random freezes, including during internet browsing;

In version 1A24 the above problems have not happened yet, but I had a single "Ab" error after configuring the XMP of the memories (Team Group Xtreem, 48GB (2X24GB), DDR5, 8000MHz, C38, Black, FFXD548G8000HC38EDC01).

 

[Mr.Fox]

For some reason the 2x24GB kits have been less stable and not as performant (looser timings such as tRFC required) for me on the Taichi, Carbon and Gene. It took a while for Intel to get firmware optimized for these modules and either AMD has not given it adequate attention or there is something weird that just doesn't play as nice with Ryzen. I have a G.SKILL XMP 8000 48GB kit that would not boot on the Carbon with BIOS defaults (JEDEC). My TeamGroup Xtreem 8200 48GB kits (two of them) booted fine on the Carbon but always had minor errors when installed in the Carbon and slightly higher latency. They were stable in normal everyday use and only had minor errors in RAM stability tests, but the G.SKILL Trident Z 8000 Neo EXPO kit has been the best performing and most stable for me. I do not use the XMP and EXPO profiles, only custom manual tuning because the XMP and EXPO profiles are too sloppy, slow and high latency and the default XMP/EXPO profiles always use inadequate voltage for anything other than sloppy loose timings.

 

[RobsonByte]

First I'm going to stabilize the CPU and then change the memory settings. I see that it is necessary to better refine their settings. I have not yet been able to test if Wifi disappears after a system freeze, as this freeze has not happened yet.

 

[Alyred]

Overall the A24 ran fairly stable in Windows 24H2 for me last night after updating the firmware with a new Windows 11 24h2 installation. I'm running a 2x24 7200 kit from Corsair, though I downclocked it immediately to 6200 2:3 FCLK:UCLK and Memclock=UClock. Gave it a good 30m with OCCT with no errors but haven't tested it longer just yet.
This is with PBO off, currently.

 

[lysyn12155d02d4]

It works stably for me too.

 

[Alyred]

This is a brand-new machine I built and hadn't had time to put together, so I haven't put the A24 version on my production machine (the one in my sig). Plan on doing that over the next day or two assuming the new build stays stable.

 

[RobsonByte]

It works stably for me too.

Still stable around here, I couldn't reproduce the crash that won't let Wifi be recognized after crashing and restarting the PC.

 

[Alyred]

Still stable around here, I couldn't reproduce the crash that won't let Wifi be recognized after crashing and restarting the PC.

Ok, that's interesting. I did get a couple of crashes last night on the new A24 that made the wifi drivers vanish, but the Bluetooth device was still there. After powering down and restarting, the wifi came back and I realized that I had forgotten to install the driver. Once I installed the driver from the MSI website, it hasn't crashed since. I attributed it to the new nVidia drivers (1/30) but not sure.
I also backed off some of the RAM timings I had put in as they were a little bit high. Something caused a restart while it was asleep and then it restarted twice that day. But since ... it's been solid too.

 

[Svet]

Updated.

 

[Indabox]

Seems A24 is working ok for most of you. Has anyone tried the new A25 beta yet? I have been watching a few posts as i get my x870e carbon next Friday and all of this is making me very anxious haha. Will be pairing it with a 9800X3D and either TeamGroup 32gb kit CTCED532G6000HC30DC01 or Kinston Fury KF560C30BBEK2-32 and just want it to work

 

[Alyred]

Seems A24 is working ok for most of you. Has anyone tried the new A25 beta yet? I have been watching a few posts as i get my x870e carbon next Friday and all of this is making me very anxious haha. Will be pairing it with a 9800X3D and either TeamGroup 32gb kit CTCED532G6000HC30DC01 or Kinston Fury KF560C30BBEK2-32 and just want it to work

...didn't even see there was an A25 until your post. @Svet, is there any changelog for what to watch out for and why A24 got a fix so fast?

 

[RobsonByte]

With the A25 version I lowered the curves until it became unstable and the system froze. I just configured the curves again and the wifi didn't disappear. Before the wifi disappeared after the system crashed.

 

[Alyred]

Ah! So maybe that's the difference..... fixed wifi after the crashes!

 

[zonachristiany12280298]

A23 and A24 reducd Random write and read iops on Samsung 990 pro ..from normal 1.4 million to around 550k .. on a picture bellow you can see A23 A24 scores ..and last one of 1.4 mill i did when reversed back to A21

 

[Alyred]

A23 and A24 reducd Random write and read iops on Samsung 990 pro ..from normal 1.4 million to around 550k .. on a picture bellow you can see A23 A24 scores ..and last one of 1.4 mill i did when reversed back to A21

Yeah, mine are low too on A24, and kind of all over the place. My 990 in my top drive is showing results like yours, the 990 in my M2_3 slot is showing low sequential reads but higher IOPS and they can range by more than 100,000 between runs.
All on A24:

 

[RobsonByte]

I noticed crashes when activating the onboard sound card. Even if Wifi and Bluetooth remain activated, and the curves remain unchanged, I only have no crashes when activating the onboard sound card.
Edit: A25 is not behaving stably. I had random freezes. I went back to A24 and the freezes continued. I went back to A25 and set a lighter curve and now it is stable.

 

[WaNi]

Hello, I have tested both the a24 and a25 beta versions, and I must say that the a25 version is significantly more stable than the a24. I haven't experienced any issues since I started using the a25.

 

[Alyred]

I noticed crashes when activating the onboard sound card. Even if Wifi and Bluetooth remain activated, and the curves remain unchanged, I only have no crashes when activating the onboard sound card.
Edit: A25 is not behaving stably. I had random freezes. I went back to A24 and the freezes continued. I went back to A25 and set a lighter curve and now it is stable.

Every BIOS revision is going to change your curves and custom RAM timings some, and you need to find the new ideal settings. Running on that bleeding edge can definitely be effected when they change some of the underlying code.

Hello, I have tested both the a24 and a25 beta versions, and I must say that the a25 version is significantly more stable than the a24. I haven't experienced any issues since I started using the a25.

What instability were you experiencing with A24? I haven't hit any issues yet with it but I'm running fairly conservative PBO curves and OC at the moment with a max temp set to 85, All-core -15 and boost +100.

 

[RobsonByte]

E

Every BIOS revision is going to change your curves and custom RAM timings some, and you need to find the new ideal settings. Running on that bleeding edge can definitely be effected when they change some of the underlying code.

What instability were you experiencing with A24? I haven't hit any issues yet with it but I'm running fairly conservative PBO curves and OC at the moment with a max temp set to 85, All-core -15 and boost +100.

In version A24 the Wifi disappeared after restarting the system due to freezing. My configuration was done with negative curves individually on the cores. Generally used between 11 and 29 negatives, boost on 200+, temps 95c. The instability was random, with freezes. I want to see how far the rabbit hole goes.

 

[Alyred]

E

In version A24 the Wifi disappeared after restarting the system due to freezing. My configuration was done with negative curves individually on the cores. Generally used between 11 and 29 negatives, boost on 200+, temps 95c. The instability was random, with freezes. I want to see how far the rabbit hole goes.

95c is pretty high and definitely thermal throttling you.
I just got my separate system I'm building up to A25 and set the configs back to what I had them before on that board (It's going to be the Wife's machine but her current one is working fine, so I get to experiment a bit...) and it seems to be running stable. Drive speeds did improve some but not back up to the speeds that @zonachristiany12280298 was seeing - but read and write broke the 1.2m IOPS barrier on multiple attempts. I'm seeing really unusually high TBW for those drives, especially since one is completely empty, hasn't been used yet (just the 4 performance tests) and the TBW is already over 1TBW. Though I don't think that's the board's issue but something with Samsung.
Otherwise, it does seem fairly stable on A25 so far. My RAM came in slightly slower with the same settings as before (a couple of thousand MB/S transfer speed slower) and with a bit higher latency (.2ns, but that could be statistically insignificant). I'm running -20 curve on all cores with +200 Mhz boost clock at the moment, and while all cores will boost to the max 5425mhz a few of the cores averages are still showing around 5350's or so, so not able to maintain that boost for as long as some of the others that are able to maintain 5390+ average.
Temps don't break 73 on mine and set my max to 85 in the BIOS. But really not approaching that at all. So I probably have some headroom with my cooler there, but probably not going to push that too much because the wife just wants it to work and not fiddle with it once I'm done. Anyway, didn't see that slightly off boost performance in A23 or A24. But I'd say that's still fairly acceptable if it's stable.
Hopefully they can find a fixable issue with the NVMe ports for the speeds to get back to normal. A drive going through the chipset definitely shouldn't show better performance than one attached directly to the CPU.