It started a week ago, at April 15. I was farming Arms Dealer GM, when suddenly I got MARMOT error. After that I started to get it every day and sometimes even several times per day. When I get MARMOT error game is seemed to be closed, but actually it stays running in background and only manual termination via Steam or Task Manager helps. Very often after getting MARMOT error my PC works for several minutes while various programs crash and finally the whole system crashes giving blues screen of death with MEMORY_MANAGEMENT code. I also experienced a complete PC freeze two times. One time I was in Vow of the Disciple on jump puzzle, my whole PC froze. I saw no response from it, so I did hard turn off. Then I turned it on, logged into Destiny, wrote join command, pressed enter - and I got the second freeze. This time I waited a bit and PC rebooted itself. I tested both my SSD and RAM via various tests - they are in OK state. If the problem was in them, I will have issues in other games and programs as well as during my job, but I have problems only in Destiny. The last time I was casually running over Nessus, doing public events and patrols for 2 hours. I got MARMOT error, I closed it, but (as I said) the game was still in background. You can see on the Task Manager screenshot that Destiny 2 used 6 GM of RAM for no reason after the error (does running over Nessus for 2h requires 6 GB of RAM?). After two minutes my DIM crashed, Discord suddenly decided to reload and finally my PC said "OK, I am done with this" and gave me blue screen of death with MEMORY_MANAGEMENT code. I am pretty sure that all these problems are caused by memory leaks that appeared after WQ release. Previously they drastically reduce FPS over the duration of game running, now it looks like it just causes MARMOT error with some weird consequences.