Made a post on this before as I encounter this Marmot error numerous times, even when going for day 1 Salvation's Edge which just demotivated me to even keep going.
Took a few months off and thought to re-gild the solstice seal and what do you know? Marmot error knocked down my front door.
There are zero things wrong with my PC - In-fact, I have since replaced all RAM sticks, motherboard, CPU, GPU and even replaced my SSD with another and an M.2 (been a busy and expensive summer). I have reinstalled a fresh Windows where I did not preserve my files. I had done all the tricks with verifying files, deleted D2 files in the temp folder, running memtest on my RAM, doing a SFC /Scannow, following the marmot error guide religiously to see if I missed anything.
I see a bunch of other folks over the months have had marmot errors and the responses from Bungie help are just all inconsistent which gives me zero faith this is being looked into. The uptake of this issue has been a problem since the season before TFS launched and this has yet to still be accounted for in the known issues page.
I'm just reporting this because I hope for everyone's sake who's facing this same issue gets the help they deserve because this near 10 year player has just had enough of this game because of this issue. I don't plan on playing this game until it's fixed. It's a big shame because it was my fave game that I grinded daily, just now i'm enjoying my time in other games where I don't have these performance/optimization issues and lack of clarity that this is actually seriously being looked into. I can't play this game on stream and cannot commit to any content like a dungeon or a raid as I might have to leave my team high and dry as it requires a file verification every time I have this error. This is absolutely embarrassing to have to explain to my stream or my team "oh sorry guys, well there's an error I keep getting where Bungie is not giving any clarity about said issue but if you could sit tight for 10-20 minutes, we will resume the show but probably get hit with the same error in a couple of hours"
-
Thought to check in to see if this received any reply from Bungie. Am I going to get any acknowledgement this side of the year?