{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
3/27/2024 8:36:28 AM
12
Double check your RAM; that looks a lot like a RAM stick has gone bad.
Check your PSU too, it could be not performing optimally.
English
-
I ran the memory check as well, nothing out of the ordinary - the computer has no issues with any of the RAM sticks. As for the PSU, the hard crash with kernel power failure stopped when I turned off "restart on system crash" - it was something software-driven that would result in a crash. I can play games like SF6 without having any issues.
-
Makes sense. I'm going to try installing it on a secondary HDD to see if there's any difference. The machine isn't randomly turning off or getting BSODs under any other circumstances. It's just Destiny 2. Crashes, sure, but the games I've been playing that do crash (HD2/Darktide) are both hilariously unstable, to the point where I can't discern whether it's a problem on my end or not.
-
Yeah, it's not the hard drive. Install to the secondary disk got into the game itself, upon launching any activity I get hit with a marmot error and crash out. Well, "crash out", the game is still running in the background and needs to be closed via task manager.
-
If you have a intel cpu go into your bios and turn off a setting called turbo boost, it also might be called something else in your bios. if that fixes the problem then i might be a cpu problem. if not then it might be something else.
-
Wasn't able to find any sort of setting like that for my PC. I reinstalled windows and D2, and I crashed halfway through Scarlet Keep (no error), succeeded in finishing Navota's strike. Then I had a marmot error that crashed out the game, while it lurked in the background (as I didn't close it while I was trying to type up my a response) the game threw up a BSOD, referring to BEDaisy.sys. I'm at a loss. Full reinstall didn't work.
-
Manually tested each of the RAM sticks. Unless they're all bad, I still crashed back to desktop with a marmot error or got into a mission midway through before crashing with the marmot error. I don't believe it's the hardware at this point. - Unless all of the RAM sticks became magically faulty in the same exact way at the same exact time, the way it crashes out is identical and independent of configuration and slot for the individual RAM sticks. - Unless a SDD and a HDD became magically faulty in the same exact way at the same exact time, the way it crashes is identical regardless of which drive Destiny 2 is installed on. - I have noticed no artifacting from my graphics card in any other application. I believe the graphics card is in working order. - My PSU is working, and since I changed the windows setting to avoid immediate restart on crash, I have not had a Kernel Power Failure 41 error thrown up by Destiny 2. - Running the Intel Processor Diagnostic Tool showed the CPU had "passed" - no errors thrown up with any of the tests.
-
Two minor changes improved my situation a small amount, but I'm still experiencing occasional marmot crashes and outright ctds with no errors whatsoever: - Whitelisted BEService_64.exe with Windows Firewall (ingoing and outgoing) from not only the common/destiny2/battleye folder but also /appdata/local/battleye/d2/ folder. - Disabled all in-game overlays I could get controls to access (Discord, Steam, XBox Game Bar). There are probably others that I am unaware of on the system. This feels like a collision and/or a misconfiguration somewhere, I'm still trying whatever I can find that will placate battleye. Everything was fine about a month ago - I can't track what changed between then and now. Minor suggestion to Bungie devs - there has to be a more gracious way to have battleye flag an error and crash the game without performing a gross memory violation that forces a BSOD. Especially if it looks identical to a more serious hardware-related error. Especially if it's sharing an error code with "game file corruption."
-
At this point I'm 100% convinced that this is a collision between HD2's anticheat (nProtect Gameguard) and D2's anticheat (BattlEye) similar to other users in this post: https://www.reddit.com/r/Helldivers/comments/1awi6ga/nprotect_potentially_messing_with_other_games/ After whitelisting further instances of BEService_x64.exe and BEService_x64_d2.exe, I played HD2 for a short period of time last night. Worked fine for an hour, and I logged out for the evening. After quitting, I got a BSOD: KMODE_EXCEPTION_NOT_HANDLED with the culprit being BEDaisy.sys. Launching D2 by itself after this also resulted in an immediate KMOD_EXCEPTION_NOT_HANDLED error (again, BEDaisy.sys) Even stopping or uninstalling nprotect gameguard does not restore functionality to D2 back to where we were about a month ago before I put HD2 on my PC, and even a system reset didn't solve the issue - though I will admit that might be an issue stemming from the firewall blocking various BEService executables. There's enough cross pollination between the two games to where, when people come back to D2 for TFS or the leadup to it, you're going to see more of these errors. I'd appreciate any feedback regarding what I should do to fix this. I don't feel there's enough information regarding the difference between a battleye spawned marmot error, the BSOD with a Page Fault error, and the BSOD with the Exception Not Handled error.
-
I would like to add onto some issues I've been running into as well and something that was very odd to me. I have been getting Marmot error codes and instant game crashes for 3 months now and I'm still trying to figure out what to do. The thing that gave me some suspicions was the fact that I am able to run the game on the Epic store but not on Steam. It is starting to make me think it could be an issue with steam itself. In my testing I at one point decided to do a full reinstall of steam where I wiped every steam file from my computer. After redownloading it I downloaded D2 again and it ended up working for over 5 hours. When I decided to get off I just wanted to check if I would get an error code again and relaunched the game just to get marmot again. Another time I was able to get into the game by changing its priority in task manager and that let me play for about 3 hours before a crash mid trials card. Last time I got a marmot error code was after that crash but now I am just getting game crashes every time. Also going into task manager it seems that D2 reset its priority to not even normal but below normal. Setting it back to real time hasn't worked since that one time. It seems that some of the things that you ran into are a bit more extreme but I still want to try and spread some more light on this because it seems that nobody has taken enough initiative to really look at this issue. This is my 3rd attempt at saying something in the forum and both other times either got information that was tested already or no response at all.
