{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by meischdaddy30:
10/30/2025 4:11:47 PM
2
Marmot
Last time I played was Monday and everything was good, but today I'm getting semantic satiation from seeing the word marmot. First time logging in since Tuesdays update. Game won't load to main menu.
Steps I've tried:
1. Verified game file integrity, no corrupt files. Loaded game, Marmot.
2. Deleted all local files, except for packages folder and re-verified. Loaded game, MArmot.
3. Reinstalled game. Loaded game, MARmot.
4. Did sfc /scannow and chkdsk .. /f on all drives (0 errors), restarted PC. Loaded game, MARMot.
5. Changed the d2 language because it's helped others in the past. Loaded game, MARMOt.
6. Windows preview update available, installed, restarted PC, verified again. Loaded game, MARMOT!
Drivers are updated
I feel like the Brady bunch over here, MARMOT MARMOT MARMOT! Steps 1-4 were all taken from your guide (https://help.bungie.net/hc/en-us/articles/4405096052244-Error-Code-MARMOT). I've done full diagnostic scans with samsung magician for my drives and they were both perfect. Plenty of space on each (166gb free and 438gb free).
The only progress I had was #2. Afterwards the game actually loaded to the main menu, but froze for 2-3 minutes when verifying contents then crashed + marmot and it won't open to main menu again unless I repeat step 2. Which I've done 3 times with the same outcome so I stopped because we all know Einstein's definition of insanity. I figure it's not my RAM because otherwise the game wouldn't have even loaded to the main menu. But I'm no professional here so maybe I'm wrong.
Thoughts?
PS: Hopefully you got a chuckle or a text message "LOL" which is the equivalent of a smirk or smile.
-
2 RepliesGood afternoon. I found a fix to our problem (potentially), no thanks to bungie. Is steam closing for you when you launch Destiny 2? I noticed after a while or trouble shooting that my steam was not minimizing when launching destiny and battle eye, but crashing. When I launched destiny today I immediately relaunched steam as soon as it closed and the game loaded in fine. It's a bit of a pain, and I cannot tell if its a hardware problem on my end or a software issue from Valve or more likely Bungie as every other game in my library is fine. Important to note I did tell steam to repair the library destiny was in before testing reopening steam, so you may have to do that as well. Hopefully renegades is worth this trouble.
