MPG X870E CARBON WIFI Beta BIOS

[Svet]

Spoiler: Older Versions

>>> 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:

---

>>> E7E49AMSI.1A9B <<<

.rar SHA-256: 9eae3f5df43c2696e64ef329c6fddc45ba2e40ec0b529a9c451fa3871b077bff
BIOS SHA-256: 2B34A9B25DDEC186AC2272334DC2666C80082B143468A4D9D470BE88AB2C4CB4

AGESA version:

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:

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:

---

Latest version: (from msi web page)
7E49v1AA3:
BIOS SHA-256: AF55A578CBDE8138906094F1CAD8C4C6A06639C4DAB23C0D7ACEA392326847AA
AGESA version:

 

[vic123159d02e5]

I guess it's up to the person that's testing, then, really. There is so much conflicting information out there about testing methodologies. I just do an in-between. Hydra Pro helps with testing through its validation. It's much more rigorous than other tests I've found, and it makes use of Cinebench, Kharu and Y-cruncher VT3. Then, after that pass, I do a 4-hour test with OCCT with a variable workload. As for memory, AIDA likes to catch some errors, memtest using hydra does that well too IMO. OCCT is kinda meh in that area from what I've seen.

I have also found that setting the right VDDG for each core is a huge factor for stability and getting further gains in the Curve Offset, so people who are struggling should look into that. Just do it in a step increment at a time. Higher seems to be better for CCD1, and lower seems to be better for CCD0. Mine are 1.060 for CCD1 and 0.980 for CCD0. It really helps. Also, this new BIOS seems to help with stability greatly from the last ones' AGESA version.

I definitely wouldn't use OCCT to test memory stability, Y-cruncher and MemTest are the best tools for the job IMO. (I'm a little less enthusiastic about AIDA64, though)

 

[PixelQubed]

I definitely wouldn't use OCCT to test memory stability, Y-cruncher and MemTest are the best tools for the job IMO.

I completely agree. From my perspective, OCCT just doesn't do the job well enough for memory testing.

 

[marceluss19]

When I was playing with 7950X3D, most sensitive test for my experiments was AIDA64 SH3 . Core Cycler, OCCT, other AIDA tests, all passed, but this one always crash when cpu was unstable.

 

[Sethos812d002b2]

Well, twice this morning and now once coming home I had the stutter requiring a restart. So A34 certainly didn't fix it, in case anyone was wondering.

 

[marceluss19]

Well, twice this morning and now once coming home I had the stutter requiring a restart. So A34 certainly didn't fix it, in case anyone was wondering.

What stutter bios related You are talking about?

 

[PixelQubed]

Well, twice this morning and now once coming home I had the stutter requiring a restart. So A34 certainly didn't fix it, in case anyone was wondering.

Well, I can tell you now it's either your SOC being set too low or your VDDP being too low. I recommend 0.925-0.975 for that. Higher or lower will cause instability with your IMC. The IMC is super stressed, causing the stuttering. Even if the RAM seems stable, it may well not be so. I would loosen your RAM timings if the VDDP settings I recommend don't work.

 

[Sethos812d002b2]

Rubbish, we just had multiple pages talking about this issue, also happens to some of their other motherboards. Even happens to people running default settings. Now the issue suddenly vanished from thin air and we start blaming the user. In fact, it gets worse after a BIOS reset to absolutely stock settings. This has nothing to do with voltages, timings or anything else.

Hell, the Tomahawk BIOS thread, entire page 2 is people talking about this very issue and being very unhappy; https://forum-en.msi.com/index.php?threads/mag-x870-tomahawk-wifi-beta-bios.409819/page-2

 

[Alyred]

Well, twice this morning and now once coming home I had the stutter requiring a restart. So A34 certainly didn't fix it, in case anyone was wondering.

Just curious, have you gone into the power settings and set the PCI Express power saving to "disabled" and are running it on "balanced" with the performance overlays when needed? This, combined with "auto" setting in the BIOS, seems to have alleviated the issue (so far, a week on) in A33. About 20s after resume from sleep, I get about 2 seconds of stutter like it's not enabling the PCI_E1 properly, but then it's fine after and my speed stays fixed at PCI v5x16. The stutter still makes me think there's something not quite right there but at least this has been working.

 

[Sethos812d002b2]

Just curious, have you gone into the power settings and set the PCI Express power saving to "disabled" and are running it on "balanced" with the performance overlays when needed? This, combined with "auto" setting in the BIOS, seems to have alleviated the issue (so far, a week on) in A33. About 20s after resume from sleep, I get about 2 seconds of stutter like it's not enabling the PCI_E1 properly, but then it's fine after and my speed stays fixed at PCI v5x16. The stutter still makes me think there's something not quite right there but at least this has been working.

Hmm, that's actually a really good suggestion. I use Process Lasso to change power profiles but when booting, it's just running Balanced. Don't think I've changed anything in BIOS specifically in relation to this, outside of disabling PSPP (PCI Link State) as some suggested, which did seem to reduce it but not eliminate it completely. But I'll try disabling the PCI Express power management thing for Balanced and see what happens. Thanks man

 

[PixelQubed]

Rubbish, we just had multiple pages talking about this issue, also happens to some of their other motherboards. Even happens to people running default settings. Now the issue suddenly vanished from thin air and we start blaming the user. In fact, it gets worse after a BIOS reset to absolutely stock settings. This has nothing to do with voltages, timings or anything else.

Hell, the Tomahawk BIOS thread, entire page 2 is people talking about this very issue and being very unhappy; https://forum-en.msi.com/index.php?threads/mag-x870-tomahawk-wifi-beta-bios.409819/page-2

