I have been playing Destiny 2 on PC since launch day with no problems what so ever. The game has been running great and it has been amazing. But starting since last night, as soon as I log on and get into orbit, my computer monitor turns off, my computer stays on for 10 more seconds then turns off, and then 15 seconds later my computer restarts. I only have this problem with D2 and I tested it out with other games and it doesn't happen. I have been troubleshooting for 2 hours now and nothing has worked. If someone from bungie can help me or someone who has had this and knows how to fix it, that would be great.
My Specs are
i7 7700k
GTX 1080ti
16gb RAM
800 Watt power supply
2TB HDD
500gb SSD
BattleTag: ABitToxic#1298
-
Edited by xISWx Kodo: 10/30/2017 12:23:22 PMExperiencing the same problem. When trying to complete Oh Captain! in Nessus while following the Harpy, my PC completely black screens and shuts down. I have to power cycle the PSU in order for it to turn back on. This is a fairly new rig, however I dumped over 40 hours into Shadow of War and god knows how many hours into Destiny before this occurred. There is no way this was my computer overheating. Nothing is over clocked and it has never shut down like this. I attempted to redo the quest 2 more times and it power cycled my PC both times at the exact same spot. So I decided to try another quest and had no problem. I get no error message. Just a critical 41 of unexpected shut down so there's no way to diagnose this issue. Current set up is: - AMD RYZEN 5 1600X 6-Core 3.6 GHz (4.0 GHz Turbo) Desktop Processor -GIGABYTE GeForce GTX 1080 DirectX 12 GV-N1080WF3OC-8GD 8GB 256-Bit GDDR5X PCI Express 3.0 x16 ATX Video Card - MSI X370 GAMING PRO CARBON AM4 AMD X370 SATA 6Gb/s USB 3.1 HDMI ATX AMD Motherboard - CORSAIR Vengeance LPX 16GB (2 x 8GB) 288-Pin DDR4 SDRAM DDR4 3200 (PC4 25600) Desktop Memory Model CMK16GX4M2B3200C16 - 750w PSU - 150gb SSD - 2TB HDD - Windows 10 Edit: I would also like to note that after the first crash I did a GFX update to ensure nothing was out of date. Hoped it would solve it since I knew I had an update that I had procrastinated. Still crashed after the update.