MPG X870E CARBON WIFI Beta BIOS

Svet

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:
Sort by date Sort by votes
kkrott87 said:
lol...
Click to expand...
but on a serious note, might be voltage sensing.. (due to BIOS?) or due to contacts.. (less likely since we assume they worked before the update). wild suggestion to rule out L1.
Layer 1 tshoot, clean all the contacts on the series of serial connections between the problem black magic fans?
 
Upvote 0 Downvote
Hello all,
I also had the "PCI-express low version lock" when booting which meant heavy stuttering in Windows (and unexpected resets if I waited long enough) unless I rebooted.
I solved it a few weeks ago by increasing my SoC Voltage to 1.280 in my case (AMD Overclocking). If I set the voltage lower than that, the lower I go the more chances I have of booting with the heavy stuttering. I have my memory set to 6400MT/s and tight timings.
If you suffer from this issue I would suggest increasing the SoC voltage. From what I've read, up to 1.3V should be safe.
 
Upvote 0 Downvote
juan.delgado.riguera152d02cc said:
Hello all,
I also had the "PCI-express low version lock" when booting which meant heavy stuttering in Windows (and unexpected resets if I waited long enough) unless I rebooted.
I solved it a few weeks ago by increasing my SoC Voltage to 1.280 in my case (AMD Overclocking). If I set the voltage lower than that, the lower I go the more chances I have of booting with the heavy stuttering. I have my memory set to 6400MT/s and tight timings.
If you suffer from this issue I would suggest increasing the SoC voltage. From what I've read, up to 1.3V should be safe.
Click to expand...
Can you show a screen shot of where in the bios you raised your Voltage*(SOC). The fields are named different. Not sure if you are referring to the CPU or NB line. Are you using PBO with PBO limits x10 and +200 ?
 
Last edited:
Upvote 0 Downvote
Bizkitca156902da said:
but on a serious note, might be voltage sensing.. (due to BIOS?) or due to contacts.. (less likely since we assume they worked before the update). wild suggestion to rule out L1.
Layer 1 tshoot, clean all the contacts on the series of serial connections between the problem black magic fans?
Click to expand...
Yeah, they've been working fine on A30 and the one before that that I don't remember which was. Yep, PBO x10 +200 and CO -15
 
Upvote 0 Downvote
Bizkitca156902da said:
Can you show a screen shot of where in the bios you raised your Voltage*(SOC). The fields are named different. Not sure if you are referring to the CPU or NB line. Are you using PBO with PBO limits x10 and +200 ?
Click to expand...
Sure, this is the SOC voltage I'm referring to:
1748944273754.png


I'm using PBO as well indeed, with scalar x5, +200 boost clock and negative 33 all core curve.
 
Upvote 0 Downvote

Attachments

  • IMG_20250601_113756.jpg
    IMG_20250601_113756.jpg
    478.6 KB · Views: 95
  • IMG_20250601_113715.jpg
    IMG_20250601_113715.jpg
    478.8 KB · Views: 95
  • 1000003917.jpg
    1000003917.jpg
    214.4 KB · Views: 92
  • IMG_20250601_114506.jpg
    IMG_20250601_114506.jpg
    532 KB · Views: 88
  • IMG_20250601_114452.jpg
    IMG_20250601_114452.jpg
    537.4 KB · Views: 96
  • IMG_20250603_145241.jpg
    IMG_20250603_145241.jpg
    444.2 KB · Views: 104
Last edited:
Upvote 0 Downvote
Bizkitca156902da said:
I was rounding up 5.425 is the actual number. I did clear CMOS 3 times, after installing the new RAM.
The RAM is just running EXPO profile.

So far the mouse lag has only occurred 3 out of 20+ boots.


If it keeps happening I will turn down the FCLK OC to start with.
Click to expand...
Yes, that's about right. I have a similar setup with an MSI 5090 Liquid SOC+ Carbon Wifi+ 9800X3d, and I haven’t experienced any issues, even with older BIOS versions. However, touching the BUS causes problems; even setting it to 102 makes my system unstable, so I avoid it. Adjusting the BUS affects more than just the VGA or general CPU; it also impacts SSDs, making it difficult to pinpoint the exact component that doesn't respond well. With three M.2 SSDs and a Soundblaster AE-5, troubleshooting becomes a bit complex and time-consuming. I find that leaving the BUS on auto and using PBO tuning works best for me. Like you, I'm reaching 5.425, and it works nicely. I also have Corsair TITANIUM 48GB 7200, but I'm running at 6400CL32 + 2200 FLCK.
As I mainly play DCS and sometimes have to be online and in the air for hours, I don't want my system crashing or being unstable, producing stuttering just to get an extra 100 or 200 MHz, which in reality doesn't even give a single FPS more. I was able to push my CPU to 5.6 GHz, or close to it, but it wasn't stable enough. While some games run perfectly fine long-term, others don't, especially DCS, which tends to stutter, freeze, and eventually crash altogether.
 
