To clarify, the game crashes to a black screen after going to orbit from free roam...for somewhere around the 5th time after running around doing patrols, public events, collecting planet mats, and such. It's not like my game crashes the first time going to orbit either, but after doing the above mentioned activities for some time of about 1-4 hours of gameplay. Never once do I alt-tab out of the game or anything.
After my screen goes black, with the game audio continuing to play normally, I have to then alt-tab out for the only time during the game to semi-exit the game (screen still black), then I have to push the windows key, create a new desktop (not going to explain, if you don't know, don't worry about it too much), [i][/i]then[i][/i] I can open task manager, kill the program, and continue with my day. Nothing shows up in Event Viewer or battle.net
Specs:
CPU: Intel Core i7-8700k @ 4.8GHz [OC]
GPU: EVGA GeForce GTX 1080 Ti FTW3
Asus Z370 TUF Plus motherboard
32GB Corsair Vengeance LPX DDR4 RAM @ 2666 MHz
Corsair H100i Pro AIO CPU cooler
Corsair RM1000x 1000w 80+ Gold Modular PSU
250GB Samsung 850 Evo Pro SSD x2
2TB Western Digital Black 7200rpm HDD
2TB Western Digital Green 5400rpm HDD [Backup]
Windows Version: Windows 10 Pro 1903 OS Build: 18362.175
-
Edited by Kiro - 13: 6/20/2019 8:36:21 AMI had a similar issue with dual 980 ti's after I did windows update last week(well more like it auto updated in my sleep). System went to hell in a hand basket and I lost a solid 30fps(165-180fps range was my avg, went to 100-130fps) when the game was stable and then crashed out in the exact way you described. -would crash out black screen -plays sounds -can control alt delete but when you click task manager to kill it you are unable to view your ui -forced to log out of current windows user profile as only viable way to access ui -can press windows key and it does pull up that side bar -no bungie error code -event viewer says application error of destiny2(seems like the only difference) I believe some how the game stopped detecting the hardware( specifically the gpus). Was one hell of a fix for me but i got it going again. Had to redo my vbios entirely... Not sure if it will fix yours but it fixed mine. Also as a side note I have heard from a number of sources forms/webchats that this latest windows update boned quite a few people.