{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by RearedSquare:
8/29/2017 8:12:11 PM
3
Destiny 2 PC Beta Crashing Randomly
Hello,
Yesterday evening I downloaded and played through the opening campaign mission that is provided in the Beta. It had absolutely no issues. Since I was having so much fun I thought I'd give the Strike a try and it randomly crashed on me about 10-15 minutes into the game. I opened up the game this afternoon to try it again and it was crashing on me in different spots during the strike usually around 5-15 minutes after starting. It didn't crash on me while I was playing the campaign mission yesterday evening and it doesn't crash on me in the menu. When it does crash I don't really get any heads up or white screen. All it does is freeze for about 3-5 seconds and then immediately closes and I see the desktop. No error's or "close the program" window at all.
Overall it is so much fun to play and I'm looking forward to October 24th when the game releases. If there is any more details I can provide to help, feel free to let me know.
SPECS:
i7-3770K (Overclocked to around 4.3 GHz)
2x (SLI) - ASUS STRIX GTX 980 OC Edition (Both are overclocked via software a little bit)
385.41 WHQL GPU Driver (Newest Driver as of right now)
32 GB RAM
Windows 10 Pro (64 bit)
-
Same crash here...can't complete the opening story mission. Gfx 770 I7-2.8Ghz
-
2 RepliesHappens to me during the boss fight. The game just closes and battle.net stops working too. Here's the crash file stack: 00007FF7D63E85AF <unknown> 00007FF7D63E791A <unknown> 00007FF7D63E3512 <unknown> 00007FF7D6DABC98 <unknown> 00007FF7D6D747FA <unknown> 00007FF7D6D72EE8 <unknown> 00007FFA19D713D2 <unknown> 00007FFA1C6954E4 <unknown> session_id: Wed_08302017_131605_003376@x64@75652554@CD_7E_02_2B_23_72_CA8A halt: RELEASE_VHALT halt information: hitch detected: mainloop world controller state activity:in_world {{!34!}} job fiber:{{!0x00834002!}} phase:{{!-1!}} iteration:0x0 stalled fatal error detected, current status was: init: init.txt version: v300_vv tiger_final release_beta pc_x64 59703.17.08.28.1255.v300_vv 17.08.28 1255 session_id: Wed_08302017_131605_003376@x64@75652554@CD_7E_02_2B_23_72_CA8A GPU Device: AMD Radeon (TM) R9 380 Series GPU VendorId: 4098 GPU DeviceId: 26937 GPU SubSysId: -486009013 GPU Revision: 241 silo_id: 1665943536955512832 signon_server_reported_content_version: 59626.59514-1 authority-over-current-bubble: false - map slice set 'HASH(0xbc84d009)':7, activity slice set 56 authority-over-domain: true world_controller state: activity:in_world environment_string: D2_ProdRetail:23 install type: 5 change-world: loaded strike_lute game_instance: 00000000699A0AA4 game_is_playback: false activity_tier: e_activity_tier.one activity-slice-set-index: 56 map-slice-set-index: 7 in-public-bubble: false activity_host_fireteam_is_connected: yes activity_host_last_fireteam_session_id: Wed_08232017_171643_161580@x64@game_svc_lp$@N07SH03SRV042 activity: strike_lute activity_host_group_target_is_connected: no activity_host_group_target_session_id: Mon_08282017_100822_015496@x64@game_svc_lp$@N07SH03SRV021 activity_host_group_current_is_connected: no activity_host_last_group_current_session_id: Mon_08282017_100822_015496@x64@game_svc_lp$@N07SH03SRV021 suspected_blocked_thread_id: 0x00000a50 system_milliseconds: time 95395702 timezone_seconds_offset_from_UTC: -28800 is_current_bubble_authority: false crash_folder_location: F:\Destiny 2\temp\crash_folder\pc_x64\crash_folder_3376_20170830_133933\ primary_bap_server_ip_address: 205.209.21.102 primary_bap_server_port: 7500 player_position_x: -2231.542480 player_position_y: -1341.633179 player_position_z: -565.314087 crashed 11 times already :/
-
2 RepliesHi there, Thank you for the detailed report! Since crash seems to happen in a multiplayer mode, you may want to try following the recommendation in our [url=https://www.bungie.net/en/Support/Troubleshoot?oid=12915]Network Troubleshooting Guide[/url]. Following the recommendation in the guide will help ensure your connection is optimized for Destiny 2 and will help rule out network problems as the cause of the crash you are encountering.
