I understand this might seem unlikely given that it's working fine as 64-bit, but that crash dump makes me want to suggest running a memory tester. It has "Poss

I understand this might seem unlikely given that it's working fine as 64-bit, but that crash dump makes me want to suggest running a memory tester. It has "Possible bit flips max confidence" of 25%. Ignore the exact percentage, I don't think it means much, but nonzero is atypical and concerning. (Definitely not a proof of anything!) "It would crash in random spots" is another piece of evidence. Some legitimate problems really do show up in a variety of ways, but it's way more common for "real" problems to show up in recognizably similar ways. And having a cluster in graphics stuff can sometimes mean it's triggered by heat or high bus traffic. I'll admit I'm biased: I work at Mozilla, and I have looked at quite a few bugs now where there were good reasons on the reporter's side as to why it couldn't possibly be bad RAM, and yet the symptoms made no sense, and it ended up being bad RAM. Our hardware is surprisingly untrustworthy these days. But I also happen to be working on things where bad RAM problems are likely to show up, so my priors are not your priors.