{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
7/8/2019 4:39:28 PM
11
-
Over two weeks now, at the very least a status update would be appreciated.
-
ETA for a potential hot-fix?!?!
-
Pretty sure we wont get a "hot fix" we have to wait for a weekly patch. What week it happens will be anyones guess.
-
Latest report is a BIOS fix. AMD has said they have pushed the data to vendors, now its up to them to release the corresponding BIOS according to this article. AMD Ryzen 3000 systems need a BIOS fix for Linux, 'Destiny 2' issues https://www.engadget.com/2019/07/12/ryzen-3000-systemd-bios/?guccounter=1&guce_referrer=aHR0cHM6Ly93d3cuZ29vZ2xlLmNvbS8&guce_referrer_sig=AQAAAHLMaesq1IJSowyi-sdF0QWloyiEKyI1vk2JmZC4r9mcvexu3Hv6LE7VKtVSANoX9RV2x4Hra8H2mRGzDv1TmsDMDPiaZVH4hQ8W6jcRPC5gML5VT_ZOnVTlI8g-lOIu_WIIqRpbYcCdb842qPbn5RFKzSP61jLQzQdS_x5hYUJK
-
A BIOS update that adds the new AMD microcode will take months in some vendors. That is not viable. This has to be fixed in software, Destiny 2 itself should stop using whatever CPU feature it is they are using.
-
https://www.pcgamer.com/amd-wants-destiny-2-players-to-help-test-a-beta-chipset-driver-for-third-gen-ryzen/
-
New AMD beta chipset drivers have resolved the issues for me and several others.
-
Yes found that out on this thread. https://www.bungie.net/en/Forums/Post/252793241?sort=0&page=0 Thanks.
-
Sorry wasnt home when you asked for a dmp file but here it is.
-
Here is your dump turned into a paste bin: https://pastebin.com/ZDp3GQrR
-
Thank you. Notepad and word both locked up trying to open it.
