Pro WS WRX90E-SAGE SE BIOS update

So the new bios is out. But as per usual, no real release notes but the usual Improved system compatibility

I have previously tried to get ASUS to release some more details on the matter, but to no avail. Does anyone with ties to ASUS or with some premium access know anything more?

It would be awesome if someone could make them release some decent notes on these updates… How hard can it be!

1 Like

It installed successfully, no regressions that I have noticed. Tho it did delete all of my saved bios settings in the profile slots.

I find that happens with every ASUS Bios update no matter the board. It happens on my X670E ProArt Mobo as well. I wish there was a way to back up my settings, and reload them after the update.

2 Likes

Yes, this is what I mean. ASUS expect us to simply know these things, when confronted they are always like:

“Thank you for please any inconvenience caused we apologize.”

It doesn’t matter, really, because the normal dude off the street doesn’t matter to them. Only when huge foggin guys from the tech influencer space starts talking, they bend the knee.

ASRock, MSI, and Gigabyte don’t support this either. Both in destroying profiles saved in the BIOS and not loading settings saved to USB. Sounds like maybe some boards will sometimes restore from USB but it’s never worked when I’ve tried.

If one’s willing to install it some of the motherboard software might have the ability to save and restore profiles that you’d expect to happen automatically at the BIOS level. Not the last time I checked, but it’s been a while.

So, so far as I know, taking pics with your phone and typing everything in again is the standard method.

Updating the BIOS firmware can definitely create situations where you don’t want old configurations applying settings that have been changed or removed. Bricking a computer this way is no fun for first-level support.

That said, it’s still important to be notified when the firmware includes breaking changes that will trigger a config reset.

I have the WRX90E-SAGE, and am about to update to 0914. Figured this was the only place that might have some details, heh, at least I did find a thread!

On the BIOS update wiping all the settings, this is true on all BIOS’s I have worked with. But the WRX90E-SAGE is particularly frustrating in this regard, compared to all my other boards. Why? Because every other BIOS, before you update, you can click “Load Optimized Defaults”, and then when you click “Save”, it shows you all of the changes that would be applied, meaning, it very very very helpfully tells you how all your current settings differ from the Optimized Defaults, so that you can write them down and reapply them to exactly what they used to be when you’re done. Every crappy $200 mobo gives you this. But not the $1300 motherboard, no! Nothing at all comes up when you click Save, no way to tell what actual settings are being changed when you load defaults, if you don’t remember what your non-default setting changes were, you’re SOL, good luck getting to where you were after the update.

Makes me so damn stabby. Why would they remove this incredibly useful feature on one of their most expensive boards??

Now, as for the OP topic, i just updated to 0914 from 0901. No negative consequences apparent on my Linux Mint 22.1.

Might as well throw this out though. A few BIOS versions back, I started getting this at the end of my shutdown procedure, after reaching target reboot.target.

“ACPI Warning: _SB.PCI1.GPPC.UP00.DP60._PRT: Return Package has no elements (empty) (20230628/nsprepkg-94)”

The shutdown then hangs for an unusually long time, like 2 minutes, before actually rebooting. I don’t know if that message is connected to the long delay after reaching reboot. target. It didn’t always do either of these things though. Seems like they started at the same time. Has anyone else run into this? If so, any idea what it is or how to fix? My research has turned up nothing.

Yes, this is always the expectation, the reality is that these high end boards are always sold in very few numbers, to tech savvy people, so the priority is dumped in favour of mid-range boards where support cost more money.

That being said, providing ample details (which they definitively have available) for enterprise and pro users who shell out for these boards, should be expected - after all, these boards are more than likely to be deployed in a production setting.

This is also my gripe with ASUS, as much hate as they’ve received from their appalling support and return policies over the years, one could think they would give us some more than bonedust in the BIOS update details. Wouldn’t you agree @wendell ?

Version 1106

13.01 MB

2025/06/13

SHA-256 :63CD5E08E6DEA588C36340FAE3936DA46581F52333F4C120ACA2554AED8C46FD

“1.Update AGESA to support Ryzen™ Threadripper™ PRO 9000 WX-Series and Ryzen™ Threadripper™ 9000 Series Processors.
2.Improve system performance.
Before running the USB BIOS Flashback tool, please rename the BIOS file (A5496.CAP.CAP) using BIOSRenamer.”

We actually got some change notes this time. Also this bios is huge, 5 MB increase

BIOS updated fine but took longer then usual. Just wanted to call out it looks like they changed some of the defaults, two I noticed were Resizeable bar and SRV-IO are now enabled.

BIOS 1106 is a significant improvement over all previous releases. Many of the issues I have been dealing with since January 2024 appear to have been addressed. This is where the BIOS should have been at board release… only took 1 1/2 years to get this far.

Noted:

  1. Failure to boot on reset for CPU mode changes (e.g., enable/disable SVM, i.e. virtualization) is corrected.
  2. Have not yet experienced POST code 0d error on reboot. (This is huge.)
  3. New tuning parameters for specific application/benchmark applications.
  4. New PBO tuning options (no longer need to drill into AMD CBS options).
  5. Improved boot times (major reduction in cycling for both cold and warm boot/reboot).
  6. Changes to default optimized configuration settings.
  7. Option to enable “workaround” for reboots as a result of some monitoring software (example: HWiNFO64) found in Tweaker’s Paradise menu
  8. AMD firmware is now ComboSP6 1.0.0.1 (don’t remember the exact name of the firmware). Likely refers to both Threadripper 7000 and 9000 series compatibility.
  9. X690 firmware updated from 0123 to 0131. About time…
1 Like

Yeh, can confirm this BIOS is at the quality I would have expected this board to ship at. Might actually pick up a 9xxx thread ripper now.

Yes, this update looks great so far. I wonder why they did the minor one last week when this huge one was just around the corner. Just ASUS logic, I guess.

I’m going to check if the AER errors are solved later this week. And I hope the PCIe switches still work :S

Did you go with the flow, or just put the cap on a dongle and installed? I have never had any issues with this naming nonsense before.

I just copied it to my efi partition and flashed it from there. Usb sticks are too much effort

Hum, on my home computer, I have no issues with the update. But typically, when I tried at the office, now ZFSBootMenu doesn’t show, the OData screen is stuck and Q code says AD - Ready to boot event. prior to this I had to set Secure Boot back to Other OS/Custom and that’s all I did.

Any ideas?

Make sure you’ve selected the correct boot device selected under Boot. Good chance it was modified during the BIOS update.

As it was early this morning when I upgraded, many details were lost. It took about 10 minutes based on the timestamps just for the update process which occurred in those pics. CAP->Dongle->EzFlash (nothing was renamed) At some point, which I don’t recall, the motherboard threw Q-Code D4 PCI resource allocation error. Out of Resources. I vaguely remember clearing the CMOS at some point. When I originally started, I was prepared to loose my AMD-RAID partition and did not. I was able to boot back in to Custom Windows UEFI.

Well, it seems that ZBM was less than happy about something. I had to pull it again to make it work. The BMC also struggled. I reflashed it and waited 30 minutes and it worked again.

If you use LUKS2+TPM and didn’t backup your keys, you will have a bad time. It doesn’t unseal after this update (previous updates doesn’t seem to have been large enough for the metrics to change.)