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

---

 

[Alyred]

@Svet Hey, any chance we can get you to post a quick SHA256 hash for these betas (like the official releases) so that we know the BIOS file didn't get corrupted during download? Might help reduce some issues if folks can verify them before applying. Thanks!

 

[hms]

@Svet Hey, any chance we can get you to post a quick SHA256 hash for these betas (like the official releases) so that we know the BIOS file didn't get corrupted during download? Might help reduce some issues if folks can verify them before applying. Thanks!

You'll get warning if you try flash bios file thats checksum doesn't match.

 

[kekolopez55154a02d1]

Hi. I'm using the A95, and I only get error 0D occasionally... Would you recommend the A99? Thanks.

 

[Vendex_AMD]

Hi. I'm using the A95, and I only get error 0D occasionally... Would you recommend the A99? Thanks.

Go for it. A99 is much better at handling those 0d/0D memory training errors that pop up on A95. If you're getting them even occasionally, the new AGESA 1.3.0.1 should help stabilize things. I've been running -30 on my Curve Optimizer across several BIOS versions now, but A99 feels the snappiest so far. Definitely worth the update if you want to get rid of those random post codes

 

[kekolopez55154a02d1]

Go for it. A99 is much better at handling those 0d/0D memory training errors that pop up on A95. If you're getting them even occasionally, the new AGESA 1.3.0.1 should help stabilize things. I've been running -30 on my Curve Optimizer across several BIOS versions now, but A99 feels the snappiest so far. Definitely worth the update if you want to get rid of those random post codes

Hello.
Before installing A99, I reset the BIOS to factory settings by removing the battery and power cable. I installed A99, and everything was perfect, except that when I activate the EXPO profile, it gets stuck on C5/AB with a yellow light after restarting... I can't activate the EXPO profile. It's strange... Any suggestions?

 

[Vendex_AMD]

Hello.
Before installing A99, I reset the BIOS to factory settings by removing the battery and power cable. I installed A99, and everything was perfect, except that when I activate the EXPO profile, it gets stuck on C5/AB with a yellow light after restarting... I can't activate the EXPO profile. It's strange... Any suggestions?

C5 and AB are typical memory training hangs. Since you did a full reset, the board might just be struggling to apply the EXPO timings on the first try.
Try this: instead of just turning EXPO on, enable it and at the same time manually set memory context restore and power down enable to enabled. Also, give it a good 2 or 3 minutes on the first boot. Sometimes it looks stuck but it is actually training in the background. If it still fails, you might need to bump the soc voltage to 1.25V manually, as sometimes auto is not enough for the initial training on A99

 

[kekolopez55154a02d1]

C5 and AB are typical memory training hangs. Since you did a full reset, the board might just be struggling to apply the EXPO timings on the first try.
Try this: instead of just turning EXPO on, enable it and at the same time manually set memory context restore and power down enable to enabled. Also, give it a good 2 or 3 minutes on the first boot. Sometimes it looks stuck but it is actually training in the background. If it still fails, you might need to bump the soc voltage to 1.25V manually, as sometimes auto is not enough for the initial training on A99

Hi. I reinstalled A99 again (it only took a few seconds this time...) and everything is perfect now. Maybe it was a bug.

Edit: The SOC with the EXPO profile is always at 1.30v

 

[Vendex_AMD]

Hi. I reinstalled A99 again (it only took a few seconds this time...) and everything is perfect now. Maybe it was a bug.

Edit: The SOC with the EXPO profile is always at 1.30v

Glad to hear it! Sometimes these boards just need a second flash or a reboot to clear out the ghosts. AM5 can be quirky like that. Enjoy the new BIOS

 

[kekolopez55154a02d1]

Glad to hear it! Sometimes these boards just need a second flash or a reboot to clear out the ghosts. AM5 can be quirky like that. Enjoy the new BIOS

Hello. The C5 errors are back... I already tried the configuration you suggested, but it keeps freezing. I have a Ryzen 7 7800X3D, an XT 7900 XTX, and ram Corsair Expo 6000. I'm going back to A95. Regards.

 

[Vendex_AMD]

Hello. The C5 errors are back... I already tried the configuration you suggested, but it keeps freezing. I have a Ryzen 7 7800X3D, an XT 7900 XTX, and ram Corsair Expo 6000. I'm going back to A95. Regards.

Sorry to hear that, man. AM5 can be a real headache with ram compatibility sometimes. If A95 was stable for you, it is definitely smarter to stick with it for now. Not every BIOS works for every setup, especially with corsair kits. Hopefully the next official release fixes those C5 hangs for good on your 7800X3D

 

[kekolopez55154a02d1]

