I’ve been having issues launching Destiny 2 on my ROG Xbox Ally X since November 12. The game was running fine before this, but now whenever I launch it through Steam, I get a black screen for a moment before it closes and returns me to Steam. No error message or anything. Initially, a small green icon with the word “On” would briefly appear before the crash. That stopped happening after I reset Windows, but the game still crashes. I’ve spent several hours trying to figure out what’s going on. So far I’ve tried: * Restarting the Ally multiple times. * Checking Armoury Crate game profiles and settings. * Rolling back my AMD graphics driver. * Attempting to uninstall the latest Windows update. * Using System Restore to roll Windows back to November 10. * Resetting Windows using the cloud download option while keeping my personal files. * Reinstalling Steam and Destiny 2. * Launching the game directly from the Windows desktop instead of Xbox Full Screen Experience. Nothing has fixed it. After resetting Windows, I actually managed to get Destiny 2 to launch briefly, but it wasn’t displaying properly in fullscreen. That’s occasionally happened before, and normally closing and relaunching fixes it. Unfortunately, when I tried launching it again, it went straight back to crashing. I also checked Windows Reliability Monitor and found two hardware-related events: * LiveKernelEvent 1a8 * LiveKernelEvent 1b8 Both were recorded on November 12. I’m not sure whether they’re directly related to the crashes. For reference, my system is running Windows 11, and the AMD graphics driver I had before attempting the rollback was 32.0.32015.7029. Windows had also installed KB5132061, although I don’t know whether that’s what’s causing the issue. I’ve since found other Ally X owners reporting almost identical problems, including this thread: https://www.bungie.net/en-us/Forums/Post/265379533 At this point, I’m out of ideas. I’ve spent hours troubleshooting and even reset Windows, but Destiny 2 still won’t launch reliably. Is anyone at Bungie aware of this issue, or is there a known fix? I’d really appreciate any information.