Hi everyone, I play Destiny 2 for about ten months now. I never experienced any issues. On the 8th when I started the game I was told that it needs a scan and repair. So i ran a scan and repair, which found and repaired something. Yesterday I played Iron Banner and got a blackscreen while hanging around in the loading screen. Was still hearing sound of the game. It then showed a little windows message telling me to run scan and repair and closed the game. I did so and it told me that nothing needed to be repaired. Later that day the same scenario happened again. The last thing I did was playing a Gambit match. Everything was fine. Today, approximately 12 hours later, I wanted to play some Gambit. It worked fine 'til I was dropped into the first round. After about 30 seconds the game crashed and told me to scan and repair. Found nothing that needed to be corrected. I started again after that and tried anew. Same result. The match worked for a short time, then kicked me out with black screen and scan and repair. I ran the scan and it found it repaired something. Glad that it worked I restarted the game, played some strikes, some lost sectors and ran around in the tower for some time without any issues and then launched a Gambit match. The same thing happened. After a short time playing I got kicked out of the game with scan and repair message and blackscreen. I ran scan and repair and searched the internet for other threads regarding this issue. According to what was written there I: - checked my RAM without any errors occuring - checked my drives with two different programs that found no problems - ran a chkdsk with /f and my device found nothing that was causing problems and needed a repair - updated my video card drivers - updated the drivers on my SSD's - updated everything my system told me could need a newer version - checked for weird characters in the file names in the directory of destiny 2 without finding any - set the games priority to High - restarted my PC multiple times during that phase and after everything was done - no other game produced any weird behaviour - I run windows 7 so I can't revert some win 10 patches that are known to cause issues - nothing is overclocked so I couldn't set it back to normal - nothing is overheated I then launched the game again and launched gambit to check if it worked. It didn't. I was able to play the beginning of the first round and got the same error. I am sad I can't play the game normally anymore. I feel extremely sorry for my mates during that matches that needed to play outnumbered because of that issue. I now am suspended from Gambit sadly, at least according to what the game told me when I opened it again after restarting, so I can't test whether whatever I do works until that timespan of one week? two weeks? more? is over. I am currently running another scan on my data. I read some system error/info in the logs that have nothing to do with destiny but could by a low chance mean that something is damaged although they could also mean nothing. The drive is a month old and everything else runs perfectly fine. I have looked into the destiny 2 crash log and realised an interesting line: halt information: resourcerer:load: Failed to load tag with path '<N/A>' and description '<N/A>' 0x80B76068 (0x01bb 104) from package {{w64_sandbox_01bb_2.pkg}} with error 'error riddle failure, {{!0x00000000!}}' install type {{!5!}} That line was there directly before the fatal error in all crash logs (just with the w64_pvp_sabre_03d5_2.pkg file for the iron banner loading screens). Does anyone have any idea what causes this issue and how to solve it?