Forget about all the solutions ppl are providing in videos and threads. I didn't find this solution anywhere and it has been the only one that worked for me. Usually ppl say just go to the destiny 2 folder and delete everything EXCEPT PACKAGES then verify files and you are good to go. I doesn't work because most people will have problems with files that are corrupted inside the PACKAGES folder, wich is the one that actually contains most of the game and the huge files (10 gb files, 1 gb files, etc). Those are the ones that actually tend to be currupted or have been incorrectly donwloaded, but for some reason the verify files doesn't seem to be working for most of this errors, THUS marmot code keeps comming back for those same files that need to be deleted first. The way to go is first you need to (1) get the MARMOT code ingame and wait for the game to properly crash and make an info file inside the CRASH folder. To find that crash folder go to file explorer and %AppData% then local and temp. (2) Enter crash_folder and find the txt file named CRASH_INFO.TXT. (3) read the file and you will most certainly find a line that says something like: resourcerer:load: Failed to load tag with path '<N/A>' and description '<N/A>' 0x80AFAF42 (0x017d 3906) from package {{packages\w64_sr_fx_017d_0.pkg}} with error 'error riddle failure, {{!0x00000000!}}' install type {{!5!}} fatal error detected, current status was: The important part is inside the {{ }} which says the file you are probably having problems with. which in this example is w64_sr_fx_017d_0.pkg. So far, all the files I had problems with start with the same prefix W64_sr_XXXX All the files that so far had problems to load something had that prefix. (4) Delete that file in destiny 2 folder inside packages and now go into your game and ask to manage and verify the files. The file will be downloaded and installed and most probably wont be a problem anymore. (5) However, if your internet is like mine that has a problem with losing packages in downloading you might have the same code MARMOT again. Just follow the same procedure and find which file is now the NEW CULPRIT. So far I've done this procedure 8 times and now I get like an entire week without finding a file with a problem (before I would get code Marmot every single game session mind you). Now what happens is that when a file I still didn't use so far in the game needs to be loaded and it is corrupted, then MARMOT appears yet again. But as I said, it became much, much less of annoyance and for most people 2 or 3 times should do the trick.