MPG X870E CARBON WIFI Beta BIOS

Svet

Svet

🛠️ ⚙️⚒️
ADMIN
Joined
Nov 20, 2003
Messages
85,694
>>> 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
 
Last edited:
Sort by date Sort by votes
sticks435 said:
Isn't all M-die currently 8000MT/S chips, just factory down-clocked to make it cheaper? I have 6400 M-die and can run 8000 no problem with manual tuning.
Click to expand...
Sort of. To hit 8000 Mt/s you need to run your memory controller clock at half the speed of your RAM, which can introduce latency even while increasing the bandwidth. Typically, you'll see better performance overall running 1:1 until you can stably support 8200-ish MT/s (I forget the exact number). The same chips can run both speeds, but they're binned differently, then put on the boards and the XMP timings are loaded to match. If you have large transfers but care less about latency (databases with large data fields) you'll see higher performance, but in gaming, lower latency is usually better in real world performance.
Again, this matters even less with x3d chips as there's less paging to RAM in many gaming scenarios.
If you have 6400 RAM, I'd run it with XMP and make sure the mclock is set to 1:1.
 
Upvote 0 Downvote
Alyred said:
Sort of. To hit 8000 Mt/s you need to run your memory controller clock at half the speed of your RAM, which can introduce latency even while increasing the bandwidth. Typically, you'll see better performance overall running 1:1 until you can stably support 8200-ish MT/s (I forget the exact number). The same chips can run both speeds, but they're binned differently, then put on the boards and the XMP timings are loaded to match. If you have large transfers but care less about latency (databases with large data fields) you'll see higher performance, but in gaming, lower latency is usually better in real world performance.
Again, this matters even less with x3d chips as there's less paging to RAM in many gaming scenarios.
If you have 6400 RAM, I'd run it with XMP and make sure the mclock is set to 1:1.
Click to expand...
Yeah, I tried 6400 and it doesn't want to work. 1.3vsoc even. Seems like my IMC is poo poo. Could try 6200 I guess.
 
Upvote 0 Downvote
sticks435 said:
Yeah, I tried 6400 and it doesn't want to work. 1.3vsoc even. Seems like my IMC is poo poo. Could try 6200 I guess.
Click to expand...
6400 at 1:1 is very hard to reach for AMD x3d chips.
If you can get it stable at 8000 and 6200, try some benchmarks and look at the latency, especially if you can push the CL and other tertiary timings to better numbers. Buildazoid has some "lazy" timings for Hynix A and M that can usually be set with decent stability on most AMD processors, though you may still need some tweaks due to the silicon lottery. For gaming, I'd take the lower of the two latencies as my daily driver.
 
Upvote 0 Downvote
Alyred said:
6400 at 1:1 is very hard to reach for AMD x3d chips.
If you can get it stable at 8000 and 6200, try some benchmarks and look at the latency, especially if you can push the CL and other tertiary timings to better numbers. Buildazoid has some "lazy" timings for Hynix A and M that can usually be set with decent stability on most AMD processors, though you may still need some tweaks due to the silicon lottery. For gaming, I'd take the lower of the two latencies as my daily driver.
Click to expand...
Yep, I have his 24Gb M-die spreadsheet that has timings and voltages for 6000 to 8000 and that is what I have been trying. So far my best was 8000 on the 1A95 bios, but I can no longer get that to be stable with agesa 1.3.0.1b which is why I'm at 6000 right now until I get more time to mess around with it.
 
Upvote 0 Downvote
For 8000 I have to use a little more vsoc 1.125 and memory 1.4 and vddp 1.05 also I am using version 1 setting that is what I am using. Also I don't use xmp I use memory try it at 8000 38.48.48.122 . And I also use the setting where u can select tighter timings. Forgot what it is call in the bios then I put the setting in for the ram timings.
 
Last edited:
Upvote 0 Downvote
dlomond said:
For 8000 I have to use a little more vsoc 1.125 and memory 1.4 and vddp 1.05 also I am using version 1 setting that is what I am using. Also I don't use xmp I use memory try it at 8000 38.48.48.122 . And I also use the setting where u can select tighter timings. Forgot what it is call in the bios then I put the setting in for the ram timings.
Click to expand...
Yeah, I was running 1.1vsoc with 1.45 memory and 1.05 vddp like you. I just manually set all the timings after setting mem/fclk on the main OC settings page, but might have to try 1.125 with this new bios.
 
Upvote 0 Downvote
I have installed the new bios for now everything is perfect except for msi centre that I have already done 3 times the update to PD FW update and every time I come back I find it to do, I did the one requested that is to unplug 5 minutes and turn the pc back on but it is not successful, then I tried with 10 minutes and then still waiting 20 minutes but does not want to know, instead the other two updates (usb 4 PD FW update and usb4 FW update) of which one equal to this one that you have to disconnect the power outlet Were successful at the first time, no one knows how to solve it? Thanks again to those who help me
 
Upvote 0 Downvote
gutashkam159902e0 said:
I have installed the new bios for now everything is perfect except for msi centre that I have already done 3 times the update to PD FW update and every time I come back I find it to do, I did the one requested that is to unplug 5 minutes and turn the pc back on but it is not successful, then I tried with 10 minutes and then still waiting 20 minutes but does not want to know, instead the other two updates (usb 4 PD FW update and usb4 FW update) of which one equal to this one that you have to disconnect the power outlet Were successful at the first time, no one knows how to solve it? Thanks again to those who help me
Click to expand...
I have the same issue. Did the PD FW update a few weeks back, ran a check again this week and it was back and said it was on the same version as before. Pretty sure it's just bugged at this point and will have to wait for them to release a new version.
 
Upvote 0 Downvote
sticks435 said:
I have the same issue. Did the PD FW update a few weeks back, ran a check again this week and it was back and said it was on the same version as before. Pretty sure it's just bugged at this point and will have to wait for them to release a new version.
Click to expand...
Thanks again, we hope they release a new version or a fix as soon as possible..
 
Upvote 0 Downvote
It's possible that your security program is blocking part of the update, preventing it from completing. I had significant issues with Bitdefender, as it flagged the update as dangerous. Even after disabling Bitdefender completely, I still couldn't update the two PD firmware files. I had to uninstall Bitdefender entirely, complete the update, and then reinstall Bitdefender Total Security. You might be experiencing a similar issue without realizing it.
 
Upvote 0 Downvote
Back
Top