hello, After renegades update the game is crashing on me nonstop, and I tried everything to resolve the issue, but nothing is helping, can you please help me. PLATFORM: Steam SYSTEM INFO: CPU: Intel Core i5-13600K (13th Gen) GPU: AMD Radeon RX 9070 XT RAM: 32GB DDR5 (Running at JEDEC/Auto speeds, XMP Disabled for troubleshooting) GPU Driver Version: the latest driver as of today OS Version: Windows 11 ISP Provider/Speed / Connection Type: Zain kuwait 5G, 600Mbps download, 50Mbps upload, wired ISSUE: Since the release of the Renegades update, the game consistently freezes and crashes to the desktop (CTD) after approximately 10 minutes of gameplay. The crashes occur without an in-game error code (weasel, broccoli, etc.). Windows Event Viewer confirms an "Application Error" (Event ID 1000) for destiny2.exe with Exception Code 0xc0000005 (Access Violation), followed immediately by BattlEye (BEDaisy) unloading successfully. REPRO STEPS: Launch Destiny 2 on Steam. Log in and load into any activity (Patrol, Campaign mission, or Tower). Play normally for approximately 10–15 minutes. Game freezes visually, audio may loop or cut out. Game closes to desktop instantly without an error message popup. ACTUAL RESULT: The game application terminates unexpectedly. Windows Event Logs show Exception code: 0xc0000005 pointing to a memory access violation, often accompanied by "Application Popup" Event ID 26 in the System logs. EXPECTED RESULT: The game should remain stable during prolonged gameplay sessions as it did prior to the Renegades update. NOTES: Troubleshooting attempted: Updated Motherboard BIOS to latest version (ASUS Prime Z790-A Wifi, Ver 1825) to ensure latest Intel Microcode is applied. Disabled XMP (X.M.P.) in BIOS to rule out RAM instability (Reverted to JEDEC stock speeds). Disabled "Local Security Authority protection" and "Core Isolation/Memory Integrity" in Windows 11 to prevent conflicts with BattlEye (Verified RunAsPPL is set to 0 in Registry). Verified game files on Steam and cleared BattlEye cache. Observation: The crash consistently produces a 0xc0000005 exception code, suggesting a conflict or instability triggered by higher CPU/Memory load introduced in the recent update.