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.

[MrPlowjoy]

Originally posted by VGShrine:

Originally posted by 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.

Good to hear you got stable! It can be achieved via tweaking BIOS settings for sure but a base PCore multiplier drop, via Intel XTU makes it more accessible for the masses.

No OC applied, other than the out of box Asus Muilticore Enhancement and XMP1 on the DRAM. On my second CPU replacement I immediately disabled Asus MultiCore Enhancement and the errors reappeared after 1-2 months.

[VGShrine]

Originally posted by MrPlowjoy:

Good to hear you got stable! It can be achieved via tweaking BIOS settings for sure but a base PCore multiplier drop, via Intel XTU makes it more accessible for the masses.

No OC applied, other than the out of box Asus Muilticore Enhancement and XMP1 on the DRAM. On my second CPU replacement I immediately disabled Asus MultiCore Enhancement and the errors reappeared after 1-2 months.

Probably that's where your issues are. By default all motherboard manufacturers set higher CPU voltages that are over 1.4V, when I built my PC I noticed that and undervolted it since day 1 to avoid degradation in the long term. Keep in mind that if you run stress tests frequently with the default Mobo OC settings you may degrade the CPU prematurely as CPUs in normal use cases it aren't likely to be running at 100% for 10 minutes or more, not even for gaming.

To add to this issue, some users reported that some applications or Windows don't handle efficiently the CPU throttling from the 12-13-14th GEN CPUs causing the CTDs or BSODs when running some demanding tasks (Video encoding, shader compilation and heavy computation processes like decompressing/compressing). This is the reason of why undervolting was recommended for this CPUs: to avoid throttling as there is no AIO or Air cooler that can handle more than 253W of heat dissipation and by default the Mobo manufacturers have the PL1/PL2 limits unlimited with higher voltages and MCE. So basically, the motherboard manufacturers are the responsible for this issues as they don't provide default settings under Intel's recommended CPU parameters.

[MrPlowjoy]

Originally posted by VGShrine:

Originally posted by MrPlowjoy:

Good to hear you got stable! It can be achieved via tweaking BIOS settings for sure but a base PCore multiplier drop, via Intel XTU makes it more accessible for the masses.

No OC applied, other than the out of box Asus Muilticore Enhancement and XMP1 on the DRAM. On my second CPU replacement I immediately disabled Asus MultiCore Enhancement and the errors reappeared after 1-2 months.

Probably that's where your issues are. By default all motherboard manufacturers set higher CPU voltages that are over 1.4V, when I built my PC I noticed that and undervolted it since day 1 to avoid degradation in the long term. Keep in mind that if you run stress tests frequently with the default Mobo OC settings you may degrade the CPU prematurely as CPUs in normal use cases it aren't likely to be running at 100% for 10 minutes or more, not even for gaming.

To add to this issue, some users reported that some applications or Windows don't handle efficiently the CPU throttling from the 12-13-14th GEN CPUs causing the CTDs or BSODs when running some demanding tasks (Video encoding, shader compilation and heavy computation processes like decompressing/compressing). This is the reason of why undervolting was recommended for this CPUs: to avoid throttling as there is no AIO or Air cooler that can handle more than 253W of heat dissipation and by default the Mobo manufacturers have the PL1/PL2 limits unlimited with higher voltages and MCE. So basically, the motherboard manufacturers are the responsible for this issues as they don't provide default settings under Intel's recommended CPU parameters.

Possibly, yeah. BIOS 1801 for the mobo has definitely brought with it a huge drop in CPU stress, though. Circa 10 degrees cooler under the same load as prior and also pulling in 20+w less, again under the same load.

[ZOIXS7]

Disable OC Setting: CPU, RAM.

Deactivate XMP2 / Enable XMP1

[Shadow]

Damn and I was thinking of getting the 14700k or the 14900k. I read somewhere that it's happening if you go above 5600MHz of RAM for the CPU. Some people said when they bought RAM kits rated at 5600 the problems went away. Anything above that causes issues, apparently.

[MrPlowjoy]

Originally posted by XIOAS:

Disable OC Setting: CPU, RAM.

Deactivate XMP2 / Enable XMP1

If you're already experiencing the problem this doesn't fix it.

[MrPlowjoy]

Originally posted by Shadow:

