As the title says. I've had two crashes since the update today. Just letting you know.
-
Same for me! Cannot play more than 5-10 min and then it Crashes to Desktop. I have Samsung SSD (not m.2 and no magician installed on my PC) Ryzen 3700x 32gb ram 3070ti never had any issues before this update so it is clearly something on bungies end with the new update.
-
10 답변Immediate change after i capped my frames @ 60FPS. Never had to do this before. IDK WTF is causing the issue but this seems to be a solid temporary fix. GL Guardians
-
2 답변작성자: Drax 8/26/2021 9:18:31 PMRyzen CPU - Nvidia 3080 Destiny2 was hanging and then crashing to desktop with no error message ever since the season 15 patch. I tried several things -- newest drivers, shader cache, nvidia control panel off, etc etc -- up to and including a full fresh download of the game with no luck. It didn't matter what activity, it would run anywhere from 5-15 min or so before hanging and subsequently crashing to the desktop with no error message. Crashed in the tower, first seasonal mission(several times), EDZ... etc. I have since gotten my game run stable with zero issues since Tuesday evening. I am unsure yet why this has worked. I have always been running the game from a Samsung 970 EVO NVME drive for probably years at this point with no issues until now. On a whim, I moved the install to another drive (Samsung 860 EVO SSD). After moving the game it has run for a couple days with zero crashes. I thought it was a fluke, so I transferred the game install back to the 970 EVO NVME drive and immediately started experiencing crashes again. I have other game installs on the NVME drive as well as my windows install (windows is on a separate partition, same drive). But I haven't detected any other issues with the NVME drive that would make me suspect that it is experiencing any hardware issues. I have now moved it back to the SSD and it is once again stable. I have not spent a lot of time trying to determine why this is the case. Windows firewall also registers application exceptions by path, so I don't know if that may be involved as I was swapping b/t F: and S: paths. Hopefully this can help someone. It is strange to me that this has worked. I did see someone mention a samsung magician, but I don't see that running on my machine.
-
작성자: konkobar 8/26/2021 10:51:56 PMI also have problem - D2 wont start and after few seconds shows "The application was unable to start correctly (0xc000007b).Click ok to close the application." I am reminded of a story from the past. Few seasons ago players had a problem with showing up at EDZ. It was the season with fractals. To fix the problem, bungie put the game back a week. They loaded a game save from a week ago, before tuesday reset, to fix the bug. Then all players had a week to the back. Bug was solved but all triumphs, exo etc reaching in this week, went to the trash for all players who not have this bug. May it not be the same solution this time.
-
The strange thing for me is that I had zero problems on Tuesday. I played Tuesday night for several hours without any issues. The problem started for me on Wednesday. I feel like I've read similar reports in this thread. If I were Bungie, I'd be asking myself what changed between Tuesday's major release and the following Wednesday.
-
1 답변
-
My game keeps crashing. I have an i9900k and 3060ti. Gave up playing pvp as kept crashing mid game. No error just freezes and closes down or I have to end it in task manager. Thanks I love destiny 2 and it’s a shame can’t get to experience this season :) thanks
-
2 답변The game crashes / freezes all the time without errors. I need to restart my machine every time. The game is not yet playable at all.
-
3 답변Same. Crashed at the intro mission cutscene with MaraSov explaining who she is, and during the intro mission. I have never encountered crashes before, but I have a good feeling this is being caused by BattleEye. I've given up on trying to play for now until I see them implement a fix on their end.
-
1 답변I tried basically everything but it keeps crashing after 5 minutes. Guess I'm going to have to wait for them to address this issue...
-
1 답변So err, the game is basically unplayable now since it crashes every few minutes. Clearly this has something to do with Battleye ... perhaps a conflict with antivirus? Bungie you better not start banning folks because the anti cheat is returning false positives!
-
3 답변I have very inconsistent crashing time, sometimes it's fine for hours, sometimes it does it on character selection. I do get a window that says "bad_module_info has stopped working" every now and then. So what ever that is, should get fixed!
-
1 답변I have had multiple crashes as well since the update. Some were when I was in orbit looking at where to go. 2 Were loading the tower. All to desktop with no error. Checked event viewer and the information there is also not helpful as it even says the app name is "bad_module_info" but the error exception code looks like a DEP error (Data Execution Protection) of 0xc0000005. A Steam forum post suggested going to the battleeye folder (default C:\Program Files (x86)\Common Files\BattlEye) and setting both BEService.exe and BEService_d2.exe to run as administrator under compatibility settings. This allowed me to actually play the game, but get serious lag issues when participating in some areas (couldn't find a consistency as to where, but EDZ was awful and stuttered every 10 or so seconds, but the new events ran fine) Ryzen 9 3900X 64.0 GB ram Radeon RX 6700 XT
-
Same Issue, no error message, just freeze and CtD. No issues before season of the lost, seemingly no pattern to when the crash happens or how frequent. Makes the game completely unplayable right now. Tried validating, restarting, manually allowing battleye though firewall, updating steam, disabling all overlays but the crash still persists.
-
4 답변Just found this on BattlEye and wondered if this potentially causing an issue for those of us with Nvidia cards: [quote]When starting my game with BattlEye enabled, random legitimate applications on my system are being terminated. Recently several Windows 10 users have started experiencing this issue without a change on our side. After investigating we have concluded that it is caused by NVIDIA’s new “(Ultra-)Low Latency Mode”. Until NVIDIA provides a fix please disable this feature by opening your NVIDIA Control Panel, selecting “Manage 3D settings” -> “Global Settings” -> “Low Latency Mode” and changing this setting to “Off”. Click “Apply” and potentially also reboot your system.[/quote]
-
작성자: Slowdraw 8/26/2021 7:11:51 PMI know I’m going against the general sentiment here, but I had the exact same crash happen to me a week or so prior to BattleEye being implemented. But it’s definitely happening to me more frequently now. I don’t know how to pin this down.
-
Got a single crash on Tuesday, and no crashes yesterday. Today I can get about 3 or 4 minutes and then it crashes back to the desktop with no error messages etc. My PC is not the issue because before the update, I played for 12 hours straight on Saturday. System is: 5950x 32Gb 3600Mhz Ram EVGA 3080Ti FTW3 Ultra 1Tb Samsung 980 Pro I don't have Samsung Magician, I don't have the Gigabyte Fusion software running, I don't have the Lian-Li software running or the EK software running. Only thing running is MSI Afterburner, Steam, Creative Sound card software. I am going to try closing the sound card software and also MSI Afterburner and see if that let's me play without crashing.
-
3 답변작성자: 123TheCloop 8/26/2021 2:04:51 PMfor anyone saying this a "MSI/Rivatuner" problem I can confirm its not. I have nearly 4000 hours on siege which uses BE and legit have NEVER had Rivatuner or MSI afterburner cause any crashing in siege. so either BE has been incorrectly implemented and is crashing regardless of the program being used or bungie have just simply launched a broken patch as usual. [b]For me anyway, the crashing is very consistent in the Astral Alignment activity (basically crash within 2-4 minutes) yet I can play hours of crucible without any problems[/b]. Also for people saying to uninstall MSI and Rivatuner (this doesnt prevent the problem) you can literally disable the overlay for D2 which simply stops Rivatuner from hooking into the render pipeline which is how it presents statistical data. BE does not and has never had issues with MSI/Rivatuner in any game that I own. heck rivatuner/MSI afterburner overlay doesnt even work in D2 because Bungie block 3rd party overlays from hooking into the games pipeline (except for Nvidia overlay) This is just yet again another PC problem because bungie fail to play test correctly. are we forgetting last seasons day 1 crashing problems? [i]EDIT:[/i] So after trying the MSI/Rivatuner "fix" which I knew wasnt the cause, still had crashing. Tried ULM to "off" (ultra low latency mode) still had crashing after 2-4 mins Tried BE through firewall still no fix. Updated to Nvidia drivers 471.68 and the crashing stopped (was previously on 471.41). I didnt reinstall drivers (just updated over them) but reinstalling the drivers using DDU to wipe it clean, then install fresh drivers could also work.
-
2 답변I had the same issue, and remembered BattlEye having issues with RGB software, so I went to task manager and killed all my iCue services running, and everything went back to running like before. Suggest some of y'all giving that shot with whatever RGB programs you may have running.
-
2 답변Turning off MSI Afterburner fixed my crashing problem completely. Crashed every 5 minutes before that. Now I boot up my pc, start MSI Afterburner, set the undervolt and clocks I want, apply, then shut down MSI Afterburner. My clocks stay the same as I put them to, and my game doesnt crash. So if you are having a crashing problem and running MSI Afterburner or EVGA Precision or any other program like that, try turning it off.