Sorry to hear that, man. AM5 can be a real headache with ram compatibility sometimes. If A95 was stable for you, it is definitely smarter to stick with it for now. Not every BIOS works for every setup, especially with corsair kits. Hopefully the next official release fixes those C5 hangs for good on your 7800X3D

No problem, my friend. Best regards, and thank you.

Edi: Thanks to your comment about RAM compatibility, I removed the Corsair Vengeance 6000MHz with the EXPO profile for AMD and installed G.Skill 7200MHz with a single XMP profile for Intel, and it works perfectly. Not a single freeze... nothing at all. I thought these Corsair modules specifically for AMD were more compatible...

 

[alexandru.mohor15c702e1]

Sharing my experience here with A99.

My specs are as follows:
CPU: 9800X3D @ 5.4 stable (PBO +175, CO -30 All cores), 360 AIO, 65C in gaming, 80C under full system stress
MB: Obviously X870E Carbon WiFi
RAM: 64GB G.Skill Trident Z5 Neo RGB 6000 MT/s with stock 30-40-40-96, running stable 28-36-36-64 CR1 @ 1.4V, VSOC 1.25, VDDIO 1.35, tREFI 65536 (A-Die). Temps don't go over 52C in gaming or high load.
GPU and the rest are less important here.

Anyway, I've been running smoothly A99 for 4 days, all my OC settings got accepted and everything seemed fine, until this morning when I started the PC and got stuck at code 00 with a green light near the debug panel. I know what yellow or yellow+red mean, but this one got me confused. The keyboard Num Lock button was responding but there was no screen activity - like a no POST but not quite.

What I've tried without any success:
- resetting CMOS, then let it cool down for a few minutes with PSU off and power cable unplugged,
- trying RAM one stick at a time + swapping them in their slots,
- removing all USB devices, all PCI-E cards,
- removing GPU,
- flashback with A99 again.

Nothing worked - it was like my MB was bricked or the BIOS crashed/ got corrupted somehow.
Finally, what did the trick was a flashback with A95 and now everything is fine again.

So while memory training was indeed smoother and faster in A99 with AGESA 1.3.0.1, I guess this BETA is still a work in progress. But really, it was the the most unusual thing I've experienced in the last couple of years. Glad that's over!

 

[kekolopez55154a02d1]

Sharing my experience here with A99.

My specs are as follows:
CPU: 9800X3D @ 5.4 stable (PBO +175, CO -30 All cores), 360 AIO, 65C in gaming, 80C under full system stress
MB: Obviously X870E Carbon WiFi
RAM: 64GB G.Skill Trident Z5 Neo RGB 6000 MT/s with stock 30-40-40-96, running stable 28-36-36-64 CR1 @ 1.4V, VSOC 1.25, VDDIO 1.35, tREFI 65536 (A-Die). Temps don't go over 52C in gaming or high load.
GPU and the rest are less important here.

Anyway, I've been running smoothly A99 for 4 days, all my OC settings got accepted and everything seemed fine, until this morning when I started the PC and got stuck at code 00 with a green light near the debug panel. I know what yellow or yellow+red mean, but this one got me confused. The keyboard Num Lock button was responding but there was no screen activity - like a no POST but not quite.

What I've tried without any success:
- resetting CMOS, then let it cool down for a few minutes with PSU off and power cable unplugged,
- trying RAM one stick at a time + swapping them in their slots,
- removing all USB devices, all PCI-E cards,
- removing GPU,
- flashback with A99 again.

Nothing worked - it was like my MB was bricked or the BIOS crashed/ got corrupted somehow.
Finally, what did the trick was a flashback with A95 and now everything is fine again.

So while memory training was indeed smoother and faster in A99 with AGESA 1.3.0.1, I guess this BETA is still a work in progress. But really, it was the the most unusual thing I've experienced in the last couple of years. Glad that's over!

Hi. The A99 was the only one where I had that 00 error, just once. Now it works perfectly.

 

[lzplzp00155602d3]

Hi. The A99 was the only one where I had that 00 error, just once. Now it works perfectly.

I'm experiencing this too, first boot，I updated the A99, but I am still encountering the 00 error. Also, the temperature is higher than my previous A7E, and the Cinebench R23 score is only 40946. I feel like it's not as good as 1A7E, idle temps are higher.

 

[dlomond]

Can you repost in English thanks

 

[Vendex_AMD]

Sharing my experience here with A99.

My specs are as follows:
CPU: 9800X3D @ 5.4 stable (PBO +175, CO -30 All cores), 360 AIO, 65C in gaming, 80C under full system stress
MB: Obviously X870E Carbon WiFi
RAM: 64GB G.Skill Trident Z5 Neo RGB 6000 MT/s with stock 30-40-40-96, running stable 28-36-36-64 CR1 @ 1.4V, VSOC 1.25, VDDIO 1.35, tREFI 65536 (A-Die). Temps don't go over 52C in gaming or high load.
GPU and the rest are less important here.

