MPG X870E CARBON WIFI Beta BIOS

Svet

Svet

🛠️ ⚙️⚒️
ADMIN
Joined
Nov 20, 2003
Messages
85,768
>>> 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)
7E49v1AA6:
BIOS SHA-256: 2AB2300AFF619FF690301FCCDBC615330A0DA9D80573D51627632968FD40FBF8
AGESA version:
Screenshot 2026-08-22 164345.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:
Sort by date Sort by votes
FYI, I think this BIOS killed my 5Gbps ethernet port. PC came out of sleep this morning and now that port can't find my router. 2.5 port works fine. I tried disabling/re-enabling device in Device Manager, uninstalling the recent Windows preview update, flushing DNS cache, reflashing 1AA3, uninstalling device and scanning for new.
 
Upvote -1 Downvote
Also if that don't work do the same thing bit clean CMOS bottom and unplug power and press power the clear all light of motherboard ten power it back on. Try the first way first.
 
Upvote 0 Downvote
Yeah, I found a thread on reddit about this same issue from last year and using the CMOS clear button worked. Never had an issue with it in the year and a half I've been using it.
 
Upvote 0 Downvote
sticks435 said:
You mean press and hold power for like 10-30 seconds?
Click to expand...
Yeah, it lets any lingering power in the capacitors drain, and can allow some stuck hardware reset that otherwise still hadn't been completely powered off. I've seen those RealTek NICs do that multiple times, even a cold restart won't fix it unless you let it wait with the power off for 10-15 minutes.
If you didn't do a full BIOS reset after upgrading that kind of thing can cause it too woth old bits still hanging around in the firmware of those ICs.
 
Upvote 0 Downvote
Doesn't flashing the BIOS restore factory defaults anyway? It also worked fine for like a day on the new bios, then it came out of sleep and stopped working haha.
Alyred said:
Yeah, it lets any lingering power in the capacitors drain, and can allow some stuck hardware reset that otherwise still hadn't been completely powered off. I've seen those RealTek NICs do that multiple times, even a cold restart won't fix it unless you let it wait with the power off for 10-15 minutes.
If you didn't do a full BIOS reset after upgrading that kind of thing can cause it too woth old bits still hanging around in the firmware of those ICs.
Click to expand...
 
Upvote 0 Downvote
sticks435 said:
Doesn't flashing the BIOS restore factory defaults anyway? It also worked fine for like a day on the new bios, then it came out of sleep and stopped working haha.
Click to expand...
Theoretically, yes. But sometimes the coders don't overwrite all the memory locations with default values, so old stuff might still be in there from the previous BIOS that now means something completely different in the new BIOS.
Best practice to make sure everything gets overwritten and set to default is to do a full CMOS reset and then set to BIOS defaults immediately after flashing, just in case.
 
Upvote 0 Downvote
sticks435 said:
Doesn't flashing the BIOS restore factory defaults anyway? It also worked fine for like a day on the new bios, then it came out of sleep and stopped working haha.
Click to expand...
This is exactly reason why I do not use sleep. You never know what was fcuked during sleep time, lol. I am testing this broken feature sometimes, last time after sleep, my power monitoring of the GPU died completely, so thanks but no thanks MS.
 
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
Hi. If you had these two memory kits at home, which ones would you use? DDR5 Corsair Vengeance RGB 32GB (2x16GB) 6000MHz CL30 EXPO-XMP, or the DDR5 G.Skill Trident Z5 RGB 32GB (2x16GB) 7200MHz CL34 XMP 3.0?
 
Upvote 0 Downvote
use A die if you have one Trident Z5 RGB 32GB (2x16GB) 7200MHz CL34 XMP 3.0 use zen timing to see if it is A die or M die

A die is better then M die A die is sometime on faster memory kits. But it is all on the cpu if you have a good cpu u can do it . I Have M die 6000 30 Timings overcock to 8000 2/1 or 6400 1/1 Higher speeed the kit more CL . I Have a 6000 30 kit M die
 

Attachments

  • Clipboard_07-01-2026_01.jpg
    Clipboard_07-01-2026_01.jpg
    85.9 KB · Views: 46
Last edited:
Upvote 0 Downvote
kekolopez55154a02d1 said:
Hi. If you had these two memory kits at home, which ones would you use? DDR5 Corsair Vengeance RGB 32GB (2x16GB) 6000MHz CL30 EXPO-XMP, or the DDR5 G.Skill Trident Z5 RGB 32GB (2x16GB) 7200MHz CL34 XMP 3.0?
Click to expand...
To add to what @dlomond was saying, A-die usually has more overclocking headroom, but won't matter too much unless you're manually adjusting your timings. If you're running XMP/EXPO stock then you're going to see mote stability and lower latency on the 6000/CL30, and having to run your RAM at CLK/2 to hit 7200 will also cause more latency.
The raw Mhz speed matters even less on x3d processors, since they will use their cache more often and have less paging to RAM during gaming, etc.
If you are willing to get into the whole RAM subtiming adjustment game, you will likely squeeze better OC performance out of the 7200 RAM (unless it is M-die) by running it at 6200+ 1:1 at CL30, but that takes some effort, time, and a lot of testing for stability.
If you are just running the XMP/EXPO settings, stick with the 6000/CL30, especially on an x3d processor.
If it is non-binary RAM (24/48GB) then it's definitely M-die, but since yours is 16GB then you'll have to plug them in and run Zen Timings to see which actual chips they are using, as in @dlomond's screenshot.
 
Upvote 0 Downvote
marceluss19 said:
This is exactly reason why I do not use sleep. You never know what was fcuked during sleep time, lol. I am testing this broken feature sometimes, last time after sleep, my power monitoring of the GPU died completely, so thanks but no thanks MS.
Click to expand...
It really feels like there must have been some other problems there to cause hardware damage. I have used sleep mode on my computers for decades and never had a hardware failure that wasn't caused by a power surge or other bad hardware.
While it's true Windows hasn't always been good at resuming from sleep (looking at you, Windows 95 through Vista), the worst it would cause is buggy operation until you restarted and sometimes memory corruption when writing to disk, but that was always a problem with an unclean shutdown in early versions of Windows. Since Windows 10 it's been pretty good so long as the hardware you've gotten installed understood what sleep mode is.
Aside from the resume-from-sleep/cold startup PCIe speed locking bug that this board has been plagued with, in my 2 identical computers I just sleep it again and then resume, and all is right as rain. And even that hasn't happened since I upgraded to AA2, though it's still pretty fresh.
Planning to upgrade to AA3 this weekend to see if patch A is smoother yet.
 
Upvote 0 Downvote
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.
 
Upvote 0 Downvote
You must log in or register to reply.
Back
Top