• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

AMD Addresses "Destiny 2" Bugs on Ryzen 3000 with a Chipset Driver Update

btarunr

Editor & Senior Moderator
Staff member
Joined
Oct 9, 2007
Messages
47,853 (7.38/day)
Location
Dublin, Ireland
System Name RBMK-1000
Processor AMD Ryzen 7 5700G
Motherboard Gigabyte B550 AORUS Elite V2
Cooling DeepCool Gammax L240 V2
Memory 2x 16GB DDR4-3200
Video Card(s) Galax RTX 4070 Ti EX
Storage Samsung 990 1TB
Display(s) BenQ 1440p 60 Hz 27-inch
Case Corsair Carbide 100R
Audio Device(s) ASUS SupremeFX S1220A
Power Supply Cooler Master MWE Gold 650W
Mouse ASUS ROG Strix Impact
Keyboard Gamdias Hermes E2
Software Windows 11 Pro
AMD fixed a bug that caused "Destiny 2" to be unplayable on 3rd generation Ryzen processors, through updated chipset drivers. The company had, earlier this month, released an update to its processor microcode with the AGESA ComboAM4 1.0.0.3ABA update (not to be confused with 1.0.0.3AB), before pulling it for causing other bugs. Ahead of its publication on AMD website, Robert Hallock, the company's technical marketing head for processors, posted a Google Drive link to the driver's installer. It bears the version number v1.07.26.0551, and is marked beta. Hallock comments that this is a "workaround" to help "get you into the game." It looks like a more permanent solution to the bug still lies in updating the microcode, once AMD figures out what went wrong with 1.0.0.3ABA.



View at TechPowerUp Main Site
 
Was it really performing that bad? I think I saw Destiny 2 played on a Ryzen 3000 series and the FPS were lower than Intel's but it was not considered unplayable unless I missed something here.
 
הורדה.jpeg
 
Was it really performing that bad? I think I saw Destiny 2 played on a Ryzen 3000 series and the FPS were lower than Intel's but it was not considered unplayable unless I missed something here.
It wouldn't launch at all, framerate was not an issue
 
according to Reddit , Destiny is the only game that use RDRAND instruction.This is an AMD bug , only Ryzen 3000
 
Last edited:
Now this makes more sense than "microcode"...
 
I must say, I’m surprised something like this even occurred. Has there been any examples in recent history where a new CPU line broke a relatively modern game, or even just a program? I know new GPUs can sometimes do this, but I can’t recall ever hearing about a CPU doing so because they typically handle backward compatibility so well.
 
Welcome to another episode of "Problems faced by a early adoptor"...
But this one is most bizzare issue of them all..i wonder if old games will run on this CPU...
 
Back
Top