OP, I had the same issue. Tested everything. In the end, it was a faulty i9-13900K.
Try looking there.
I've got some more details to add to this case. My friend was running into this about a month ago. It kept getting worse and worse until the game would just crash to desktop without showing any error. As it got worse, he would also have applications randomly crash, especially Discord and Chrome. In Chrome, tabs would crash with the error "STATUS_ACCESS_VIOLATION". I've attached a screenshot of this... that I just took a few minutes ago. It seems that my computer is now also spiraling into a mess of instability like his did. He took it to Micro Center and they concluded it was a faulty CPU (he also had an i9-13900 series processor). Since his CPU replacement, he's had no crashes in-game. Given that my computer is following the pattern of decline that his experienced, I believe Intel might be having a quality control issue with their high-end CPUs or something.
It's just so strange. Even my terminal applications are crashing now. The process will just die all of a sudden. I was running a Python script and it now randomly exits. One of the times it crashed, it claimed there was a data type mismatch (the code didn't reflect this). It looks like applications will have their memory corrupted while they're running. Chrome pulled a disappearing act (it crashed) while I was typing this very message. I think I'm gonna RMA my CPU.
There is indeed a BAD batch(es) with the i13900... , ya could lookup the cpu partnumber and check it it was from a bad batch !
Sometimes a cpu just get fgaulty/broken.
Make sure youre memory isnt fooling you 😉
If ya go for official support and point out ya do not got comptabile (qvl) memory installed they probarly stop support you !
Also they like to shell new parts as long it will be more $$.
Cheers
@Rokebo73 wrote:ya could lookup the cpu partnumber and check it it was from a bad batch !
Are you saying "just look around online" or do you know an actual place I can look up whether my CPU came from a known bad batch?
@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. 🤓
@thedudeguy1 Good to read youre problem is solved.
Also good to know (for other poeple) that software does not always report / show the issue, as i said in other topics to other people many , many times already !
Same as memory test tools, they do not always report / show an error if something is wrong , WHY ? I cant tell ya, but hardware is hardware , and if something is bad/faulty it could mess up the whole system !
Software will not always report / show an issuies , UNFORTUNALLY !!
Im glad youre back into the game !!!
GAME ON !!
Cheers
PS THIS TOPIC NEED TO BE PINNEND AND NOTED.
TEST TOOLS (FOR CPU / GPU / MEMORY) DO NOT ALWAYS REPORT / SHOW AN ISSUE WITH HARDWARE !!!!!!
BUT YA STILL NEED TO TEST ALL HARDWARE TO FIND THE CULPRIT !
Also keep in mind that socket lga1700 and cpu could or are already bend, with those temps out of the box it can influence connections/pins and also
cause issues ya read all about in other topics.
Dont screw them to tight or oneven those screws with your (custom) AIO or AIR cooler,
A reseat from CPU could already solve youre issue if it is not the memory / Hz (XPM/DOCP.....) / OC / psu , ect ect
If ya did reseat cpu a CLR CMOS need to be done also , dont forget to reconfig bios settings after CLR CMOS (check manual for clr cmos).
Post youre info what it did for you after reseat cpu (and did all other trouble shoot first mentioned above here!)
@off3nc3 wrote:
@Rokebo73Hilarious post , bad batches of 13900.. I'm running the same CPU stock clocks and i've played every game on my system since snes emulators to Starfield/Armored Core 6 and literally every title maxxed out this year and finished without a hitch.
Stop blaming the CPU and the hardware the issue is on their netcode , they can't patch this game properly as this issue has been ongoing for 6+ months now.
Unfortunately I have the same issue and have replaced everything but the CPU. CPU is i9 14900k and passed every test, until i ran a 48 hour Aida 64 stress test and found multiple cores failing, Intel is starting the RMA process for me. There are a bunch of bad chips actually.
Asus Rog Z790 Maximus Formula (Bios 1202)
Intel i9 14900k
Corsair Vengeance 5600mhz 2x48gb (96gb total)
Crucial t700 4tb M.2 SSD
Corsair iCue Link H170i 420mm AIO LCD
Asus TUF OC 4070ti Super
Thermaltake 1650w PSU
Phantek Enthoos Pro 2 Case
Samsung Odyssey G9 49" monitor l
2 Dell 27" 240hz Gaming Monitors
