EDIT: IT STARTED WORKING!! I HAVENT CHANGED ANYTHING ON MY END. All I did was restart my PC one last time tried the game and now it works.
-
For me it still crashes. Tried restarting, verifying again, but as soon as I launch into an activity, it exits...
-
Having the same problem. Tried everything I could think of or suggested by others. Just posting here to make sure Bungie knows more than just a handful of people are having this issue.
-
Same issue for me unfortunately (since 9/26 afternoon). Glad yours started working! There's hope. Just adding my experience to the thread. Ran through all the suggested solutions (validating Steam files, reinstalling, updating game drivers, deleting temp files, etc...). Booted up the game via GeForce Now on an entirely separate machine and still crashed when trying to Launch out of orbit to any destination. Not sure if messing with any 3rd party inventory managers (DIM, light.gg) would have played a part in causing this. For now I'll pray to the Bungie gods and just keep trying.
-
Still crashing for me as-well, Good thing yours is fixed
-
Bumping for exposure for others still having this issue.
-
Bumping back to top
-
Wrote on another topic about this issue, but reposting it here in case it helps visibility: I came here due to this exact same issue and found your post when looking around. I played Destiny 2 for pretty much 8+ hours today with no issues before this started, I was helping a friend that recently came back to the game (they are on PS5) after being away from it for a couple of years. At night we were doing patrols on the Castellum as I was teaching him about resonance weapons, crafting and whatnot while trying to get him a mini-tool, after running around there for a couple of hours the game froze and crashed twice in a matter of 15min or so after no issues the whole day, after the last crash I got out of the PC for a bit. After I came back in an hour or so and tried to join him back I found that I was unable to load into any destination at all. The game opens with no issues, I can access all of my characters, the store, the tabs, can move things around with DIM, but as soon as I try to load into any destination at all I encounter a hard crash (crash to desktop). Have tried everything available from my side, to my knowledge this looks a lot like some truncated issues server side. Got into a friend's account to test and was able to load into anywhere with no problems at all. UPDATE: downloaded D2 on my PS5 and encountered the same issue of crashing when trying to load into any destination UPDATE 2: downloaded D2 to my laptop and same thing. So this is definitely not something client side.
-
this is happening to me as well. Nvidia GPU, Intel i9, Windows 10 21H2, MSI Mobo
-
My account was fine today. I linked my epic account to my bungie profile a few a hours ago to grab the epic emblems and now the game crashes to desktop in all three platforms epic, steam and PSN. Looks like the cross save is screwed up. At bungie.net I can see my characters for steam and the other two platforms don't match. Worst part is I can't unlink them because I bough silver a few days ago. Bungie HELP please
-
Just would like to add my voice to the conversation. From all my testing it's definitely account based, as the crash happens on 3 separate computers and Stadia. A fresh account works just fine on said systems. Sadly it does seem to be a issue on the server-side end so we are currently SOL until Bungie notices this thread. I guess I'll go touch some grass until this gets fixed ¯\_(ツ)_/¯
-
Edited by Grim: 9/26/2022 6:57:36 PMPutting my note here as well, same thing happened this morning (roughly 10 hours ago), did some rounds to fix it: cache deletion, file verification, totally reinstalling the game, updating, then rolling back on the GPU driver, nothing worked, the game contiues to crash, both steam and epic versions. After reading through all the similar posts, I really think that this issue isn't on "our end". Hopefully this'll get fixed as soon as possible. Ps.: Checked my crash log as well, and though the code at the end of the runtime error is different, apart from that, it is kinda the same as Silphy previously wrote. Could this be because of the cross save perhaps?
-
Edited by realb00mer: 9/25/2022 11:53:59 PMSame issues on Windows 11 22H2, RTX 3080 I messed around with Windows virtual memory and got the game working. I was able to go to Destinations in game. GO TO: System Properties > Advanced > Performance > Settings > Advanced > Virtual memory > Change... 1. Uncheck -> Automatically manage paging file size for all drives 2. Check -> No paging file 3. Click -> Set 4. Click -> Ok 5. Restart After restart do the same thing again but set a Custom size in MB I have 32 Gigs of RAM, so I used the following sizes: 1. Initial size (MB): 16000 2. Maximum Size (MB): 32000 3. Click -> Set 4. Click -> Ok 4. Restart Try Destiny again. It worked for me, maybe will work for you guys. Good luck
-
Anyone have any insight to this? Checked this morning and same exact issue.
-
Topic body
-
We’ve had 1 response that someone got it working again. Any others?
-
Edited by Mo: 9/25/2022 12:42:54 PMi tried to change the Window mode from ( Windowed Fullscreen ) to ( Fullscreen ) and this fixes the problem
-
Hey got an update, it started to work for me now. When the game stopped responding on the main menu as it did, I have it a few mins and came back to my PC to find the game didn't crash, and now it works fine every time I launch it. Didn't try anything to fix it so it's solved for me magically.
-
Edited by Silphy: 9/25/2022 7:14:05 PMOkay so, I made a new PC steam account and can play just fine on that, which excludes any hardware or system issues. Played all the way through the tutorial missions until I could load into the tower with players.
-
I forgot to mention, the game does make crash logs during this. They should be located at %localappdata%\Temp\Destiny 2\crash_folder\crash_folder_[random-string]\crash_info.txt Mine says halt: ### RUNTIME ERROR: EXCEPTION_ACCESS_VIOLATION at 00007FF74718FE90 halt information: (<unknown>) crash: tried to read address 000000000000002E fatal error detected, current status was: And then a ton of status information at the time of the crash. Does this mirror everyone else?
-
I borrowed a Destiny 2 / Steam account to test and it worked. With the borrowed account, I was able to cleanly load into activities and fly on planets. Result of the test, it's not due to the players not being able to load into activities, it's the account frozen in orbit.
-
Same trouble here, I made the upgrade for Windows 11, new steam instalation and the same thing happened. Tried everything there is on internet.
-
Have you verified the game files?
-
i reckon theres a few people with the same issue. after thorough testing it seem NOT to be from you personal device, but rather an account wide issue for certain players. furthermore, it seems to be a problem with placing these players in an instance, hence the crashing with no error on loading a zone. this isn't fixable(most likely) by you but rather an error on bungie's part
-
Same problem, played a lot yesterday and now suddenly it doesn't work any more. Did a ton of troubleshooting, including the usual culprits like verifying and graphics drivers. I did do something new by participating in the Vow of the Disciple raid and when I left my fireteam, it immediately forced me into a cutscene about Rhulk, which was notable. Normally it only does this when I start the game.
-
I have now completely reinstalled Windows and graphics drivers. So far no success Game keeps closing when starting an activity and I see my desktop again.
-
I have the same issue I tried to uninstall the game,update the GPU drive, and turn off shader cache size but nothing works it's weird yesterday the game was completely fine I have no idea what happened today