Is Your Game Running Out of VRAM? Compare Memory and Stutter

Choose your symptom

• Dedicated memory is nearly full and movement stutters — Compare texture quality with the same route and scene.
• Only a small dedicated-memory amount appears on integrated graphics — Read shared memory and system RAM too.
• A VRAM warning appears despite a low counter — Check the selected GPU, timing and exact warning.
• Memory use falls but stutter remains — Move to other explanations instead of repeating the same change.

STEP 1: Identify the game GPU and both memory counters

1. With the game running, press Ctrl+Shift+Esc. In Task Manager’s Processes view, use the game’s GPU engine entry where available to identify its GPU number. In Performance, select that same GPU and record its name.
2. Immediately after the symptom, record Dedicated GPU memory and Shared GPU memory as used / displayed capacity. A small dedicated-memory value on integrated graphics does not by itself mean a fault or insufficient memory.

Result and next action: If the GPU is uncertain, confirm its name before interpreting a reading. Keep the two memory categories separate and record the symptom at the same time.

STEP 2: Match the symptom with one setting to compare

1. Distinguish a memory warning, hitches during movement and deterioration after a long session. A game’s VRAM estimate may describe settings rather than measured use, so do not treat it as the same counter as Task Manager.
2. If a discrete GPU is near its dedicated-memory capacity when symptoms appear, lower texture quality by one level in the game. For an added high-resolution texture pack or mod, use its documented disable method separately and preserve any required configuration.

Result and next action: Record the original value. Change one item, not a whole quality preset, and keep resolution and the test scene unchanged.

STEP 3: Compare memory and symptoms on the same route

1. Record the save, resolution and route. Restart if the game requires it to apply textures, then revisit the same scene and compare dedicated/shared memory plus warnings or the number of hitches.
2. If memory use falls but the symptom persists, investigate other causes. If it improves, revisit again to see whether the result repeats. Restore an unhelpful change and use the result branches below.

Result and next action: A lower counter alone is not an improvement in playability. Separate the first visit from repeat visits because loading or shader preparation can also change the result.

Read dedicated, shared and total memory separately

1. On a discrete GPU, dedicated memory refers to its graphics memory. For a display such as 7.6 / 8.0 GB, distinguish current use from capacity. Other applications can contribute to the use shown in Performance.
2. Shared GPU memory uses system RAM. In an illustrative 0.5 / 8.0 GB reading, 0.5 GB is in use; the 8.0 GB limit is neither current use nor extra dedicated VRAM. A combined total does not turn an 8 GB graphics card into a 16 GB card.
3. Integrated graphics may reserve some system RAM and use additional shared memory. A dedicated figure such as 128 MB cannot be compared directly with a discrete card’s VRAM to decide whether a game will run.
4. Use the same Performance counter for before/after comparisons. Per-process memory figures can count shared resources differently; Microsoft also documents a Windows 10 per-process counter issue. Do not add process totals together and call the result physical VRAM use.

Match the observation to the moment of the problem

1. If GPU engine is hidden, check the Processes column headings for that option. Match the number to the GPU name in Performance. If the game’s engine cannot be identified there, check its display settings and GPU name; do not guess the number.
2. Record both memory counters just after a hitch and during a normal scene. Switching away from the game can change its workload, so note how the observation was taken. Also record system RAM in Performance → Memory, especially for integrated graphics.
3. Near-full dedicated memory plus movement hitches makes memory pressure a candidate, alongside loading or shader preparation. Compare texture quality and repeat the route twice. Hitches only on the first visit with ample memory call for a different comparison.
4. If shared memory and system RAM rise during long sessions, compare background video or recording apps one at a time. Repeat at a similar session length rather than comparing a fresh launch with hours of play.
5. For a warning with a low reading, keep the exact message and time. A different selected GPU, a brief peak or an allocation request can make a later snapshot misleading; the low value does not invalidate the warning.

Make a reversible texture comparison

1. Keep the same save, resolution, display mode and route. Record the original texture setting, both memory readings, warnings and hitches. If the first visit differs, repeat the original route before changing anything.
2. Lower only texture quality by one level, apply the change and restart if required. If there is no texture option but the game has an optional high-resolution texture DLC, follow its official removal/disable instructions and wait for the change to finish. Do not remove unrelated DLC or game files.
3. Illustrative example only, not a hardware test: dedicated use falls from 7.7 / 8.0 GB to 6.3 / 8.0 GB, shared use from 0.9 / 8.0 GB to 0.3 / 8.0 GB, and about three hitches per route become zero on two visits. This supports investigating memory pressure, but does not isolate it as the only cause.
4. If only the numbers fall, do not claim success. Texture changes can affect other work, including shader preparation; compare first and repeat visits separately.

Choose the next check from the result

1. Memory use and symptoms improve: keep a usable quality setting and check other scenes. Memory falls but symptoms remain: restore the unhelpful quality reduction and compare stutter, loading or other workload factors.
2. Neither reading nor symptom changes: confirm the setting applied and that you observed the game’s actual GPU. Use the related low-GPU-usage guide for GPU selection.
3. Crashes or warnings continue: record the full warning, game version, GPU, settings and system RAM use. Use the crash guide and official game support. Consistently low FPS needs the separate rendering-load comparison in the FPS guide.
4. Do not edit registry numbers to claim more physical VRAM or treat a page file as dedicated graphics memory. Preserve original settings and do not delete game files based only on their names.

Protect saves and keep changes reversible

• A near-capacity reading is not proof of a memory shortage or broken GPU.
• Do not change textures, resolution, drivers and mods together; you would lose the comparison.