Destiny 2 AMD Ryzen 3000 Issues solved with chipset driver update
Bungie’s Destiny 2 doesn’t currently work with on AMD’s latest CPU. It’s was not clear why this is currently the case. The problem cropped up a few days ago when Ryzen 3000 early upgraders found they couldn’t run the game. A week ago, Redditor Trinsikk posted. AMD now has a solve available.
AMD has issued a statement regarding a fix for the continued compatibility problems Ryzen 3000 users have been dealing with:
"AMD has identified the root cause and implemented a BIOS fix for an issue impacting the ability to run certain Linux distributions and Destiny 2 on Ryzen 3000 processors. We have distributed an updated BIOS to our motherboard partners, and we expect consumers to have access to the new BIOS over the coming days."
Robert Hallock, the company's technical marketing head for processors, posted this (incl fix):
Concerning Destiny 2, this is indeed something we caught after launch. Plain and simple: I'm sorry. It is not a title that is in our standard test suite, as it's difficult to reliably benchmark. Going back to the topic of Destiny 2, I'm hoping you can help me test a workaround driver that should get you into the game. This is a beta chipset driver, and it may give you an installer warning or two if you're upgrading an existing driver, but I believe this should work around the D2 launch issue.
AMD Ryzen 5 3500 and three Pro models Coming - 07/29/2019 08:40 AM
AMD will be releasing a Ryzern 5 3500 as well as Ryzen Pro variants of the Ryzen 5 3600, Ryzen 7 3700 and Ryzen 9 3900. A Eurasian registration database points that out....
Review: AMD Ryzen 5 3600 Six core processor - 07/22/2019 01:38 PM
We again review a six-core model Ryzen 5 3600 processor, you know, the one without an X. It's 200 MHz slower on the base and turbo clocks, but a whopping 50 bucks cheaper. Worth it? Yeah, we think so...
Review: AMD Ryzen 5 3600X Six core processor - 07/19/2019 01:36 PM
We recently reviewed the Ryzen 7 3700X & Ryzen 9 3900X processors from AMD. How about the 3600 series six core parts eh? Well, let's check out the new Ryzen 5 3600X in this review, which quite fr...
AMD Ryzen 7 3800X overclocked to 5.9 GHz on LN2 / DDR4 at 5774 MT/s - 07/15/2019 06:27 PM
Well, one thing is a certainty, there's isn't a lack of news on AMD products lately. A pro-overclocker (Tsaik) subzero cooled a Ryzen 7 3800X with LN2. The 8-core processors was able to reach 5.9 G...
AMD Ryzen 7 3700X & Ryzen 9 3900X review with benchmarks leaks out - 07/05/2019 06:39 PM
It is apparently rather hard to keep articles offline, even for some very professional and well funded websites. After yesterday's NAVI leak today the turn goes towards the German-based pcgameshardwa...
Senior Member
Posts: 8825
Joined: 2005-07-15
LOL that's why it would not launch, i had no idea it was my 3600 causing it. :p
EDIT: Installing that chipset driver now to test.
Senior Member
Posts: 15299
Joined: 2018-03-21
LOL that's why it would not launch, i had no idea it was my 3600 causing it. :p
EDIT: Installing that chipset driver now to test.
It apparently doesn't work if SVM is enabled in the bios, suggesting there might be some register save and restore trickery at work.
Senior Member
Posts: 126
Joined: 2007-05-28
So is it a BIOS update or a chipset driver update needed ?
Headline says chipset, text says BIOS o_O
Senior Member
Posts: 15299
Joined: 2018-03-21
it was supposed to be a bios update, but they are resolving it with a driver right now.
Senior Member
Posts: 15299
Joined: 2018-03-21
It actually is known why Destiny 2 wouldn't launch,
the game makes use of the RDRAND x86 instruction on Intel Haswell+, and AMD Jaguar+ architectures, AMD's implementation is guilty of returning -1 after coming out of certain power states, instead of a value in an expected range as the Seed would determine.
This should only have posed a problem on Zen 1/2 after a Sleep and resume cycle, but because Ryzen 3k is completely sleeping individual cores it was experiencing the same thing without such a cycle.
Reason for this is that AMD doesn't implement core entropy states.
What is not known is how the chipset driver resolves it.
Is it saving the state prior to letting the cores sleep and then restoring them on the next time the instruction is utilised?
Is it virtualizing an entropy state or just emulating the instruction entirely?