Anyway, I've been running smoothly A99 for 4 days, all my OC settings got accepted and everything seemed fine, until this morning when I started the PC and got stuck at code 00 with a green light near the debug panel. I know what yellow or yellow+red mean, but this one got me confused. The keyboard Num Lock button was responding but there was no screen activity - like a no POST but not quite.

What I've tried without any success:
- resetting CMOS, then let it cool down for a few minutes with PSU off and power cable unplugged,
- trying RAM one stick at a time + swapping them in their slots,
- removing all USB devices, all PCI-E cards,
- removing GPU,
- flashback with A99 again.

Nothing worked - it was like my MB was bricked or the BIOS crashed/ got corrupted somehow.
Finally, what did the trick was a flashback with A95 and now everything is fine again.

So while memory training was indeed smoother and faster in A99 with AGESA 1.3.0.1, I guess this BETA is still a work in progress. But really, it was the the most unusual thing I've experienced in the last couple of years. Glad that's over!

That sounds like a classic cold boot issue, which is still a bit hit-or-miss on the AGESA 1.3.0.1. Since your num lock was responding, the system actually passed the CPU/RAM initialization but got hung in a zombie state right before handing over to the OS.
Your ram timings are quite aggressive, especially that tREFI at 65536. While it might be stable under load at 52C, A99 seems more sensitive to memory training parameters during a cold start. I've been running A99 myself for a while now with a similar setup (9800X3D at -30 CO) and it's been perfectly stable, but I'm not pushing the RAM as tight as you are.
The fact that a flashback to A95 fixed everything proves your hardware is fine, but if you want to give A99 another shot later, maybe try backing off the tREFI or the CAS latency just to see if it clears that 00 code on boot

 

[Leefort]

Updated last week my bios from A60 to A95, no issues so far. Everyting seems to beheave exactly the same way. Don't really want to bother with beta A99, cuz it doesn't let me to install it from the bios GUI directly and I'm too lazy to get the USB stick stuff going. I guess I'll just wait for the next offical version.

 

[Vendex_AMD]

Updated last week my bios from A60 to A95, no issues so far. Everyting seems to beheave exactly the same way. Don't really want to bother with beta A99, cuz it doesn't let me to install it from the bios GUI directly and I'm too lazy to get the USB stick stuff going. I guess I'll just wait for the next offical version.

Stay on A95 then, it's a solid version. A99 is mostly about faster RAM training and some AGESA tweaks, but if you're happy with how it runs now, there's no point in the extra hassle with the usb stick. Better wait for the official non-beta release

 

[davidsalaskalendar912b102a5]

Sharing my experience here with A99.

My specs are as follows:
CPU: 9800X3D @ 5.4 stable (PBO +175, CO -30 All cores), 360 AIO, 65C in gaming, 80C under full system stress
MB: Obviously X870E Carbon WiFi
RAM: 64GB G.Skill Trident Z5 Neo RGB 6000 MT/s with stock 30-40-40-96, running stable 28-36-36-64 CR1 @ 1.4V, VSOC 1.25, VDDIO 1.35, tREFI 65536 (A-Die). Temps don't go over 52C in gaming or high load.
GPU and the rest are less important here.

Anyway, I've been running smoothly A99 for 4 days, all my OC settings got accepted and everything seemed fine, until this morning when I started the PC and got stuck at code 00 with a green light near the debug panel. I know what yellow or yellow+red mean, but this one got me confused. The keyboard Num Lock button was responding but there was no screen activity - like a no POST but not quite.

What I've tried without any success:
- resetting CMOS, then let it cool down for a few minutes with PSU off and power cable unplugged,
- trying RAM one stick at a time + swapping them in their slots,
- removing all USB devices, all PCI-E cards,
- removing GPU,
- flashback with A99 again.

Nothing worked - it was like my MB was bricked or the BIOS crashed/ got corrupted somehow.
Finally, what did the trick was a flashback with A95 and now everything is fine again.

So while memory training was indeed smoother and faster in A99 with AGESA 1.3.0.1, I guess this BETA is still a work in progress. But really, it was the the most unusual thing I've experienced in the last couple of years. Glad that's over!

Make sure to turn on your monitor manually before.

Been happening on A95 to me, if i dont have a monitor turned on, or in the GPU a DisplayPort, not hdmi, hdmi will sometimes refuse to give video if without a Display Port also being used.

 

[kkrott87]

Does anyone know how this motherboard is behaving with the new 9950x3d2?