[b]Edit 6: Issue fixed. Can load into the tower and HELM again. No action taken, assume bungie fixed it. [/b] Edit 5: Made a video: https://www.youtube.com/watch?v=mrAT8o89yT8 Edit 4: As per iaenr's excellent suggestion, tried Geforce Now, a game streaming service. Still crashes. Edit 3: [b]Info reply down below updated with stickied thread topics[/b] Edit 2: [b]Added info in reply below[/b] [b][u]Edit 28/9/'22: Bungie, after hours of troubleshooting and many players having the same issues when using other people's PC's to test, we can 99% confidently say it's a profile bound bug beyond our ability to fix. [/u][/b] We need someone to investigate if we're stuck in an unending ghost session somehow, if we somehow got a corrupt item or shader which crashes the client on load, If steam/bungie's cloud has a corrupt file or cache somewhere we cannot remove, Etc. Copy my profile on your end to test if you want, I [i]guarantee[/i] you it'll crash on any system when loading any place. Please give us some acknowledgement this and the other threads were noticed, there is no other way to contact you. [b]Original post:[/b] Problems started last friday the 23rd/Saturday morning when the previous day everything was fine. Problems started roughly the same time for all affected. Tried all the usual troubleshooting steps. Tried deleting my CVARS just in case, no luck. Tried validating files half a dozen times. [b]My alt account can play just fine though, so [u]there's nothing wrong with my system[/u].[/b] I played through the entire starting campaign and part of witch queen on the alt account to test. [u]Just this, my primary account can't[/u], and it crashes out of destiny 2 when trying to load the tower, the HELM or any planet. Edit: relatively unique stuff I've tried compared to other player's topics: Tried setting destiny2.exe and destinylauncher.exe to high performance in the windows system->graphical settings menu, as well as NVIDIA's control panel. Tried disabling Intel HD graphics and run only on the Geforce 1080, then tried it the other way around. In both cases it crashes to desktop the same way. Tried limiting firewall to load instances as solo player (don't generally use this, but someone on reddit who had their issue fixed randomly mentioned it was among the things they tried) Destiny's crashlog mentions the following: [quote] ### RUNTIME ERROR: EXCEPTION_ACCESS_VIOLATION at 00007FF6B085FE90 halt information: (<unknown>) crash: tried to read address 000000000000002E fatal error detected, current status was: etc. [/quote] Edit: Reply below has the full log in a pastebin