{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
4/3/2024 6:13:28 AM
4
Came back about a week later (4/2/2024). No issues with any other games I'm running, nprotect and battleye both had updates since last time I ran D2. Immediate Marmot error upon entering into a strike.
File integrity is fine - all 3016 files validated with no errors found. Still a collision between anticheats, and I don't know enough about either nProtect Gameguard or BattlEye to find a solution.
English
-
Attempting to follow BattlEye's FAQ to fix the issue resulted in a disastrous BIOS update that kept crashing the system. When I rolled back the BIOS to the prior version, reinstalled windows (again) and reinstalled Destiny 2, I was hit with a Marmot error from queuing for a strike. What changed in the last month and a half to where my system, with a completely fresh Windows, Steam, Destiny 2 and BattlEye install, can't even boot into a strike without crashing out with a Marmot error? The files are all in working order, according to steam, BattlEye was freshly reinstalled, my RAM is in working ordering, my CPU is in working order, and my hard drives are both fine. What else can I try to fix this? Check each individual sub-release for the BIOS between the current and final version?
-
Crash log from Temp\Destiny 2\crash_folder\crash_info.txt Marmot Error: resourcerer:load: Failed to load tag with path '<N/A>' and description '<N/A>' 0x80AFA466 (0x017d 1126) from package {{packages\w64_sr_fx_017d_0.pkg}} with error 'error decompression, {{!0x00000000!}}' install type {{!5!}} ... delete the file, then verify the game contents and... Crash to desktop, no visible error: ### RUNTIME ERROR: EXCEPTION_ACCESS_VIOLATION at 00007FF60CF5AF8B halt information: (<unknown>) crash: tried to read address FFFFFFFFFFFFFFFF Ok we're back to something trying to BSOD me with an access violation.
-
Relaunched, tried another strike, got Marmot'd again. Crash log now points to resourcerer:load: Failed to load tag with path '<N/A>' and description '<N/A>' 0x80E14B00 (0x030a 2816) from package {{packages\w64_sr_combatants_030a_0.pkg}} with error 'error decompression, {{!0x00000000!}}' install type {{!5!}} Different package this time. Deleted and verified to redownload the package. Relaunched, tried another strike, got Marmot'd again. Crash log now points to resourcerer:load: Failed to load tag with path '<N/A>' and description '<N/A>' 0x80EB3DB8 (0x0359 7608) from package {{packages\w64_sr_sandbox_weapons_0359_2.pkg}} with error 'error decompression, {{!0x00000000!}}' install type {{!5!}} ... different package. I'd either be crazy or become crazy if I continued. Any feedback from Bungie would be appreciated.
-
Updated Destiny 2 on my older machine (some hideous amalgamation of case and hardware, borne of an Alienware thin machine combined with a Radeon 1070 that's about 10 years old, stuck on Windows 10 due to a mobo/cpu limitation), to which it updated through the local network, pulling the files from the downloaded D2 on my current machine. No errors, worked fine. No marmots in sight. Considering the hardware checked out just fine on my current PC, the configuration of what I have installed with my current hardware somehow "went bad" in the last month and a half to the point where a fresh reinstall won't fix the marmot errors.
