The “Out of video memory” error on Core i9-13900K and i9-14900K systems is usually caused by CPU Vmin shift instability during shader decompression, not a lack of GPU VRAM. To fix it, update your motherboard BIOS to load microcode 0x12B or newer, enforce “Intel Default Settings” in your UEFI, and downclock your P-core multiplier by 1x–2x if physical silicon degradation has already begun.
The Paradox: Why a CPU Instability Triggers a Video Memory Crash
High-end rigs pairing an Intel Core i9-13900K or i9-14900K with an NVIDIA GeForce RTX 4080 or RTX 4090 frequently crash in Unreal Engine 5 games such as The Finals, S.T.A.L.K.E.R. 2, and Lords of the Fallen. The crash reporter explicitly cites an “Out of video memory trying to allocate a rendering resource” error or flags a DX12 shader decompression failure. On a GPU equipped with 16GB to 24GB of VRAM, this error is misleading because the graphics memory pool is rarely exhausted.
The issue occurs during the initial game launch and level loading phases when Unreal Engine offloads heavy asset decompression to the CPU via libraries like RAD Game Tools Oodle. When compressed shaders and rendering assets are unpacked across all available threads, the CPU experiences severe transient load spikes. If the processor calculates incorrect values during decompression due to clock duty cycle shifts, memory pointers corrupt and the engine’s DirectX 12 pipeline fails to allocate the requested resource, triggering a false VRAM exhaustion crash.
Genuine VRAM exhaustion can be ruled out by monitoring memory allocation in Windows Task Manager under the Performance tab. If your RTX 4080 or RTX 4090 shows gigabytes of free dedicated video memory at the moment of the crash, the failure is occurring inside the CPU execution pipeline.
The Root Cause Chain: Vmin Shift and Circuit Degradation
Intel confirmed that 13th and 14th Generation desktop processors suffer from a condition known as Vmin Shift Instability. The physical defect is localized to a clock tree circuit inside the IA core that is exceptionally vulnerable to accelerated aging under high voltage and elevated temperatures. Over time, electrical stress causes a duty cycle shift in the internal clock lines, requiring higher minimum voltages (Vmin) to remain stable at target boost frequencies.
Four operational factors combine to trigger this failure state:
- Uncapped Motherboard Power Profiles: Factory motherboard defaults frequently ignored Intel guidance, delivering extreme power targets and aggressive loadlines.
- eTVB Algorithm Bugs: Early microcode allowed high-frequency Thermal Velocity Boost states to engage even when operating near thermal maximums.
- SVID High-Voltage Requests: The CPU VID algorithm requested transient voltage spikes exceeding 1.55V during bursty single-threaded and multi-threaded transitions.
- Elevated Idle and Light-Load Voltages: Core voltage remained unnecessarily high during low-activity periods, degrading the clock tree even while the PC was relatively idle.
When the degraded clock tree encounters the multi-core decompression load of Unreal Engine 5, timing errors occur instantaneously. The engine interprets corrupted decompression streams as an unrecoverable graphics hardware error, closing the process immediately or generating a blue screen (BSOD).
Microcode updates prevent further voltage damage on healthy silicon, but they cannot reverse physical degradation that has already occurred. If your processor continues crashing on verified baseline BIOS settings, the chip has suffered permanent hardware degradation and must be replaced via warranty RMA.
Step-by-Step Fix and Stabilization Workflow
Follow these sequential diagnostic and remediation steps to stabilize your system and determine whether your processor requires replacement.
- Flash the Latest Motherboard BIOS: Download the latest UEFI release for your motherboard model from the manufacturer’s support portal. Ensure the release incorporates microcode revision 0x12B (or newer, such as 0x12F) to eliminate excessive SVID voltage requests during idle, light load, and eTVB boost scenarios.
- Enforce Intel Default Settings in BIOS: Enter your UEFI setup and select the “Intel Default Settings” profile (or set SVID Behavior to “Intel Fail Safe” / CPU Cooler Tuning to “Boxed Cooler 253W”). Ensure PL1 and PL2 limits are locked to factory guidance (typically 253W for i9-13900K and i9-14900K) rather than unlocked to 4096W, and verify ICCMAX is clamped.
- Test Stability with Intel Processor Diagnostic Tool: Boot into Windows and run the official Intel Processor Diagnostic Tool. Allow the utility to run its complete suite of stress tests to see if mathematical execution or cache errors flag an immediate hardware failure.
- Apply a Temporary P-Core Multiplier Reduction: If crashes persist during Unreal Engine shader compilation, install Intel Extreme Tuning Utility (XTU) or enter your BIOS to lower the Performance Core (P-Core) Ratio from 55x/57x down to 54x or 53x. Dropping the multiplier reduces the clock demand below the degraded Vmin threshold, serving as an immediate workaround to complete shader compilation.
- Initiate an Intel RMA Request: If the processor requires manual underclocking or undervolting below base factory specifications simply to avoid crashing in standard DX12 titles, contact Intel Customer Support. Intel extended the warranty coverage on 13th and 14th Gen boxed desktop processors by two years (totaling five years of coverage) to handle replacements for degraded units.
Intel Microcode Revisions and Targeted Fixes
Intel released a series of progressive microcode updates to resolve the various voltage vectors contributing to Raptor Lake degradation. Review the patch history below to verify your BIOS version includes the comprehensive fixes.
| Microcode Version | Release Date | Primary Technical Target | Impact on Unreal Engine Stability |
|---|---|---|---|
| 0x125 | June 2024 | Fixes eTVB algorithm running aggressive boost states at elevated core temperatures. | Reduces thermal-induced decompression crashes during long compilation runs. |
| 0x129 | August 2024 | Caps SVID voltage requests from exceeding 1.55V under standard operational loads. | Mitigates high-voltage spikes that accelerate physical silicon wear. |
| 0x12B | September 2024 | Encompasses 0x125/0x129 and eliminates elevated voltage requests during idle and light workloads. | Primary comprehensive fix preventing clock tree circuit degradation. |
| 0x12F | May 2025 | Refines voltage behavior for systems running continuously under multi-day low-activity states. | Targeted longevity fix for continuous-operation workstations and desktops. |
Ruling Out Engine-Side TDR and Allocation Bugs
While CPU Vmin instability causes the vast majority of these errors on Core i9 hardware, genuine GPU pipeline timeouts (TDR events) can trigger similar symptoms in developer builds and heavily modded titles.
When a GPU operation takes longer than the default Windows threshold (2 seconds), the OS resets the graphics driver, throwing DXGI_ERROR_DEVICE_HUNG or DXGI_ERROR_DEVICE_REMOVED. In development environments or unoptimized scenes with heavy hardware ray tracing, you can extend this timeout buffer via the Windows Registry.
- Open the Windows Run dialog (Win + R), type
regedit, and press Enter. - Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers. - Create two new DWORD (32-bit) values named
TdrDelayandTdrDdiDelay. - Set the base of both values to Decimal and enter
60to increase the driver timeout threshold from 2 seconds to 60 seconds. - Restart your PC to commit the driver scheduler parameters.
For project creators working inside the Unreal Editor, you can also force the engine’s texture streaming pool back to standard operational limits by opening the developer console (tilde key) and executing r.Streaming.PoolSize 1000. Adding the launch argument -gpucrashdebugging outputs detailed GPU state logs to [Your Project]/Saved/Logs.
Frequently Asked Questions
Why does the error message say I am out of video memory if my GPU is fine?
Unreal Engine uses the CPU to decompress assets before sending them to the graphics card. When an unstable CPU introduces silent data corruption during Oodle decompression, the engine’s DX12 rendering backend fails to allocate the corrupted resource descriptor and misinterprets the failure as a lack of available VRAM.
Does lowering the P-Core multiplier reduce game performance?
Lowering the P-Core ratio by 1x or 2x (e.g., from 55x to 53x) reduces peak CPU clock frequency by roughly 200–400 MHz. In 1440p and 4K gaming workloads, the performance impact is virtually unnoticeable because the system remains GPU-bound on an RTX 4080 or RTX 4090.
Are 12th Gen Intel CPUs or AMD Ryzen chips affected by this specific bug?
No. 12th Gen (Alder Lake) desktop CPUs, Intel Core Ultra mobile processors, and AMD Ryzen processors do not suffer from the Raptor Lake clock tree degradation issue. If a Ryzen or 12th Gen system encounters an “Out of video memory” crash, it is typically caused by true VRAM exhaustion or unstable system RAM overclocking.
Will updating to microcode 0x12B fix my CPU if it already crashes frequently?
Microcode updates only alter voltage algorithms to stop further degradation on healthy circuits; they cannot repair damaged silicon. If your Core i9 processor continues to throw decompression and memory errors after applying the 0x12B BIOS update, the CPU is permanently degraded and should be replaced through Intel’s warranty RMA process.