I’ve overcome the UE5 failures with BIOS updates to set stock power limits, and dumping base clock multipliers down so the CPU only hits 5.4ghz all core instead of 5.7, and have been running this for a year with no issues.
I did hit “Play” before the download was at 100%, and had a blue screen, and then my next blue screen was when my download was reclaiming space. Once it came back and finished it’s been fine. I just repaired and watched my CPU usage spike to 100% for the full duration of the scan, repair download, and space reclamation process with temps steadily climbing up to 67c for the ~10 minute process.
I think this is bnet client file handling issues, almost like the pre-patch data was encrypted and it was decrypting it all on the fly as it unpacked it based on how intensive this was on CPU. (I also wonder if they used encryption, lost a key, and had to re-encrypt and upload it for the patch and that was the go-live delay based on CM post.)