[b]Summary[/b] Destiny 2 intermittently exits to desktop on PC with no error message, no crash dialog, and no consistent Event Viewer entry. The issue occurs after variable amounts of playtime (30–120+ minutes) and appears unrelated to GPU load, thermals, or overall system stability. This behavior began after the Renegades Destiny DLC and did not occur previously on the same hardware. [b]Symptoms[/b] • Destiny 2 silently exits to desktop • No Bungie error code displayed • No crash dialog • Often no corresponding Event Viewer entry • Sometimes a brief UI freeze before exit, sometimes immediate Occurs most commonly during the following activities: • Character screen • Traversal • Social spaces • Low-intensity gameplay Not correlated with: • High GPU or CPU load • Overheating [b]Frequency[/b] • Intermittent and nondeterministic • Can occur after ~30–45 minutes, ~1–2 hours, or sometimes longer • Same configuration may run stable for hours one session, then exit earlier the next [b]Hardware[/b] • CPU: Intel Core i9-14900KF • GPU: NVIDIA RTX 4070 Ti Super • RAM: 64 GB DDR5 (MemTest86 passed, no errors) • Storage: NVMe SSD • OS: Windows 11 (fully updated) [b]Software Environment[/b] • NVIDIA Game Ready Driver (latest at time of testing) • No third-party overlays active during testing • BattlEye enabled and allowed through firewall • Windows Defender only (no third-party antivirus / EDR) [b]What Has Been Ruled Out (Extensive Testing)[/b] The following did not resolve the issue: System isolation and OS testing: • Fresh Windows reboot • Fresh Windows install including full drive format • Fresh standard (non-admin) Windows user profile • Minimal software environment (Steam + Destiny only) Graphics and performance settings: • Disabling all overlays (Steam, Discord, NVIDIA, SteelSeries, etc.) • Disabling Hardware-Accelerated GPU Scheduling (HAGS) • Disabling Variable Refresh Rate (VRR) • Disabling HDR • Exclusive fullscreen mode • Multiple FPS caps tested • NVIDIA shader cache enabled, disabled, and set to driver default Hardware and drivers: • GPU power limiting and undervolting • Memory tested at JEDEC speeds • E-cores disabled for testing • Audio drivers simplified / disabled System resources and security: • No background applications running • Pagefile enabled; commit well below limits • No Windows Resource Exhaustion events • No security or Defender events Even with a fresh Windows install, fresh user profile, and minimal software, the game exited after approximately 30 minutes. [b]Observations / Patterns[/b] • Crashes often occur in social spaces or traversal areas and less often during combat • Examples include Tharsis Outpost, riding the pike in tunnels during the first encounter of Equilibrium, and reentering open areas in Reclaim after combat • Often coincides with asset streaming or transitions • GPU temperatures are normal at time of exit • System remains fully stable before and after the crash • Other games and workloads are stable on the same system [b]Hypothesis (for Bungie engineers)[/b] This behavior appears consistent with an engine-level in-process failure, such as a race condition, use-after-free, or resource lifetime issue. It may be triggered by interactions between Destiny’s engine and modern high-end PC hardware, driver scheduling, or asset streaming behavior. The nondeterministic timing and lack of OS-level errors strongly suggest this is not caused by user configuration or external process termination. [b]Impact[/b] This issue makes Destiny 2 unreliable for: • Long play sessions • Raids and dungeons • Teaching / sherpa runs As a clan leader, unexpected exits are highly disruptive to coordinated group activities. [b]Request[/b] Please investigate potential engine-side stability regressions affecting high-end PC configurations, particularly around: • Asset streaming • Social spaces • Modern GPU scheduling behavior If there are known workarounds or upcoming fixes, any guidance would be greatly appreciated. I’m happy to provide additional logs or test specific changes if that would help narrow this down.