To everyone experiencing shader compilation "Out of video memory trying to allocate a rendering resource" errors

[MrPlowjoy]

To everyone experiencing shader compilation "Out of video memory trying to allocate a rendering resource" errors

Your CPU is faulty and has Core errors. It's not your GPU, its your CPU

Crashing with this sort error message (and others, including straight up CTDs) when performing shader compilation is famously caused by broken CPUs, namely the Intel 13x and 14x series, and more specifically (but not solely) the 13900k and 14900k variants.

Anyone affected by shader comp crashing on the aforementioned CPUs just needs to open Event Viewer and do a parse for 'WHEA-Logger' warnings. Inside those entries, look for 'Translation Look Aside Buffer' and 'Internal Parity Error'. There will be lots. That's a bad CPU.

Furthermore, the CPU core errors, which are PCore-based can be surfaced by running OCCT whilst applying a very slight OC via BIOS, with SVID=Typical and LLC=4. OCCT will out Core errors almost immediately and then throughout the rest of the run. You may even get OCCT to report Core errors without these BIOS tweaks, depending on how bad the CPU has gotten. Attempt any this at your own risk. I'm simply reiterating how I was able to isolate down.

Need more proof? This is a thread I stumbled over when investigating my own exact same problem.

https://www.reddit.com/r/buildapc/comments/11uftum/rtx_4090_i9_13900k_pc_build_crashing_with/

And this quickly became drenched all the same issues...

https://www.reddit.com/r/intel/comments/13o29w5/13900k_will_no_longer_run_dx12_games_crashingctds/

and the list goes on and on and on and on, and this is only a small fraction of whats out there...

https://www.reddit.com/r/remnantgame/comments/17lpz8g/13900k_not_stable_on_stock_during_first_shader/

https://www.reddit.com/r/intel/comments/12bybl5/something_wrong_with_13900k/

https://www.reddit.com/r/intel/comments/17ku82f/13900k_degradation_i_have_faulty_cpu_and_try_my/

https://www.reddit.com/r/intel/comments/17aob62/13900k_wheas_19_or_bsod_during_shader_compilation/

https://www.reddit.com/r/pcmasterrace/comments/17gb3p0/13900k_out_of_video_memory_or_bsod_during_shader/

The only solution is to either drop the PCore multiplier down, I got stable at 52x but it can vary (and still degrades, so needs more ongoing effort) or RMA. You can drop the PCore using Intel XTU but again, use at your own risk (although its fairly straightforward for anyone with basic PC tech understanding).

*I'm on my 4th 13900k in just over a year*, which has so far been working for a few months.

This is a CPU hardware defect. Nothing in software or OS or BIOS (other than a BIOS-level downclock), will provide a stable system. You can trust me, given I spent close to 6 weeks troubleshooting my own system before isolating it to the CPU.

----

Edit: Just want to make one point really clear; these errors don't generally manifest out of the box. That is, it takes time before the CPU becomes affected. In my case, every CPU took between 1-3 months before the exact same behaviour started to show. DX12 and shader comp, either at initial shader comp or during gameplay, would crash the game client out.

One that continually caused these errors for me was Fortnite DX12 with all the settings ramped to top or one step down from the top

The issues started small. Very occasional errors as per the title, when trying to load the game, but clicking away and trying again would mostly work. Then sometimes work. Then never work, indicating the CPU was degrading. Then even in times where it would load to the menu, trying to get to the staging area would crash out, again with the same error. Checking the game log, it pointed to the shader comp causing a fatal error.

Replacement CPUs fixed all that. For a while. But in those cases, the game would load up and go into a match but during gameplay, would CTD. Checking the game log again, it showed that shader decompression, due to traversal, was again causing a fatal error.

Every time these errors happened, using OCCT with the settings I stated, would show Core errors.

The list of games affected is huge. Every DX12 shader based game will crash at least during initial shader comp or if not, as above, some time after. If shader comp can be gotten past, it might seem OK but as soon as you update the GPU driver, or the game is patched, it will perform shader comp again and that's why some people can see it as hit and miss.

--

Edit#2 for those who resolutely believe this is a game-code specific problem that the devs will fix.

The issue is widespread. Just google "Out of video memory trying to allocate a rendering resource". Over two million results. Other game devs are actively stating the PCore multiplayer workaround on their tech support pages, pertinent note being they're not fixing it in code....

Fatshark
- https://support.fatshark.se/hc/en-us/articles/360021425793--PC-How-to-Resolve-Data-Corruption-Errors?fbclid=IwAR3sTt1GpEPV4sMYLu12zWde1ZXYj6PsYN0g3Fxx9hwrDXu8nWTh8Ni-tfw

"Intel i9 13900k/i7 13700k: Underclock 'Performance Core' Speed
It has been noted that players with the Intel i9 13900k/i7 13700k CPU are prone to these crashes. Players have been able to work around this by underclocking the 'Performance Core' speed using Intel XTU, from x55 to x53."

