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

[MrPlowjoy]

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.

[Trash Panda Express]

I've been dealing with random issues in PC games for nearly a year and I'm pretty sure this is exactly my issue! Thanks for posting all this. I have a i7 13700k and I dropped the Pcore down by one, to 52, and the game booted immediately.

[MrPlowjoy]

Publicado originalmente por Trash Panda Express:

I've been dealing with random issues in PC games for nearly a year and I'm pretty sure this is exactly my issue! Thanks for posting all this. I have a i7 13700k and I dropped the Pcore down by one, to 52, and the game booted immediately.

Sorry to hear but yeah, its a very widespread issue. So widespread in fact, that several game developers have the Intel XTU "fix" stated on technical support FAQs. Crazy situation to be in.

[d3adf1sh]

it may also have something to do with e-cores. cyberpunk had a big problem with it. the solution was to disable e-cores in bios.

[Termix]

I read some articles at release, that the socket is probably at fault, since it can deform the CPU over time. Not sure if this has something to do with it.

There are several topics on that issue, like here:
https://linustechtips.com/topic/1504852-intel-12th-gen-processor-and-motherboard-bending-problem/

[Offence]

Old news , i already posted about it x55 to x54 on p-cores or swap to AMD , this intel gen is fudged.

[a.bortoletto]

14900k @ stock 5.7 P Cores, 4.4 E Cores 1.31V and RTX 4090 @ stock, the game runs perfect @2560x1440 with Ray Tracing enabled and DLSS Off

[MrPlowjoy]

Publicado originalmente por d3adf1sh:

it may also have something to do with e-cores. cyberpunk had a big problem with it. the solution was to disable e-cores in bios.

Nothing to do with ECores.

[MrPlowjoy]

Publicado originalmente por a.bortoletto:

14900k @ stock 5.7 P Cores, 4.4 E Cores 1.31V and RTX 4090 @ stock, the game runs perfect @2560x1440 with Ray Tracing enabled and DLSS Off

You may want to reconsider that cocky attitude. All three of my prior 13900ks also worked flawless. For a few months of heavy DX12/shader cache gaming. Then they all started to fail in identical ways and all reports show the 14900k is already in the same situation.

[MrPlowjoy]

Publicado originalmente por Termix:

I read some articles at release, that the socket is probably at fault, since it can deform the CPU over time. Not sure if this has something to do with it.

There are several topics on that issue, like here:
https://linustechtips.com/topic/1504852-intel-12th-gen-processor-and-motherboard-bending-problem/

Yep, I thought the same originally but CPU bending affects just the surface area. That could mean some PCores are being hit harder than others but all the investigation I've performed suggests CPU bending wouldn't result in Core errors, just means some cores may run slightly hotter than others.

I wouldn't discount it completely of course, it's another possible reason. This is part of the issue, nobody has been able to lock it down. The consistent factors are Intel 12th-14th Gen CPUs + 690/790 motherboards.

[a.bortoletto]

Publicado originalmente por MrPlowjoy:

Publicado originalmente por a.bortoletto:

14900k @ stock 5.7 P Cores, 4.4 E Cores 1.31V and RTX 4090 @ stock, the game runs perfect @2560x1440 with Ray Tracing enabled and DLSS Off

You may want to reconsider that cocky attitude. All three of my prior 13900ks also worked flawless. For a few months of heavy DX12/shader cache gaming. Then they all started to fail in identical ways and all reports show the 14900k is already in the same situation.

I just reported my feedback, I currently have installed: TEKKEN 8,Like a Dragon: Infinite Wealth and Avatar Frontiers Of Pandora and they all run perfectly . Avatar has been installed since December of last year and I still have no problems with the shaders

[MrPlowjoy]

Publicado originalmente por a.bortoletto:

Publicado originalmente por MrPlowjoy:

You may want to reconsider that cocky attitude. All three of my prior 13900ks also worked flawless. For a few months of heavy DX12/shader cache gaming. Then they all started to fail in identical ways and all reports show the 14900k is already in the same situation.

