Z
ZackW13
Hey all.
This issue first started happening to me a month or two ago. The entire computer will freeze for several seconds before the monitor (or monitors) turn(s) a single, random color while the speakers play a loud BBRRRTTT sound and the whole pc shuts down. It immediately reboots with no trouble, but everything I had open is closed and the system is aware it experienced a hard shutdown.
It used to be the case that I could immediately reopen Destiny and resume playing for hours without any further trouble, but the problem now occurs every single time I try to play the game, and within seconds of doing anything aside from chilling in the single-player idle menu. The game will start up fine, I'll be able to select my class with no problems, and I can chill on the introductory screen indefinitely without issue. I'll select any destinationband it'll go through the loading sequence flawlessly every time, but the second my screen changes from the loading fly-up sequence to the start of player control, the game can crash at any time. The fastest crash happened before my character even rendered, while the longest I've been able to play in the past two weeks was 20 minutes, but then it died again.
Here's the comp specs. I'm playing on a plugged-in MSI Dominator Pro gaming laptop with a GTX 1070, i7-6700HQ core processors, 8gb of GDDR5 video memory, and the game itself is saved on the 1TB solid state hard drive. It's 3.5 years old, and it has zero issues with literally anything else I've ever done; it only crashes on Destiny 2, and only in the last two months. The issue doesn't seem tied to the graphics, because no matter what level of settings I roll with the game disintegrates. The GEForce app continues to recommend that I play the game at maximum everything (which doesn't even come close to maxing out my available video memory, according to the in-game calculator on the video settings screen), but even on the lowest of low it still craps out every time. I use an ethernet connection that's perfectly stable, and I've tried a complete uninstall and reinstall of the game to no avail. I've also had the built-in MSI diagnostic software running while I deliberately baited out the issue, all it showed me was that the CPU and GPU temperatures were totally normal, and that the memory/cpu/gpu usage were highest in the space loading sequences but completely normal and unremarkable at the time of the crashes while at a destination.
Anyone have any idea at all what I can try next? I've been looking through the event logs, but all I can seem to find is a statement that the system shut down unexpectedly with no further useful info (although I'm no expert with the event log lingo). Is there some Windows 10 update that's happened recently that's prevented the game from accessing my hardware like it used to? I can't think of any explanations for why this game and this game alone is suddenly hard-restarting a computer that's handled it effortlessly for 3.5 years and continues to handle every other game with ease. The game itself has not had any major overhauls in the last few months that would explain this issue, at least to my knowledge. I've sent these same inquiries to the developer, but haven't heard back just yet.
Thanks in advance!
Continue reading...
This issue first started happening to me a month or two ago. The entire computer will freeze for several seconds before the monitor (or monitors) turn(s) a single, random color while the speakers play a loud BBRRRTTT sound and the whole pc shuts down. It immediately reboots with no trouble, but everything I had open is closed and the system is aware it experienced a hard shutdown.
It used to be the case that I could immediately reopen Destiny and resume playing for hours without any further trouble, but the problem now occurs every single time I try to play the game, and within seconds of doing anything aside from chilling in the single-player idle menu. The game will start up fine, I'll be able to select my class with no problems, and I can chill on the introductory screen indefinitely without issue. I'll select any destinationband it'll go through the loading sequence flawlessly every time, but the second my screen changes from the loading fly-up sequence to the start of player control, the game can crash at any time. The fastest crash happened before my character even rendered, while the longest I've been able to play in the past two weeks was 20 minutes, but then it died again.
Here's the comp specs. I'm playing on a plugged-in MSI Dominator Pro gaming laptop with a GTX 1070, i7-6700HQ core processors, 8gb of GDDR5 video memory, and the game itself is saved on the 1TB solid state hard drive. It's 3.5 years old, and it has zero issues with literally anything else I've ever done; it only crashes on Destiny 2, and only in the last two months. The issue doesn't seem tied to the graphics, because no matter what level of settings I roll with the game disintegrates. The GEForce app continues to recommend that I play the game at maximum everything (which doesn't even come close to maxing out my available video memory, according to the in-game calculator on the video settings screen), but even on the lowest of low it still craps out every time. I use an ethernet connection that's perfectly stable, and I've tried a complete uninstall and reinstall of the game to no avail. I've also had the built-in MSI diagnostic software running while I deliberately baited out the issue, all it showed me was that the CPU and GPU temperatures were totally normal, and that the memory/cpu/gpu usage were highest in the space loading sequences but completely normal and unremarkable at the time of the crashes while at a destination.
Anyone have any idea at all what I can try next? I've been looking through the event logs, but all I can seem to find is a statement that the system shut down unexpectedly with no further useful info (although I'm no expert with the event log lingo). Is there some Windows 10 update that's happened recently that's prevented the game from accessing my hardware like it used to? I can't think of any explanations for why this game and this game alone is suddenly hard-restarting a computer that's handled it effortlessly for 3.5 years and continues to handle every other game with ease. The game itself has not had any major overhauls in the last few months that would explain this issue, at least to my knowledge. I've sent these same inquiries to the developer, but haven't heard back just yet.
Thanks in advance!
Continue reading...