{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
12/25/2023 1:59:45 PM
11
Hi there!
According to your DxDiag report, your system is consistently experiencing AppHangB1 error codes with Destiny 2. This normally means that your system is having resource allocation issues.
Please make sure that you are up to date with your drivers, as well as up to date on your BIOS. As BIOS update processes are unique to each system or mainboard, we cannot provide guidance on how to do this. It can also cause boot issues if the process is not followed to the manufacturer's standards. Please refer to your system's support site for further guidance on how to do so.
English
-
My motherboard is on the second most recent BIOS release which was finally had a version of AGESA that fixes two issues plaguing the platform at the same time (previously fixed in different releases individually but never together at the same time). The only update since then was a security fix which is still a beta BIOS that I'm not interested in updating to until the non-beta version is released. As far as NVidia drivers, they are about a month old and the only major fix was for a discord streaming issue that I just admittedly hadn't cared enough to update for. Chipset drivers were up to date as of at least a few months ago, and Windows is up to date. I'm not sure what driver could possibly be so out of date that it would cause this. Given this has survived a full reinstall of Windows and has been an issue for at least a year now, I do not have any other ideas beyond it being an issue with the game itself. I am trying the other poster's suggestion of a clean boot, but it does take the game being open for several hours to verify that it still is crashing.
-
Question: have you activated SAM (Smart Access Memory) for your AMD system?
-
Edited by Phaaze: 12/25/2023 7:30:59 PMI have it setup so that Nvidia control panel reports that Rebar is enabled. I'd have to double check the specifics in the BIOS but I know above 4G encoding is on and whatever else was needed to get that working. I assume that is what you are asking as to my understanding SAM is just the name for AMD's implementation of Rebar.
-
Not just that, sometimes Sam/ReBAR can cause some strange issues... In your Bios/UEFI, is the PCI-E speed for the video card set to Auto, 4x or something else?
-
Edited by Phaaze: 12/26/2023 2:21:02 AMPCIEX16 Bifurcation and Slot Configuration are both set to auto. Bios shows slot information as "PCIEX16: PCIe 4.0 x16 @ 4.0 x16", and Nvidia control panel also shows x16 Gen4. I can try either turning Rebar off, but it's not even enabled for D2 to begin with. Alternatively I could force it on with inspector, but either way I've never noticed any other issues with rebar being enabled for other applications/games.
-
Edited by Crisidelm: 12/26/2023 8:47:26 AMPlease, give it a try, both ways (turn if off first, then if the games still hangs after an amount of time, turn it on for Destiny 2 too). Try setting PCIEX16 slot Configuration to 4x instead of Auto.
-
Edited by Phaaze: 12/28/2023 12:13:25 AMAnd now I'm done with testing both ways and still the game hangs. I have no reason to believe it is caused by PCIE configuration or Rebar/SAM. As a sanity check I ran SFC and verified the game on steam to see if there was any corruption with the OS or the game and both had none. I have no reason to believe there is any instability with my system, certainly not enough to cause daily crashes specifically on only this game when actively playing for extended 6+ hour sessions.
-
Edited by Phaaze: 12/27/2023 6:48:16 AMI can confirm it still hangs after testing with PCIEX16 set to 4x and rebar/SAM disabled. I will test with forced rebar tomorrow.
-
Alright, I'll give all of that a try and it'll take a while to test still as it only happens during active gameplay. Sitting in orbit for a whole day won't cause any issues, but doing stuff in game builds up to the hang always. I will also try to get a memory dump when it hangs next if I'm able to through task manager. I don't know if that will work or not but I realized a bit too late when it last hung that there was an option for that in task manager.
-
Hi. Enabling bifurcation on your PCI slot will only lower the link speed, there's no need in doing so. Do you have Precision Boost Overdrive and/or Curve Optimizer set up for your Ryzen CPU? Try disabling them or at least disable Curve Optimizer. Destiny is very sensitive to CPU stability and will crash to desktop if anything is amiss. Is XMP/DOCP enabled for your RAM? Frequencies above 3200MT/s on Ryzen CPUs are dependent on the memory controller being able to handle them, specially if you're running more than 2 sticks of RAM. Try selecting the profile 2 or disabling it completely to test.
-
Edited by Phaaze: 12/26/2023 1:20:42 PMNo, the CPU and GPU are both running at stock. I am also certain that the RAM is stable. I'm well aware of how the game responds to instability and have gone through all that before. It does not crash to desktop, the game is hanging. Occasionally it will also hang but recover after a few seconds, but that isn't common. There is never anything to repair if I have steam scan and repair the game. Similarly Windows has no corruption when running SFC. I'm confident the system is stable.
