AMD released a beta chipset driver update for Destiny 2 issue that prevented Ryzen 3000 owners from playing the game. AMD still call it a workaround as they work on a full update but many players report that the update works as intended.
Earlier this month, AMD officially released their long-awaited Ryzen 3000 CPUs. The new parts improved Ryzen's gaming performance massively, which is why many gamers decided to upgrade their battle stations with a CPU from Ryzen 3000 series lineup.
And while the majority of these gamers enjoyed the increase in performance, Destiny 2 players reported a strange issue, which prevented them from playing the game.
AMD subreddit and Destiny 2 forums were quickly filled with posts in which players claimed that after hitting the play button in Battle.net, Destiny2.exe file appears in Windows Task Manager but the game refuses to launch.
Players also reported that after they replaced Ryzen 3000 with their older CPU, the game works just fine. AMD and Bungie quickly responded that they are aware of the issue and are working on a fix.
However, more than two weeks passed since Bungie's confirmation, which made players think they could wait for the fix a bit longer than expected.
Fortunately, the fix has arrived today in the latest chipset driver update v1.07.26.0551 . AMD's Technical Marketing Manager Robert Hallock asked Destiny 2 players to test a workaround driver that should help them get into the game.
It's a beta chipset driver and "it may give you an installer warning or two if you're upgrading an existing driver" but according to many Reddit users, it works just fine and they can play the game without any issues at the moment.
Hallock also wrote that Destiny 2 is not a title that is in AMD's standard test suit, as it's difficult to reliably benchmark which is probably the reason why the issue wasn't patched before the launch.
This is not the first time that Destiny 2 has problems with AMD's CPUs. Two years ago, players with Phenom II reported massive crashes to desktop. Bungie fixed the issue two months after the launch.