The "Out of video memory" error isn't always VRAM: How to check and fix it

¿The “Out of video memory” error is not always a lack of VRAM? If you've encountered the "Out of video memory" message while launching a game and thought it was due to a lack of VRAM, you're not alone. That diagnosis is tempting but incomplete.: In many cases, the problem is not the available video memory, but rather how the game compiles shaders, system compatibility, drivers… and even CPU instability.

For example, a real case with Marvel Rivals: the error appeared while compiling the shaders at startup, on a very high-end computer with an i9-14900K and an RTX 4090. With that configuration, VRAM was not exactly the bottleneck.The effective solution wasn't lowering frequencies or cutting graphics, but rather a small trick with Windows compatibility that allowed the shader compilation to complete and the game to play normally.

What "Out of video memory" really means and why it pops up even if you have plenty of VRAM

The message suggests that the GPU has run out of video memory, but in practice it is often a generic error condition that is triggered by other causes. During shader compilation the game allocates and releases resources at full speed., and any conflict with the Windows graphics subsystem, drivers, shader cache, or even general system stability can lead to that warning.

In titles that preload or rebuild shaders on first boot after each patch, A small stumble at that stage can break the process with messages that look like VRAM. If you're also using modern hardware with features like Resizable BAR or 4G decoding, the interaction between BIOS, drivers, and the game—and how the iGPU and the dedicated one fight— can influence how those resources are managed.

How to tell if the problem isn't VRAM: clear signs

There are patterns that suggest it is not a lack of video memory. If the error appears exactly while "compiling shaders" at startup, is a first clue. If you're using a high-end RTX and the game crashes before displaying the 3D scene, that's another. And if the symptoms are accompanied by minor system instabilities, it's even clearer.

Over the past few months, some users with 13th and 14th generation Intel processors have described a number of symptoms that they mistake for GPU issues. The famous "Out of video memory" may appear along with micro-stops, visible stuttering or FPS drops in games with Unreal Engine, and have nothing to do with VRAM as such.

Other signs that have been seen on affected computers include Memory read/write error messages when opening apps (e.g. trying to launch OBS while running Destiny 2), unexpected shutdowns due to alleged memory failures, and sporadic system crashes that point to general memory management, not the graphics card.

If you use a USB DAC like Focusrite Scarlett Solo and listen randomly distorted audio, can be another instability issue that pollutes the Windows audio buffer. In these cases, increasing the buffer size to 512 or more is often a stopgap while the underlying cause is addressed.

Even when browsing, some report that in Chrome or Chromium-based browsers the warning "This page has a problem" appears with the code "STATUS_ACCESS_VIOLATION"That error smacks of failed memory accesses or data corruption in transit; again, the pattern is related to the CPU/IO, not a full VRAM.

Quick fix that works in Marvel Rivals: Enable Windows 8 compatibility to compile shaders

In Marvel Rivals there is a very effective method to bypass the error during compilation, without touching frequencies or degrading your gaming settingsThe idea is to temporarily force Windows 8 compatibility mode for the game executable, let it complete the shader compilation, and then disable compatibility to play with normal performance.

Guidelines (with Steam): Open your Library, right-click on the game, and go to “Manage > Browse Local Files.”In the game folder, locate the main executable (the .exe file that launches the game). Open its Properties and go to the Compatibility tab.

Under Compatibility, check "Run this program in compatibility mode for:" and select Windows 8. Apply the changes. Start the game and wait for the shader compilation to complete; don't close it prematurely. This step is key to prevent the error from appearing..

When the compilation is complete, close the game. Go back to the executable's Properties, go to Compatibility, and uncheck the box to return to normal mode. Apply and launch the game again. From here, the game should start normally.

Keep in mind two nuances: Compatibility mode may penalize performance, which is why it's not a good idea to leave it permanently. And after each patch that requires recompiling shaders, you may need to repeat the process to avoid the initial stumbling block.

Other useful measures: shader cache, drivers and file verification

In addition to the compatibility trick, there are general settings that can help. In the NVIDIA Control Panel, under Global Settings, check the shader cache size parameterSetting it to a value appropriate for your storage can reduce unnecessary rebuilds and prevent cache corruption. It's not a magic bullet, but it helps prevent silly bottlenecks.

