JavaScript is required to use Bungie.net

Help

Help us help you.
2/12/2018 1:39:02 PM
2

Game keeps crashing for the past week

Game keeps crashing after playing anywhere from 5 - 60 mins. At first the crashes were due to corrupted .pkg files and I have since fixed several of those by deleting said .pkg file and running the scan and repair tool. After doing this 3 times it seemed to fix the crashing. Now I am getting a different crash report. The new crash is due to a RUNTIME ERROR. Any help would be appreciated. Running a Ryzen 7 1700 gtx 1060 6GB 16 GB DDR4 3200mhz 500GB SSD No temps exceeding 65C stack: 00007FF74693A1BE <unknown> 00007FF746901007 <unknown> 00007FF746901337 <unknown> 00007FF74690D3B7 <unknown> 00007FF746095007 <unknown> 00007FF74609283B <unknown> 00007FF746095259 <unknown> 00007FF7460D1E68 <unknown> 00007FF7460D1F1F <unknown> 00007FFF4C731FE4 <unknown> 00007FFF4D82EFB1 <unknown> session_id: Mon_02122018_071148_000888@x64@52379468@59_F7_FE_14_BF_53_6F71 version: d2_rc tiger_final release pc_x64 61966.18.01.12.0839.d2_rc 18.01.12 0839 thread information: thread_name: unknown, thread_id: 00000c18 halt: ### RUNTIME ERROR: EXCEPTION_ACCESS_VIOLATION at 00007FF74701E085 halt information: (<unknown>) crash: tried to read address FFFFFFFFFFFFFFFF fatal error detected, current status was: init: init.txt version: d2_rc tiger_final release pc_x64 61966.18.01.12.0839.d2_rc 18.01.12 0839 session_id: Mon_02122018_071148_000888@x64@52379468@59_F7_FE_14_BF_53_6F71 GPU Device: NVIDIA GeForce GTX 1060 6GB GPU VendorId: 4318 GPU DeviceId: 7171 GPU SubSysId: 1633892418 GPU Revision: 161 silo_id: 1665943536960952320 signon_server_reported_content_version: none reported 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:106 install type: 5 change-world: loaded strike_lute game_instance: 00000000C939D7D4 game_is_playback: false activity_tier: e_activity_tier.one activity-slice-set-index: 56 map-slice-set-index: 7 in-public-bubble: false AH active workspace: <no active workspace> activity_host_fireteam_is_connected: yes activity_host_last_fireteam_session_id: Fri_02022018_171629_110396@x64@game_svc_lp$@N07SH02SRV055 activity: strike_lute activity_host_group_target_is_connected: no activity_host_group_target_session_id: Sun_02112018_133216_081516@x64@game_svc_lp$@N07SH01SRV058 activity_host_group_current_is_connected: no activity_host_last_group_current_session_id: Sun_02112018_133216_081516@x64@game_svc_lp$@N07SH01SRV058 system_milliseconds: time 3059251 timezone_seconds_offset_from_UTC: 18000 is_current_bubble_authority: false crash_folder_location: C:\Users\johnh\AppData\Local\Temp\Destiny 2\crash_folder\pc_x64\crash_folder_888_20180212_080031\ primary_bap_server_ip_address: 205.209.21.102 primary_bap_server_port: 7500 world_controller_state_manager status: activity:in_world (goal:002:activity:in_world) player_position_x: -2218.789063 player_position_y: -1333.352417 player_position_z: -628.579285

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • If you google search your exact exeption_access_violation it looks like this problem occurs with the 1000 series of cards. An unofficial reddit post ( https://amp.reddit.com/r/DestinyTechSupport/comments/7n7yh4/troubleshooting_guides_framerate_crashing/ ) Suggests rolling back your graphic card drivers to 385.69 , found at the nvidia official website http://www.nvidia.com/Download/Find.aspx

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

    1 Reply
    You are not allowed to view this content.
    ;
    preload icon
    preload icon
    preload icon