Remnant 2
- https://www.remnantgame.com/en/news/article/11551423?fbclid=IwAR1x74b4uo7dnGLPDEUwyR87WMqiKFJM7WGN7JAFPO0KUfPzS93M_DWQ4_w

"--Out Of Memory when Loading (Intel 13th generation CPU’s)--
We have identified an issue on some Intel 13th generation CPU’s where upon startup the game will display a message about being out of video memory or the crash reporter will pop up referencing an issue with decompressing a shader. If you experience this problem, you will likely also see it in other DX12 games.

If your CPU is overclocked, try setting it back to the defaults. If you’re not overclocked or that doesn’t work, try installing Intel Extreme Tuning Utility"

And even Epic acknowledge it
- https://www.epicgames.com/help/en-US/fortnite-c5719335176219/technical-support-c5719372265755/out-of-video-memory-trying-to-allocate-a-rendering-resource-error-a20960841352859

There will be tons more. I've seen this problem on the Hogwarts forums, just by chance and more recently, Suicide Squad, here - https://steamcommunity.com/app/315210/discussions/0/4204741842669464852/?ctp=6

There has been debate that the CPU was always faulty to start with, rather than degrading but my experience as mentioned above is that the order ends up being, sometimes the error happens and if you try again the game works. Then after some time, the error happens more and its trickier to get games working. Then some time later, zero DX12 shader games run at all, complete breakdown.

[Feeterican]

Thanks MrPlowjoy

[Fummelwilli]

Hi there,
sadly these problems are not new:

https://www.intel.com/content/www/us/en/support/articles/000096448/processors.html

Seemingly back then mostly MSI boards suffered from it. Chances are high, that they messed up their microcode again.

[risond]

I can confirm I have had this same problem since day 1 and until now I didn't realize what it was. I had thought it was simply my cooling solution, so I undervolted, limit my PL1/2 and fixed my p-cores at 55x which in games is always just under that but I never have an issue with this config. Once I try to increase to anything higher like 56x, 57x, etc. I get a complete system freeze when loading certain games(TLOU Part1, Immortals Aveum, etc.).

I am running a pretty decent board(Aorus Master z790) and Aorus Master 4090 GPU. I am pretty frustrated to say the least. I guess my question is, will this remain stable at the lower clock speed or will it eventually degrade to the point it isn't usable?

It seems that Intel should be addressing this issue because this is not acceptable. How are other folks doing high-end OC builds not encountering these issues? I don't have a custom cooling solution but I have more than 3 grand invested in this rig so I expect it to last 5 years or more.

UPDATE: I ran several different tests including avx2 offset, undervolting, etc. and I think I found a solution. If I set the Core Current Limit(ICC) to something other than auto, I am able to OC my p-cores to 57x and ecores to 44x. I haven't tried going higher but before this change, the avx2 test intel xtu would crash the system and ue5 games would hard freeze it. I set the current limit to 400(amps) and that is keeping it stable at 57x/44x. I am still thermal throttling and power limit throttling but at least it doesn't freeze the system. That throttling can be fixed with a custom loop. I am using a ek lux d-rg 360 cooler.

[mady]

i'm getting this issue trying to use UE4 and this thread popped up but i have a ryzen 3700x, related at all? how do you parse event viewer?

[Osiris]

I have a 13900KF and have not had any problems at all.
MSI MPG Z790 Mobo.
Nothing has failed to run.

[Gurkoel]

https://www.theverge.com/2024/7/22/24203959/intel-core-13th-14th-gen-cpu-crash-update-patch

Might be interesting for some of you

[Jaden Bunny]

A BIOS update sorted the crashing for me. Not sure if it will be a permanent solution if the hardware is indeed crappy. I was assured by my supplier / builder that it affects the Gen 14s more than the 13s but it was CTD almost every-time I played until I updated the BIOS. No crash yet since.
Updating your BIOS can be risky so take care peeps if attempting, follow instructions carefully and double/triple check it's the right one for your exact MoBo - my builder, who had my system's details on file, kept trying to send me the wrong one... I had to work out the error and find the right one and I know NOTHING.
I hope that has solved the issue but no telling. I am furious, Intel have lost my respect.

[Gurkoel]

I will contact intel for a replacement, as too much voltage causes CPU weardown ... I mean its their fault so ...

[Stugots]

This is the hardware fault to be found in some 13/14 series CPU's, it's oxidation in the CPU from a manufacturing fault. Intel has now confirmed the via oxidation, a fabrication-level issue, was "fixed" in 2023, but who really knows.

Data centers are now not using these CPU's anymore as they where getting high failure rates from them as they're used 24/7.

(Note: It's not all but a high percent will fail in time depending on use etc and some will not fail at all due to either oxidation or the micro code in the CPU has a bug and the voltages are too high which damages over time and causes instability and a fix for this is coming in August.)

[TOXA_TLH]

does that affect laptop CPUs?
I'm about to buy a laptop with i9 14900HX, so I hope it doesn't.