It is also convenient update to the latest GPU drivers and, in the game client itself, verify file integrity. Any file corruption during the last update may manifest itself just as the game attempts to compile or load shaders.

Advanced Measures with Risk Warning: BIOS Update and Platform Settings

Some users have gone a step further and addressed the issue from within the platform. Updating your motherboard BIOS can stabilize your build workflow., optimize PCIe/ResBar management, and resolve awkward firmware-driver interactions. It does require some care, though.

First of all: This requires technical knowledge and carries riskIf you don't feel comfortable, it's best to ask for help or avoid it. If you continue, the typical steps are:

• Identify the exact model of your motherboard and go to the manufacturer's website.
• Download the latest BIOS version and, if it comes compressed, extract the file.
• Enter the BIOS/UEFI interface (usually with Del or F2 at startup).
• Back up your custom settings (XMP, CPU/DRAM overclocking, etc.) Some BIOSes (e.g. Asus) allow saving profiles.
• Use the flashing tool integrated (EZ Flash, M-Flash, Q-Flash…) and points to the file.
• During the update, Do not touch the PC or turn it offA power outage in the middle of the process can render the board unusable.
• After restarting, check that they are modern features enabled if your GPU uses them: Resizable BAR and 4G decoding.
• If your cooling system is falling short, consider learning how to How to force the GPU fan without additional software or disable Intel Adaptive Boost Technology to avoid unnecessary thermal spikes.

After updating, save, reboot, and test. In one documented case, BIOS update ended up being the permanent solution the problem, after weeks of resorting to compatibility mode. What's more, months later it was confirmed again that the BIOS change had left the system stable.

When the GPU isn't the culprit: Symptoms of instability on Intel 13th/14th gen

A worrying failure rate has been observed on some 13th and 14th generation Intel CPUs. What is relevant here are the symptoms, because many are mixed with games and graphics and can be confused with VRAM. Look for these signs:

• The classic warning of "No video memory" which sometimes appears, even on computers with top-of-the-range GPUs.
• Stuttering or micro-stutter, one-second hiccups and FPS drops (more visible in titles with Unreal Engine).
• Emerging from memory reading/writing when opening apps (example: OBS while running Destiny 2), crashes or freezes due to alleged memory errors.
• Audio very distorted on USB DACs like Focusrite Scarlett Solo. Mitigable by increasing the buffer to 512 or more, but it is a symptom of system instability.
• In Chromium browsers, hang with «STATUS_ACCESS_VIOLATION» which point to memory access/management issues.
• Instability with XMP profiles assets even if the RAM is capable of those speeds.

There are major signs that should put you on red alert. If you see the BIOS message upon booting up, “USB over current protection”, don't ignore it: the IO subsystem is part of the CPU package and could indicate damage. If in doubt, detect which process prevents ejecting a USB It helps you rule out software conflicts. Another sign is booting into safe mode due to repeated crashes.

In the field of BSODs, pay attention to modules and recurring codes: ci.dll, wdf01000.sys, dxgkrnl.sys, wimfsf.sys; and codes such as PAGE_FAULT_IN_NONPAGED_AREA, EXCEPTION_ON_INVALID_STACK or DRIVER_OVERRAN_STACK_BUFFER. If you get into a screenshot loop, It is very likely that the CPU is KO and touch process RMA.

More clues: In the Event Viewer, check WHEA-Logger warningsTranslation Lookaside Buffer (TLB) or Internal Parity errors often indicate CPU degradation or corruption. And watch out for something more subtle: decompression errors in game tools and clients (Xbox dropping large installs during updates, GOG failing to patch while full downloads work). Even Windows Update can stumble on those diff and compression operations.

To finish the diagnosis, if you get into a BSOD loop and a Linux live USB doesn't boot either, and the Windows installer crashes with a BSOD, the combination is very bad: it usually means the problem is with the hardware, not the operating system. In that scenario, RMA as soon as possible.

Remember that the failure rate varies by CPU and motherboardOne case with an ASUS ROG STRIX Z790-A GAMING WIFI gave problems, while another ASRock Z790 worked without incident. Each platform is unique.

Recommended check steps before blaming VRAM

