Confuration Info CPU: i7 7700k@4.6 Ghz GPU: Asus Strix 1080Ti OC RAM: 16GB G.Skill F4-3000 GPU Driver Version: NVIDIA 388.00 Operating Systyem: Win10 Version 1709 (OS Build 16299.19) DxDiag: https://1drv.ms/t/s!Apt22NRwTA9IqDylGW_MAKFa-Lyw Issue Information: Destination/Activity: Any, doesn't seem to matter. Has happened mid mission or mid public event, or immediately after loading screen. I have been unable to deduce any sort of pattern. Description: The game freezes and a window pops up with the text "Problem reading game content. Please close Destiny 2, run "Scan and Repair" in Blizzards Battle.net then restart Destiny 2 to try again." I have followed the steps outlined ie "Scan and Repair" in Battle.net about 10 times now, and every time scan finishes without finding any errors, saying "Scan Complete. No Repair Required.". Originally the game was installed on a HDD had the problem, and so I transferred it to a new SSD. The problem persisted. I then uninstalled Destiny 2 and Battle.net, ran system updates, updated NVIDIA driver, and then reinstalled Battle.net and Destiny 2. The issue still persists. The issue is recurring about every 40-60 minutes of game play time, and I cannot predict when it will happen. Sometimes it happens immediately after a loading segment between missions, and other times in the middle of mission or public event. I have tried deactivating my antivirus and firewall, and the problem still occurred. I am at a loss as to what the problem is. I wish the game would provide some more information as to the reason for the crash to make it easier to diagnose. I have seen other reports of people with this issue, but unsure how common or uncommon. EDIT: I have not been able to resolve the issue, however I have figured out how to access the crash logs (thanks to BeefCurtins in the comments here). I have traced the problem to errors validating the hash in the.pkg files, as well as some issue regarding "Failed to load tag 0x80C0E59B (0x0207 1435) with error error bad handle" as an example. Every crash is different and references a different .pkg file or tag & handle. Here are examples of the Crash_Info files: Error validating hash in .pkg file: https://1drv.ms/t/s!Apt22NRwTA9IqEHDMozFMtYFsEKH Failure to validate tag: https://1drv.ms/t/s!Apt22NRwTA9IqEA4TNwxKKHwbKTY Maybe this info can help. EDIT 2 FIXED (For me at least!) Ok, this is weird but I think I found a fix.... I have been playing for >2.5 hours which is more than double anything I have been able to play so far. All I did was go to my Destiny 2 folder and set the destiny2.exe to run as administrator, as well as battle.net. I have no idea why this seems to have worked, and I will update if it ends up crashing again. I am curious if this works for anyone else. Good luck!