{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
5/14/2025 5:57:50 PM
3
Hi there,
Please try the following steps (ignore step 4 as it relates to NVIDIA cards):
[quote]1. Enable "Game Mode" in Windows 10 or, if you already have "Game Mode" enabled, try disabling it.
2. If you use EVGA Precision for overclocking, you may want to disable that since it doesn't play well with Destiny 2. MSI Afterburner might be a good alternative to use.
3. In your Settings, cap your framerate to keep GPU usage below 90% to see if this helps.
4. If you have an NVIDIA graphics cards, see if the card stabilizes using NVIDIA's temporary debug mode.
5. Some players have reported that a mild underclock for GPU clock of around -100MHz and GPU memory around -50MHzz may help with this issue.[/quote]
If the crashes continue, you may want to try re-installing the current GPU drivers or rolling back to a previous different set of drivers than the one you previously tried rolling back to.
English
-
So I did all of that and it seems like capping the framerate worked (I capped it to 144 which is my monitors refresh rate as well as the vsync setting) as I tried each of these suggestions all at once and it seemed to work, then I tried each one individually and it started crashing again, except for when the framerate was capped, so problem solved.......for about an hour and half. After playing some heavy metal games, I was half way through the 2nd encounter on Spire of the Watcher when it froze and crashed again, with the same Exception code in the Event Viewer (0xc0000005).
-
And now its going back to only lasting 5 mins before freezing and crashing, even with the settings where it lasted about an hour before
-
Thanks for the update. Users with similar issues report having the problem solved after rolling back to a previous set of drivers. We recommend trying a different set, or if there has been a new driver update in the last few days, try the newest update instead.
