How to Fix Hogwarts Legacy Out of Video Memory Error (2026 VRAM Guide)

The “Out of Video Memory” error in Hogwarts Legacy almost always means the game is asking your GPU for more VRAM than it has free at that moment, not that your hardware is genuinely incapable of running the game. The two fixes that resolve it for the vast majority of players are dropping the Texture Quality setting one notch below what the in-game menu auto-selects, and clearing the DirectX 12 shader cache. Everything else on this list targets edge cases where those two fixes alone are not enough.

Hogwarts Legacy was built on a modified Unreal Engine 4 with aggressive texture streaming, and it has a well-documented habit of over-reporting the VRAM it actually needs. Avalanche Software patched the worst of the memory leaks in the 2023 updates (notably the April 2023 “Patch 4” and later DLC-era builds), but the engine still crashes with an Out of Video Memory dialog whenever the texture streamer fails to evict older assets in time. The fixes below target that specific failure mode, in order of how often they work.

Quick Reference: What Fixes This Error

Before you work through each fix, scan the table. The first two rows solve the error for roughly 80 percent of players. Anything lower down is worth trying only if the ones above did not stick.

Fix	Time to apply	How often it works
Drop Texture Quality to Medium (or one notch lower than recommended)	30 seconds	Very high
Delete the DirectX shader cache folder	2 minutes	High
Update to the latest NVIDIA or AMD driver	10 minutes	High on newer GPUs
Disable ray tracing and Frame Generation	30 seconds	High on 8 GB cards
Cap framerate at 60 fps	30 seconds	Medium
Close browsers and overlay apps that hold VRAM	1 minute	Medium
Increase Windows paging file	3 minutes	Low to medium
Edit Engine.ini streaming pool size	5 minutes	Last resort

Fix 1: Drop Texture Quality One Notch

The in-game Auto preset consistently picks a Texture Quality that is too high for the card it detects, especially on 6 GB and 8 GB GPUs like the RTX 3060, RTX 3070, RTX 4060, and RX 6600. Open Settings → Display → Graphics and set Texture Quality to Medium. If you are on an 8 GB card and want to keep textures on High, pair it with DLSS Quality or FSR Quality upscaling so the render buffer takes less memory.

Texture Quality is the single largest VRAM consumer in this game. Dropping from High to Medium typically frees 1.2 to 1.8 GB of VRAM at 1440p. Shadow Quality is the second biggest offender; set it to Medium as well if you are still crashing.

Fix 2: Clear the DirectX 12 Shader Cache

Hogwarts Legacy compiles DirectX 12 shaders on first launch and after every driver update. When the cache gets corrupted, the game sometimes tries to reload every shader into VRAM at once and triggers the Out of Video Memory error on entering the Floo Flame network or loading Hogsmeade. Clearing the cache forces a clean recompile.

On NVIDIA hardware, open File Explorer and paste this path into the address bar:

%localappdata%\NVIDIA\DXCache

Delete everything inside that folder. Also clear:

%localappdata%\NVIDIA\GLCache

On AMD systems, delete the contents of:

%localappdata%\AMD\DxCache and %localappdata%\AMD\GLCache

Then launch Hogwarts Legacy and let it sit on the first loading screen for two to three minutes while it rebuilds shaders. Do not tab out. Tabbing out during shader compilation is another documented trigger for this exact crash.

Fix 3: Update Your GPU Driver to the Current 2026 Build

NVIDIA and AMD have both shipped driver branches that specifically call out Hogwarts Legacy memory handling in their release notes. On NVIDIA, any Game Ready Driver dated after the 546 branch fixes the original VRAM leak on RTX 30- and 40-series cards. On AMD, Adrenalin 24.3.1 and newer resolves the related streaming stall on RX 6000 and RX 7000 cards.

Open GeForce Experience or the NVIDIA app (NVIDIA’s 2024 replacement for GeForce Experience) and check for updates, or go to nvidia.com/drivers and download the latest Game Ready Driver. AMD users should open the Adrenalin software and use Settings → System → Check for Updates. When you install, choose the Custom → Clean Install option; a stale driver residue is itself a common cause of VRAM mis-reporting.

Do not use driver cleaner utilities unless the clean install option fails. DDU (Display Driver Uninstaller) in safe mode is only needed if you see the Code 43 device error in Device Manager alongside the video memory crash.

Fix 4: Turn Off Ray Tracing and Frame Generation on 8 GB and Smaller Cards

Ray-traced reflections, shadows, and ambient occlusion each add between 400 and 800 MB of VRAM overhead at 1440p. Frame Generation, whether NVIDIA DLSS 3/3.5 or AMD FSR 3, holds two frames of data in the GPU’s framebuffer at once and can add another 600 MB to 1 GB.

In Settings → Display → Graphics, set Ray Tracing to Off and set Frame Generation to Off. Keep regular upscaling (DLSS Super Resolution or FSR) on Quality, as these reduce VRAM use rather than add to it. The result on an 8 GB card is typically a 1.5 to 2.5 GB drop in VRAM usage and the disappearance of the Out of Video Memory error on the spot.

Fix 5: Cap Framerate at 60 fps

An uncapped framerate lets the engine queue more texture requests per second than a capped one, which inflates peak VRAM use during fast-traversal scenes (broom flight over the castle, Hogsmeade pan shots, Floo Flame transitions). Capping solves the peak without touching the average.

