08-11-2025 11:46 AM
I’m getting BSODs with EXPO memory profiles on my ROG STRIX B650E-I since updating to BIOS 3278. This configuration was completely stable with EXPO-II for over a year on at least four prior BIOS versions. I noticed another thread related to this, but it's been locked so I couldn't reply (the solutions proposed within did not work for me). Is there an upcoming BIOS or AGESA update that addresses the issues?
My system:
Problem:
What I’ve tried:
08-11-2025 03:10 PM
Welcome to the fun that is Agesa 1.2.0.3x / 32xx bioses. I'm in the same boat, my binned 6200 cl 32 had to be brought down to 6000 cl 30 under EXPO 1 and manual voltage for CLDO and VSOC with both Memory Context Restore and Quick Learn turned off.
Surprisingly, AIDA says its performing better than older bioses versions, so I guess there was some truth to increased performance. That being said, it took a week and couple corrupted windows installs to get to stability. It seems trying to get UCLK=MEMCLK and Quick Learn + Memory Context to work in hand doesnt work for now..
08-11-2025 09:56 PM
Glad to know that I'm not alone, but also this isn't great. I've seen the same MCR + UCLK issues. My system was 100% stable at DDR5-6000 EXPO II on older BIOSes but is unstable even at 5800 now. @Momo_dk can you share more about what you did? I'm curious if you've tried only disabling Quick Learn but keeping MCR on, or vice versa. I am trying to think if I should bother messing around or leave EXPO off until a future update can address the issues.
08-12-2025 07:39 AM
The main thing I did was to turning off MCR and Quick Learn and applying 1.265v for vsoc and 1.1v for cldo. This seem to let expo 1 for 6000 work just fine for running UCLK=MEMCLK.
I would run OCCT for 30 mins on RAM, stop at any error.If passed, onto CPU+RAM for 30 mins. I know you're supposed to do longer, but I got impatient with spending days figuring out what's causing BSOD and/or application crashes in background.
I have yet to start back down vsoc voltage or try see if I can push for 6200 expo 1 yet, but I'm almost certain its MCR/Quick Learn that causing most of my issues.
FYI my kit is a Corsair Dominator 32gb x2. CMP64GX5M2B6000Z30 to be specific.
08-17-2025 02:53 AM
My MB is B650E-I GAMING WIFI (I guess its the same for all B650E-I ?)
I have the CORSAIR Vengeance DDR5 RAM 32GB (2x16GB) 6000MHz CL30-36-36-76 and my Expo I profile is also unstable since the BIOS update to 3278. I can boot up but once I play Battlefield 6 for example, the game just crashes/closes after 5-10 min. If I deactive it, everything works fine.
Before I updated I still had a BIOS version from 2024 and that EXPO profile worked perfectly fine.
Can I manually adjust something in the AI tweaker so the EXPO profile works again? Is the voltage too low? Im somewhat of a noob on mem overclock.
08-23-2025 10:49 PM
Please list the actual kit PN
08-17-2025 11:09 PM
Within AMD Nitro settings, set 2/3/1.
See if this helps.
08-21-2025 01:06 PM
Thanks for the input everyone... sounds like this is affecting multiple kits (Corsair + G.Skill) on the B650E-I with BIOS 3278 / AGESA 1.2.0.3x.
From what I’m seeing:
So this looks like a bug in how EXPO training works with 3278. Can someone from the ASUS team confirm if this is a known AGESA issue and whether a fix is planned in an upcoming BIOS?
08-23-2025 05:54 PM
I wouldn't say UCLK=MEMCLK increases stability.. Maybe get 99% stability but once every 2 weeks, the memory training just go eh and the system super unstable (apps crashing left and right) until a restart.
The bug really started with version 3222 and got worse with 3278 for my x670e-i. Last stable for me and my Corsair kit (6000mhz cl30 2x 64gb) was 3208 where I could go to EXPO I 6200 with FCLK 2166 along with primary and secondary timing tweaks. It's frustrating I can't go back to 3208 now that I've also upgraded to 9950x3d (thinking the IMC was fried in my 7800x3d, but noooo...)
08-23-2025 10:37 PM - edited 08-23-2025 10:49 PM
Newer AGESA seems to have increased vSOC required for some OC looking at some reports. Seems to mainly affect 1:2. I wouldn't say it's a bug.
Check AMD Nitro settings as suggested, or enable EXPO Tweaked if available.