How do you deal with VRAM filling up in Proton without tanking settings?

November 19, 2026 5 answers
Asked by quickParry.8R

Some games gradually use more VRAM until they hitch or the desktop locks up. A DXVK memory cap doesn't seem to hold, and a native Vulkan game ignores it. What should I try before dropping all the graphics settings?

Answers

mechGyro_7F

First check which renderer the game is actually using. DXVK handles Direct3D 9, 10 and 11, while Direct3D 12 generally goes through VKD3D-Proton. A native Vulkan renderer bypasses DXVK, so a dxvk.conf setting won't control it.

Also, dxgi.maxDeviceMemory is not a hard VRAM limit. It changes the amount of memory reported to the game, but the game and driver can still allocate beyond that number. Treat it as something to test, not a safety fence for the desktop.

quickParry.8R:

That explains why the cap didn't do anything for the Vulkan renderer. I'll check each game's renderer before changing more config.

Reply to this answer
whiffMeterBySundial

For a Direct3D 12 game, you could test VKD3D_CONFIG=force_host_cached as a launch environment variable. One report on an NVIDIA card found lower VRAM allocation and better eviction with it, including in path-traced games.

That's a useful lead, not a general fix for every card or game. Compare the same locations and settings with and without it, and watch for performance changes. It won't help a game using DXVK or a native Vulkan renderer.

Reply to this answer
P2airdashByMug

Don't assume a rising counter proves a leak. Games can cache assets, and tools may report allocation, usage, or available memory differently. Those numbers aren't necessarily measuring the same thing.

Try a repeatable route, then return to the same spot and compare the readings after a similar amount of time. Note whether performance recovers as well as whether the number falls. It won't prove exactly what's happening, but it gives you a much better comparison when testing changes.

Reply to this answer
DOSdaydream

If the whole desktop can freeze, leave some VRAM headroom rather than relying on a reported cap. Closing GPU-using apps may help. If that's not enough, try reducing texture quality or other memory-heavy settings one step at a time instead of lowering everything.

For recovery, check whether Magic SysRq is enabled before testing. If the display is attached to the same GPU, a desktop lockup may also make a local terminal inaccessible. None of this guarantees you'll avoid a driver lockup, but it can make experiments less painful.

Reply to this answer
kartApex~Wide

Changing renderers is worth a controlled test, but don't assume Direct3D 12 will be more stable than Vulkan. If it crashes, note the driver, Proton version, renderer and settings, then change one thing at a time. A reproducible crash or freeze report is more useful than a pile of config tweaks.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions