02-21-2025 09:05 AM - edited 03-13-2025 11:05 AM
Please share any experience with version 5002. Is it stable? Any performance loss or gains?
As of right now, I only see that it implements security updates and the latest AGESA, I have no idea to what extent for the security update, but I'm pleasantly surprised to see a new BIOS update when the board is almost 6 years old now.
Thanks ASUS, i think.
1.Updated AGESA version to ComboV2 PI 1.2.0.E.
2.Implemented security updates.
edit: 3/13/2025
Other than my BIOS settings being reset and LED firmware updating, 5002 has been stable, and I appear to have gained almost 1% in Cinebench R20. Others have claimed no performance gains, and some have had minor issues.
ComboV2 PI 1.2.0.E includes updates to fix two known CVE(Common Vulnerabilities and Exposures) - CVE-2024-0179 and CVE-2024-21925. I'd recommend updating for this reason alone.
CVE-2024-0179 is a vulnerability in the AmdCpmDisplayFeatureSMM driver related to System Management Mode (SMM). It allows locally authenticated attackers to overwrite SMRAM (System Management RAM), potentially leading to arbitrary code execution. This vulnerability has a CVSS score of 8.2 (High), indicating significant risk
CVE-2024-21925 is a vulnerability in the AmdPspP2CmboxV2 driver. It involves improper input validation, which could allow a privileged attacker to overwrite SMRAM (System Management RAM). This could lead to arbitrary code execution, posing a significant security risk. The vulnerability has a CVSS score of 8.2 (High), indicating its severity
03-03-2025 12:04 PM
Have you tried resetting BIOS settings to default, rebooting and then reconfiguring again?
03-28-2025 04:17 PM
Same, Asus Crosshair VIII Formula.
Since Day 1 and many bios versions 0 Problems.
Latest i have was 1.2.0.8
After Update i had my first ever happened usb drop out °_°
System feels a lot more unstable, sudden applications crashed without any reason.
I have to say my system is 24/7 on never suspend for years.
Longest time without restart if i remember correctly over 300 days.
Windows updates are blocked via group policies (10 x64 Enterprise version 22H2)
-30 AllCore Curve Optimizer since Day 1 i got it. No probs until now.
So i switch back as soon as possible.
Just for the information ^^
03-03-2025 02:27 PM
Also I would like to add. Since 5002 my machine has been hard locking when left idle overnight. this has never happened before.
03-03-2025 04:05 PM
are you using curve optimizer? just sounds like a problem I had all the time.
03-07-2025 08:18 AM - edited 03-08-2025 08:40 AM
I'm curious what's causing this. I haven't had any issues while idle for a few hours, but I don't leave my PC on over night. After the update, I believe everyone had to change their BIOS settings back, could something have changed here, like an Overclock setting?
Does it happen every night, or intermittent? If it's intermittent, do you use a UPS?
Have you tried changing your Ryzen Power Options to High Performance or something else?
Does anything turn off after an extended period under Advanced Power Options?
Does anything show up in Event Viewer during the period of time that it froze?
03-09-2025 08:59 AM
I'm curious about the event viewer as well, prior to the bios updates addressing security issues I was able to do a -20 all core using curve optimizer and my pc would never crash even sitting idle for hours but then after I updated the bios I started noticing my computer had restarted itself and 1 day I actually caught it crash just prior to my monitor turning off and that's when I saw tons of whea errors on random cores crashing, after googling a bit tried -10 and -5 which would still crash just far less often so I disabled curve optimizer and that was the errors went away and I quit having idle crashes. Just sounds like the same issue the OP is having but we won't know if he doesn't come back and tell us. I always try my settings at least once on every bios to see if something has fixed it but no dice.
03-09-2025 09:34 AM
Match APIC ID in WHEA log with core using CPU-Z export, then adjust per core CO accordingly.
03-10-2025 06:26 AM
ok I got bored and decided to play around with individual cores just to see what would happen, changed my vcore to - 0.1000mv and set the curve to -25 on all cores and left my pc sit, I have it set to standby after an hour so when I checked 2 hour later and saw it was still on I knew I'd have data so I pulled the whea logs and dropped the corresponding cores to -20 and left it sit again for 2 hours and this time only I only had 1 whea error so I set that core at -15 and made it so my pc wouldn't power off after 2 hours. Left it sit overnight and so far no whea errors but I know it takes days to know for sure if it's stable so I'll keep an eye on it. vcore peaks at 1.356v and now even with a 10 min cinebench run I'm between 4.6 and 4.7 ghz with +900 points vs what I had before, it would usually settle at 4.4 by the time it started it's 2nd run of rendering so thanks for the motivation, I gave up on it 2 years ago and just left well enough alone.
03-09-2025 10:01 AM - edited 03-09-2025 10:02 AM
when I get bored enough to chase cores around I will give it a try, what I've used ever since my curve optimizer quit playing nice was leaving it at auto and using a - offset of .1500mv on the vcore, clocks maintain 4.9ghz and peak at 5ghz in games and 3dmark runs and 4.8 during cinebench runs while not really effecting the score vs what I was getting with curve optimizer, I did have to adjust some of the PBO limits otherwise temps would start bringing the clocks down. I've pretty much been running it this way for well over a year.
03-09-2025 10:25 AM
I have an update. More fiddling and I have it mostly stable but is requiring more voltage. As another poster stated i was stable with all core -10 curve optinizer before and now not so much. Have to pump more voltage to the memory controller. Also ive found that when the machine is locked up after the monitors turn off. If i power cycle one of the monitors it magically comes back to life. If i have a render or simulation running it messes up at that point the system becomes unresponsive. My cinebench r23 scores are roughly the same as before (28000). Ive also experienced a handful is hard system reboots when running simulations. Not good. I hope asus is looking into this. The previous bios was perfect. But i would like to have the latest security updates.