UPDATE: If I set my SLI to only use one GPU, the game works. I think either NVIDIA or Bungie broke it with an update. Bungie can you please look into it?
UPDATE 2: I installed a really old driver of 418.81 and the game now works with SLI enabled!!! So it seems like NVIDIA broke it.
UPDATE 3: I spent hours installing each driver version and found out which one is causing the issue. I have an open support request with NVIDIA. The last working version is 436.48 and it fails with 440.97.
UPDATE 4: I tried the latest driver 441.66 and it seems to have fixed the issue!
UPDATE 5: Nevermind, I tried again and got the error. It must have been using the older driver until I restarted my computer. Back to square 1.
Original Post:
BattleTag (with a numerical suffix): (You should change this template since the game is on Steam now.) The template is here: https://www.bungie.net/en/Forums/Post/236455208
GargantulaKon is my Steam name
Configuration Info
CPU: Intel i7-6920HQ 2.9 GHz
GPU: Dual NVIDIA GeForce GTX 980 running in SLI
RAM: 32 Gbs
GPU Driver Version: 441.66
Operating System: Win10x64 v1909
DxDiag: https://pastebin.com/GxpBqE9T
Issue Information
Destination/Activity: After signing in and before my 3D character (choosing my class) should appear is where the crash occurs.
Description:
I've spoken to NVIDIA and did a clean uninstall with DDU and clean install. I have already uninstalled and re-downloaded the game.
I tried rolling back to one version of the GPU drivers with the same issue.
Other games work fine. Destiny 2 used to work on my computer with Battle.net and after I downloaded it on Steam. A recent Destiny 2 update might have caused the issue. I used to be on Battle.net and transferred my account. The second time I tried to log in after not playing for some time. It asked me again to re-confirm my character migrations. I thought that was odd since I remember doing so already. I did not buy Shadowkeep yet. Maybe that is the reason? I've tried googling for this issue, but it seems to be specific to my configuration.
-
2 RepliesBroccoli is associated with rendering issues, usually the game process is losing access to the GPU, and Destiny is really finicky about it. It can be anything, a driver issue, a windows install issue or even a hardware issue due to aging. You can try doing a underclock, taking -50mhz from the GPU clock using MSI afterburner, or disabling SLI for destiny through the nvidia control panel. Refunds are made through the platform you bought from, if you choose to do it you will have to ask steam.
-
8 RepliesDo you have any overclocks?