Meg X570 Unify doesn't post with ram anything higher than 3200mhz with a Ryzen 5800x

[ajaguck152b02d6]

I have this board and today I upgraded from a 3900 to a 5900 using the A81 bios update file. Everything seems to be working okay at the correct RAM speeds however I cannot adjust the ARGB settings on my G.Skill Trident Neo sticks. The G.Skill software doesn't even detect them, so they're stuck in the default rainbow cycle mode. Is this a known issue that's being worked on?

Thanks!

I notified both MSI and Gskill about this -- both sides said they are working on a fix.

 

[SeoulFinn]

Do you have any other problems with beta BIOS? Some reported earlier that the previous "final BIOS" had problems showing temps in monitoring software and USB acting up.

 

[joshuacant]

HWiNFO is showing all the right sensors as far as I can tell. Other software, like Corsair iCue, isn't. That probably means some programs need an update to support Zen 3 chips.

No USB issues so far, but I've only had it for a day.

 

[ssateneth]

For people trying to run their ram at their rated speed, try setting your fabric clock (FCLK FREQUENCY in BIOS) to 1600 or less (Stock is 1066). I have had good success doing this and I am able to run RAM up to 4733MHz perfectly fine with no WHEA / bus interconnect errors. See attached photo.

Keep in mind, this is considered a BANDAID fix. FCLK should be fully capable of 1900-2100 on Zen 3 (Ryzen 5000 series) without any errors. This just bypasses the issue.

 

[newlin9]

For people trying to run their ram at their rated speed, try setting your fabric clock (FCLK FREQUENCY in BIOS) to 1600 or less (Stock is 1066). I have had good success doing this and I am able to run RAM up to 4733MHz perfectly fine with no WHEA / bus interconnect errors. See attached photo.

Keep in mind, this is considered a BANDAID fix. FCLK should be fully capable of 1900-2100 on Zen 3 (Ryzen 5000 series) without any errors. This just bypasses the issue.

================

AMD AGESA ComboV2 1.1.0.0 (C), while being the latest revision, is STILL a BETA BIOS. It is the same V2 code AMD released to ALL vendors. The problems are certainly not unique to MSI 5XXX motherboards either. Perusing on the GByte, ASUS, ASROCK, etc. forums V2 1.1.0.0(C) is not performing as well as expected and won't last long on the "BETA BURNER."

