Well, it's because the disks are being bonded by the UEFI >> OS needs a way to talk to the pseudo HW device created by the board / RST.I ended up installing the Asus-provided drivers, and it works now.
And now just to worry you a bit, monitor your CPU/IMC voltages for a while in HWiNFO during workloads or while idle to see what the max voltages being pumped into your CPU are. Just to be on the safe side coz ASUS has been guilty of killing a few CPUs lately
Their enthusiast boards had their best monkeys doing the UEFI coding and they might have passed their knowledge onto the lesser UEFI monkey coders there. Personally, I would just double check the voltages for additional peace of mind.In all seriousness, do you think it would be an issue with my board? It's corporate-tier, and I'm not even currently running the memory at anywhere near Raptor Lake speeds (4800 MHz at the moment).
Their enthusiast boards had their best monkeys doing the UEFI coding and they might have passed their knowledge onto the lesser UEFI monkey coders there. Personally, I would just double check the voltages for additional peace of mind.
Yes. Just check the max voltage value over a period of running different workloads.I'm keeping tabs on CPU voltages mainly, right?
Just do a synthetic benchmark to put it under max load.
Yes, before you can create a new RAID array, you have either to break the old one (the related information are within the hidden track0 of both SSDs) or to do a secure erasure of all data (inclusive the hidden ones).When I go into the RAID (Intel Rapid Storage Technology) menu in the BIOS, it says no disks are detected. Is this because I still have the striped (RAID-0) data on the 2 disks from my previous rig?