{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by realb00mer:
9/25/2022 11:53:59 PM
15
Same 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
English
-
Edited by realb00mer: 9/26/2022 6:47:10 AMI am sorry that this worked only for me. I looked at crash_info.txt from destiny and had the error: RUNTIME ERROR: EXCEPTION_ACCESS_VIOLATION at 00007FF674AFEB7B I thought that was a memory/virtual memory issue, so I fiddled with it. Indeed, the game worked on another steam account i have. Game on EPIC crashed on the Cross Save account. Well guess is a profile issue or something. Try changing gear and weapons before going to a Destination. PS: Don´t install Windows 11 22H2 update. It sucks and Destiny chokes like crazy. Thank you all
-
This is then error I get, ### RUNTIME ERROR: EXCEPTION_ACCESS_VIOLATION at 00007FF78718FE5B Mine and your numbers are similar but different.
-
Edited by Silphy: 9/26/2022 7:59:11 AMIn regards to that update, another poster has a potential fix: https://www.bungie.net/en/Forum/Post/261811075/0/0
-
I checked this method, and I don't even have NVIDIA FrameView SDK service installed.
-
Just rolled back to Windows 11 21H1 (22000.1042). Let all updates install. Installed Nvidia 516.94, Steam and Destiny 2. Nothing else. No messing with settings. Nada. No stuttering. All is fine. What a mess
-
No fix at all ... I use Windows 10 2H21 with an AMD Radeon Vega 64 and Intel Core i7 8700k.
-
Ah that sucks... Sorry it wasn't any help. Maybe amd has a similar module?
-
Edited by Silphy: 9/26/2022 1:44:48 AMSo if your theory is correct, it's a system specific issue you can fix by changing memory settings. But in my and other people's cases, I can play the game on another test account just fine, only my main account crashes. That excludes system or hardware issues, it has to be account specific. I suppose that gives us another thing to test: someone should log in on a friend's PC and see if their (broken) account works on another system. If it doesn't, that would definitively conclude that it's an account-based issue. I would, but nobody nearby plays destiny. In any case thanks realb00mer, for trying to help. Glad you got your problem solved at least.
-
Tried it already, and it crashes there as well. My acc. -> My PC -> Crashes My acc. -> Friend's PC -> Crashes Friend's acc -> My PC -> Works Friend's acc -> Friend's PC -> Works
-
Thanks for sharing, good to know. Another user made a topic: https://www.bungie.net/en/Forums/Post/261814079?sort=0&page=0 It made me (and SashQa) think; maybe it's steam specific. If the game works on another launcher like Epic, steam possibly has some corrupted file that it loads in via the cloud on any machine that uses an affected profile. That's literally the only other option I can think of besides something on Bungie's servers that's broken on our profiles.
-
Gonna try it on Epic too soon, but if it works, it still can't be a solution because I'm not gonna pay again for the DLCs :(
-
It's mostly for troubleshooting purposes. If there's an indication its a steam file, next step is systematically nuking steam cache, download, shader and config files until it's fixed. Maybe transplant files into the alternate account until it breaks too, which points to the culprit.
-
Tried it and still the game exits without any error codes when launching into an activity. :(
-
Yep, just tried this and same thing.
-
Absolutely booking it home to try this!
