BattleTag: Shruggie#2892
Configuration Info:
CPU: Intel i5-7600k
GPU: NVIDIA MSI GTX 1080 Ti
RAM: 16 GB DDR4
GPU Driver Version: 388.00
Operating System: Windows 10 Pro (Version 1709 - OS Build 16299.19)
DxDiag: https://pastebin.com/Fikn1se0
Issue Information
I cannot get through the initial starting mission without the game freezing up, black screening (I can still hear sound) and eventually crashing to the desktop without an error code reported.
I initially tried playing on the highest graphical settings - The game would crash when I encountered the first pack.
I found that setting my VSYNC to 60 FPS rather than uncapped increased the time before the crash by a few minutes but the end result was still the same.
I Also dropped the graphical settings to high with 60 FPS but the end result was just the same.
I'd appreciate some kind of response this. I know there are issues reported for AMD users but I'm disappointed as this PC is a new build I purchased solely to play Destiny 2.
If anyone else is having similar issues with system specs close to mine please comment. I hate to be that guy but it looks like I'm heading for a refund unless there is some sort of feedback.
P.S does Destiny 2 log errors anywhere / is there somewhere I can check to see if its a hardware fault?
English
#Help
-
2 RepliesMy DxDiag https://pastebin.com/W8haeh1M Just wanted to say i have the EXACT same problem as shruggie, also tried to delete the CVARS file, with some success a while longer, but ultimately crashed again. GPU GTX 770 CPU i7 4770 Windows 10 RAM 16BG
-
1 ReplyStill the same problems here. I really cant het how they ignore us like that! Bunch of scammers
-
After another crash I found the following buried in the event viewer: Display driver nvlddmkm stopped responding and has successfully recovered. It appears my graphics drivers are temporarily crashing which is crashing the game. I'm hesitant to blame the card as I've run other games and the heaven benchmark fine. My only other idea could be the PSU (650W) which is failing. Has anyone encountered this before?
-
Completely uninstalled my Nvidia drivers (boot to safe mode then used Display Driver Uninstaller). I only re-installed the graphics driver and audio driver (388.13), skipping over Geforce Experience. I was able to play through the prologue mission I had been crashing on, although I'm not sure if this was down to luck going by some of the crash reports. This was at 60 FPS on highest settings.
-
Problem still occurring after latest patch and driver update (388.13). I used the Geforce Experience to optimise Destiny, it didn't look like it modified much (it still optimised to highest) but I got about 15 minutes play time before it crashed. It seemed to crash at a scripted point. Latest Dxdiag (Swapped over to DisplayPort) - https://pastebin.com/7YUWa4Dn
-
Same thing here. I've tried everything and nothing has worked so far.
-
1 ReplyProcessor: Intel I7 4770k 3.5ghz GPU: NVIDIA MSI GTX 1060 6gb Ram: 16gb OS: Windows 8.1 Issue: My game runs smoothly consistently, then at random times (none consistent) the game will crash. This happens AT LEAST once every hour. There is no specific point for crash either, it can happen in orbit, it can happen in Crucible, it can happen in pve fighting vex, or fighting cabal, or fighting the fallen. The game just freezes and CTD with a prompt saying to 'Scan and Repair'. I have scanned and repaired EVERY time the game crashes and the blizzard app never finds anything wrong with the scan.
-
Tried 60 FPS on medium at 2540x1440. The game was running great with GPU usage sitting at around 82%. This then looked to spike to 100% and the crash occurred again.
-
2 Repliesare other games of yours crashing too? i had a similar problem my older mobo didnt pick up 3d graphics and had to switch mobo
-
I seem to have had success by: 1. Disabling G-Sync 2. Capping V-Sync at 30 fps. 3. Dropping my graphics settings down to medium. I was able to at least finish the mission with no crashes yet (touch wood). The main thing I noticed that my hwmonitor was maxing out cpu usage / gpu usage so it sounds like a performance issue. I'm going to up my settings to high at 30 fps to see if I can get away with it. I'm running at 2540x1440 by the way.
-
I'd read elsewhere that it could be down to a temp issue in the GPU (even though system stats look fine), I know that MSI cards control the fan speed depending on load so I maxed it to 100%. Still the same crash issue.
-
Been trying different things all night. My initial attempt to play lasted around 5 - 10 minutes before it crashed out again. I then enabled G-Sync on my monitor and it became unplayable (crash as soon as I encountered a pack). I then dropped all my settings down to low with 30 fps cap and still crashed on the first pack. I've taken a screenshot of the hwmonitor at the time it crashes: https://drive.google.com/open?id=0B6ecQ6P5ldzLQUs2QkdQMzlJSWc It all looks to align with my GPU / CPU hitting 100% usage going by MSI afterburner logs. As a general test, I ran the heaven benchmarking on ultra to stress test the system. Heres a dump of hwmonitor for it: https://drive.google.com/open?id=0B6ecQ6P5ldzLWmtuU0FjWDhoR0U Getting to the point where a refund is going to be the only option.
-
I have windows wallpaper shuffling occurring on regular intervals (I think it's 15 minutes) which might coincide with the crashes I'm experiencing, I heard someone mention this in another thread which has me thinking this might be an avenue to test. Given up for the night trying to troubleshoot this. I'm a developer in my day job so not enjoying spending my time trying to debug in my off hours :(
-
Tried turning off the auto fan control in MSI Afterburner to see if it was a temperature issue. Again I got 10 minutes gameplay before crashing. One thing I did notice was my GPU usage spiked to 100% when the crash occurred (before this it was sitting steadily at around 30 - 50 depending on what was going on on screen. The 100% spike occurred when I was standing idle.
-
Tried deleting the \Users\USER_NAME\Appdata\Roaming\Bungie\DestinyPC\prefs\CVARS.xml file. I got further into the starting mission and thought it had resolved the issue only for it to crash again. Really frustrating that it's not providing any error info around why the game is crashing.