Looking on this forum alone, you see the most premium MSI X570 & B550 boards (Ultra, Ace, Godlike, Carbon) all having quite similar BUGs that are causing similar operating headaches (USB failing, GPU failing to post, 36XX+ DRAM not running past 2133, etc.

As much hype as AMD spun rolling out Zen3, there wasn't as much "refinement" in their V2 AGESA code for Zen3 this time around as there was for V1 AGESA Zen2. I don't think I'm just imagining that, especially since the higher end boards are all reporting very similar BUGs in the early AGESA implementation.

 

[Alan J T]

Hi guys check your Bios page for your board new bios

 

[Anonymous1243]

.

 

[Alan J T]

Still nothing for the Tomahawks which I believe are their most popular...

I'm thinking it will only released to one or 2 board till the release of the new AMD GPU goes public odds are the bios is for Reviewers to test and benchmark the new cards with the new CPU

 

[WhiteZero]

I just got the X570 Unify and have a 5800X arriving soon, so I was a bit dismayed to see this thread. Hopefully MSI are going to have a new stable BIOS soon.

 

[joshuacant]

With the A81 update my Unify has been working great with my 5900X, other than not being able to control the ARGB on my RAM.

 

[Kalistas_82]

I just got the X570 Unify and have a 5800X arriving soon, so I was a bit dismayed to see this thread. Hopefully MSI are going to have a new stable BIOS soon.

just try it out - although you can see the problems left and right - i have a X570 Unify with 5900X and 32GB GSkill TridentZ Neo 3600 CL16 running flawlessly with xmp on..(Bios ver. A7)

 

[Cisco78]

Using G.Skill Trident Royal 4000mhz CL15 on Zen2, no issues, updated to 5900X and boom on MSI Meg Ace x570. Beta BIOS has done nothing.... will they fix this? Literally just bought board... ugh

 

[husky87]

just try it out - although you can see the problems left and right - i have a X570 Unify with 5900X and 32GB GSkill TridentZ Neo 3600 CL16 running flawlessly with xmp on..(Bios ver. A7)

is that the samsung B die or hynix cjr?

 

[Kalistas_82]

is that the samsung B die or hynix cjr?

sadly cant check atm - still waiting for my RX 6800 XT (the system had no Gfx Card atm - and my wife wont let me cannibalize her system again )

 

[a.barnes.j15a402ea]

I might be late to the party here.
I did a new build on Saturday night, first build in about 15 years. I think I have run into the same issue with the DRAM speeds.

MAG B550 Tomohawk
Ryzen 5 5600x
2x16 Patriot Viper Steel Series 3600mhz
ASUS Rog strix Rtx 2600 super

So initially couldn't post. LED for RAM and GPU. Eventually got to Bios screen RAM was set to 3200mhz. Installed windows etc. Went back to bios changed DRAM speed to 3600mhz in Profile 1. Wouldn't post at all. Tried flashing the bios, did nothing. Resetting the bios with a screw driver seemed to work.

Managed to update the bios Sunday morning. I can manually set to 3400mhz.
But when set to 3600mhz, though it will boot up Windows there were some serious instability issues.

Dropped it back to 3400mhz.

(Edit: Steam "uninstalled" games at 3400mhz. And games would crash on start-up. Dropped it back down to 3200mhz, problem seems to be solved)

Can I confirm is this a MSI bios issue? Or should I return the sticks or the mobo?

I have also noted some instability with the blue tooth signal with a tp-link AX3000 I installed.

 

[Alan J T]

I might be late to the party here.
I did a new build on Saturday night, first build in about 15 years. I think I have run into the same issue with the DRAM speeds.

MAG B550 Tomohawk
Ryzen 5 5600x

Can I confirm is this a MSI bios issue? Or should I return the sticks or the mobo?

At the Moment it is a Know Bios problem only way to clock your ram is manually and not let the Fabric timer thingy go over 1600

 

[a.barnes.j15a402ea]

At the Moment it is a Know Bios problem only way to clock your ram is manually and not let the Fabric timer thingy go over 1600
View attachment 142824

Thanks for the quick response. Appreciate it!
I'm guessing this is why I am getting the x3 beep code as well for memory issues on boot.

 

[Alan J T]

Could be the Bios or the CPU is not playing nice with setting over 1600 at them moment But I would say AMD will get it sorted just may take a few Weeks and not hours like some seem to demand of them. New CPU with New type of Memory on the Die. Seems going from 16MB mem to 32MB on the CPU had caused some hiccups.

 

[WhiteZero]

I finally did my build today with the Unify and a 5800X. Installed the latest " 7C35vA82(Beta version) " BIOS, turned on XMP for 4 of these sticks, and everything is working fine so far.

 

[yazamir]

Could be the Bios or the CPU is not playing nice with setting over 1600 at them moment But I would say AMD will get it sorted just may take a few Weeks and not hours like some seem to demand of them. New CPU with New type of Memory on the Die. Seems going from 16MB mem to 32MB on the CPU had caused some hiccups.

Stop talking nonsense "AMD is to blame for everything"! I installed a new beta BIOS 7C35v1D2 on the X570 ACE and FCLK immediately started working on 1900 (before that on 7C35v1C a maximum of 1600). At the same time, the version of SMU 56.34.00 was not changed, it is the same on both BIOS.
Even if AMD gives some advice to the MSI on how to use its firmware, then it is 100% the responsibility of the MSI to warn users about the limitations of specific BIOS. If this were done, then the forum would not have this topic and many others like it!
I am sure that in future BIOS, the FCLK lock on 1900 will also be removed. Although overclocking the FCLK to 5000 Ryzen no longer brings such a profit as in the previous series.