The “Out of Video Memory using direct X storage” message in Hogwarts Legacy is not a generic hardware limitation warning. It is a UE4.27 engine-level assertion that fires when the game’s texture streaming pool cannot secure contiguous VRAM blocks for the DirectStorage decompression pipeline. In practice, this means the error triggers before your GPU actually runs out of memory on paper. The engine fails to allocate a specific address range it expects, often because another process fragments the pool or because the shader cache on disk is stale enough that the streaming budget calculation produces an invalid value.
- Likely Causes
- Fix 1: Delete the DirectStorage Shader Cache
- Fix 2: Close VRAM-Consuming Background Processes
- Fix 3: Lower Texture Quality and Streaming Pool Size
- Fix 4: Add Launch Arguments to the Epic Games Launcher
- Fix 5: Disable WDDM Graphics Compression
- Fix 6: Clean Reinstall GPU Driver
- Fix 7: Reset VRAM Clocks to Stock
- If Nothing Works
- FAQ
Players with 8 GB and even 12 GB of VRAM report the crash, which tells you this is rarely a raw capacity problem. It is a memory management conflict between the engine’s virtual texture system, Windows display driver model (WDDM) memory compression, and whatever else is holding a footprint on your GPU. Here is how to isolate and resolve it.
Quick answer: Our top pick in 2026 is the DirectStorage shader cache corruption — our #1 rated choice. See the full ranked comparison, alternatives and buying advice below.
Likely Causes
| Cause | How to Confirm | Fix Difficulty |
|---|---|---|
| DirectStorage shader cache corruption | Error string contains “direct X storage”; deleting the cache folder resolves the crash on next launch | Easy |
| Background processes consuming VRAM (Discord overlay, browser hardware acceleration, RGB software) | Open Task Manager, sort by GPU column; any non-game process above 200 MB is suspect | Easy |
| WDDM memory compression conflict on Windows 10/11 | Disable the registry key HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers and the error changes behavior or disappears | Moderate |
| VRAM allocation exceeding physical limit due to texture quality setting | GPU-Z shows VRAM usage pinned near maximum before crash; lowering Texture Quality from Ultra to High resolves it | Easy |
| Epic Games Launcher pre-allocating memory or overlay interfering | Error persists in DX12 mode but vanishes when launched with -noverify or -skipbuildcheck added to launch arguments | Easy |
| GPU driver using an incompatible profile for UE4 titles | Clean reinstall with DDU followed by the Studio driver (NVIDIA) or Adrenalin optional profile (AMD) changes the outcome | Moderate |
| Page file disabled or set too small | Virtual memory settings show “No paging file”; re-enabling system-managed page file allows the engine’s spillover path to work | Easy |
| Overclocked VRAM or GPU core causing allocation errors | Error disappears after resetting clocks via MSI Afterburner or AMD Adrenalin | Moderate |
Fix 1: Delete the DirectStorage Shader Cache
How to check
Navigate to %localappdata%\HogwartsLegacy\Saved\Config\Windows\ and look for folders named DirectStorage or files matching *.ushaderbytecode. Also check %localappdata%\HogwartsLegacy\Saved\Shaders\. If these directories exist and the game was recently patched or you changed GPU drivers since they were created, they are the prime suspect.
What to do
Close the game and any launcher. Delete the entire Shaders folder and any DirectStorage subfolder inside Saved\Config\Windows\. Relaunch Hogwarts Legacy. The game will recompile shaders on first boot, which may take 3 to 5 minutes of black-screen loading. This is normal.
How to undo it
There is nothing to undo. The engine regenerates these files automatically. If you want a safety net, copy the folders to your desktop before deleting them rather than removing them permanently.
Fix 2: Close VRAM-Consuming Background Processes
How to check
Open Task Manager with Ctrl+Shift+Esc, switch to the Details tab, right-click the column headers, and enable the “GPU” column. Sort descending. Note any process consuming more than 150 MB of GPU memory while the game is running.
What to do
Common offenders are Discord (GPU column shows 80 to 300 MB with overlay active), web browsers with hardware acceleration enabled, MSI Afterburner OSD, and RGB utilities like iCUE or Armory Crate. For Discord specifically, go to Settings, Game Overlay, and toggle off “Enable in-game overlay.” For browsers, disable hardware acceleration in their respective settings pages. For RGB software, exit the application entirely rather than minimizing to tray.
How to undo it
Re-enable overlay or hardware acceleration after confirming the game runs stable. If it crashes again with those features active, you have identified your constraint.
Fix 3: Lower Texture Quality and Streaming Pool Size
How to check
Open GPU-Z or the NVIDIA Control Panel’s on-screen monitor and observe VRAM usage during gameplay. If it reaches above 95 percent of your card’s total capacity before the crash, texture streaming is your bottleneck.
What to do
In-game, navigate to Settings, Video, and change Texture Quality from Ultra to High. Then open Engine.ini at %localappdata%\HogwartsLegacy\Saved\Config\Windows\Engine.ini with Notepad. Add the following lines under [SystemSettings]:
TextureStreamingPoolDimPercent=0
r.Streaming.UseAsyncLoading=0
These force the streaming pool to use synchronous loading, which reduces the peak VRAM footprint at the cost of slightly longer load times between areas.
How to undo it
Remove the two lines from Engine.ini and restore Texture Quality to your preferred setting.
Fix 4: Add Launch Arguments to the Epic Games Launcher
How to check
Open Epic Games Launcher, go to your Library, find Hogwarts Legacy, click the three-dot menu, and select Manage. The “Additional Command Line Arguments” field should be empty or contain only default flags.
What to do
In that field, enter: -dx12 -noverify -NoSteamController. The first flag locks the game to DirectX 12 mode explicitly (UE4 sometimes defaults to a hybrid path). The second skips the launcher’s integrity check that can hold a memory reference. Save and relaunch.
How to undo it
Delete the arguments and restart the launcher.
Fix 5: Disable WDDM Graphics Compression
How to check
Open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers. Look for a DWORD named HwSchMode. If it is set to 2 (WDDM 3.0), compression is active.
What to do
Change HwSchMode to 1 to force WDDM 2.0. Reboot. This disables the OS-level memory compression that UE4.27’s DirectStorage path does not handle well. You may notice a small performance change in other games.
How to undo it
Set HwSchMode back to 2 and reboot.
Fix 6: Clean Reinstall GPU Driver
How to check
If previous fixes did not resolve the error and your driver is older than the game’s latest patch or you have run multiple driver updates in place, residual configuration files may conflict.
What to do
Download Display Driver Uninstaller (DDU). Boot into Safe Mode. Run DDU and select “Clean and Restart.” After reboot, install the latest NVIDIA Game Ready or AMD Adrenalin driver. Do not restore previous driver settings from any tool. Launch the game and test.
How to undo it
Not reversible without another DDU cycle. Keep the installer file handy.
Fix 7: Reset VRAM Clocks to Stock
How to check
Open MSI Afterburner or AMD Adrenalin. If the memory clock offset is anything above +200 MHz or you are running a factory-overclocked card with an aggressive BIOS profile, this is relevant.
What to do
Set all sliders to default (zero offset). Apply. If the error vanishes, you have a memory timing sensitivity issue specific to this engine’s allocation pattern.
How to undo it
Restore your previous offsets once the game is updated or a patch addresses the allocation bug.
If Nothing Works
At this point in 2026, the remaining options are: verify game file integrity through the Epic launcher’s “Verify” button under Manage; install the game on an NVMe drive rather than a SATA SSD (the DirectStorage path has known edge-case bugs on slower storage); or switch to DX11 mode by adding -dx11 instead of -dx12, which bypasses the DirectStorage allocator entirely at the cost of losing hardware-accelerated ray tracing. If none of these help, your GPU may have a physical VRAM defect that manifests only under UE4’s specific allocation pattern, which is rare but not unheard of.
FAQ
Do I actually need more than 8 GB of VRAM to play Hogwarts Legacy?
No. The official minimum is 4 GB and most players with 8 GB cards run the game without errors after applying the fixes above. The “Out of Video Memory” label is misleading because the engine is reporting a failed allocation, not a full pool.
Why does the error mention “direct X storage” specifically?
That is the name of the UE4 module (FDirectStorageAsyncRead) that handles compressed texture decompression on the GPU. When the allocator fails, the assertion prints the module name regardless of whether the root cause is actually storage-related.
Can I fix this without editing Engine.ini?
Yes, if the cause is a background process or driver issue. The Engine.ini edits are specifically for cases where the streaming pool size calculation itself is the problem, which tends to happen on cards with exactly 6 or 8 GB VRAM at Ultra texture settings.
Will a future game patch remove the need for these fixes?
Avalanche Software patched the DirectStorage assertion path in an update that shipped shortly after launch, but the underlying streaming behavior remains sensitive to system configuration. Some fixes are still necessary depending on your hardware combination.
Ready to decide? Our #1 pick for 2026 is the DirectStorage shader cache corruption.
Live price & availability on Amazon.