Damn and I was thinking of getting the 14700k or the 14900k. I read somewhere that it's happening if you go above 5600MHz of RAM for the CPU. Some people said when they bought RAM kits rated at 5600 the problems went away. Anything above that causes issues, apparently.

I can confirm that's not accurate. I run 5600 rated DRAM throughout and I've had problems with all three prior CPUs.

[Shadow]

Originally posted by MrPlowjoy:

Originally posted by Shadow:

Damn and I was thinking of getting the 14700k or the 14900k. I read somewhere that it's happening if you go above 5600MHz of RAM for the CPU. Some people said when they bought RAM kits rated at 5600 the problems went away. Anything above that causes issues, apparently.

I can confirm that's not accurate. I run 5600 rated DRAM throughout and I've had problems with all three prior CPUs.

Ouf. Guess I'm sticking with my 12700k until the 15th gen then.

[Offence]

Originally posted by MrPlowjoy:

Originally posted by 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.

Why RMA ? It's an easy fix to downlock to x54 and keep on truckin' , ain't no way im swapping to AMD and overheat on a latest 7950x for example.

It's time to face the music and wait for intel's next chips until then these are doing great , minus-plus the minor downlock.

[MrPlowjoy]

Originally posted by -=🗲Offence🗲=-:

Originally posted by 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.

Why RMA ? It's an easy fix to downlock to x54 and keep on truckin' , ain't no way im swapping to AMD and overheat on a latest 7950x for example.

It's time to face the music and wait for intel's next chips until then these are doing great , minus-plus the minor downlock.

Because in my experience, the downclock requires more tweaking down over time. I've seen examples where it started at 53x and the most recent had to be 51x.

This is the problem. It's a degradation.

[VGShrine]

Originally posted by MrPlowjoy:

Originally posted by -=🗲Offence🗲=-:

Why RMA ? It's an easy fix to downlock to x54 and keep on truckin' , ain't no way im swapping to AMD and overheat on a latest 7950x for example.

It's time to face the music and wait for intel's next chips until then these are doing great , minus-plus the minor downlock.

Because in my experience, the downclock requires more tweaking down over time. I've seen examples where it started at 53x and the most recent had to be 51x.

This is the problem. It's a degradation.

The degradation only happens if you run your processor at your motherboard default settings and it will accelerate if people run benchmarks with those settings very often. Also, the ratio configuration doesn't solve the problem, the Core Voltage need to be updated so it doesn't use the higher voltage from the Mobo default settings and keep the PL1/PL2 at Intel specified values to avoid throttling unless you have a really good cooling solution that allows you to run it at higher PL1/PL2 values.

As I mentioned in my previous reply, I don't think it's a processor defect and more negligence from the motherboard manufacturers as they sell mobos with stupid default configurations just for the sake of publicity. I haven't found any official statement from Intel nor reports from PC media regarding defective CPUs due to premature degradation beside the Reddit posts you shared.

People that buys "Unlocked" K series processors need to know what they are buying and how to tweak it's OC settings. If people doesn't want to deal with this stuff they can purchase a non-K processor which is tuned by Intel itself and doesn't allow the motherboard to apply any OC settings.

I would stop telling people that their hardware is defective or to RMA their processors as it's most likely that those just only need to undervolt it to run at Intel's specifications.

[a.bortoletto]

Originally posted by VGShrine:

Originally posted by MrPlowjoy:

Because in my experience, the downclock requires more tweaking down over time. I've seen examples where it started at 53x and the most recent had to be 51x.

This is the problem. It's a degradation.

The degradation only happens if you run your processor at your motherboard default settings and it will accelerate if people run benchmarks with those settings very often. Also, the ratio configuration doesn't solve the problem, the Core Voltage need to be updated so it doesn't use the higher voltage from the Mobo default settings and keep the PL1/PL2 at Intel specified values to avoid throttling unless you have a really good cooling solution that allows you to run it at higher PL1/PL2 values.

As I mentioned in my previous reply, I don't think it's a processor defect and more negligence from the motherboard manufacturers as they sell mobos with stupid default configurations just for the sake of publicity. I haven't found any official statement from Intel nor reports from PC media regarding defective CPUs due to premature degradation beside the Reddit posts you shared.

