MPG X870E CARBON WIFI Beta BIOS

Svet

🛠️ ⚙️⚒️
ADMIN
Joined
Nov 20, 2003
Messages
85,906
>>> 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)
7E49v1AA7:
BIOS SHA-256: 060DCBFB7B80454820B56418A55255BEF9E79686C6CF43D1522D015AA5B82CFE
AGESA version:
Screenshot 2026-09-23 003104.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:
To be honest, for me, all this is just for fun of tweaking something. I am playing at 4K with 5090, 120fps locked with Xbox Elite Controller. Process lasso, Xbox app, core parking or without, I do not see difference ;) I am using my comps for work 90%.
Honestly, the difference is negligible in most games. Really, it's strategy games or city simulators that seem to affect the most.
 
Unfortunately manually overriding amds options are the best way to squeeze some extra performance out of games since not every game will be faster due to X3D tech. Others still have better luck with higher clock speeds which the CCD1 will provide over CCD0. It really depends on how memory is handled in some game engines compared to others too. Latency and huge cache isn't the only factor for performance. It's more of a general marketing trick. It helps performance in some scenarios but not all. The X3D dies can't always achieve the same frequency that non X3D dies can due to cache sensitivity.
VDDP .950 1.3 SOC
 
This is my current memory timings across 4 DIMM's. I think that's a plus for this motherboard, really, since it seems to handle memory quite well. Yes, that's also due to me having a pretty strong IMC on my CPU, but still, I think it's pretty good on the motherboard's end. The only thing I don't like about testing is that if the board fails posting, there is no auto revert to stock while keeping the settings available to the user. So you have to keep saving profiles and clearing CMOS. It's a bit of a pain in that regard.
1747328559901.png
 
This is my current memory timings across 4 DIMM's. I think that's a plus for this motherboard, really, since it seems to handle memory quite well. Yes, that's also due to me having a pretty strong IMC on my CPU, but still, I think it's pretty good on the motherboard's end. The only thing I don't like about testing is that if the board fails posting, there is no auto revert to stock while keeping the settings available to the user. So you have to keep saving profiles and clearing CMOS. It's a bit of a pain in that regard.
VSOC 1.26-1.27 seems to be the sweet spot, at least for me. I think a lot of XMP settings put it at 1.3 though.
You're pushing your voltage a bit on those sticks (specced at 1.35v), are you seeing any temperature issues? Are you using any active RAM cooling?
ZenTimings always shows my CPU VDDIO at .8000v, but I see yours at .8500v. Did you set that manually? I assumed that it just wasn't reading the timing properly in the software...
Edit: Realized I typoed my VSOC.
 
Last edited:
This is my current memory timings across 4 DIMM's. I think that's a plus for this motherboard, really, since it seems to handle memory quite well. Yes, that's also due to me having a pretty strong IMC on my CPU, but still, I think it's pretty good on the motherboard's end. The only thing I don't like about testing is that if the board fails posting, there is no auto revert to stock while keeping the settings available to the user. So you have to keep saving profiles and clearing CMOS. It's a bit of a pain in that regard.
View attachment 201993
can you post your aida64 mem bench scores?
 
VSOC 1.26-1.27 seems to be the sweet spot, at least for me. I think a lot of XMP settings put it at 1.3 though.
You're pushing your voltage a bit on those sticks (specced at 1.35v), are you seeing any temperature issues? Are you using any active RAM cooling?
ZenTimings always shows my CPU VDDIO at .8000v, but I see yours at .8500v. Did you set that manually? I assumed that it just wasn't reading the timing properly in the software...
Edit: Realized I typoed my VSOC.
No active cooling on the DIMM's apart from general case airflow. The temps, I believe, are not too bad. I forgot to turn them down to 1.43v, and yes, they are speced at 1.35, but they had issues running at that with the expo profile. As for the VDDIO, it has to be read wrong. I believe VDDIO is higher than that. On the VDDG, my IO voltages are at 1.020v and 1.060v, respectively.

Edit:
In regards to temperature, the GSKILL RAM I have found doesn't really have much issue keeping cool at highish temps. I could go down to 1.42v with my current settings, but that's not enough for these pushed timings. I'm getting no errors with my current setup, but I will have to double-check temps. I wouldn't consider, from what I've read online, that 1.45 is high compared to others I've seen by buildzoid and other RAM overclockers. They did not mention having specified cooling on the DIMM's apart from when it was running at 1.5V+
 
There seems to be a common misunderstanding about voltages, how they work, and their impact on a system. Keep in mind that some voltages should not be tampered with, as they are directly related to current, temperature, and how the chipset manages adjustments during workloads or idle states.
 
There seems to be a common misunderstanding about voltages, how they work, and their impact on a system. Keep in mind that some voltages should not be tampered with, as they are directly related to current, temperature, and how the chipset manages adjustments during workloads or idle states.
Agreed. Base reference voltages should not be messed with. My RAM, after reducing the voltage down to 1.37v, is pretty cool. I've seen the hottest DIMM reach 66.4 degrees, but that's on a constant AIDA stability test.
 
Same here.
Right at the SECOND MSI Logo where the OS is should load. And only on cold boot, restarts are fine.

But at least 7E49v1A3 works perfect for me.
New official BIOS, same cold boot bug as the one before. Aaaand back to 7E49v1A3.

I’m starting to think it’s because of the Agesa Version
 
can you post your aida64 mem bench scores?
Sure! Sorry for taking so long. I was sorting some stuff out. Also, my FSB is at 99.2 MHz for some reason. It changes every boot between 99 MHz and 101.4 MHz. Latency changes between 67.2 ns to 70.8 ns randomly. Thats super dependent on what ever is going on in the background.

1747421860602.png
 
Hi there!
Any news on fixing the PCIE related bug?
Is it supposed to be fixed by the 7E49v1A4 official BIOS (the description on the download page is kinda vague)?
Thanks!
 
Last edited:
Hi there!
Any news on fixing the PCIE related bug?
Is it supposed to be fixed by the 7E49v1A4 official BIOS (the description on the download page is kinda vague)?
Thanks!
no issues with PCIe lines here but to be fair I never ever experienced any issues from day one I put this build together:
MPG X870e Carbon WIF+9800X3D+msi 5090 Liquid SOC (before msi4090 Liquid X) +48GB Corsair TITANIUM 7200@6400 + 2 GEN4 SSD +1 GEN5 SSD
 
Back
Top