{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
11/24/2017 7:22:06 PM
13
Consistent Crash every 32mins
BattleTag: Bigballs23#1571
CPU: AMD FX(tm)-8350 Eight-Core Processor (8 CPUs), ~4.0GHz
GPU: NVIDIA GeForce GTX 970
RAM: 16GB DDR4
GPU Driver Version: 23.21.13.8831
OS: Windows 7 Professional 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.170913-0600)
DxDiag: https://drive.google.com/open?id=14emi1U-aQ2XB68BUncYk3pjHqwKJyzLI
Issue Description
Destiny 2 Launches and plays flawlessly. However It crashes consistently around the 32min mark. I noticed that the crashes seemed to be happening at similar intervals so I decided to time them. This is very consistent and it is about 32 minutes relative to Destiny 2's Start menu. If I were to stay at the start menu, the game would crash accordingly. I tried this in attempt to distinguish between game play and standard idling at the most basic menu.
I have tried scan and repair upon every crash resulting in no repairs taking place.
I tried running as Admin on both battle.net and Destiny2.exe.
I tried declocking my gpu and setting fan speed to 100%. The GPU comes factory OC'd.
I tried running with the absolute minimum graphics settings.
I tried deleting the CVARS file.
I tried running the game with all other programs and unnecessary programs closed.
I am finally reaching out to Bungie support as I have exhausted all of my options. I have read through pages and pages of work arounds other users have been able to implement but they have yet to work for me. I have yet to try a fresh install of windows, but that's something I'm reserving as an absolute last resort.
-
2 RepliesEdited by Sinnergy: 11/25/2017 10:32:20 PMSame issue here. The timing for me is nearly always 42mins. To me this has the feel of a memory leak, or similar resource overflow. The game works perfectly.... until whatever it is fills up. Then Crash to Desktop. I've been posting about this each week for 4 weeks. Haven't had a reply, and the "bug" is not mentioned anywhere by Bungie. Classy. On the off chance they are working on it on the DL (because some pinhead corporate type has suggested silence is the best policy), I'd suggest you all post your DXDiag outputs and the pertinent part of any Destiny Crash files. You can find your crash files in: %temp%/Destiny 2/crash_folder/... They look like: crash_folder_3992_20171126_022928 -> crash_info.txt The pertinent part of mine simply says: ------------------- halt: RELEASE_VHALT halt information: hitch detected: mainloop world controller state activity:in_world {{!34!}} job name: 'resourcerer process events', owner: 'system owner' stalled resourcerer_cleanup ------------------- ... which certainly sounds like a resource issue. Or more often: ------------------ halt: ### RUNTIME ERROR: UNKNOWN EXCEPTION C0000008 at 0000000077D28078 halt information: (<unknown>) ------------------ Which just sounds like someone failed to do proper testing.
