Hey there! Next time your game crashes, could you paste your DxDiag here?
You can find this by doing the following:
[quote]• Press (Windows Key + R) to bring up the Run dialog box, enter this command “dxdiag” without quotation marks.
• Click on “Save all information”.
• Copy the text and use a text dump website (i.e. [url=http://pastebin.com]PasteBin.com[/url]) to paste the information.
• Create a link and post it here.[/quote]
English
-
DxDiag on D2 CTD: https://pastebin.com/0BpzpieD
-
Your EXCEPTION_ACCESS_VIOLATION seems to be the issue. You may use this [url=https://ugetfix.com/ask/how-to-fix-exception-access-violation-error-on-windows-10/]link[/url] here to see if this solves your problem. You may want to follow the instructions based off of the first header. There are two other methods as well to isolate this issue. Method 1: Perform a clean boot which eliminates software conflicts when trying to install or update a program as well as running a program in Windows 10. This [url=https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows]link[/url] will help you perform a clean boot. Method 2: This [url=https://support.microsoft.com/en-us/help/4027498/microsoft-store-fix-problems-with-apps]link[/url] here will help you download Apps Troubleshooter. You also have a Windows error "AppHangB1". For the best experience, it is recommended that players update their drivers to their most recent versions, and accept any Windows updates that have yet to be applied before accessing Destiny 2 on PC. If your console controller is plugged into a USB port, take it out as that may also cause crashes. Here is some information which may help: [quote]- Try disabling or not running any GPU utilities such as MSI Afterburner or EVGA Precision. - Setting Destiny 2 and Steam to "Run as Administrator". - Setting an exception to your antivirus and removing Windows Firewall. - [url=https://appuals.com/apphangb1-error/]Here is an article[/url] which shows steps that might help you. - You may also want to update your OS and drivers.[/quote]
-
Can you tell me more about how you found this out? When I look through the DxDiag it shows basically no conflicts/issues apart from VBCable not being signed, which I suspect is unrelated. (I ask merely out of interest as a developer myself, but I mostly live in Unix land)
-
At the end of the DxDiag file there is a section called Windows Error Reporting, that lists the latest recorded errors.
-
If you look in the event viewer, you will see AppHangB1 when trying to play Destiny 2. You can also see the error numbers c0000005 which indicates an access violation that needs to be fixed.
-
@Crisidelm ahh thanks!! yeah i see that now: ``` Problem signature: P1: Corsair.Service.DisplayAdapter P2: 3.33.0.2 P3: 5f22b27c P4: System.Management P5: 4.8.4084.0 P6: 5dda3e36 P7: 8a P8: 51 P9: PSZQOADHX1U5ZAHBHOHGHLDGIY4QIXHX P10: ``` Is this maybe suggesting an issue with my memory (Corsair) or the iCue light control software?
-
Could very well be; iCUE is well known to cause a plethora of problems
-
Interesting. Will test some stuff and update after a work meeting!! Thanks again
-
Will do, and thanks for adding the steps in there!