MPG X870E CARBON WIFI Beta BIOS

Svet

Svet

🛠️ ⚙️⚒️
ADMIN
Joined
Nov 20, 2003
Messages
85,701
>>> 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
dlomond said:
So this this is how you troubleshoot. Unplug everything use 1 stick of ram and GPU and CPU do a BIOS update or be on the latest one. Then do a full cmos reset ( press cmos clear and unplug the power until all lige are off the board then take finger off cmos clear borron. Only run bios defaults do not set anything. Do a a fresh install of windows .only install and driver and network drivers and Nvidia drivers.and AMD drivers what happens then this is the tricky part . They're going after part by part and see where the problems are.. for example, I use a razor keyboard and nod32 antivirus. Back a year ago I was having problems with my antivirus conflicting that my razor software. Try that .
Click to expand...
After that unless you find somebody with the same issue and two of you guys can work it out to see was he in each system? It's going to be hard to find out that's why I say change the board.
 
Upvote -2 Downvote
Aside from other replies, I have found that the PCIe speed getting stuck issue happens less often when I lower the SoC voltage. There's definitely a sweet spot there... FCLK seems to not like higher voltage settings (at the XMP setting of 1.3, for instanct), but the RAM itself needs an increasing amount of SoC voltage to be stable at higher speeds. I'm guessing certain motherboard component quality varies between different runs too.
My board had plenty of other driver-related problems (both MSI and nVidia) during initial board release and for months afterwards, but never saw the PCIe lock issues. Then around A33 I started seeing them, and getting stuck at 2.0 will pretty much instantly crash the nVidia driver and force a black-screen system restart.
At vSoC 1.28 I was seeing the lock every few restarts/resume-from-sleep. Now at vSoC 1.26 I'm seeing it at 4.0 every once in a while, though today it's at 3.0. I do have Spread Spectrum enabled. A sleep/resume will likely get it back up to 5.0 (it did). I didn't see them at all at vSoC 1.23 in A44, but since A50 the RAM/FCLK isn't stable running at 2133/6400 1:1 for me (it was in A44). Sadly, this board has been plagued with random problems like this that MSI hasn't been able to fix.
But I hadn't quite gotten to upgrade to A52, and now I see A60 is out now. MSI, you're going to run out of numbers...
 
Last edited:
Upvote 0 Downvote
I actually did try and lower my SoC voltage some weeks ago, not sure if it was you or someone else who suggested it but I had just been running Auto voltages (though they behaved and stayed within reasonable range). Bumped it down to 1.250 and it didn't seem to change anything for me, at least. Same frequency of PCI lock stutter. Luckily, for me at least, FCH Spread Spectrum has solved it 99%. I did have a single boot two weeks ago where I got it, even with Spread Spectrum but it has been behaving. Only seen it that once in over a month or more.
 
Last edited:
Upvote 0 Downvote
Sethos812d002b2 said:
I actually did try and lower my SoC voltage some weeks ago, not sure if it was you or someone else who suggested it but I had just been running Auto voltages (though they behaved and stayed within reasonable range). Bumped it down to 1.250 and it didn't seem to change anything for me, at least. Same frequency. Luckily, for me at least, FCH Spread Spectrum has solved it 99%. I did have a single boot two weeks ago where I got it, even with Spread Spectrum but it has been behaving. Only seen it that once in over a month or more.
Click to expand...
If it's stable for you, the lower you can go the more wattage is available overall for the rest of your processor. :ROFLMAO:
 
Upvote 0 Downvote
Sethos812d002b2 said:
Stop this rubbish. There's a ton of reports and it hasn't been acknowledged, thus there is no grounds for an RMA as it's so sporadic. Everyone RMA'ing would just end up having to pay for the troubleshoot at a store, only to have it sent back. When it can be largely fixed by a setting, then it's clearly not a cut and dry issue. And just because it doesn't happen to "you", doesn't mean it's some made-up issue, several people have tried to say that in this thread as well. Not every issue affects everybody, that's not how issues in general work.
Click to expand...
Stop this BS. If something do not working as intended, RMA, or throw out of the window and f…k manufacturer for practices you mentioned. You are fine with faulty hardware, ok, you just have low standards.
 
Upvote -3 Downvote
marceluss19 said:
Stop this BS. If something do not working as intended, RMA, or throw out of the window and f…k manufacturer for practices you mentioned. You are fine with faulty hardware, ok, you just have low standards.
Click to expand...
You can easily tell you have no concept of money or done actual RMA in your life. Of course no one throws a motherboard worth hundreds of dollars out the Window or initiates an RMA process that will leave you without a motherboard for days or weeks, to it possibly being sent back as not having any faults and you pay for the troubleshoot fee when it's a very sporadic not officially confirmed issue. That isn't being fine with anything, what are you on about, grow up.
 
Upvote 0 Downvote
The only way to troubleshoot problems is to change out hardware. to do that u need hardware to swap. find someone that will do that for you your buy new again and sell the old stuff. that is about all you can do .ok put it ticket into msi tech support . I would go buy a new board form gigabyte and try that if that don't fix the problem return it. Or take it to someone like computer shop that has the parts. When i buy parts in Canada i have 15 days to make sure they work if not it go back .
 
Upvote -1 Downvote
To clarify something here, I have been on BOTH camps, good and bad I had unexplained, never fixed issues of what I refer to as the "AMD hardware lottery."
I faced numerous problems with my 3950X +X570 ACE and later with the 5950X+ X570S ACE MAX in the past.
Despite my frustrations, others claimed they never encountered similar issues ???? like WTF ???
My frustration with AMD led me to switch to Intel, starting with the 13900KF, which proved disastrous, followed by the even more problematic 14900K.
After enduring multiple struggles and issues across several generations of both AMD and Intel systems, I finally found stability and performance with my current setup: the R7 9800X3D + X870E Carbon WIFI +MSI 5090 Liquid X SOC.
The last stable and best-performing system, including gaming, before this one, I remember being the i7 9700 K-based system, all in between, including AMD and especially INTEL: just utter GARBAGE.
I understand that some people may experience issues with their particular boards and HW setups. However, I believe that if a board has inherent issues of that magnitude and does not perform as advertised, no BIOS update will ever resolve it. It never did for my issues on my previous AMD platforms.
 
Last edited:
Upvote 0 Downvote
lysyn12155d02d4 said:
But does BIOS 61 include firmware upgrades? Change PT FW version - what firmware is this?
Click to expand...
Typically, a BIOS successor should incorporate all previous advancements. However, Im uncertain in this case. Initially, we had version F, then reverted to Ewith included FW update, and now, we're switching back to F but no mention of the same FW update. I downgraded to version E due to a firmware update, whatever it entailed, and now I'm planning to upgrade to version F with this new BIOS. Crazy!
 
Upvote 0 Downvote
I love my first msi board I and a gigabyte master on the last 6 system that is one thing I can say msi is very short on what they are changing. Love they are updating bios so fast . But I also like tinkering with the bios . It's great for me.
 
Upvote -1 Downvote
I have flashed bios 60 yesterday, and I noticed a slight improvement in performance in the CPU and the system in general and stability so far.
For BIOS 61, I think it’s better to wait for the next release (62 or 65) so it’s more stable.
 
Upvote 0 Downvote
kkrott87 said:
What problems did you encounter? I flashed this .61 30 minutes ago.
Click to expand...
I used the settings I had set up for 52 BIOS and 61 BIOS didn't open. After changing a few settings, the system opened, but then it froze after about an hour and I had to turn it off and on again.
52 is doing fine at the moment. :)

PBO Advanced
Scalar = Auto
Positive 200 Mhz
CO All cores -30
Soc 1.285 V

Memory 6400 Mhz
MCR = Enabled
Efficiency = Tighter
 
Upvote 0 Downvote
I don't know, temps seems a bit higher on this .61 BIOS

Same config as always:
PBO Advanced
PBO Limits: Mobo
Scalar = 10x
Positive 200 Mhz
CO Per core -35 (on X3D cores only)
 
Upvote 0 Downvote
Back
Top