In-game: Settings → Display → Graphics → Frame Rate → 60. If the in-game cap does not hold, use the NVIDIA Control Panel Max Frame Rate per-app setting or, on AMD, Radeon Chill with a 60 fps target. On variable refresh displays, 60 fps is still below a typical 144 Hz panel’s ceiling and remains smooth.

Fix 6: Close Background Apps That Hold VRAM

These specific programs are repeat offenders for pinning VRAM while the game is running, and quitting them before launch often fixes the crash on cards near their memory limit:

Chrome and Edge with hardware acceleration on can hold 500 MB to 1.2 GB of VRAM even in the background. Quit them fully; closing the window is not enough on Windows. Use Task Manager to verify no browser processes remain.

Discord with its overlay on reserves VRAM for its in-game UI. Disable the Discord Overlay in Settings → Game Overlay.

OBS Studio, NVIDIA ShadowPlay, AMD ReLive, and the Xbox Game Bar all allocate an encoder framebuffer from VRAM. Turn off any you are not actively using. Xbox Game Bar: Windows Settings → Gaming → Xbox Game Bar → toggle off.

MSI Afterburner with RivaTuner Statistics Server is fine, but its on-screen display should be set to “Text only” rather than graph mode, which itself draws a small VRAM buffer.

Fix 7: Increase the Windows Paging File

Windows will spill texture data to the pagefile on the system drive when VRAM runs out. If your pagefile is fixed too small, that spill fails and you get the crash dialog rather than a frame-rate dip. Setting the pagefile to “System managed” on the fastest SSD in your system gives Windows the room it needs.

Press Windows key + R, type sysdm.cpl, and press Enter. Go to Advanced → Performance → Settings → Advanced → Change. Uncheck “Automatically manage paging file size for all drives,” select your primary SSD, choose “System managed size,” click Set, then OK, and reboot.

On a 16 GB RAM system with a 500 GB SSD, Windows will typically allocate around 24 GB of pagefile. That is normal and not a sign that you need more RAM; it is simply giving the streamer somewhere to spill.

Fix 8: Verify Integrity of Game Files

A corrupted .pak file in the game’s content folder can cause the engine to reload the same asset repeatedly, inflating VRAM use until the crash. Every storefront has a verify path:

Steam: Library → right-click Hogwarts Legacy → Properties → Installed Files → Verify integrity of game files.

Epic Games Store: Library → three-dot menu on Hogwarts Legacy → Manage → Verify.

GOG Galaxy: Library → Hogwarts Legacy → Settings gear → Manage installation → Verify / Repair.

Xbox / Microsoft Store app: Library → Hogwarts Legacy → three dots → Modify → Repair.

Let the verification complete; depending on disk speed it takes five to twenty minutes for this game’s roughly 85 GB install.

Fix 9: Edit Engine.ini to Cap the Streaming Pool

This is a last-resort fix that is reliable on 6 GB cards. It caps how much VRAM the Unreal texture streamer will try to reserve, which forces the engine to recycle memory more aggressively at the cost of a slight pop-in near you in dense scenes.

Close the game. Open File Explorer and paste this path:

%localappdata%\Hogwarts Legacy\Saved\Config\WindowsNoEditor

Open Engine.ini in Notepad. Add these lines at the bottom:

[SystemSettings]
r.Streaming.PoolSize=3000
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.HLODStrategy=2

The number after PoolSize= is megabytes. Use 3000 for a 6 GB card, 5000 for an 8 GB card, and 7000 for a 10 GB card. Save, set the file to read-only (right-click → Properties → Read-only), and launch. The read-only flag stops the game from overwriting your edit on the next load.

Fix 10: Run Windows Update and DirectX Runtimes

Windows 11 version 24H2 and Windows 10 22H2 both shipped WDDM 3.2 memory management improvements that materially change how DirectX 12 games report VRAM. If you are behind on cumulative updates, the in-game memory check will mis-calculate available VRAM and fire the error on a card that has plenty free.

Settings → Windows Update → Check for updates. Install anything pending and reboot. Then download and run the Microsoft DirectX End-User Runtime Web Installer to refresh the shared DirectX components the game loads at startup.

When None of the Above Work

If you have applied every fix and the crash still occurs, the two remaining causes are almost always hardware:

GPU overclock instability. Reset your GPU to stock clocks in MSI Afterburner, AMD Adrenalin, or NVIDIA Performance Tuning. A factory overclock that is marginal under synthetic loads often fails under Hogwarts Legacy’s bursty memory access pattern.

Failing VRAM. Run OCCT’s VRAM test or MemTestG80 for thirty minutes. VRAM errors will show up as red pixels or test-specific error codes. If you see them, the card is genuinely failing and no software fix will help. Contact the card manufacturer for an RMA; most GPUs ship with a two- or three-year warranty, and both NVIDIA (1-800-797-6530) and AMD (1-877-284-1566) can route you to the correct board partner.

Bottom Line

The Hogwarts Legacy Out of Video Memory error is a VRAM budget problem, not a hardware death knell. On any card with 6 GB or more, dropping Texture Quality to Medium, clearing the shader cache, and updating to a 2024-or-later GPU driver resolves it for the overwhelming majority of players. Everything beyond Fix 3 is for unusual configurations: ray tracing on an 8 GB card, a corrupted game install, or an overclock that is no longer stable. Work the list top to bottom and stop the moment the error goes away.