If you see “Out of video memory” in a game, resist the urge to turn everything down to minimum. Try this sequence of checks to isolate the cause:

• Launch the game and see if the error matches shader compilationIf so, apply the Windows 8 compatibility trick temporarily to complete the process.
• Update GPU drivers, verify game files and clear/rebuild the shader cache if the title allows it.
• At NVIDIA, check out the shader cache size in Global Settings. Avoid absurdly small sizes if you use a lot of modern titles.
• Check general stability: disable XMP and any overclock temporarily, and see if the problem goes away.
• Open Event Viewer and search for WHEA-Logger with TLB/Parity errors. If they appear, it indicates a bad CPU/IMC signal. To dig deeper, you can analyze Windows startup with BootTrace.
• Pay attention to BSOD codes and modules repeated (ci.dll, dxgkrnl, etc.). Repetition implies hardware or driver pattern.
• If you use USB DAC and listen broken audio, raise the buffer to 512+ as mitigation while you continue diagnosing.

After these tests, if the behavior is normalized with the complete compilation of shaders and with clean drivers, VRAM was probably not the problem.If it persists and major symptoms appear, consider taking action on the platform (BIOS) or the RMA.

Notes and user experiences: Compatibility vs. BIOS

In the cited case of Marvel Rivals with i9‑14900K + RTX 4090, the flow was clear: Enable Windows 8 compatibility for build-only purposes, then disable it and play normally. This routine was effective for weeks and after several patches, repeating it whenever the game required a recompile.

Over time, it was proven that update the motherboard BIOS and the problem disappeared for good. Months later (July 9, 2025), it was confirmed that this update kept the system stable in Marvel Rivals and other applications. Moraleja: Compatibility mode is a useful bypass, the BIOS fixes root when the source is on the platform.

Best practices for keeping shader scares at bay

To minimize shader compilations from ruining your startup, take care of these details: Don't close the compilation process halfway When the game tells you it's working, let it finish even if it takes longer than you'd like.

Avoid having aggressive tools open during the first boot after a big patch: Recorders, overlays, and apps that inject hooks may interfere. If you need OBS, wait until the game is stable before launching it.

If your storage is tight or fragmented, consider free up space and defragment HDD (if the game is running mechanically) or, on an SSD, leave enough headroom for the shader cache. The cache needs room to breathe.

Check that the BIOS settings are activated consistent platform options with your GPU (Resizable BAR / 4G Decoding) and no unstable undervolts/overclocks. A system that appears "stable" on desktop can become unstable when compiling thousands of shaders.

When to ask for help or initiate an RMA

If after applying the compatibility trick, updating drivers, verifying files and even update BIOS If you keep seeing BSOD loops, WHEA errors, “USB over current protection” message, or unable to boot Linux/Windows installation, don’t waste time: open an RMA.

Document with screenshots the error codes, note the modules that appear in the BSOD and describe reproducible steps (e.g., "crashes when compiling shaders"). This information helps support understand that it's not just a graphical tweak.

A game spitting out "Out of video memory" doesn't always mean you're running out of VRAM; sometimes it's the indicator of another fever. If the error appears in the middle of compiling shadersThe temporary Windows 8 compatibility solution allows you to complete the process and play normally, and when combined with up-to-date drivers, a well-sized shader cache, and verified files, it reduces recurrences. When micropauses, memory errors when launching apps, browser freezes with "STATUS_ACCESS_VIOLATION," distortion in USB DACs, WHEA-Logger with TLB/Parity, repeated BSODs with modules like dxgkrnl or ci.dll, or even "USB over current protection" messages also appear, the clue points to platform instability (commonly seen on certain 13th/14th gen Intel systems). In such cases, a smart BIOS update may be the ultimate remedy.If that doesn't work, it's time for RMA. In the meantime, don't underestimate the value of letting the game compile its shaders alone: ​​sometimes, the "miracle" is as simple as that.

Related article:

Why Windows doesn't free up VRAM even when you close games: real causes and how to fix them

Cristian Garcia

Passionate about technology since he was little. I love being up to date in the sector and, above all, communicating it. That is why I have been dedicated to communication on technology and video game websites for many years. You can find me writing about Android, Windows, MacOS, iOS, Nintendo or any other related topic that comes to mind.