OK, so I have re-installed the game twice, and verified more times then I can count. Deleting the Steam file steam_appid64 (somehow it's an app extention on mine?) and that causes the game to have the error rather then launching at all. I tried running in Admin, that slowed the error for a while. Re-installing makes it take a lot longer to show up- about 6 hours of game play the first time, and 5 the second re-install. Verifying files seems to do nothing, no files are missing unless I deleted steam_appid64 per Bungie's suggestion again, then it finds that and nothing else. Crash seems to be related to a new event or quest showing up as completing a quest has caused most of the crashes, and a public event showing up/entering the area of a public event has caused more. Also, out of nowhere a public event showing has twice caused all text to disappear, and the menu to be blank, and not work. Fortunately Task-manager killing still works just fine. I have all the DLC, and the issue started after I migrated my account successfully, then bought Shadowkeep. Crash happened less then half an hour later. Tried deleting old character, starting a new after my first re-install, that delayed it about 6 hours. voice-lines keep running on a black-screen after crash, and the little error box pops up dropping me to desktop with Destiny 2 still running on black screen. Friend commented that until I closed it he could still see me as active on the server. Connection where I am is very good, I have 16GB RAM, intel integrated graphics, I5 processor on a Lenovo laptop. Planetside 2 runs fine, Warframe runs fine so I know it ain't my hardware. Please help, after re-installing twice, and verifying 30 odd times I have no idea what to do since the only 'fixes' available either want me to open the game already running (steam won't let me do that y'all) or delete a file that if deleted, caused the game to crash instantly on launch.
I've got a Ryzen 3 2200 G, 16GB (4x4), a 250 GB SSD for the install folder, and a 2060 for my GPU and I still have this issue. I've also found out that Xbox users are also having this same issue so its not just a PC issue