I keep crashing consistently when landing at a destination/tower and getting the error code marmot message. I have tried many things reinstalling the game, verifying game files, deleting specific files, etc...
and the game keeps crashing when I go to a destination after logging in but I have rare moments where I can play for a bit with no crash but eventually the game will crash.
Here are my specs
PLATFORM: Steam
SYSTEM INFO:
CPU: Intel Core i7 7700K @ 4.20GHz
GPU: 4095MB NVIDIA GeForce RTX 2070 SUPER (MSI)
RAM: 32.0GB Dual-Channel DDR4 @ 1069MHz
GPU Driver Version: 555.99
OS Version: 22H2 (OS Build 19045. 4529)
ISP: Metronet
Upload: 287.07 Mbps
Download: 231.23 Mbps
DxDiag: [url]https://pastebin.com/Nan2gBpD[/url]
ISSUE: Game crashes when landing on a destination
REPRO STEPS
1. Log in
2. Open navigation/destinations
3. Go to destination
ACUAL RESULT: At or close to the end of loading screen the game crashes with error code message
EXPECTED RESULT: Game doesn't crash when landing
CRASH LOG: [url]https://pastebin.com/L2hx803C[/url]
NOTES: The game does crash but it doesn't actually close because its still open in task manager
Here is an image as proof: [url]https://imgur.com/a/cESpOUh[/url]
-
So I'm having the same issue (except now I'm getting random shutdowns while playing), but based on my own evaluation (reviewing old posts referencing the Marmot error), Bungie will likely not respond to this post ([url=https://www.bungie.net/en/Forums/Post/264033285?sort=0&page=0]my post[/url] is almost a week old with no reply). That being said, given your DxDiag, you have multiple storage options. One of the things I did was move Destiny 2 off my secondary 980 Pro to my OS nvme drive. I also uninstalled and reinstalled Steam entirely (if you plan on trying this, backup your screenshots first). And after reinstalling D2, I checked both Public and Private on the network dialog that appears when first launching the game. One of these three things seems to have addressed the issue. Lastly, I am getting a new PSU to address the shutdowns, but what I noticed is that the most recent NVIDIA drivers might've been the culprit, so I rolled back to 551.61 from February, and I went all day yesterday with no PSU shutdown. Just mentioning that in case you want to give that a go as well. I used [url=https://youtu.be/oDMyQuqixhE]this video[/url] as a guide to roll back my drivers (as I've never done it before). All in all, I only started having this Marmot issue [i]after[/i] the release of the Final Shape. So whether they'd like to address it or not, we're reacting to an issue with the game itself. Hopefully you can get it isolated and figured out.