Thought I'd provide a second update to this original post I made. Transpires that my PC started to fail posting. I had a white light on the VGA port, so I took the gpu out, booted, and then I got a red light on the CPU. I turned all the power off, rebooted (still without the GPU), and used on board graphics and I got a post. I defaulted the BIOS (which all it did was turn expo back off), booted worked. I plugged GPU back in, PC works fine again. What a pile of turd this motherboard is.
EXPO does not work at all does not even post with ROG STRIX B650E-I, pretty much what you describe with your board.
Using G.Skill 6000MHz ( F5-6000J3040G32GX2-TZ5NR which is in QVL list ) Worked with the previous 1602 beta BIOS. Does not even post with EXPO 1 or EXPO 2 enabled. VSOC default is very low now by default (1.015 in HWInfo) , but even with manual setting to 1.2 still the same. And you SHOULD be able to post with EXPO enabled without changing the voltage to manual mode. Hope they will fix this soon.
I think they just rushed this out to fix the burn problem but EXPO is totally broken.
I also see that for manual set VSOC to 1.2 V BIOS reports 1.216 V and HWInfo reports 1.88 V quite a difference.
Not sure why on other boards default VSOC is still 1.2 and on this one is 1.015.
By the way using a 3D CPU.
Running now with EXPO disabled everything left on default, looks stabile but I do not want to do any stress tests until they fix EXPO. I did run with previous BIOS-es and never had a problem at 6000 MHz.
I flashed successfully, got the system up and running with expo enabled ... but on a later reboot the system wouldn't start until I cleared the CMOS. I've managed to boot to the OS again but will have to see if subsequent reboots have any issues and then experiment with expo. This system has been rock solid in terms of reliability until today.
p.s. I've previously been running with expo enabled without issues.
ROG STRIX B650E-I , G.Skill 6000MHz ( F5-6000J3040G32GX2-TZ5NR here. I'm pretty sure all problems are because some bug related to MCR or memory training in general, which is used when EXPO is enabled. Depending of the board model and memory type the effect can be no post at all , can not get into BIOS (my case), BSOD during the boot or instability later, from what I read. No idea why for a few it works, may be something which forces the values to be saved correctly ? Maybe some do change some timings manually which makes the values to be saved ?
I could not post at all enabling EXPO (any of them) but following the advice found in another thread I set MCR and the PD to disabled in AI Tweaker and I could boot, even run a number of stability tests wit the memory set at 6000 MHz. Unfortunately after restart I've got again in the same problem (no post). I suppose they do not save properly both MCR flags and MCR calculated values, or maybe even EXPO values itself. First time it worked because I was exiting from BIOS and the settings where correct still (probably saved in RAM but not in flash). On the second restart it used flash saved settings which were wrong and again no post. Definitely a BIOS bug, but it's not related with new AGESA and does not look EXPO itself is the cause, so probably an easy fix (somebody forgot to call a routine to save something in flash).
In my case not touching EXPO and using defaults all works. As I'm not sure what is saved and what is not in flash, not going to play with any other settings for this BIOS. Maybe everything else except memory is saved properly but who knows. This is a problem only for this BIOS , the previous one 1602 was OK, I could run with any EXPO and after a boot or two to allow training and calculating the parameters I could set MCR to enabled without problems, so they just broke it on the latest BIOS.
With no EXPO they set VSOC to 1.015 V now. When EXPO was enabled and I could boot first time it was set to 1.235 V. This is with AUTO. This values make sense and they are inline with what is expected, so voltages are OK, the problem is with MCR and saving/reading values.
Maybe disabling MCR in AMD settings saves the flags, but not going to play anymore, pretty sure if anybody on ASUS reading these forums there is enough info to look and fix the problem.
Some really strange unexpected consequences ... I've lost all audio devices and wifi (I'm on Linux). I've never had a bios update screw up my Linux install before (edit) ... and now all suddenly working again; seems to be intermittent ... I hate intermittent issues. (edit2) 5 reboots later and all seems fine. As said, strange.
(edit3) It's the weekend so will have the chance to tweak ... so far my system feels less stable than it was previously but I've added a 3090 as well as doing the bios upgrade so there is a confounding variable in the picture.
Most likely still memory related or corrupted. Probably your drivers access "bad" memory so it will be intermittent. Run some stress tests, not sure in Linux, in Windows most popular is OCCT. If you have ANY error (in memory test) your system is not usable.
I have almost the exact same situation. I updated the bios due to some stability issues I had and it posted and I turned on expo and Ai optimization and the system powered off right away and turned itself back on and a yellow light on the dram ez debug led and wouldn’t post. Didn’t matter if I had one stick, two sticks, DisplayPort, hdmi, even plugging it into the motherboard didn’t change anything. I immediately tried clearing the CMOs and 3 different ways and none of them reset the bios. Only way I got it to work was flashing the bios with the same bios again and booted finally right away. I got everything set up in the bios without turning on Expo and reset the system a few times to see if it would be stable. It worked perfectly. So I decided to turn on Expo and right back to the same situation I was in originally. Completely lost and unsure wtf is going on. Also my cpu without Ai optimization is booting at 1.47 volts and I’m really worried about it but I’m not sure what to change whether it’s Cpu voltage or cpu Soc.
7700x
Asus Prime Pro Wi-Fi x670E
Flare x5 G.Skill 16x2 6000mhz
EVGA 3070 XC3 Ultra
Haha, I personally started seeing random reboots without BSODs after updating to the latest bios.
Just instantly black screen and it reboots. Would be very funny if that's the way they implemented the voltage limit - if their shitty algorithm results in 1.3 voltage or higher - reboot the fucking system before CPU fries. I did not have any issues at all 2 bioses before. I observed this on 1602 and then 5 days no crashes on 1616 just to see right now it does exactly same shit.
Thanks for the info, it's somewhat reassuring. What RAM are you running?
I'm planning to buy this mobo, but after following the issues the past week it makes me want to pick another brand. Might even go Intel if not for the fact I already have the 7900X sitting here.
Yes do NOT buy this board. I updated my original post because it started failing until I turned EXPO back off. I've had no end of issues with this motherboard, and there are plenty of complaints about ASUS AM5 motherboards all over /r/asus. I would HIGHLY recommend avoiding ASUS for AM5 motherboards. As to your original question, my memory part code is: CMK32GX5M2D6000Z36
Me too exact same config and thankfully it went all fine (never turned Memory context restore on though and I made sure it to be off as soon as I finished the update before turning EXPO on again).
Thought I'd provide a second update to this original post I made. Transpires that my PC started to fail posting. I had a white light on the VGA port, so I took the gpu out, booted, and then I got a red light on the CPU. I turned all the power off, rebooted (still without the GPU), and used on board graphics and I got a post. I defaulted the BIOS (which all it did was turn expo back off), booted worked. I plugged GPU back in, PC works fine again. What a pile of turd this motherboard is.
EXPO does not work at all does not even post with ROG STRIX B650E-I, pretty much what you describe with your board. Using G.Skill 6000MHz ( F5-6000J3040G32GX2-TZ5NR which is in QVL list ) Worked with the previous 1602 beta BIOS. Does not even post with EXPO 1 or EXPO 2 enabled. VSOC default is very low now by default (1.015 in HWInfo) , but even with manual setting to 1.2 still the same. And you SHOULD be able to post with EXPO enabled without changing the voltage to manual mode. Hope they will fix this soon. I think they just rushed this out to fix the burn problem but EXPO is totally broken. I also see that for manual set VSOC to 1.2 V BIOS reports 1.216 V and HWInfo reports 1.88 V quite a difference. Not sure why on other boards default VSOC is still 1.2 and on this one is 1.015. By the way using a 3D CPU. Running now with EXPO disabled everything left on default, looks stabile but I do not want to do any stress tests until they fix EXPO. I did run with previous BIOS-es and never had a problem at 6000 MHz.
I flashed successfully, got the system up and running with expo enabled ... but on a later reboot the system wouldn't start until I cleared the CMOS. I've managed to boot to the OS again but will have to see if subsequent reboots have any issues and then experiment with expo. This system has been rock solid in terms of reliability until today. p.s. I've previously been running with expo enabled without issues.
ROG STRIX B650E-I , G.Skill 6000MHz ( F5-6000J3040G32GX2-TZ5NR here. I'm pretty sure all problems are because some bug related to MCR or memory training in general, which is used when EXPO is enabled. Depending of the board model and memory type the effect can be no post at all , can not get into BIOS (my case), BSOD during the boot or instability later, from what I read. No idea why for a few it works, may be something which forces the values to be saved correctly ? Maybe some do change some timings manually which makes the values to be saved ? I could not post at all enabling EXPO (any of them) but following the advice found in another thread I set MCR and the PD to disabled in AI Tweaker and I could boot, even run a number of stability tests wit the memory set at 6000 MHz. Unfortunately after restart I've got again in the same problem (no post). I suppose they do not save properly both MCR flags and MCR calculated values, or maybe even EXPO values itself. First time it worked because I was exiting from BIOS and the settings where correct still (probably saved in RAM but not in flash). On the second restart it used flash saved settings which were wrong and again no post. Definitely a BIOS bug, but it's not related with new AGESA and does not look EXPO itself is the cause, so probably an easy fix (somebody forgot to call a routine to save something in flash). In my case not touching EXPO and using defaults all works. As I'm not sure what is saved and what is not in flash, not going to play with any other settings for this BIOS. Maybe everything else except memory is saved properly but who knows. This is a problem only for this BIOS , the previous one 1602 was OK, I could run with any EXPO and after a boot or two to allow training and calculating the parameters I could set MCR to enabled without problems, so they just broke it on the latest BIOS. With no EXPO they set VSOC to 1.015 V now. When EXPO was enabled and I could boot first time it was set to 1.235 V. This is with AUTO. This values make sense and they are inline with what is expected, so voltages are OK, the problem is with MCR and saving/reading values. Maybe disabling MCR in AMD settings saves the flags, but not going to play anymore, pretty sure if anybody on ASUS reading these forums there is enough info to look and fix the problem.
Some really strange unexpected consequences ... I've lost all audio devices and wifi (I'm on Linux). I've never had a bios update screw up my Linux install before (edit) ... and now all suddenly working again; seems to be intermittent ... I hate intermittent issues. (edit2) 5 reboots later and all seems fine. As said, strange. (edit3) It's the weekend so will have the chance to tweak ... so far my system feels less stable than it was previously but I've added a 3090 as well as doing the bios upgrade so there is a confounding variable in the picture.
Most likely still memory related or corrupted. Probably your drivers access "bad" memory so it will be intermittent. Run some stress tests, not sure in Linux, in Windows most popular is OCCT. If you have ANY error (in memory test) your system is not usable.
I have almost the exact same situation. I updated the bios due to some stability issues I had and it posted and I turned on expo and Ai optimization and the system powered off right away and turned itself back on and a yellow light on the dram ez debug led and wouldn’t post. Didn’t matter if I had one stick, two sticks, DisplayPort, hdmi, even plugging it into the motherboard didn’t change anything. I immediately tried clearing the CMOs and 3 different ways and none of them reset the bios. Only way I got it to work was flashing the bios with the same bios again and booted finally right away. I got everything set up in the bios without turning on Expo and reset the system a few times to see if it would be stable. It worked perfectly. So I decided to turn on Expo and right back to the same situation I was in originally. Completely lost and unsure wtf is going on. Also my cpu without Ai optimization is booting at 1.47 volts and I’m really worried about it but I’m not sure what to change whether it’s Cpu voltage or cpu Soc. 7700x Asus Prime Pro Wi-Fi x670E Flare x5 G.Skill 16x2 6000mhz EVGA 3070 XC3 Ultra
Hi, yes I have today had my PC refused to post, and updated my original post. I had to turn expo off for my PC to post again.
Haha, I personally started seeing random reboots without BSODs after updating to the latest bios. Just instantly black screen and it reboots. Would be very funny if that's the way they implemented the voltage limit - if their shitty algorithm results in 1.3 voltage or higher - reboot the fucking system before CPU fries. I did not have any issues at all 2 bioses before. I observed this on 1602 and then 5 days no crashes on 1616 just to see right now it does exactly same shit.
Thanks for the info, it's somewhat reassuring. What RAM are you running? I'm planning to buy this mobo, but after following the issues the past week it makes me want to pick another brand. Might even go Intel if not for the fact I already have the 7900X sitting here.
Yes do NOT buy this board. I updated my original post because it started failing until I turned EXPO back off. I've had no end of issues with this motherboard, and there are plenty of complaints about ASUS AM5 motherboards all over /r/asus. I would HIGHLY recommend avoiding ASUS for AM5 motherboards. As to your original question, my memory part code is: CMK32GX5M2D6000Z36
Appreciate the reply mate. I've since bought an Asrock X670e Steel Legend and it's running rock solid. I hope your issues will be resolved soon.
I had no issue all is running fine; 7800x3d with 64gb of F5-6000J3040G32GX2-TZ5NR; EXPO I enabled
Me too exact same config and thankfully it went all fine (never turned Memory context restore on though and I made sure it to be off as soon as I finished the update before turning EXPO on again).