You cant bring a completely different motherboard into the equation and state that’s the issue when clearly it’s not. The guy is saying he is suffering from stuttering. Talking from my own experience, my own PCI lane config seems completely fine and I ruled out anything running on the PCI lanes ages ago. As far as I am concerned, different motherboard, different problems. X870 and X870E are not the same. Similar yes but they are different in how the PCI configuration is handled. I personally looked into this because it was a huge concern for me when buying my Carbon X870E and they have a different PCI structure, just like ASUS does with their X870 line and that was causing PCIE drop out issues because of a mode switch.

 

[Sethos812d002b2]

You cant bring a completely different motherboard into the equation and state that’s the issue when clearly it’s not. The guy is saying he is suffering from stuttering. Talking from my own experience, my own PCI lane config seems completely fine and I ruled out anything running on the PCI lanes ages ago. As far as I am concerned, different motherboard, different problems. X870 and X870E are not the same. Similar yes but they are different in how the PCI configuration is handled. I personally looked into this because it was a huge concern for me when buying my Carbon X870E and they have a different PCI structure, just like ASUS does with their X870 line and that was causing PCIE drop out issues because of a mode switch.

You could start by actually reading this thread and stop clogging it up with everything completely unrelated to BIOS updates, then you might not bury what has been talked about for multiple pages. The PCI stuttering issue has been discussed for multiple pages, with even someone from MSI confirming they are investigating the issue. Why on God's green earth would you suddenly start to pretend it doesn't exist.

 

[PixelQubed]

You could start by actually reading this thread and stop clogging it up with everything completely unrelated to BIOS updates, then you might not bury what has been talked about for multiple pages. The PCI stuttering issue has been discussed for multiple pages, with even someone from MSI confirming they are investigating the issue. Why on God's green earth would you suddenly start to pretend it doesn't exist.

Apologies for me being uninformed. I didn’t realise you were talking about a sleep issue related to the PCI resume state. I just assumes when you mentioned stuttering, you where talking about something related to a configuration error. I never saw anything mentioned about it before since I am new to here personally. I will test sleep/hibernation to see if I get the same results but personally I wouldn’t use it since hibernation has caused corruption in the past. I just save and turn off since its the safest way to do things in regards to data integrity. Also I really see hibernation as a laptop thing more than most.

 

[Sethos812d002b2]

Apologies for me being uninformed. I didn’t realise you were talking about a sleep issue related to the PCI resume state. I just assumes when you mentioned stuttering, you where talking about something related to a configuration error. I never saw anything mentioned about it before since I am new to here personally. I will test sleep/hibernation to see if I get the same results but personally I wouldn’t use it since hibernation has caused corruption in the past. I just save and turn off since its the safest way to do things in regards to data integrity. Also I really see hibernation as a laptop thing more than most.

My apologies for coming off so brash. I can just feel my patience with the issue is reaching a low point, so any pushback just becomes a quick temper point. I could have been more clear in what exactly I mean. I don't use sleep nor hibernation, at all. This is purely from cold boots, seems most prevalent on boots where the PC has been off for some time, i.e overnight etc. So this is not hibernation or sleep induced. Though I will try and see if the above suggestion could work.

 

[PixelQubed]

My apologies for coming off so brash. I can just feel my patience with the issue is reaching a low point, so any pushback just becomes a quick temper point. I could have been more clear in what exactly I mean. I don't use sleep nor hibernation, at all. This is purely from cold boots, seems most prevalent on boots where the PC has been off for some time, i.e overnight etc. So this is not hibernation or sleep induced. Though I will try and see if the above suggestion could work.

No problem, I understand where you are coming from. I have been contending with stability issues of my own. You build a system that’s the price of a car, you expect it to just work with no issues. It’s crazy this platform is having so many issues really.

 

[sgmwright]

Well, I can tell you now it's either your SOC being set too low or your VDDP being too low. I recommend 0.925-0.975 for that. Higher or lower will cause instability with your IMC. The IMC is super stressed, causing the stuttering. Even if the RAM seems stable, it may well not be so. I would loosen your RAM timings if the VDDP settings I recommend don't work.

Thanks! this fixed my stuttering issue, I think I love you...

 

[Alyred]

Hmm, that's actually a really good suggestion. I use Process Lasso to change power profiles but when booting, it's just running Balanced. Don't think I've changed anything in BIOS specifically in relation to this, outside of disabling PSPP (PCI Link State) as some suggested, which did seem to reduce it but not eliminate it completely. But I'll try disabling the PCI Express power management thing for Balanced and see what happens. Thanks man

Hopefully it's not apocryphal. I also use Process Lasso and just switched the performance profiles to the "Performance Overlays" and run the rest in Balanced to prepare for the eventual upgrade to a 9950x3d, since the balanced mode is the only one that properly parks cores normally. Though I'm thinking that process lasso should help pin the proper CCD cores to games...

 

[marceluss19]

Hopefully it's not apocryphal. I also use Process Lasso and just switched the performance profiles to the "Performance Overlays" and run the rest in Balanced to prepare for the eventual upgrade to a 9950x3d, since the balanced mode is the only one that properly parks cores normally. Though I'm thinking that process lasso should help pin the proper CCD cores to games...

Why parking cores when using Process Lasso? All background tasks assigned to CCD1, lasso games to CCD0 and AMD nonsense with parking cores, game mode, Xbox app etc. You can throw out of the window.

 

[PixelQubed]

Why parking cores when using Process Lasso? All background tasks assigned to CCD1, lasso games to CCD0 and AMD nonsense with parking cores, game mode, Xbox app etc. You can throw out of the window.

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.

 

[PixelQubed]

Thanks! this fixed my stuttering issue, I think I love you...

I am glad that solved your issue. What did you end up setting it to?

 

[marceluss19]

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.

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%.