Sharing my own experience with this error as a separate topic for greater visibility. This error started occurring and 'crashing' my game after the festival of the lost release this year. Ever since then, I have periodically seen the marmot error occur while playing the game. Specifically, it happens while loading into destinations/activities, although it has rarely occurred a couple times while in patrol. What actually happens is that an error box with marmot and a trailing message appears (game files corrupt... etc.), but the game continues running as a background process (it cannot be brought back in the foreground and resumed, although steam considers it a running process). This happens intermittently and seems to go away for a few hours after a hard reset of the PC or a reinstallation of the game. Please note that I have gone through all of the official help page steps for this error code (back in October when it first started and multiple times thereafter, including this week). Steam never finds any problem or corruption when verifying the files, which adds to the frustration of this error. I've seen scattered reports of crashes being looked into and others experiencing this kind of error, but I would like to see if this specific scenario can be acknowledged, as while intermittent, it is disruptive and has been ongoing long enough to be considered a real pain. Unofficial channels that have reported this error have diverse solutions/suggestions that did not actually resolve this, including reinstalling Steam (which I tried by removing every folder and file outside of steamapps and steam.exe before updating it again), reinstalling battleeye specifically, and disabling rootautoupdate (the full path of which is not actually present on my pc's regedit). All of these have been unsuccessful in my case and there doesn't appear to be anything useful in Event Viewer as it doesn't actually crash. If I can provide a full procdump of the 'problematic' Destiny 2 process while it is in this bad state, please let me know if or how I can help. EDIT: Bungie is aware of the issue - since 10/15, but the acknowledgement was my primary concern. https://www.bungie.net/en/Forums/Post/259860590?sort=0&page=0 EDIT 2: Ran Windows Memory Diagnostic and actually found hardware problems. I was skeptical at first, but then I started receiving 'Out of Memory' and 'Status Access Violation' errors on chrome when swapping tabs. Finally, borderlands 2 even crashed and the game threw errors trying to verify it's files through the Epic Launcher. I had Corsair Vengeance LPK DDR4 3000 RAM sticks (8GB) for comparison and 1 seems to have died after 3 years (Took out 2 sticks and started receiving a bunch or the chrome issues regularly, swapped them with the other 2 I had previously removed at random and haven't had an issue for a few days). I've ordered new RAM sticks completely regardless, but this was a mess I hope few have to follow. TLDR: If the Marmot error happens when loading into areas or seemingly at random, this can be a canary in the coal mine scenario for your computer's RAM or another memory related fault like it was for me.