VIDEO_MEMORY_MANAGEMENT_INTERNAL: Fix 0x10E in Windows 11

By LK Wood IV · 2026-10-04 · ~10 min read · St. Louis County, MO

VIDEO_MEMORY_MANAGEMENT_INTERNAL is bug check 0x0000010E. It means Windows’ video memory manager reached a condition it could not recover from. It does not mean “your graphics card ran out of VRAM,” and it does not condemn the memory chips on the card.

Microsoft’s 0x10E reference says the bug check is usually caused by a video driver behaving improperly. Its explicit resolution is to check Windows Update for an updated video driver. The later settings and hardware tests are TechFuelHQ’s one-variable-at-a-time diagnostic order, not additional Microsoft instructions.

First, make sure this is the right stop code

Windows has several graphics and memory blue screens whose names blur together. The number separates them — and prevents a long detour through the wrong tests.

Write down all four values shown with the bug check if the blue screen or your crash record provides them. For 0x10E, Parameter 1 is the useful router. Microsoft says it describes the type of video-memory error. A value missing from Microsoft’s table needs individual examination rather than a guess.

What 0x10E is reporting

Windows’ video memory manager is called VidMm. Microsoft’s VidMm and GPU scheduling documentation says it sits inside the DirectX graphics kernel, manages GPU memory, and works with the GPU scheduler. The Windows components that implement this work include dxgkrnl.sys, dxgmms1.sys, and dxgmms2.sys.

When a crash report names dxgmms2.sys, it identifies a Windows component in the path where the failure surfaced. The filename is a location — not a verdict. Microsoft says these files are part of the operating-system installation, are not separately downloadable, and are designed to work with the other OS files that accompany them. Do not replace one with a copy from a download site or another PC.

The 0x10E page currently lists 68 Parameter 1 values, from 0x1 through 0x44; nine of those rows explicitly name a driver error or a display-driver-interface call — 0xB, 0xF, 0x10, 0x12, 0x13, 0x16, 0x19, 0x2D, and 0x2E — while the phrases “memory corruption” and “bad hardware” do not appear; those are counts and wording from the published table, not incident data showing how often any cause occurs on Windows PCs.

The table supports starting with the driver, but it neither identifies nor excludes a hardware fault. I would not buy or RMA a card on the stop-code name alone.

Use Parameter 1 to choose the branch

You do not need to translate every table row. The groups below collect rows that are useful for routing this guide.

Microsoft supplies the middle column. The right column is TechFuelHQ’s editorial next test; Microsoft does not prescribe it per parameter.

The table routes investigation; it does not rank causes or prescribe repairs itself.

If your value is not in that short list, read its exact row on Microsoft’s page. Do not turn a table description into a diagnosis it does not make. For example, 0x25 says the GPU attempted to write over an undefined aperture area. That does not tell you whether the initiating fault was firmware, a driver, unstable tuning, or failing hardware.

Fix 1. Update Windows and the approved display driver

Microsoft’s own resolution for persistent 0x10E crashes is to check Windows Update for an updated video driver. Start there. Microsoft’s Windows driver-update instructions also say a manual driver should come from the device manufacturer’s site, and document rollback when trouble begins after an update.

1. In Settings > Windows Update, install the normal pending Windows updates and restart.
2. Install the current display package intended for your model. On a laptop or branded desktop, check the PC maker’s support page and choose only a package listed for that exact model and Windows version.
3. If the crash began immediately after a display-driver update, roll back to the last version that was stable on this machine instead of repeatedly installing the same package.
4. If ordinary update or rollback does not change the result, use the clean-install procedure in the GPU driver crash guide.

Change one layer at a time.

A simultaneous BIOS update, driver update, Windows repair, and hardware swap may stop the crash, but it leaves you with no idea which change mattered — and no useful evidence if the blue screen returns next week.

Retest the trigger.

Fix 2. Put the GPU and video memory back to stock

Microsoft’s 0x10E page does not name tuning as a cause. This guide still removes core, VRAM, voltage, and power-limit tuning as an isolation step so a repeat test has fewer variables.

• Reset GPU core offset, memory offset, voltage curve, and power-limit changes.
• Close tuning utilities so they do not reapply a profile at sign-in.
• If the card has a physical dual-BIOS switch, shut down before moving it and document the original position. Use the card maker’s instructions.
• Retest the workload that normally triggers the crash.

A clean run at stock settings suggests that one of the removed settings correlated with the crash. It does not prove which setting caused it. Repeat the same trigger before drawing that conclusion.

Stop there if it stays stable.

Fix 3. Treat hybrid graphics as one stack

