Destiny 2 crashing or not starting on PC?

Here are the PC issues of Destiny 2 that Bungie is currently investigating! Players report that Destiny 2 crashes or does not start.

For many Guardians, the PC launch of Destiny 2 on October 24 went quite smoothly. They only waited a few minutes in the queue and could then embark on new adventures.

However, there were also some other reports: There were talks of server issues and lags, and some users complained that Destiny 2 crashes constantly or does not start at all.

Bungie has now released an overview of all known problems on PC – including “critical issues” – that they are currently investigating.

Help, Destiny 2 is not working!

First and foremost, Bungie provides you with a few standard workarounds if you can’t get Destiny 2 running on PC. You should check if all Windows updates and drivers are up to date.

In addition, when problems occur, you should try to close the Destiny 2 client and the Blizzard app, and then delete the existing CVARS.xml file. You can find the file this way: UsersUSER_NAMEAppdataRoamingBungieDestinyPCprefs – upon restarting Destiny 2, a new CVARS.xml file will be created.

These are the “critical issues”:

On some laptops, the Fullscreen mode cannot be selected. You should then choose the “Windowed Fullscreen Mode”.
Destiny 2 only runs with processors that have Supplemental Streaming SIMD Extensions 3 (SSSE3).
Trumpet error code: If you have this error code, you can change the Blizzard region. This might help according to Bungie.
Clan overview: According to some user reports, the clan overview is still missing in Destiny 2 on PC.
Continuous sign-in: Some players cannot log in – they get stuck indefinitely on the login screen.

Bungie has not provided any information on when they can fix some of these issues.

Currently, there are major issues with the “AMD Phenom II” processors. The game crashes constantly on these. According to Bungie, these CPUs are below the minimum system requirements and are not officially supported. However, they are trying to fix the issue.

Further PC problems that were already known before the launch:

SLI, HDR, and VSYNC: Players may encounter rare issues when enabling SLI or HDR in some non-native resolutions as well as disabling VSYNC. The best result is achieved when using these features while also using the maximum available resolution of your display.
If AMD Crossfire is active, you should not switch tabs (ALT+Tab). Otherwise, the Destiny 2 client may crash.
“Saxophone” error codes at startup: Players may erroneously encounter “Saxophone” error codes when starting the Destiny 2 application from the .exe file. Players encountering this issue should close the application and open it via the Blizzard Battle.net app.
Inactivity: In some activities, players are returned to the start screen due to inactivity and cannot log back in. Players facing this issue need to close and reopen the Destiny 2 application.
Sign-in after disconnections: A general error code may appear when the internet connection is interrupted. This can cause players to be unable to log back in after reconnecting. Players facing this issue need to close and reopen the Destiny 2 application.
Buffalo error codes on multiple PCs: Players may encounter Buffalo error codes when logging into Destiny 2 on multiple PCs simultaneously. To avoid this issue, players should ensure that they are signed out of Destiny 2 on all PCs on which they are not currently playing.
Cursor in Tri-Monitor configurations: Changing the resolution between 5760×1080, 4080×768, and 3072×768 may cause the mouse cursor to only be able to move on the right screen. Players encountering this issue should exit and reopen the Destiny 2 application using ALT + TAB. You can also enable windowed mode with ALT + ENTER.
Tri-Monitor Depth of Field: Depth of field effects can appear quite harsh on some tri-monitor configurations. Players encountering this depth of field issue can disable the function in the graphics settings.
Windows 10 Game Bar: The Windows 10 Game Bar may not function in fullscreen mode. Affected players who want to use this feature should use windowed mode or fullscreen windowed mode.
Numeric keypad mapping: Players may not be able to map most numeric keypad keys using control.
Image size on AZERTY keyboards: Players may receive the wrong key indicator when trying to adjust the image size on an AZERTY keyboard.
Input method in fullscreen mode: Players using the input method may encounter a black screen or lag when entering characters in fullscreen mode. These players are advised to use windowed mode or fullscreen windowed mode.
Close application: When Destiny 2 on PC is closed, players must close the application with the mouse. Controllers cannot select the in-game button that closes the Destiny 2 application.
Corporate and university networks: Some players may not be able to play Destiny 2 on corporate or university networks.