People that buys "Unlocked" K series processors need to know what they are buying and how to tweak it's OC settings. If people doesn't want to deal with this stuff they can purchase an F processor which is tuned by Intel itself and doesn't allow the motherboard to apply any OC settings.

I would stop telling people that their hardware is defective or to RMA their processors as it's most likely that those just only need to undervolt it to run at Intel's specifications.

On my Apex Z790 Encore with 14900k I have MCE set: Disabled, Enforce All Limits and it runs according to Intel specifications of 243W max.

As for frequencies, I keep the CPU at stock and a voltage of 1.31V.

The compilation of shaders does not depend exclusively on the CPU, but also on the type of memory support (m.2 is the best choice) and on the video card.

At the moment no problems with my games including Suicide Squad and TEKKEN 8

[THORGRIM]

hey i was just telling a guy about this issue with 13 series today ill link this to him. great write up man.

[Offence]

Originally posted by -=🗲Offence🗲=-:

Originally posted by 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.

Why RMA ? It's an easy fix to downlock to x54 and keep on truckin' , ain't no way im swapping to AMD and overheat on a latest 7950x for example.

It's time to face the music and wait for intel's next chips until then these are doing great , minus-plus the minor downlock.

My issues dissapeared completely after going to x54 and it's been months since then no issues at all. I highly highly doubt this will go down any further if it will this chip has 3 years warranty anywayz.

But thinking that we will have to downlock the chip further and further to make it operable is just doom posting.

Originally posted by a.bortoletto:

Originally posted by VGShrine:

The degradation only happens if you run your processor at your motherboard default settings and it will accelerate if people run benchmarks with those settings very often. Also, the ratio configuration doesn't solve the problem, the Core Voltage need to be updated so it doesn't use the higher voltage from the Mobo default settings and keep the PL1/PL2 at Intel specified values to avoid throttling unless you have a really good cooling solution that allows you to run it at higher PL1/PL2 values.

As I mentioned in my previous reply, I don't think it's a processor defect and more negligence from the motherboard manufacturers as they sell mobos with stupid default configurations just for the sake of publicity. I haven't found any official statement from Intel nor reports from PC media regarding defective CPUs due to premature degradation beside the Reddit posts you shared.

People that buys "Unlocked" K series processors need to know what they are buying and how to tweak it's OC settings. If people doesn't want to deal with this stuff they can purchase an F processor which is tuned by Intel itself and doesn't allow the motherboard to apply any OC settings.

I would stop telling people that their hardware is defective or to RMA their processors as it's most likely that those just only need to undervolt it to run at Intel's specifications.

On my Apex Z790 Encore with 14900k I have MCE set: Disabled, Enforce All Limits and it runs according to Intel specifications of 243W max.

As for frequencies, I keep the CPU at stock and a voltage of 1.31V.

The compilation of shaders does not depend exclusively on the CPU, but also on the type of memory support (m.2 is the best choice) and on the video card.

At the moment no problems with my games including Suicide Squad and TEKKEN 8

Give it a few months :)

[THORGRIM]

Originally posted by VGShrine:

Originally posted by MrPlowjoy:

Because in my experience, the downclock requires more tweaking down over time. I've seen examples where it started at 53x and the most recent had to be 51x.

This is the problem. It's a degradation.

The degradation only happens if you run your processor at your motherboard default settings and it will accelerate if people run benchmarks with those settings very often. Also, the ratio configuration doesn't solve the problem, the Core Voltage need to be updated so it doesn't use the higher voltage from the Mobo default settings and keep the PL1/PL2 at Intel specified values to avoid throttling unless you have a really good cooling solution that allows you to run it at higher PL1/PL2 values.

As I mentioned in my previous reply, I don't think it's a processor defect and more negligence from the motherboard manufacturers as they sell mobos with stupid default configurations just for the sake of publicity. I haven't found any official statement from Intel nor reports from PC media regarding defective CPUs due to premature degradation beside the Reddit posts you shared.

People that buys "Unlocked" K series processors need to know what they are buying and how to tweak it's OC settings. If people doesn't want to deal with this stuff they can purchase an F processor which is tuned by Intel itself and doesn't allow the motherboard to apply any OC settings.

I would stop telling people that their hardware is defective or to RMA their processors as it's most likely that those just only need to undervolt it to run at Intel's specifications.

the f also has this problem