Upvote 0 Downvote
Bizkitca156902da said:
Thank you, so I found people using 'AMD Overclocking' vs 'Override' not sure what the difference is.
Click to expand...
AMD overclocking you can let it deliver an "auto setting" (that would fluctuate and probably be a little more aggressive than the simple auto mode), whereas override is a fixed voltage. (you can also set a fixed voltage with AMD overclocking setting, but I don't see the point in doing that)
 
Upvote 0 Downvote
Tr
juan.delgado.riguera152d02cc said:
Hello all,
I also had the "PCI-express low version lock" when booting which meant heavy stuttering in Windows (and unexpected resets if I waited long enough) unless I rebooted.
I solved it a few weeks ago by increasing my SoC Voltage to 1.280 in my case (AMD Overclocking). If I set the voltage lower than that, the lower I go the more chances I have of booting with the heavy stuttering. I have my memory set to 6400MT/s and tight timings.
If you suffer from this issue I would suggest increasing the SoC voltage. From what I've read, up to 1.3V should be safe.
Click to expand...
Try changing spread spectrum from auto to "enabled" and see if it fixes it. Doing that did for me.
 
Upvote 0 Downvote
Indabox said:
Tr

Try changing spread spectrum from auto to "enabled" and see if it fixes it. Doing that did for me.
Click to expand...
I tested that to no avail due to the comments in this thread, both enabled and disabled the issue persisted for me until I increased the SoC voltage. I actually have spread spectrum disabled for a few weeks now and haven't had the issue.
 
Upvote 0 Downvote
danvisinic153902d9 said:
Address Hash Bank + CS Enabled, Swap Apu
Click to expand...
Maybe that was some issue with older BIOS? I see you're using build from January. I have latest beta (A41) on my Carbon and enabling first option didn't make any noticeable difference. Enabling CS and setting Swap Apu resulted in not booting.
Still trying to get stable OC system with this BIOS. Months ago I had old BIOS (A1A), got it to be super stable 10+h stress tests, but I didn't have tight OC.
A33 felt worse. now on A41 I can get up to 2h of VT3 in y-cruncher, most benchmarks similar to what was on A1A, but now with lower latency. I have a feeling that something with CO handling changed between A1A and A41, I have to reduce negative values to make it more stable.
 
Upvote 0 Downvote
kkrott87 said:
This A41 BIOS update broke my Lian Li LCD wireless fans. Strangely, only one set of three fans connected in a daisy chain keeps disconnecting and reconnecting, while the other set of three works perfectly fine.

EDIT

I was stupid enought to not see that the data cable of the fans was loose.
Click to expand...
Just updating you guys. Please disconsider this. The data cable came loose for some reason. Everything is fine now

EDIT------

I was actually right. The data cable wasn't loose. The problem persists.
 
Last edited:
Upvote 0 Downvote
Blackbird7 said:
Maybe that was some issue with older BIOS? I see you're using build from January. I have latest beta (A41) on my Carbon and enabling first option didn't make any noticeable difference. Enabling CS and setting Swap Apu resulted in not booting.
Click to expand...
Sorry, my bad, don't think always new betas are an upgrade, Address Hash Bank + Hash CS Enabled & Swap Apu they did something
1000004102.png

Blackbird7 said:
Still trying to get stable OC system with this BIOS. Months ago I had old BIOS (A1A), got it to be super stable 10+h stress tests, but I didn't have tight OC.
A33 felt worse. now on A41 I can get up to 2h of VT3 in y-cruncher, most benchmarks similar to what was on A1A, but now with lower latency. I have a feeling that something with CO handling changed between A1A and A41, I have to reduce negative values to make it more stable.
Click to expand...
Yeah, all new released Bioses are tricky and results can much vary, coz too much diff. cpu, mobo, mems in combo's are, too more diff. stability issues you'll find cause still imature Agesa's behavoir are going to be tested first on our rigs, before launch, no worries about new 1.2.0.3d will shown soon :censored:
It is a long term date I can only guess before a non-beta stable Agesa vers AMD will be able to fix in a final version for all our rigs, parts, scenarios & stuff, especially in mems OC nomad land DDR5 frequencies territory
Since I was flashed all new released Bios version, through I found nothing works stable with my same OC profile, I'll stick with A24 1.2.0.3aPatchA for my best one Profile setup (y)
CPU clocks 5,5-5,7 mem 8045mhz PBO Limit Manual 225/125/205 Boost+150 CO-20ALL
Screenshot (705).png
 
Last edited:
Upvote 0 Downvote
Everyone writing about CO -20 or even lower, but I managed to get my 9800X3D stable on +200 boost only with CO per core, in range 0 to -12. I guess I had very bad luck with getting so bad silicone. Maybe I could get more from it with lowering boost, I see you have +150, or play with curve shaper. But when I tried that, I just made it worse.
I'll do bit more tuning and hope new BIOS will be available soon and get me some improvements.
This is current config... It looks like FCLK 2133 was causing some rare freezes, after I reduced it to 2066, mem benchmark is slightly worse (2%), but I did lower some timings and that reduced latency about 2%.
1749064443973.png
 
Upvote 0 Downvote
Back
Top