As the title says, random crash to desktop. No error codes, no bungie message or crash handler.
Only thing I could find is the following events in Windows Event viewer that match the time of crash:
[quote]Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff7477a19c3
Faulting process id: 0x65c0
Faulting application start time: 0x01d799663fd29f9a
Faulting application path: bad_module_info
Faulting module path: unknown
Report Id: 5a4578d2-9de9-44b8-a7fd-35efcd9706c6
Faulting package full name:
Faulting package-relative application ID:[/quote]
[b]Edit: [/b]This is basically happening ever 5 minutes for me now.
Destiny currently unplayable.
Have read some theories that this is to do with the introduction of BattleEye
Can't see any evidence of this yet.
[b]Edit: [/b]Seeing many with similar issues and particularly with Ryzen CPUs
My specs are:
[quote]CPU - Ryzen 9 5900x
GPU - RTX 3080 Driver version 471.68
RAM - 32 GB 3600MHz
Storage - Destiny running on Samsung EVO 860 SATA SSD
OS - Windows 10 Pro 64 bit 21H1[/quote]
[b]Edit:[/b] Found crash logs in C:\Users\%username%\AppData\Local\Temp\Destiny 2\crash_folder\
[quote]version:
v500_rc.main tiger_final release pc_x64 96750.21.08.09.1845.v500_rc.main 21.08.09 1845
thread information:
thread_name: unknown, thread_id: 00003f24
halt:
### RUNTIME ERROR: EXCEPTION_ACCESS_VIOLATION at 00007FF68BEB1261
halt information:
(<unknown>)
crash: tried to read address FFFFFFFF686A1739[/quote]
Any ideas for a resolution with be much appreciated.
[b]Edit:[/b]
After much trial and error I managed to solve my issue.
I should have tried things one at a time to keep track of what specific change fixed it.
The following is what I did:
[quote]- Set windows defender exceptions for BEService.exe and BEService_x64.exe in C:\Program Files x86\Common Files\BattlEye\ and BEService_d2.exe in \Destiny 2\battleye\ directories.
- Reset BIOS to "Optimized Defaults" (I have an ASUS x570) and did the bare minimum changes.
Set RAM speed, -0.1 CPU undervolt, enable fTPM.
- Did a program cleanup (didn't have a lot) uninstalled a few programs including MS PowerToys but nothing else of note.
- Closed MSI Afterburner and disabled from startup. (prior I had only a slight undervolt to minimize coil whine)
- Reinstalled Destiny.
- Reinstalled BattlEye via the bat files in \Destiny 2\BattlEye\ directory.
For me right clicking the bat files and running as admin didn't seem to do anything.
I had to run them from a admin CMD prompt.
Launched CMD as admin. (right click run as admin)
:d > enter (destiny installed on my D drive.)
cd "D:\Program Files\Valve\Steam\SteamApps\Common\Destiny 2\BattlEye\" > enter
Uninstall_BattlEye.bat > enter
Reboot
Relaunched Destiny and allowed BattlEye to install again.[/quote]
[b]Edit:[/b]
Have done some more troubleshooting.
Issue seems to be caused by PBO2 (precision boost override) curve optimization.
I can have PBO on, set things like max boost and set temp target ect but as soon as any amount curve optimization is done Destiny crashes.
This could be a conflict with my negative 0.1 CPU volt offset and PBO. (I'm trying to keep my system cooler and quieter) However this is stable in every other game I've played recently.
Witcher 1, Witcher 2, Ascent, ESO, Divinity 2, Shadow of the Tomb Raider.
Seems to be there is some instability with Destiny since SotL that only effects systems in very specific circumstances. All speculation as I'm not a software engineer or game dev. :)
For anyone still having issues I'd be checking any CPU or GPU overclocks, undervolt or for Ryzen PBO settings. Even if you haven't set anything yourself MB manufacturers like ASUS often have some of these settings set to Auto by default!
-
2 RepliesHey i tried your fix and i thought it was working until i went into the 30 year anniversary dungeon and/or wellspring. EXCEPTION_ACCESS_VIOLATION . I currently have a 5900x and 6800xt. I disabled my pbos but it still happening. Do i have to disable everything even the stuff that is just on auto and ram dodcp in bios? i just wanted to undervolt to reduce heat.
-
2 RepliesSo this solved my crashing issues, but now I get some minor hitching and massive frame drops/stutters when doing even the simplest of things, even though my Frame counter in the top right maintains the highest level of frames.
-
Oh my god thank you, I have been having this issue for weeks now and finally found this thread. I just had to disable PBO fMax and suddenly no more crashes.
-
exactly this issue today after freeze and crash to destopkt, bad_module_info on event viewer
-
1 ReplyI have an Intel CPU and have had the same problem (bad_module_info) for the last 3 days. This evening, every time I loaded into a crucible match the game would crash. I am running Windows 10 Home 20H2 and noticed there was a newer version available but I think you are already running the latest (aside from the Insider preview). I started the game with my antivirus disabled for 15-minutes, while letting the Windows update client (https://www.microsoft.com/en-us/software-download/windows10) update in the background. The game has not crashed since and I haven't yet restarted the computer to let the updates install. So I suspect it has to do with the antivirus. We have 2 similar pieces of hardware: - 3600 MHz RAM but I already disabled the XMP profile so its been running at 3200 since last night. So I dont think it's the RAM. - Destiny is running off a Samsung 970 Pro m.2. I read somewhere else that someone had a similar issue (though it wasnt specifically Destiny) with a bad_module_info error. They thought it was the Samsung Magician software v3.6, they reverted to v3.42 (or whatever the release before the 3.6 update was) and they stopped experiencing the error. I exited Magician to see if that was it but the game continued to crash with Magician closed. I still suspect the anti-virus. I'll update with more info as I experience/compile it.
-
1 ReplyEdited by El Tello: 8/26/2021 1:00:21 PMExactly the same crashes as yours. Started just after this Tuesday update. My first crash was on the cocoon mission, had 2 crashes there, then afterwards all over the place. I cannot seem to reproduce it, it seems random but I'm sure it isn't. [quote]Ryzen 5 3600 ROG STRIX GTX 1080Ti on latest version 471.68 Samsung Evo 970 NVMe Gen3 Win10 (21H1) Latest Version 10.0.19042 Build 19042[/quote] Notes: 1- Avira Free Personal is running, never had problems with it. 2- Samsung Magician is always closed and auto start OFF, game crashes with that completely unloaded from system. 3- Adata 3200 ram, but never had problems. 4- Some crashes are with-in 5 minutes, one standing still in tower switching a weapon, other claiming an engram from rahol. Other times i can play for hours without crashes. 5- Event viwer and DXDIAG below [quote]Event Viwer Faulting application name: bad_module_info, version: 0.0.0.0, time stamp: 0x00000000 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x00007ff7f1813a0a Faulting process id: 0x3f84 Faulting application start time: 0x01d79a77482c5869 Faulting application path: bad_module_info Faulting module path: unknown Report Id: aa9dd726-5fbc-43f9-88fe-51941614755b Faulting package full name: Faulting package-relative application ID: [/quote] My dxdiag: https://pastebin.com/UrazzWGQ