{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
3/18/2024 11:53:14 PM
1
Error Code Marmot (the bane of my existence)
I have over 2000 hours on this game, and for the past 2 months I haven't been able to launch my game. Every time I try to launch I get error code marmot telling me to verify my game files, so I do that but again error code marmot. I have done everything I can to fix it, deleting everything in the Destiny 2 disc folder and verifying files, I've tried to edit things in registry edit to launch my game, I've gone into reddit forums and found specific files to delete and verify with but still no luck. I have tested my ram, I've made sure my drivers are up to date, I even spent 2 days cleaning out my entire PC making sure that it's dust free. I've checked my security settings and made sure nothing named Destiny, Steam, or Bungie was blocked. I don't know what to do. I really want to at least play one week of guardian games so I can get the skimmer but I don't know if I'll be able to at this point.
-
1 Antwortenif you've already followed these steps: - uninstall the game completely (preferably a clean-as-possible uninstall with something like Revo Uninstaller to clean its leftover registry entries, be careful if you use that one) - from the start menu or in the address bar of explorer, type %appdata% then open the 'Bungie' folder there if present and delete the 'DestinyPC' folder - from the start menu or in the address bar of explorer, type %temp% then delete the 'Destiny 2' folder there if present - uninstall BattlEye if it stuck around as any other game you play that may need it will reinstall it - make sure your graphics drivers are up to date and (following a fresh reinstall after the above) you're still getting the error, it's possible that it's a hardware issue. sometimes a failing ram stick can cause this. Memtest86 is good about letting you know if there's a ram issue
