Since Saturday, everytime when I try to load into any kind of activity from orbit, the game simply closes itself without and error code, nor any error messages. Did nothing special except doing Last Wish and King's Fall on Friday.
Solutions that I've tried and did not work:
1. Verifying integrity of game files (multiple times)
2. Deleting the game's cache (twice)
3. Reinstalling the game (4 times)
4. Updating drivers/firmware
5. Power cycled my modem (twice)
6. Restarted my PC (multiple times)
I have no idea what else to try so any help or a response at least would be appreciated...
EDIT: Tried it on two different PCs, and my PS5 and it crashes on all platforms, tried it with a F2P account created as test, and it works on all platforms without crashing. So I assume the issue isn't on my side.
EDIT: Neither @BungieHelp on Twitter, nor @dmg_04 their Senior "Community" Manager won't respond for almost a week now slowly...
UPDATE: Tried again a few minutes ago, and I was able to arrive in Helm. Now I'm gonna go over all the places like tower, the planets, etc. and give feedback. In case it's fixed, thank you very much for the mysterious person who fixed it. I'll return soon with the updates.
UPDATE #2: Since an hour or so it seems working I did strikes, bounties, nightfalls, visited the tower, helm, throne world, so it seems like fine for now. But the root cause is still missing so I don't know what fixed it. I did not changed or tried anything else other than reinstalling the game a few days ago and every day trying if it crashes or not. Even today it crashed a few times, and since then it works.
#AnswerUs
-
Also, just wondering, did you use DIM (destiny item manager) before this problem started? I don't think it is the cause but if it was then it would be interesting.
-
yeah its not on u been happening to me as well even changed os still no luck our accounts are frozen in that instance till bungie resolves the issue, multiple posts including my own have gotten large community support upwards of 20 votes. Still no response from a moderator or staff to help out with this issue.
-
I am stuck at orbit since sunday (Sept 25th) and I posted in another thread. Tried it on my PS4, same crash. I am hoping atleast for a mention on TWAB.
-
The issue seems to be connnected to your account somehow. I have tried everything and I mean everything and nothing has worked. The game crashes as soon as I load into any destination or activity but I can stay in orbit for what is seems like forever. Then I tried to make a new account and I loaded into the tower without any issues on my first try.
-
Bumping this, Bungie, please say something
-
not sure if this would help but it is worth a shot. https://www.bungie.net/en/Forums/Post/261825775?sort=0&page=0
-
Fyi, buying silver dont fix it lol.
-
Yeah me too, it is a problem with the account not the network or device.
-
I’m always getting contacting servers since this season started. Xbox as gotten worse. I even got a two week ban for internet issues which is this game as all my other play fine just destiny is screwed up
-
Glad to see I'm not the only one.
-
Yup, same here, had the issue since friday. It's an account error resulting in thread_name: unknown, thread_id: 00005114 halt: ### RUNTIME ERROR: EXCEPTION_ACCESS_VIOLATION at 00007FF6D3B6FE90 halt information: (<unknown>) crash: tried to read address 000000000000002E adress violation like this was commonly seen for most people with the issue. it can be checked by going to C:\Users\(your username)\AppData\Local\Temp\Destiny 2\crash_folder\ and looking for this text in the crash_info file. Really hope bungie s gonna fix this soon!
-
-
Edited by dyl: 9/27/2022 10:36:28 AMSame here.
-
yes same tried every thing nothing works since 27-09-2022. its seems from the server side, hope bungie fix it ASAP.
-
I've been struggling with the problem since noon on Saturday September 24th, 2022 (European time). I've tested and tried a lot myself that day, but haven't found a solution. And no response to my post https://www.bungie.net/de/Forums/Post/261806769?showBanned=0&path=0 either.
-
Same issue here since yesterday (26/09/2022). This is a bad problem to begin with, but even more so with the fact that we can't really do anything, except wait, and try to get some attention on this.