- Edit: Reseating my RAM has fixed the issue! :) Two days ago, I noticed a significant performance drop in Destiny 2. I normally get around 110 FPS, but now I’m only hitting ~60 FPS, with major performance hitches that can dip as low as 40 and lower. Previously, restarting my PC worked to solve this issue, at least twice. Since yesterday, the issue is now persistent. These performance drops begin immediately on boot and are not cumulative like typical memory leaks. As well, other games perform fine, with similar VRAM usage. In addition, I’ve been getting RADAR_PRE_LEAK_64 errors related to destiny2.exe, as seen in Event Viewer logs: Fault bucket 1626273438571786364, type 5 Event Name: RADAR_PRE_LEAK_64 Response: Not available Cab Id: 0 Problem signature: P1: destiny2.exe P2: 32594.0.0.0 P3: 10.0.19045.2.0.0 Other info, PC Specs: Operating System: Windows 10 Home 64-bit (Version 19045) Processor: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 CPUs), ~3.2GHz Memory: 16GB (16384MB) RAM Graphics Card: NVIDIA GeForce GTX 1070 (8GB VRAM) Display Driver: Version 32.0.15.6614 (NVIDIA, 11/5/2024) Memory/Performance Stats: Private Bytes: ~5.9-6.5GB (Peak: 6.5GB) Working Set: 3.9GB Page Faults: ~1.88 million (Increasing) Virtual Size: 12GB Destiny 2 VRAM Utilization: 29% (Similar to Rainbow Six Siege at higher VRAM utilization ~35%) GPU Utilization: 98% (Both HWMonitor stats, also similar to Siege) Actions Taken: Ran Revo Uninstaller and Display Driver Uninstaller to clean up drivers. Rolled back Windows 10 Updates. Verified game files and ran MemTest86, sfc, and DISM health checks (all clean). Clean boot, running Destiny 2 with non-Microsoft services disabled. Tried Destiny 2 on Low/High Settings, Render Resolution is at 100. Also, deleted my cvars folder. Tested playing other games, primarily using Rainbow Six Siege's in-game benchmark, so far Destiny is the only game with performance issues. Page File: 11.7GB used, 20.9GB available At this point, I’ve exhausted most common solutions, but the issue remains! I’m hoping someone can help me narrow down the cause, whether it's game-specific, a driver problem, or something else.