DirectX E_OUTOFMEMORY Error
Hi there! Ever since around season 4 I've intermittently gotten a DirectX error (screenshot attached) while loading into a map. Allegedly, it fails to allocate enough VRAM for some DirectX API call. From other posts here, that error seems to be a red herring and the problem is elsewhere. Over time, I've been getting it more and more frequently which makes me wonder if it's a hardware defect that's worsening over time. More recently, I've even had the DirectX error while sitting on the main menu screen before I've entered a single match (although that's less common). I've also sometimes had the game CTD without giving any error at all. Just *poof* and it's gone. I can't fathom what the problem might be at this point but from what I've seen in the other threads here, this is a common problem with my CPU. Here are my specs:
Motherboard: ASUS Prime Z790-A WiFi 6E
CPU: Intel i9-13900KF (Batch# X245E824 in case that's relevant) (I haven't done any overvolting, undervolting, overclocking, or underclocking)
Memory: G.Skill Trident Z5 RGB Series (2 16GB sticks totaling 32GB) (Part number F5-6000J3636F16GA2-TZ5RK) (Set to XMP I in the UEFI settings)
GPU: ASUS TUF Gaming GeForce RTX® 4080 OC Edition Graphics Card
I've attached my DxDiag and the output from the following three wmic commands which I've seen asked for in other posts:
- wmic /output:mb_mem_bios_info.txt memorychip list full
- wmic /append:mb_mem_bios_info.txt baseboard get product, Manufacturer
- wmic /append:mb_mem_bios_info.txt bios get smbiosbiosversion
@Rokebo73 You seem to be the expert with this issue so if you have time, I'd be infinitely grateful for your wisdom. Let me know if there's any other info I could provide that would help diagnose this problem.
Oh yeah, I did check to see if the memory I'm using has been tested and validated with my MOBO but I couldn't find it on the list here. However, I don't think it's because my memory is incompatible. If that were the case, I would think that I'd have had this error for much longer and it wouldn't have cropped up in recent months.
OP, I had the same issue. Tested everything. In the end, it was a faulty i9-13900K.
Try looking there.