OP, I had the same issue. Tested everything. In the end, it was a faulty i9-13900K.
Try looking there.
Hey there! Thanks for all the suggestions. I'm away from my computer at the moment so I can't provide all that info you requested just yet. I'll be back in about a week and I'll be able to look further into this then. One thing I give you are the results of a recent experiment.
I tried an experiment to see if one of my sticks of RAM was the culprit. It's not a perfectly sound experiment because I didn't check the memory speed (I noticed my mobo restarted several times at boot while doing memory training so it probably didn't successfully use the default speed) while Windows was running. What I tried was using just one of the sticks of RAM and I played for several hours and only had the error once. I encountered E_OUTOFMEMORY only one time in the span of several hours which is really odd. Usually it happens several times in a row. The next day, I tried the other stick of memory and had no issues at all.
Again, this wasn't very scientific and I suspect that the memory speed was lower which may be why it was more stable. Still, I wonder why the DirectX error refers to being out of memory. I would think it's referring to VRAM and not my actual memory. Or is the error just a red herring and it can be triggered by something other than a memory issue?
Oh yeah, about your question as to whether the memory part number is correct, I noticed the command's output was incomplete which is why I provided the full model number in my 1st post. I have a picture of the memory and it confirm the full model number.
Anyways, I'll be back with some of the info you asked for in about a week. Thanks again for your assistance!
@thedudeguy1 quote: Or is the error just a red herring and it can be triggered by something other than a memory issue?
yes it is possible, but... !
I did check for the partnumber in the Memory QVL.
This partnumber is not in the QVL, the memory is not compatible with youre system and cpu !!!
If ya still got some return guarantee at those memory sticks (and the box where it was in), i would return them and change them for memory thats in the QVL.
Good you posted the picture, good info that is needed , and this explains all
Im am very sure if ya got compatible memory , there will be no issues with the XMP ya select !
This will also bring more performance to youre system !
This will solve youre issue and stress 😉
Keep us up to date when ya returned/changed memory !!!!
So other forum readers could use this info to.
See ya in a week, have a good time.
Cheers
EDIT: I add website with compatible memory for youre cpu/motherboard
If ya buy new memory , make sure that ya buy 2 sticks in one and the same box.
Cause this will be memory thats from the same batch, to make sure there arent issues with different sticks from different batcjes !
(dont forget to select the correct CPU type first !!!!)
https://www.asus.com/motherboards-components/motherboards/prime/prime-z790-a-wifi/helpdesk_qvl_memory/?model2Name=PRIME-Z790-A-WIFI
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?
