JavaScript is required to use Bungie.net

Help

Help us help you.
Edited by Vex: 4/9/2022 11:40:09 AM
0
5
Vex
Vex

Constant Game Crashes

Since about the time of the Witchqueen release I'm facing an increased number of sudden game chrashes. The game freezes for about 10-20 seconds while I am still hearing game sound and then just closes and brings me back to my desktop. This happens mostly in activities with other people. I haven't ever encountered any game chrash when playing solo, a decent amount of crashes in 3-player activities like strikes and more than 1 or 2 chrashes per hour in activities like raids (Most notably the Vow of Disciple Raid, I get kicked out every second time I fight against rhulk), Wellspring or PVP. There seem to be 3 factors to determine the amount of crashes. Number of Players in the activity, number of Clanmembers in the activity and FPS. The higher these 3 factors are, the more likely my game is to crash. My PC: Asus ROG Strix RTX 2080 Ti Ryzen 7 5800X Gigabyte X570 Ultra Gaming Motherboard 32GB DDR4-3600Mhz Corsair Vengeance RGB RAM 165Hz WHQD (1440p) MSI Optix Monitor (Main Monitor for Gaming) 2x Samsung 4k 60Hz Monitor Windows 10 Pro 21H2 Build 19044.1586 NVIDIA GeForce Game Ready-Driver 512.15 No Overclocking (anymore, disabled it after the first crash) Solutions I have tried: Updating all programs, drivers, and upgrading to Windows 11 Rollback to Windows 10, complete fresh install of OS and every program, including Destiny Disabling ingame overlays from steam and geforce experience Higher Priority in Task Manager for Discord Deactivating Compatibility Mode and Fullscreenoptimization and activating "Run as administrator" (Helped a little) Windows Event Display shows the following event after every game crash: (German) Application Error ID 1000 Name der fehlerhaften Anwendung: bad_module_info, Version: 0.0.0.0, Zeitstempel: 0x00000000 Name des fehlerhaften Moduls: unknown, Version: 0.0.0.0, Zeitstempel: 0x00000000 Ausnahmecode: 0xc0000005 Fehleroffset: 0x00007ff6df58c5cc ID des fehlerhaften Prozesses: 0x6810 Startzeit der fehlerhaften Anwendung: 0x01d84b88c713aa92 Pfad der fehlerhaften Anwendung: bad_module_info Pfad des fehlerhaften Moduls: unknown Berichtskennung: 95ccc09e-388b-474a-a942-a766a60aa111 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
English
#Help #pcsupport

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon