{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
3/29/2026 1:50:04 PM
2
Crashing After Character Select
Hi, Im a returning player from the start of the renegades campaign. I recently got a pc and wanted to play destiny as of now. I transferred my ps5 account to my pc on steam and whenever i load into the game, i see all my characters and try to play one. I click a character and my game goes black then crashes. I saw it could be a mida ornament or some new armor ornaments but i used dim to take off all ornaments and transfer all loot to vault leaving my character with basic stuff. I updated my drivers, cleared nvidia cache, i looked at my crash logs and searched for similar cases, found nothing. Ive also tried both studio drives and gameready drives, and editing performance settings via the nvidia app to edit the in game settings. Im unsure if its a transfer of data issue, a driver issue, a 5070 incompatibility, or im just being stupid to something obvious.
my specs
OS: Windows 11 Home (64-bit)
CPU: AMD Ryzen 7 7800X3D (8 cores / 16 threads, ~4.2 GHz)
Ram: 32 GB
GPU: NVIDIA GeForce RTX 5070
Crash Report:
stack:
00007FF76FCAA53A <unknown>
00007FF76FCAB2D4 <unknown>
00007FF770C73883 <unknown>
00007FF770C68CD4 <unknown>
00007FF770C771FE <unknown>
00007FF7709C5892 <unknown>
00007FF771405B9C <unknown>
00007FF771335CB6 <unknown>
00007FF7706BCC89 <unknown>
00007FF771343661 <unknown>
00007FF770FA572F <unknown>
00007FF76FD45A31 <unknown>
00007FF770F6C76F <unknown>
00007FF7709C9AA8 <unknown>
00007FF770F68B11 <unknown>
00007FF77062D2D3 <unknown>
00007FF77062D59F <unknown>
00007FFE4E71E8D7 <unknown>
00007FFE4FAAC48C <unknown>
session_id:
Sun_03292026_085742_0022532@x64_steam@76561198259096957@12_85_1D_03_3D_04_7933
version:
v500_rc.main tiger_final release pc_x64 242705.26.03.12.1931.v500_rc.main 26.03.12 1931
thread information:
thread_name: unknown, thread_id: 000012d0
halt:
### RUNTIME ERROR: EXCEPTION_ACCESS_VIOLATION at 00007FF7705E264F
halt information:
(<unknown>)
crash: tried to read address 0000000000000000
fatal error detected, current status was:
init: init.txt
version: v500_rc.main tiger_final release pc_x64 242705.26.03.12.1931.v500_rc.main 26.03.12 1931
tigerheart_version: 1.2-d2.v950+10083505
session_id: Sun_03292026_085742_0022532@x64_steam@76561198259096957@12_85_1D_03_3D_04_7933
GPU Device: NVIDIA GeForce RTX 5070
GPU VendorId: 4318
GPU DeviceId: 12036
GPU SubSysId: 612898730
GPU Revision: 161
silo_id: 1665943537230960640
signon_server_reported_content_version: 242705.242705-0
authority-over-current-bubble: false - map slice set 'HASH(0x8265820b)':0, activity slice set 0
world_controller previous_state: character:signin
world_controller state: cleanup
world_controller state_reason: normal_flow
environment_string: D2_ProdRetail:4226
install type: 5
change-world: loaded orbit_d3.orbit_new
game_instance: 5EDC0927C5379D1A
network_time_get: time 52964
game_is_playback: false
account_id: 4611686018449239766
activity-slice-set-index: 0
map-slice-set-index: 0
in-public-bubble: false
character_id: 2305843009755984311
system_milliseconds: time 117212
tiger_milliseconds: time 56715
tiger_runtime: 0:00:56
is_current_bubble_authority: false
pc_platform: steam
pc_platform_ui: unknown
pc_windows_version: Windows 11
language_system: english
language_ui: english
language_audio: english
language_current: english
crash_folder_location: C:\Users\camvi\AppData\Local\Temp\Destiny 2\crash_folder\crash_folder_22532_20260329_085840\
primary_bap_server_ip_address: 172.97.56.86
primary_bap_server_port: 7500
world_controller state_status: cleanup (goal:000:pregame) (requested tasks: 0x00a001020c8fdf3c) (active tasks: 0x0000000004020100) (pending tasks: 0x00a0010208000200)
player_position_x: unknown
player_position_y: unknown
player_position_z: unknown
-
Hello there, Thank you for reaching out and reporting this issue. Since the crash is happening right after character select, it usually points to either: Something in the local Destiny 2 config/cache, or A conflict with overlays / background software, or A bad game file that didn’t get caught by the initial install. Methods to try: 1. Clean up Destiny 2’s local config/cache Fully close Destiny 2 and Steam. Go to: C:\Users\[YourUser]\AppData\Roaming\Bungie\DestinyPC\ Rename the DestinyPC folder to something like DestinyPC_backup. Launch Destiny 2 again – it will recreate a fresh config and cache. If it works after this, something in the old settings/shaders was corrupted. 2. Strip out overlays and background tools Temporarily disable all of these, even if they’ve never caused issues in other games: Discord overlay GeForce Experience overlay Steam overlay (right‑click Destiny 2 in Steam → Properties → uncheck “Enable the Steam Overlay…”) Xbox Game Bar / Windows Game overlay MSI Afterburner, RivaTuner, RGB / motherboard utilities, capture software, FPS overlays, etc. Then try launching and selecting a character again. 3. Verify / Scan & Repair the game files In Steam: Right‑click Destiny 2 → Properties → Installed Files. Click Verify integrity of game files and let it fully complete. If any files were redownloaded, test again after it finishes. 4. Try a very “safe” graphics profile Just for testing: Set Destiny 2 to Windowed or Borderless Windowed. Turn V‑Sync off. Disable HDR, G‑Sync/Freesync, and any forced settings in the NVIDIA Control Panel for Destiny 2. Set graphics to Low or the lowest preset, then try loading a character. If it works like this, you can slowly turn settings back up until you find what triggers the crash.
-
1 ReplyEdited by Crisidelm: 3/29/2026 3:10:41 PMDo you have the GG armor ornament sets on for any character? If you do, that's the reason.
