ill use this thread to collect some new test bioses for the boards, maybe also to explain some less understood options
to disable cores ccd go here and choose ccd xx bit map down core.
each ones stand for an enabled core
best to disable from the back, ie:
instead of 0011000
after selection press downcore apply changes or discard if made mistake
7950x not boosting pass 5.5G -> check that CStates is not disabled
Detailed Explanation on CState Boot Limiter
X3D OC Preset for those MB with asynch BCLK Support: (for simple slight perf boost for X3D)
DOCP/EXPO Tweaked: (for simple timings tightening)
for crosshair and strix e-e:
explanation of segment2 Loadline:
customize a heterogenous loadline for a dual segment workload range.
example above shows loadline=L6 when current is in range of 0~40A, and Level4 when current is above 40A.
Adds for x3d
dynamic ccd priority switch with core flex, os / driver agnostic so win10 win11 ok
Algo as follows:
If condition reached and ccd0 specified, then check current mem/cache activity > threshold and hysteresis reached, if fulfilled then switch
If condition reached and ccd1 specified, then check current mem/cache activity <=threshold and hysteresis reached,, if fulfilled then switch
Default hysteresis =4
Can combine multiple algos for ccd priority so combinations are wide
works on non x3d too but of course senseless on it. detailed explanation here.
Solved! Go to Solution.
Did you clear cmos before and after bios update ?
Why to do this before? The BIOS upgrade anyway resets to default in any case. I did however do two attempts, one of them loading the CMO from 1413 into new 1602 and after receiving lots of memory errors I did a CMOS reset and re-configured the same settings again. Same result. Tried to play with MC voltages and timings but was unable to find a stable configuration on 1602.
You just said you didn't clear before&after and now you're telling us it didn't do any difference, nice storyteller.
So perhaps this was a misunderstanding.
I wrote "After upgrading to BETA BIOS 1602 I was actually unable to find any stable settings besides JEDEC defaults. So I went back to 1413." I didn't clear CMOS before the upgrade as any BIOS upgrade is anyway reverting to defaults. Then I tried to load quickly the CMO of previous 1413 and it didn't work. After this I did of course clean CMOS again and set up new settings. So perhaps this is what you would describe "good practice of skilled IT support". Still it was a no-go so I reverted to previous BIOS.
I still believe it shouldn't be necessary to clean CMOS. Personally I am still disappointed by the fact it is still in the year 2023 impossible to upgrade a BIOS and keep settings. This is blocking me from doing upgrades remotely as some systems won't boot with default settings. For other manufacturers such as HP you can do remote-upgrade of BIOS and it keeps all the settings. Of course defaulting on setting items which have been added but keeping the ones changed by the user like boot order, secure boot settings, enabled/disabled components etc. For ASUS motherboards I find the settings reverted to stock each time after an upgrade (same as resetting CMOS). So I need to re-do all settings like disabling WiFi+BT+Audio+NIC each time after the upgrade.
So perhaps this was a misunderstanding.
I still believe it shouldn't be necessary to clean CMOS. Personally I am still disappointed by the fact it is still in the year 2023 impossible to upgrade a BIOS and keep settings.
When I upgraded to 1004 I changed "my favorites" tab to show only curve optimizer. Then I upgraded to every stable bios release, doing clear cmos before&after, guess what ? "My favorite" tab has not been reset to default. 😂
During decades of IT support I've seen a lot of strange behaviors when rushing bios updates, from ghost settings to wide array of bugs, from laptops to blade servers, and most of the time doing the before&after cleaning resolves the issue.
Well, that doesn't work if the bios version itself is already buggy.
Guys, it has nothing to do with ASUS.
The so much waited AGESA 188.8.131.52 is broken.
I have random BSODs (never had before) on 1410 beta (X670E-E) and I'm not even running EXPO, but stock RAM.