Windows 10: Destiny 2 crash on open - possible hardware issue

So this problem has persisted for a couple of days but a game I've been trying to play, Destiny 2, refuses to start. Whenever I click 'play' on Steam it will "start" but not really since nothing pops up and then closes itself after a couple of seconds. It was working just fine about 6 days ago, but ever since then, it's stopped working. I've checked my task manager and it does show the .exe starting but as I said, nothing actually pops up in a window and after a few seconds, it closes itself. I've gone through and updated and/or reinstalled all the drivers I can, cleared Steam's cache, deleted my cvars.xml a game file that might've fixed the problem, validated my files, restarted my computer multiple times, started it in compatibility mode and as an admin, reinstalled Destiny and Steam, and it still refuses to start. Pretty much anything I can think of up to a clean boot, I've tried. For a little extra context, I attempted to overclock my GPU before this started and I'm worried that might've caused the problem. When the problem started I loaded a system restore point from before there were any issues and it still refuses to work. I've gone through my reliability monitor and took note of 4 Windows hardware errors that had occurred while I was overclocking and hadn't occurred anywhere beforehand.


Here is my DxDiag: https://pastebin.com/40Fk6Wjg

Here are the 4 hardware errors that I found: https://pastebin.com/uVjzN5QB


Any chance someone can help me with this, please? I first thought this might be an issue with the program but now I'm worried that I messed up big time somewhere along the way. Adding on one more thing is that other applications and games seem to be working just fine with no issues it's just this one that is having problems. Would be amazing if this could be fixed so thanks in advance.

:)

 

Destiny 2 Error Code Weasel

Can someone validate if the steps in this post helps resolve
Destiny 2 error code weasel on PC

 

Destiny 2 early access

Hi Noah,

We understand that you're trying to play the early beta access for Destiny 2 on Xbox One. We suggest that you visit this
page and check out the information posted under the product description of Destiny 2.

Let us know if you have other questions.

 

Destiny 2 Launches with Day One Issues

Today is the day, we've all been waiting for. Destiny 2 is finally available. Unfortunately, there are a few issues with the PC version. Game errors are inevitable, and they are part of every game launch. Some game developers just prefer to keep them hidden from the public. So kudos to Bungie for being honest and releasing a list of the known issues to the public.

For a start, Bungie is recommending all Destiny 2 PC players to install the latest Windows updates and display driver for their PCs before playing the game. NVIDIA users should be using the latest GeForce Game Ready 388.00 WHQL driver that was released yesterday, while AMD users can grab the Crimson ReLive Edition 17.10.2 driver. The company has also suggested restarting the Destiny 2 client and Blizzard application as a temporary workaround. If you continue to experience issues, then a deletion of the existing CVARS.xml file is required. The file is located in \Users\USER_NAME\Appdata\Roaming\Bungie\DestinyPC\prefs\.




Day 1 PC Known Issues List
Listed below are issues that Bungie is aware of that exist in Destiny 2 on PC.

• SLI, HDR, and VSYNC: Players may experience some rare issues when enabling SLI, HDR, or disabling VSYNC in some non-native resolutions. For the best experience, players are encouraged to use these features while running at their display's maximum available resolution.
• Saxophone Errors when Launching: Players may erroneously encounter Saxophone errors when launching the Destiny 2 application directly from the .exe file. Players who encounter this issue must close the application and relaunch through Blizzard's Battle.net app.
• Idling to Title Screen: In some activities, players who are returned to the title screen due to idling may be unable to log back in. Players who encounter this issue must close and relaunch the Destiny 2 application.
• Login after Disconnects: A generic error code may appear to players who lose internet connection, which may block an affected player from logging back in even after reconnecting. Players who believe they are encountering this issue should close the Destiny 2 application and relaunch.
• Buffalo Errors on multiple PCs: Players may encounter Buffalo errors when logging in to Destiny 2 on multiple PCs at the same time. To prevent this issue, players must ensure that they are logged out of Destiny 2 on any PC that they do not currently intend to play on.
• Cursor in Tri-Monitor Configurations: Changing resolution between 5760x1080, 4080x768, and 3072x768 may trap the mouse cursor in the right-most monitor. Players who encounter this issue should ALT+TAB out of the Destiny 2 application, then back. Players may also toggle Windowed Mode by pressing ALT+ENTER.
• Tri-Monitor Depth of Field: DOF effects may be overly aggressive on some tri-monitor configurations. Players who encounter issues with DOF can disable this feature in the Graphics Settings.
• Windows 10 Game Bar: The Windows 10 game bar may not work in Fullscreen Mode. Affected players who wish to use this feature should use Windowed or Windowed Fullscreen Mode.
• NumPad Binding: Players are not able to bind controls to most NumPad keys.
• Screen Bounds on AZERTY Keyboards: Players may receive an incorrect key prompt when adjusting screen bounds on an AZERTY keyboard.
• IME in Fullscreen: Players who are running Input Method Editors may encounter a black screen or delay when inputting characters in Fullscreen Mode. For the best experience, these players are encouraged to play in Windowed or Windowed Fullscreen Modes.
• Closing Application: When closing Destiny 2 on PC, players must close the application via mouse input. Controllers cannot select the in-game button to close the Destiny 2 application.
• Corporate and University Networks: Some players may be unable to play Destiny 2 on corporate or university networks. Players who encounter this issue must contact their IT department, to meet the connectivity standards outlined in our Network Troubleshooting Guide.

Source: Bungie