JavaScript is required to use Bungie.net

Help

Help us help you.
9/18/2022 2:51:03 AM
1
Consistently getting error code marmot. Deleting the BattleEye folder then verifying integrity of files works as a temporary fix, but after an hour or so it will happen again. I have run the "chkdsk" command on every drive in my computer and they are all operating normally. This is not an isolated incident as there are numerous other reports of this across the internet and on this forum. No one has found a permanent fix. I would like help to resolve this issue instead of being ignored like every other post about this code. Thanks.
English
#Help #Errorcodes

Posting in language:

 

Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

View Entire Topic
  • [i]Copied my response from a separate thread[/i] I had Marmot errors happening too, everything else running completely fine.. BUT, then I started noticing browser tabs crashing suddenly, discord had a weird crash and another game crashed too, now the other game crashing only happened once, but it was enough for me to become more suspicious. So, I decided to test my RAM using something called Memtest86, Straight away after 15 seconds or so, it was spitting out errors, I could see the names of the packages memtest86 was sending and also what the RAM returned, for every error, 1 letter or number had been switched with another. Conclusion, Destiny was right.. I was getting corrupt data, even though I rarely saw the problems elsewhere, hell I even use Lightroom and Photoshop that regularly use 90% of my 32GB of RAM and no crashes, but apparently it was affecting Destiny 2 first. I then ordered a new RAM kit, they arrived next day (Today), I installed them and ran Memtest86 again, it passed all 13 tests twice, so it was definitely my old RAM that was the culprit. [b]Suggestion:[/b] If you have a spare USB drive laying around, look up some videos on how to use Memtest86, download and image it to the drive and test your RAM, even though you're not seeing problems with other things, there could very well be a problem with your RAM that's just waiting to get worse and or corrupt your system files. Hopefully this can help you get to the bottom of this, because it certainly helped me.

    Posting in language:

     

    Play nice. Take a minute to review our Code of Conduct before submitting your post. Cancel Edit Create Fireteam Post

You are not allowed to view this content.
;
preload icon
preload icon
preload icon