OP, I had the same issue. Tested everything. In the end, it was a faulty i9-13900K.
Try looking there.
@off3nc3 Hilarious post. It was, in fact, a bad 13900. I spoke with Intel and they had me run some tests. All of which passed (except the XTU stress test which failed once but then succeeded for all subsequent runs). I got tired of being stuck with an unstable system so I went to Micro Center and got an i9-13900K and swapped it into my system. It runs like a dream now. I haven't received that error again and 2042 has only crashed ONCE in the past few days and only after an eight hour session. I told Intel this and they concurred with my opinion that, given nothing else in my system has changed, the processor is to blame. Intel has begun the refund process with me so I can return the faulty processor to them. I'll be hanging onto the good one that I got from Micro Center.
@Rokebo73 Thanks for your assistance in trying to help me diagnose this. @iElessar You were right on the money. It was because of a bad CPU. 🙌
@off3nc3 You have absolutely no clue what you're talking about. That DirectX error has nothing to do with netcode. Please stop talking like you're some sort of subject matter expert if you haven't the faintest clue what's going on. @Rokebo73 was way closer to figuring this out than you were. Just because you're running the same CPU as me doesn't mean that Intel can't possibly have a quality control issue that led to bad batches of it being sold in the wild. 🤓
I’m glad OP.
Did you replace it completely?
@iElessar Yep! Took out the faulty one, cleaned the paste off of it, boxed it up, and am waiting for shipping instructions from Intel. I bought a new one from Micro Center a few days ago, applied thermal paste, installed it, and have been gaming on it without issue for the past several days.
