The game has been crashing quite frequently recently, and I’m sharing the requested crash files/logs below for investigation:
Crash files:
Crash Details
The crashes do not appear to follow a specific pattern. So far, I have experienced crashes in the following situations:
During Crucible runs
When opening the map
While performing a charged attack with the Claymore
When teleporting between floors in the Crucible
When using Rune Skills
Troubleshooting Already Performed
I have tried the following troubleshooting steps:
Ran the game as Administrator
Disabled Steam Overlay
Disabled Discord Overlay
Updated Xbox controller firmware
Updated NVIDIA graphics driver to the latest version
Confirmed there are no pending Windows Updates
Tested both -dx11 and -dx12 launch options
Changed graphics settings from Quality to Performance
Limited FPS to 60
Verified the integrity of the game files through Steam
Despite these steps, the crashes are still occurring.
I am now going to try completely reinstalling the game to see if this resolves the issue.
I really enjoy playing the game, especially the Crucible, so it is quite frustrating when the game crashes unexpectedly and interrupts the experience.
Could the development team please investigate the crash logs and help identify the underlying cause? If there are any additional logs, settings, or diagnostic information that would be useful, I’m happy to provide them.
Hopefully the crash files can help narrow down the issue and eventually get this resolved.
Thank you for your help and for continuing to improve the game.
this may be your problem? you are in a high high color bit profile setting while having HDR support unavailable to satisfy colour requests and is crashing your system. try to drop down and see if your system launches without error
next thing to try is to roll back your Nvidia drivers to a previous and more stable version when the game was not crashing.
Nvidia is notorious for releasing bad driver updates and patches; especially in the past several months.
@Silas-Inservio-Pax HDR is basically the depth of RGB demand requested per each pixel,
traditionally a defaulted system on 1080p will be on a 8bit color debth, (each pixel omits 8 colors) 2k and 4k monitors require a stronger demand going up to 16 and 32 bit colour depth, which is one of the visual aspects that makes the difference of quality between the tiers.
A system requesting a higher bit depth than can be provided by the GPU its going to cause excessive load and slow the system which can lead to crashes from too many missed dependencies which is the final entry at the end of the player log.
another thing to try is going into your BIOS and disabling XMP profile if you have it enabled. similarly to the HDR request demand if your ram timings are improperly set, stability will be effected. here are some examples of BIOs menu’s for reference and instructions. disclaimer do not change bios settings you don’t know what they do or understand
i am a stranger on the internet trying to help and am not accountable for your hardware
the XMP profile is a low risk setting to disable / enable, but the err of caution is always respected, if the driver rollback dosnt work take the little time and research what XMP is and refer to your motherboard manual for specific instructions on how to access it safely
i tried to enter bios from my laptop but i dont see the XMP option. checked google and it say my HP OMEN hide the option , so can’t change it from the normal bios.
both companies are just rolling out vibe coded hardware drivers. its genearlly best to wait a couple days when a new driver pack is launched to see how the community reacts to it so youll know what kind of errors to look for in your machine post updating