Laptop and multi-GPU systems can involve an integrated GPU, a discrete GPU, and cross-adapter allocations in the same session. Microsoft’s table specifically includes cross-adapter states at 0x41 and 0x42.

Start with the PC maker’s current packages for the exact model. If the firmware or graphics control panel offers a supported integrated-only or discrete-only mode, repeated tests in each mode can compare the two paths. This controlled troubleshooting suggestion goes beyond what Microsoft infers from 0x41 or 0x42. Do not disable the only display adapter on a machine with no safe way back.

For a desktop with two add-in cards, remove the secondary card for a controlled test if doing so is physically safe and the primary card can drive the display. Repeat the comparison. A difference between configurations is evidence about the path. It does not prove that one card is defective.

Fix 4. Repair Windows’ copy of the graphics components

Microsoft does not say 0x10E implies damaged Windows files. If Windows servicing or System File Checker already reports corruption, use Microsoft’s system-file repair instructions, which put DISM before System File Checker. Open Terminal as administrator and run:

Run this branch only when Windows has given you separate file-integrity evidence.

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Restart after both commands finish. This step is for damaged or mismatched operating-system files. It cannot stabilize an overclock, repair a failing memory chip, or correct a defective power supply.

Avoid sites offering individual DLL or SYS downloads. Microsoft’s VidMm documentation says the relevant kernel graphics files ship only as part of the operating system and that graphics-driver developers must not mix versions of them.

Fix 5. Test hardware only after the software path is clean

In this guide’s editorial workflow, hardware isolation begins when 0x10E repeatedly returns with a current or known-stable driver and GPU and VRAM settings at stock. Microsoft does not give that escalation threshold on its 0x10E page. If the display also shows persistent blocks, colored flashes, or broken geometry, the GPU artifact guide provides a separate diagnosis for that evidence.

Use repeated comparisons that can distinguish paths; one clean run is never conclusive.

1. Log the trigger. Note the application, display configuration, temperature, and whether the crash followed resume, sign-in, or a monitor change.
2. Test one display path. Disconnect optional monitors and adapters. A clean run narrows the trigger but does not prove the disconnected monitor is defective.
3. Test the card in a known-good system, or a known-good card in this PC. A failure that repeatedly follows one card is a stronger isolation signal than the filename in one dump, but it is still not proof by itself.
4. Test system RAM when the evidence points beyond graphics. Multiple unrelated stop codes, memory-profile instability, or errors outside graphics workloads justify the 0x1A memory test path. A lone 0x10E does not.

Simple VRAM pressure is not a verdict. Microsoft’s GPU-segments page explains how VidMm manages segment types and allocations; it does not say capacity exhaustion causes 0x10E. A VRAM meter alone cannot establish why VidMm reached an unrecoverable condition.

What not to do

• Do not buy a GPU from the stop-code name. The official cause section points first to the video driver.
• Do not replace dxgmms2.sys or dxgkrnl.sys by hand. If Windows integrity checks report corruption, use the conditional DISM and SFC path above.
• Do not edit TDR registry values as a 0x10E fix. Microsoft’s TDR registry documentation says end users should not manipulate those keys; they are for targeted testing and debugging during driver development.
• Do not use 0x1A advice for a 0x10E crash. System-memory testing may become relevant later, but the first branch is different.
• Do not treat Microsoft’s 68 table rows as cause statistics. They are error types, not a tally of user crashes.

A conservative diagnostic order is therefore: exact code, Parameter 1, current or rolled-back display driver, stock GPU settings, conditional Windows file repair, then controlled hardware isolation. The driver step is Microsoft’s explicit 0x10E resolution; the remaining order is TechFuelHQ’s editorial workflow for changing one variable at a time.

Sources

• Microsoft Learn: Bug Check 0x10E: VIDEO_MEMORY_MANAGEMENT_INTERNAL — definition, Parameter 1 table, cause, and resolution; accessed October 2, 2026.
• Microsoft Learn: Video memory management and GPU scheduling — VidMm, VidSch, and the Windows graphics-kernel files; accessed October 2, 2026.
• Microsoft Learn: GPU segments — memory segments and aperture behavior; accessed October 2, 2026.
• Microsoft Support: Update drivers through Device Manager in Windows — Windows Update, manufacturer downloads, reinstall, and rollback paths; accessed October 2, 2026.
• Microsoft Support: Use the System File Checker tool to repair missing or corrupted system files — DISM and SFC order and commands; accessed October 2, 2026.
• Microsoft Learn: Testing and debugging TDR during driver development — TDR registry keys are for driver-development testing and debugging, not end-user manipulation; accessed October 3, 2026.