{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by m4rilyn:
11/5/2018 7:25:03 AM
5
Forsaken causes my PC to crash and reboot
I am currently facing an issue where my computer will reboot itself after about 1-2 minutes of starting the Forsaken campaign mission "High Plains Blues". The crash occurs after loading into the Tangled Shore and roaming about.
I have tried several times and the same thing occurs in every instance except a slight difference in the delay before crashing. There is however, no issues when i attempt to do other content such as gambit and roaming about other planets doing events.
I have current tried deleting the CVARS file, scanned and repaired the game, run as administrator and also locking vsync at 30fps.
PC SPECS
CPU: i5 4430
GPU: GTX 1060 6GB
RAM: 8GB DDR3
GPU DRIVER: 416.34
OS: WINDOWS 10
-
m4rilyn, It's most likely the same issue [u][b]many[/b][/u] of us are experiencing with the game. Bungie seems to be ignoring the issue, as people have been complaining for months if you dig through the forums. It seems to have gotten worse since the latest update, as many of us can no longer even play the game because of the constant crashing. Please visit the link below for more information and join in the conversation. We will not back down until Bungie fixes the issue! https://www.bungie.net/en/Forums/Post/249595962?sort=0&page=0 #D2BROCCOLIGATE
-
I have the same issue and I have an i75820k and a GTX 1080. I can play the game for hours and I goto the tangled shore to do Cade-6s mission my entire computer reboots every single time. HELP!
-
3 RepliesHello, Are you still experiencing this issue?
-
1 Replywhat are your pc specs what does event viewer say not enough information above to tell what is happening
-
1 ReplyThis options [b]didn't[/b] help me but they're worth atry. -reinstalling the game -deleting CVAR -copy GFSDK_Aftermath_lib.dll in the Destiny 2 folder -running the Blizzard reapair tool -(of course) restarting the System -starting the Blizzard and Destiny 2 Launchers as admin -starting the Game itself as admin -resetting overclocked hardware -starting the game with one monitor in setup -deactivating screen capturing programms
