Nightingale

Nightingale

View Stats:
MrPlowjoy Feb 20 @ 11:19am
2
To everyone experiencing shader compilation "Out of video memory trying to allocate a rendering resource" errors
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.
< >
Showing 1-15 of 20 comments
Arc Feb 20 @ 11:26am 
Here's official RAD response to this with fixes depending on HW configs:
https://www.radgametools.com/oodleintel.htm
MrPlowjoy Feb 20 @ 11:45am 
Originally posted by Arc:
Here's official RAD response to this with fixes depending on HW configs:
https://www.radgametools.com/oodleintel.htm

Its the first time I've seen that. Excellent breakdown and very, very useful information.
I´m having the exact same issues with my 13900KS and Asus ROG Strix z790-F with newest Bios, Win 11, DDR5 7200 MHz Ram, RTX 4090. No OC just all limits removed. Started having issues with WHEA Logger warnings in event Manager after 2-3 months. Then just random but rare CTD. Spiderman Remastered crashes often and I can reproduce the crash by fast traveling. Now I´m also having crashes in shader comp steps in Unreal Games. Underclocked from x56 to x54 and it works... for now.
Arc Feb 21 @ 3:23am 
Originally posted by Robspassion:
...No OC just all limits removed...
Note that removing power and other limits IS part of overclocking, and it's not "just" a minor thing either, it's pretty significant part of overclocking.
Thanks for posting this it definitely needs to be more well known. I myself have dealt with this since release. 2 faulty i9 13000k processors one stock and one with lowered limits and I’m now 5 months into my 13700k with no issues. Intel need to step up and isolate this issue as it is very widespread but still unknown to many.
PC Secs at the bottom.

This is the info I was looking for for a few weeks now and it came up in my google feed on my phone this morning. I've been scratching my head while hitting it on a door. I just bought this PC in mid December and built in on New Years night. As for installing all my game and then running them went just fine that first week. Then I got the driver update and after I launched Call of Duty MWIII or CoD HQ and the Pre-load shaders locked up my PC completely. No Control at all. But on my other PC next to me I saw that the PC disconnected from network via steam net sharing. It's getting worse and worse. The second time it happen I lost the use of my keyboard but the mouse still worked. Then the third time or third driver update caused not only my keyboard to not work but also my sound card. The only way to fix the sound card was to shut down the PC but keep the PSU on and unplug the sound card and plug it back in and the sound worked the keyboard was just unplugging them and plugging them back in. As for now I installed the 0904 bios update on my Z790 Dark Hero and ran Time Spy and it CTD during the second frame time run and then I ran it again right away and it passed through. I haven't tried Call of Duty yet since I just downloaded the new driver just an hour ago. I'm just waiting to install a reset switch since it's not on my PC case and go through the BIOS and set the fail safe and turn down the power from 4096W to something that wont run a city. (side note: I was talking to a friend and a basic electronics company with all the SMT machines and Wave solder machines and solder irons and it's the size of a small Wal Mart only pulls 1600 amps and my motherboard defults to 4096 AMPS... WTF lol).

SPECS:
i9 14900K
ASUS Z790 Dark Hero
ASUS Strix RTX 4090
Corsiar Vengence 64GB 6400MHz
Creative AE-7
Samsung 990 pro
Last edited by Feeterican; Feb 22 @ 3:28pm
dlmyth Feb 22 @ 4:10pm 
Thanks for the information.
Originally posted by 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.

Add me to the list. Went all over the internet spreading the news about this; no-one would believe me.

This is really going to bite MS hard when they release MSFS2024, as they are insisting on DX12 only for it.

Intel owes us all a new CPU which doesn’t degrade. PC board manufacturers need to officially note this for all users of their product, and provide updated BIOSes that respect the official PL1 and PL2 power limits.

This is an outrage. I spent many months of valuable time chasing this with no decisive way to identify and determine the problem.

I finally came up with the XTU down clock solution, which is just a hack when all the tools and benchmarking and built in optimizations, even just using XMP! are pointing in the opposite direction.

I consider this a collective industry engineering failure. At least no-one got sucked out of a hole blown on a cabin at high altitude due to some loose bolts, but this is far more widespread and potentially consequential.
SQUUUUZE Feb 27 @ 12:22pm 
This affects 14900k as well. Same exact pattern you described with a slow burn to the CPU. Crash here and there and then all of a sudden no game would launch for me and I was getting the "out of memory" errors. Ended up getting another 14900k. Had a ASUS Z690 Hero and used AI OC.
Mutharex Feb 27 @ 12:26pm 
Yeah it's a UE5 issue common to other games that run on that engine, Banishers, Lords of The Fallen etc
kan Mar 1 @ 7:19pm 
I had this exact issue a couple months after getting an i7-13700k and I hadn't see any info on it for months and months, all DirectX12 and Unreal Engine games wouldn't launch so I was forcing DirectX11 to play it.

Thank you for giving out this info, at least its a temporary fix for games that won't let me use DirectX 11, I set Intel XTU to 52x and it solved the issue at least for now with all the games I had issues with.
Last edited by kan; Mar 1 @ 7:21pm
Update: After updating the BIOS on my Z790 Dark Hero and setting the memory profile to XMP II, it made it through the Pre-Load Shaders in MW3. Before my memory profile was set on XMP I and MW3 would insta freeze and crash and burn. As for now it's working but that's not to say I launch a different game in the future and I end up having issues. This was also right after the Nvidia driver 551.61.

SPECS:
i9 14900K
ASUS Z790 Dark Hero
ASUS Strix RTX 4090
Corsiar Vengence 64GB 6400MHz
Creative AE-7
Samsung 990 pro
Originally posted by Feeterican:
Update: After updating the BIOS on my Z790 Dark Hero and setting the memory profile to XMP II, it made it through the Pre-Load Shaders in MW3. Before my memory profile was set on XMP I and MW3 would insta freeze and crash and burn. As for now it's working but that's not to say I launch a different game in the future and I end up having issues. This was also right after the Nvidia driver 551.61.

SPECS:
i9 14900K
ASUS Z790 Dark Hero
ASUS Strix RTX 4090
Corsiar Vengence 64GB 6400MHz
Creative AE-7
Samsung 990 pro

Yeah. sadly its not the XMP setting. You're on the cusp of the issues, likely the shader comp chose a different PCore to the one(s) failing this time around. It's just a matter of time.

There's a big thread over on Reddit that goes over BIOS-level changes to the CPU power max across a few settings. That's your best bet.
Originally posted by MrPlowjoy:

Yeah. sadly its not the XMP setting. You're on the cusp of the issues, likely the shader comp chose a different PCore to the one(s) failing this time around. It's just a matter of time.

There's a big thread over on Reddit that goes over BIOS-level changes to the CPU power max across a few settings. That's your best bet.

Can you link the Reddit thread or let me know what key words to look for?
Originally posted by Feeterican:
Originally posted by MrPlowjoy:

Yeah. sadly its not the XMP setting. You're on the cusp of the issues, likely the shader comp chose a different PCore to the one(s) failing this time around. It's just a matter of time.

There's a big thread over on Reddit that goes over BIOS-level changes to the CPU power max across a few settings. That's your best bet.

Can you link the Reddit thread or let me know what key words to look for?

https://www.reddit.com/r/overclocking/comments/1axepvu/optimizing_stability_for_intel_13900k_and_14900k/
< >
Showing 1-15 of 20 comments
Per page: 1530 50