02-26-2024 04:43 PM - edited 03-02-2024 10:00 AM
after what happened in the link: https://rog-forum.asus.com/t5/amd-600-series/bios-v2413-is-incompatible-with-processors-with-two-ccd...
now still using the BIOS version v2412, I'm noticing a strange defect in AI OPTIMIZED's overclock management. It simply is not accepting any voltage value for the cores and there is also no way to improve the settings of the options present in the VRM DIGI+. Suddenly the Windows operating system started to crash, both before it finished loading and after and after a period of time. Restarts also occur when testing heavier load applications, such as Cinebench. I have already changed the values of the optimization curve, from negative values (-30) to zero, but the system still crashes.
I ran the Cinebench test again with AI OPTIMIZED mode disabled and using the core ratio option at x52.50. The voltage of the cores is in automatic mode. Even though temperatures were quite high during the short test time (105.6°C), the system did not crash or restart. Now we are in a hotter summer, but before it was cooler weather. The AI OC probably didn't know how to deal with it.
When leaving the clock value lower, to check, there was no system crash.
CPU CORE RATIO x52.50
CURVE OPTIMIZER
ZenTimings_6000 optimized
this was the configuration I was using to try to stabilize and avoid system crashes:
DIGI PLUS VRM
Solved! Go to Solution.
03-21-2024 05:47 PM
It was difficult to find the cause of the problem, but I actually have the solution now, it wasn't what I initially imagined and I reported the solution on the forum: AMD COMMUNITY FORUM
02-28-2024 03:04 AM
To resolve it, it was necessary to deactivate the AI OPTIMIZED option. Overclocking is being manual.
02-28-2024 06:35 PM
After some more tests I discovered that, in addition to the heat due to the hotter summer climate, it was also the vSoC that, being low, ended up having problems with the faster memory.
03-02-2024 09:58 AM
I also adjusted the VDDG voltage higher (CCD: 1050 and IOD 950)
VDDG
however, the problem was on Windows (KB5034765) update too.
03-21-2024 05:47 PM
It was difficult to find the cause of the problem, but I actually have the solution now, it wasn't what I initially imagined and I reported the solution on the forum: AMD COMMUNITY FORUM