{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by MLady:
1/20/2022 7:35:56 PM
5
I confirm the hotfix released on 1/20/22 does NOT fix the issue.
Keep telling me to update my drivers, come on.
English
-
The next time the game crashes, could you link me to your DxDiag? To find this information: [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. Please don't use Google Drive. • Create a link and post it here.[/quote]
-
https://pastebin.com/2grv1U7z This contains many more crashes happened today.
-
Thank you. From what I'm seeing: It appears you are receiving the error "[url=https://www.google.com/search?q=radar_pre_leak_64&rlz=1C1GCEU_enUS822US824&oq=radar&aqs=chrome.0.69i59j69i57j35i39j69i61j0l2.1527j0j4&sourceid=chrome&ie=UTF-8]Event name: radar_pre_leak_64[/url]" which has to do with memory. You may want to use the [url=https://support.microsoft.com/en-gb/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system]Windows System File Checker[/url] tool to repair missing or corrupted system files, and you may want to perform a disk check on your hard disk to make sure there are no errors. It appears you're receiving Windows error [url=https://www.google.com/search?q=Event+name%3A+BEX64+AND+%22Destiny+2%22]Event Name: BEX64[/url]. Players have reported that if you look into your crash info. and open it in a text editor, you may find an error similar to [quote] "RUNTIME ERROR: VCPPEXCEPTION_MODULE_NOT_FOUND at 00007FFB5D8C95FC halt information: (<unknown>) tried to load GFSDK_Aftermath_Lib.dll fatal error detected"[/quote] or something similar. If you find this error, you may want to locate the GFSDK_Aftermath_lib.dll file ([i]Program Files/Destiny 2/bin/x64[/i]) and copy it into your main Destiny 2 folder ([i]Program files/Destiny 2[/i]). Your Destiny 2 Crash Info. could be located in:[spoiler]Program Piles/Destiny 2/temp/crash_folder/pc_x64/crash_folder (random numbers)/crash_info.txt[/spoiler] Hope this helps resolve your issue. You are receiving the Windows error " [url=https://www.google.com/search?q=Event+Name%3A+CLR20r3]Event Name: CLR20r3[/url]" consistently. If you got this error then it means the Microsoft .NET Framework on your PC is corrupted or has problems. [url=https://dotnet.microsoft.com/learn/dotnet/what-is-dotnet-framework]The .NET Framework is what runs apps on your PC[/url].[quote]- Reinstall Microsoft .NET Framework by removing the default framework and installing a new Microsoft .NET Framework. - There are some registry cleaners you can find and use to delete old registry files which may still present on your PC. - Finally, here's a [url=https://www.google.com/search?q=Event+Name%3A+CLR20r3]Google Search[/url] that may help you find a solution to this issue.[/quote]
-
Thank you very much for answering. As suggested, I ran the System File Checker (sfc / scannow) and found no integrity violations. I checked all disks, even though while troubleshooting I moved the game in 3 different drives, to see if that could help. I placed GFSDK_Aftermath_lib.dll into the main folder. I ran the .NET Framework repair of the version 4.8 (the one installed on my PC) through the official .exe running it into the Command Prompt as ndp48.exe /repair. Deleted junk registry keys. Sadly, it didn't help. The game crashed with the same Broccoli error in the second run of dares of eternity. It's frustrating to see my pc running God Of War at constant 95% GPU usage for hours just before seeing your answer and seeing Destiny crash while GPU usage is never above 60% (fps cap, but it would be CPU limited anyway)... New DXdiag https://pastebin.com/XKx5JSMT I also found in the event viewer some interesting reports, I didn't check if they were in the DXdiag already: https://pastebin.com/ynZwmVJb I hope you find these useful. I absolutely ran out of ideas right now, so did my mates.
-
https://pastebin.com/TSfE3wBR Here's another one. NOTE: there's a series of errors caused by CorsairService.exe that is pretty common right now and it's due to iCUE. Killing the service at Windows startup prevents the error from happening, but the crashing in Destiny still persists. Thus, it's 100% NOT related to the crash.
