Black Myth: Wukong 'Out of Video Memory' Crash & Shader Compilation Fix
The 'Out of video memory trying to allocate a rendering resource' crash in Black Myth: Wukong primarily affects systems with high-end GPUs (RTX 4080/4090) paired with Intel 13th and 14th Gen Core i9/i7 processors during initial shader compilation, or systems with an inadequate Windows virtual memory paging file.
- ▸Lower Intel Performance Core Ratio from 55x to 53x/54x via Intel XTU or BIOS microcode update 0x12B
- ▸Manually expand Windows Virtual Memory Paging File to 16,384 MB - 32,768 MB on your fastest NVMe SSD
- ▸Add -dx11 to Steam Launch Options to bypass unstable DirectX 12 shader caching
Step-by-Step Resolution Steps
Click steps to track progressDownclock Intel 13th/14th Gen P-Cores to 53x / 54x (Intel XTU Fix)
Download official Intel Extreme Tuning Utility (XTU). Lower your 'Performance Core Ratio' by 1x or 2x (e.g. from 55x to 53x). This stops the OODLE decompression thread collision that tricks Windows into reporting an Out of Memory error during initial shader compilation.
Expand Windows Virtual Memory Pagefile (PowerShell)
Ensure Windows has ample committed virtual memory to handle Black Myth: Wukong's massive 130GB uncompressed asset stream. Run PowerShell as Administrator to expand the system paging file.
Set-CimInstance -Query 'Select * from Win32_PageFileSetting' -Property @{InitialSize = 16384; MaximumSize = 32768}Clear Corrupted Shader Cache & Launch with -dx11 Option
In Steam Library → Right-click Black Myth: Wukong → Properties → General → Launch Options. Type '-dx11' (without quotes). This forces fallback to the DirectX 11 API pipeline to bypass problematic DX12 shader locks.
Did these steps resolve your error?
Your feedback updates our verified fix telemetry for players worldwide.
32GB High-Speed DDR5 RAM Kit (6000MHz CL30)
Unreal Engine 5 titles require high memory bandwidth. Upgrade to 32GB DDR5 for zero memory hitching in Black Myth: Wukong.
Why Does This Error Happen?
Understanding the root cause prevents recurrence during competitive matches:
- 1Intel Core 13th/14th Gen CPU transient voltage/clock instability during Unreal Engine 5 OODLE shader decompression
- 2Windows Virtual Memory (Paging File) set too low or managed on a slow mechanical drive
- 3Corrupted DirectX 12 PSO (Pipeline State Object) shader cache in AppData
- 4Overclocked GPU VRAM or excessive power limit triggering DirectX device removal
Frequently Asked Questions (Out of Video Memory)
Why does it say Out of Video Memory when I have a 16GB or 24GB GPU?
Unreal Engine 5 throws a generic 'Out of Video Memory' error when memory allocation or shader decompression crashes midway through execution. On Intel 13th/14th Gen CPUs, this is caused by silicon microcode instability rather than a lack of physical VRAM.
Can I switch back to DirectX 12 after the shaders finish compiling?
Yes! Once you pass the opening prologue and the shaders are fully cached, you can remove '-dx11' from your launch options to re-enable Lumen ray tracing and DLSS Frame Generation.