I just reported my feedback, I currently have installed: TEKKEN 8,Like a Dragon: Infinite Wealth and Avatar Frontiers Of Pandora and they all run perfectly . Avatar has been installed since December of last year and I still have no problems with the shaders

And all I'm saying is, its not an out of the box problem its a degradation. So keep an eye on it over the next month or two, depending on how much you game and get ready for the RMA. It's very likely to happen.

[Termix]

Publicado originalmente por MrPlowjoy:

And all I'm saying is, its not an out of the box problem its a degradation. So keep an eye on it over the next month or two, depending on how much you game and get ready for the RMA. It's very likely to happen.

I've had my CPU for quite a while and nothing happened, but to be fair I locked it at 125W TDP, since I expected some issues in the long run and the thermals unthrottled had me worried on day 1.

But ofc it's not a viable option for everyone to limit the CPU to 125W, even though there are no major disadvantages in gaming.

[VGShrine]

Publicado originalmente por MrPlowjoy:

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.

I faced that issue as I undervolted my 13900K by -0.090mV and using PL1/PL2 253. After checking the WHEA logs I found the parity errors only for the period I had the above undervolt setting. I tested my CPU settings with Cinebench r23 and Prime95 and neither of them generated WHEA Errors.

After some BSODs I decided to tune up my undervolt configuration and reduced it to -0.075mV and PL1 200W and PL2 253W (I needed the PL1 change as it's summer in my location and my room gets hot around 33C and that delta temperature doesn't allow my AIO to keep the CPU temperature under 90C). I ran Cinebench r23 and Prime95 again with no WHEA errors and this time I also added the 7-zip benchmark as that should be a similar compression/decompression workload for the CPU as the shader compilation done by some games and after monitoring HWInfo, no WHEA errors were registered.

Since that last adjustment, I have had no crashes neither instability issues with other applications. I have been testing latest games to test the CPU and no WHEA error/warning logs have been registered.

I have my 13900K for a year now and the WHEA error/warning logs I have are only for the period I apply the -0.090mV undervolt.

Here it is my current PC configuration: https://valid.x86.fr/lygtu5

One question for OP: Of all your KS processors that you had with this issue, were you applying any kind of OC? Even if you have been using the CPUs at stock, all Mobo manufacturers have stupidly higher voltages for the z790 chipsets out of the box and running your CPU at stock values with voltages higher than 1.4V degrades the CPUs in the long term. If you applied OC have an eye on the CPU voltage as Ideally you should have running below 1.35V.

[Thanor]

Publicado originalmente por MrPlowjoy:

Publicado originalmente por a.bortoletto:

I just reported my feedback, I currently have installed: TEKKEN 8,Like a Dragon: Infinite Wealth and Avatar Frontiers Of Pandora and they all run perfectly . Avatar has been installed since December of last year and I still have no problems with the shaders

And all I'm saying is, its not an out of the box problem its a degradation. So keep an eye on it over the next month or two, depending on how much you game and get ready for the RMA. It's very likely to happen.

Is this just an issue with the K series of the 13th and 14th gen? Or will it "likely" happen to all the 13 series and 14th series processors? For the record this same degredation happened to my 13900k in december and I upgraded to 14900k which seemed to fix it. Now I am getting the optimize shader error on this game unless i set the SVID on my mobo to Intel Fails Safe.

[MrPlowjoy]

Publicado originalmente por Thanor:

Publicado originalmente por MrPlowjoy:

And all I'm saying is, its not an out of the box problem its a degradation. So keep an eye on it over the next month or two, depending on how much you game and get ready for the RMA. It's very likely to happen.

Is this just an issue with the K series of the 13th and 14th gen? Or will it "likely" happen to all the 13 series and 14th series processors? For the record this same degredation happened to my 13900k in december and I upgraded to 14900k which seemed to fix it. Now I am getting the optimize shader error on this game unless i set the SVID on my mobo to Intel Fails Safe.

Can't say, all my energy went into the K situation but there its uniform across the 700 and 900s.