Hi! On behalf of a friend I started investigating this in the forums and have found tons of listed cases of the exact same problem. The problem is that the game has severely reduced FPS/responsiveness on character select, equipment menu, and eververse screens, then any attempt to load any destination generally results in a nearly unplayable experience that results in a crash within 2-5 minutes. There are at least 30 reports that I have found in the PC help section with just cursory digging. There has been one poor Moderator/Mentor that has been trying to address these things, but overall the lack of any visibility from Bungie or even a small acknowledge of "Yeah hey that may be related to X/We're looking at it" would bring some bloody solace to these people who, honestly, have all been completely screwed out of the entire Dawning event unless they kicked on a spare laptop or something to grind. The problem seems to have manifested shortly after the December 17th hotfix, https://www.bungie.net/en/Explore/Detail/Update/49994 Here is a broken down highlight reel of what I have determined comparing multiple painfully quiet threads and DXDiags shot into the wind. --- Commonalities --- --- CPU --- --- AMD Ryzen --- Doctor Hat AMD Ryzen 7 3800X 8-Core Processor https://www.bungie.net/en/Forums/Post/257976813?sort=0&page=0 https://pastebin.com/MiYaF7H5 Sol Chariot AMD Ryzen 7 3700X 8-Core Processor https://www.bungie.net/en/Forums/Post/257993238?sort=0&page=0 https://pastebin.com/zuZqr2Ry Peter 758 AMD Ryzen 7 2700X 8-Core Processor https://www.bungie.net/en/Forums/Post/257977064?sort=0&page=0 https://pastebin.com/QA6zVqG9 Oni-Link40 AMD Ryzen 7 2700X Eight-Core Processor https://www.bungie.net/en/Forums/Post/257966295?sort=0&page=0 https://pastebin.com/q2GVmM9J MontesVerdes AMD Ryzen 5 3600 6-Core processor https://www.bungie.net/en/Forums/Post/257999341?sort=0&page=0 https://imgur.com/a/fHaevSE Not a DXDiag but specs MonokumaTV AMD Ryzen 5 3600 6-Core Processor https://www.bungie.net/en/Forums/Post/257965906?sort=0&page=0 https://pastebin.com/tZk0yUTc Abdhul AMD Ryzen 5 1500X Quad-Core Processor https://www.bungie.net/en/Forums/Post/257959262?sort=0&page=0 https://pastebin.com/bR6Y6t5v --- Intel --- SatanicEcho Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 CPUs), ~3.6GHz https://www.bungie.net/en/Forums/Post/257982326?sort=0&page=0 https://pastebin.com/DLrcqubd Chimera91 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 CPUs) https://www.bungie.net/en/Forums/Post/257968812?sort=0&page=0 https://pastebin.com/TLiKXZ9q Drowshall Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 CPUs) https://www.bungie.net/en/Forums/Post/257966480?sort=0&page=0 https://pastebin.com/DphT0FRQ Hinata Hyuga Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 CPUs) https://www.bungie.net/en/Forums/Post/257943500?sort=0&page=0 https://pastebin.com/up90fGXj --- Unknown --- ThePancake https://www.bungie.net/en/Forums/Post/257965772?sort=0&page=0 OldManJenkins https://www.bungie.net/en/Forums/Post/257976813?sort=0&page=0 Zhangkerui https://www.bungie.net/en/Forums/Post/257976813?sort=0&page=0 DXDiag pastebin is gone --- Windows OS --- All cases are Windows 10: Pro or Home, 64 Bit (10.0, Build 18363) (18362.19h1_release.190318-1202) or (10.0, Build 19042) (19041.vb_release.191206-1406) All cases are DirectX 12 --- GPU --- Mix of cards, all NVIDIA 2070s, 2060, 1660s, 1080, 1060s, and even a 960 1440 or 1080p DisplayPort, DVI and HDMI were all present Version: all on 27.21.14.6089 except one guy who was on 27.21.14.5671 --- HARDWARE --- Audio/video capture and speakers/audio card were almost completely unique Same with I/O, like keyboard etc, USB, PS/2, SSD and HDD, etc. --- Error Signature --- --- AppHangB1 --- Most were AppHangB1. Same signature and fault bucket across the board. Fault bucket 1762365875195829865, type 5 Event Name: AppHangB1 Response: Not available Cab Id: 0 Problem signature: P1: destiny2.exe P2: 24550.0.0.0 P3: 5fd594d5 P4: d51d P5: 67246080 and Fault bucket , type 0 Event Name: AppHangB1 Response: Not available Cab Id: 0 Problem signature: P1: destiny2.exe P2: 24550.0.0.0 P3: 5fd594d5 P4: d51d P5: 67246080 --- AppHangTransient --- Some cases involved AppHangTransient (notably AppHangTransient did not couple with AppHangB1, they were not always present together, and AppHangTransient was not in every case) Fault bucket , type 0 Event Name: AppHangTransient Response: Not available Cab Id: 0 Problem signature: P1: destiny2.exe P2: 24550.0.0.0 P3: 5fd594d5 P4: unknown P5: unknown P6: unknown P7: unknown --- RADAR_PRE_LEAK_64 --- Radar pre leak 64 happened in one case, but for several people if it occurred it was for a different game. However, in this case there were also AppHangB1 elements. Fault bucket 1196231372427560029, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: destiny2.exe P2: 24550.0.0.0 P3: 10.0.18363.2.0.0 There were also some APPCRASHes and AppHangTransient without an AppHangB1 but it was only in one case (Peter 758) --- Conclusion --- There appears to be no distinct commonality between any of these errors other than either it happens way more often on Ryzen CPUs or Ryzen users are more likely to post about it =P That said, the distinct common factor is AppHangB1 with the exact same signature across the board. However, general fixes tend to not work. Clean driver reinstalls, disabling third party controller software, updating drivers, rolling drivers back, changing video settings, shifting NAT around, swapping gear around, fiddling with adaptive sync or resolution or refresh rate, reinstallation, verifying game cache, flushing DNS, reinstalling Steam, creating a new account, creating a new character, run as administrator, firewall tomfoolery, etc. Nothing works consistently or very often, though sometimes these things do seem to fix it for one person or another. While it is not my job, so I will be slow at this, I ask anyone who is experiencing the same issue to post their DXDiag here for collection purposes and I'll edit the main thread with more commonalities as I find them. Update - While other methods didn't work for my friend, Whiplash below clued in a Reddit brand of snake oil that ended up working. To explain in detail: NVidia Control Panel -> Manage 3D Settings -> Program Settings -> Destiny 2 -> Halfway down you override Shader Cache from Global On to OFF. This actually coincides with what my original belief was to be the problem given that the biggest impact seemed to be when in the character screen or equipment screen. That some texture/shader/material got effed up. Unsure if this is the root of the problem, but it also coincides with the fact that every case I had looked into involved an Nvidia card. Bungie, if you have any traction on this post at all, please look at this or poke Nvidia about it. Update 2 - Today's Nvidia drivers on 1/7/2021 seem to have made the problem much worse and crash faster when shader cache is on. Neat.