{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Atheons Milk Shooter:
1/6/2022 3:21:23 PM
2
MARMOT will be the end of me
So, after surfing all the sub reddits, bungie help forums, youtube, you name it, I simply cannot find a fix for the error code: marmot that has worked for me. This has gotten to the point where I'm contemplating giving up as I only just came back to the game a few months ago and purchased both forsaken and shadowkeep given the f2p vault that occurred. Now I have the forsaken dlc sitting in my account half completed just waiting to be vaulted. I've verified files, uninstalled and reinstalled the game, deleted multiple different files and re-verified to reinstall them such as battleye. I've even gone as far as running the memory diagnostic to eliminate any potential hardware issues. FYI this error has happened ever since I've tried to run the game on my new pc if that helps. I simply can't understand how bungie has known about this problem for months now and still haven't come out with a 100% effective solution, I guess they have more important things to do (like make more money off witchqueen). I thought I'd post this as a last ditch effort in case there is some genius out there who can be more helpful than bungie themselves. Apologies for the huge rant, however I know I'm speaking on behalf of many frustrated players.
Thankyou.
-
Does the error occur consistently (i.e. every time you hit enter on the startup page), or was it similar to my situation with it happening intermittently at seemingly random moments - during load times/patrol? You mentioned that you have a very small amount of other things running, but have you played other games that utilize Battleeye? In the first scenario (with consistent crashes), I've seen a few reports that uninstalling/removing other copies of Battleeye (like from rainbow six siege) can help prevent what might be a conflict of some sort from causing the Marmot error. Not sure if it will help, but I thought it worth mentioning as I can see you went through a majority of the other troubleshooting steps suggested, including the one that ultimately resolved it for me - memory. The full list of battleeye supported games can be found here - https://www.battleye.com/ Lastly, it's worth checking the crash folder location to see if you can find any details on the specifics of your marmot crash if all else fails - default location: C:\Users\'YourUsername'\AppData\Local\Temp\Destiny 2\crash_folder Mine was a memory fault trying to access a seemingly null location.
