Greetings all.

I'm curious how widespread nonbooting 0d error code is for fellow owners of the Gigabyte Aorus Master x670e (or other AM5 board owners running AGESA 1.0.0.7 based bioses) after updating to either of the F11 bios updates.

Twice now, after running the computer for awhile (24 hours) and getting some odd behavior in games and rebooting, the system hangs on a 0d error that forces a manual onboard bios reset to boot. I didn't have this issue with F10 bios versions. This isn't a FOR SURE issue, since I've not yet done extensive memory testing nor rolled back to F10 to see if the issue occurs, but I figured I'd make a post in case anyone else is running into the issue with F11b or c. I have reseated the RAM, and the only changes I'm making to the default BIOS settings are enabling SATA RAID, expo timings, and subsequent low latency and high bandwidth enabled toggles. Due to the whole exploding processor thing, I've been wanting to keep up with the latest BIOS updates, but am wondering if I'll need to go back to F10 and if it's safe to do so running everything but my RAM at stock speeds (with RAM using the only EXPO timings available for it).

The system has a G.Skill TridentZ5 NEO RGB CL30-40-40-96 2 x 32GB kit, 7950x3D at stock speeds with a Liquid Freezer II 420mm, Gigabye Aorus Master Geforce 4090, WD Black 4 TB m.2 NVME with Windows 11 Pro, two Samsung 960 EVO SATA drives not in RAID, and two big 'ol WD RED SATA drives in a RAID 1 using AMD's RaidExpert stuff. PSU is Antec Signature 1000w.