Greetings Guardian, I encountered the MARMOT error code in Destiny 2, and I'm looking for a way to fix it. If you would happen to know a method I haven't tried yet; I would appreciate it very much if you'd share it. [i]I'll try to explain everything as briefly as possible, but this will still probably be a lengthy post. Sorry for that.[/i] [When did I encounter the error?] I started getting MARMOT about a month ago. Back then, I could continue playing after a simple restart. In the past week the errors got more and more frequent, to a point where i couldn't even log in. So at first it happened during random in-game activities and after a while it happened during the sign-in process. Currently I have almost 500 hours in Destiny 2. I started encountering MARMOT at around 350-400-ish hours. I was playing for quite a while without issues, and to my knowledge nothing changed on my system since then. No new programs, no new Steam games, nothing. [Does the error still persist?] Yes. I'm guessing I did manage to fix a part of it (I will details this below), because now I can jump into Vanguard Ops and play a strike or two before getting MARMOT during loading into or while in a strike. The error persists, and I'm looking for help to fix it. [b]EDIT[/b]: I no longer get MARMOT. Check the end of the post to see what worked for me. [Destiny 2 info] I play on Steam. I play on Windows 11. (Bungie doesn't support Linux as I've found out in an attempt to switch OS-es.) I play with HDR enabled, in windowed-fullscreen mode. I own almost all currently available DLCs, including Lightfall, Final Shape and the Annual Pass. [PC info] Please tell me if anything else would be relevant here. These specs are well above Steam's recommended system requirements. - Ryzen 9 5950X - EVGA FTW3 ULTRA (Geforce RTX 3080) - 64GB RAM - 2 nvme2 SSDs, 1TB each [What did I try so far?] I'll try to list everything: 1. Verify integrity of game files on Steam. - See for details: https://help.bungie.net/hc/en-us/articles/4405096052244-Error-Code-MARMOT 2. Delete some game files that may be corrupted manually, and then verify integrity of game files. - See for details: https://help.bungie.net/hc/en-us/articles/4405096052244-Error-Code-MARMOT - Some people suggested deleting everything but the "packages" folder. This didn't work for me. I ended up on an in-game verification screen during the login process that would eventually result in another error code. (MARMOT or BEAVER, i am unsure) - Some people suggested deleting specific files (`cache_phr_xxx.dat`; `bin\x64\steam_api64.dll`). After deleting and verifying these I wouldn't end up on a new screen, but rather end up with the original MARMOT during sign-in. 3. Remove BattleEye. - Run `battleeye\Uninstall_BattleEye.bat` or run `sc delete BEServic` in cmd as admin. Both have the same result in my experience. - Delete `C:\Users\[user]\AppData\Local\BattleEye`. - Delete the `battleeye` folder. - Ensure that no other game relies on BattleEye. - Verify game files and allow BattleEye a fresh reinstall. 4. Clear AppData - Delete `C:\Users\[user]\AppData\Local\Temp\Destiny 2`. 5. Check SSD integrity - Run `sfc /scannow`. - My SSDs are Samsung made, so I used Samsung's Magician software to check them. Both are in good shape according to "full tests". 6. Check RAM integrity - I used MemTest86. It ran for 10 hours, but found no errors. 7. Update NVIDIA drivers 8. Disable XMP profiling 9. Edit Windows Registry - Add a new variable here `HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\SystemCertificates\AuthRoot`, called "DisableRootAutoUpdate" and set it to zero. 10. Reinstall Destiny 2 - While attempting many of the above solutions, I did reinstall Destiny 2 about four-five times. 11. Install Destiny 2 on a separate disk. - I did install Destiny 2 on my secondary built in nvme2 SSD. 12. Run Steam as administrator 13. Changing ping in Steam 14. Clear Steam download cache 15. Allow Destiny 2 through Windows Firewall 16. Remove additional antivirus software - When I was investigating the previous (15.) point it came to my mind that maybe my additional antivirus software is blocking something. I didn't bother tinkering around with it. I removed the "shiny, silver robot" from my computer. - I believe this is what caused me to be able to log in again to Destiny 2 without getting MARMOT. But please keep in mind that I'm still crashing after 1-2 matches of VanguardOps so my issue wasn't entirely fixed by this. I thank you in advance for any tips on how to fix this issue. Hoping for the best, Just A. Guardian [b]EDIT:[/b] I made this post after three days of debugging, but I didn't stop trying to fix the issue after I made the post. It looks like I finally fixed it: Meaning I could do a 3h Destiny 2 session without getting any errors. A few thoughts on the topic: 1. If the mods don't mind, I'm gonna leave this post here. If somebody is battling with MARMOT in the future, they'll find an exhaustive list of possible fixes here. 2. I also intend to leave this post here to show the devs that MARMOT is a thing in 2024, and maybe my description can help fix some part of it. I don't like it that we have to edit Windows registry to fix a game bug. I'm sure there is another way. 3. [b]The fix: After `16.` (and `15.`) I did `9.` and MARMOT got resolved.[/b] Technically these also had an effect: the command in `5.`, `7.`, `11.`, `14.`. Remember that you have to restart your computer after `9.`. I heard that it is good practice to keep the OS and games on separate drives, so I kept that change. Also: Please don't remove your antivirus software! I'm probably gonna reinstall mine and tweak it to a point where it doesn't bother game communication, but still serves its purpose. 4. How to investigate? - If you can't get past login because you get MARMOT: Check antivirus and Windows' default anti-malware software. - If you get MARMOT in-game during random activities: Check `9.`. Remember to restart your computer afterwards! - Reinstalling the game could probably resolve your issue in some cases. But this is a 110GB game. If Steam verifies it, than the issue probably won't be in your game assets. - `1.` and `2.` are the official solutions, but in my testing Destiny handles these scenarios. If I started up my game without manually doing `2.`, I would just end up in an in-game verification screen that would eventually let me into the game. So I wouldn't bother too much with these. - `4.` resolves BEAVER. It didn't have much to do with MARMOT, but clearing AppData is not a bad idea. - `12.` and `13.` can resolve some network issues, but I guess they are not tied to MARMOT in any way. - Some people reported that hardware issues can also cause MARMOT. If you have exhausted all other options, then try `5.`, `6.` and `8.`.