How to Fix VIDEO_MEMORY_MANAGEMENT_INTERNAL BSOD (0x0000010E)
What error 0x0000010E means
Your graphics card has its own memory (VRAM), and Windows runs a dedicated video memory manager inside the kernel that allocates, tracks, and frees it for games, browsers, and every app that draws on screen. When that manager finds its internal records corrupted — a freed block that is still marked in use, a double-free, a list that no longer adds up — it stops the system with VIDEO_MEMORY_MANAGEMENT_INTERNAL (stop code 0x0000010E) rather than let graphics memory get written over randomly.
The name tells you where to look: this is a graphics-subsystem problem, not a storage, network, or "video file won't play" problem. In the vast majority of real-world cases the trigger is a faulty or corrupted graphics driver, an unstable overclock, an overheating GPU, or failing VRAM chips. Corrupted Windows system files and bad system RAM are rarer causes. The fix order below follows that ranking: clean driver reinstall first, heat and overclock second, system files third, VRAM hardware testing last.
Common causes
- A corrupted or buggy graphics driver: the top cause — a driver install that went wrong or a new release that introduced this bug check.
- An overheating GPU: dust-clogged fans or blocked airflow push the card past stability, corrupting video memory under load.
- GPU overclocking: memory-clock overclocks in tools like MSI Afterburner are a classic trigger of this exact error.
- Corrupted Windows system files: damage to the kernel components that implement the video memory manager itself.
- Failing VRAM or system RAM: dying memory chips on the graphics card (or bad system RAM feeding it) corrupt the data the manager guards.
How to fix error 0x0000010E — step by step
Work through these fixes in order. Step 1 fixes the most common scenario; the later steps cover heat, software, and hardware causes.
- Reinstall your graphics driver cleanly with DDU. This blue screen is overwhelmingly a graphics driver problem, and a plain reinstall over the old one often leaves the corruption in place. Download Display Driver Uninstaller (DDU) and the latest graphics driver from NVIDIA, AMD, or Intel — not from a third-party driver pack. Disconnect from the internet so Windows Update cannot push a driver mid-repair, boot into Safe Mode (interrupting boot three times in a row gets you to Troubleshoot > Advanced options > Startup Settings > Restart, then press 4), run DDU, and choose "Clean and restart." After the reboot, install the driver you downloaded, restart again, and use the PC normally. If the crashes started right after a driver update, install the previous version instead — a brand-new release can introduce this exact bug check.
- Check the GPU temperature and cooling. The video memory manager crashes when the GPU is unstable, and overheating is a classic trigger — especially during games or video rendering. Install HWMonitor or HWiNFO and watch the GPU temperature while the crash scenario runs: idle should sit roughly between 30 and 45°C, and under load it should stay under about 85°C. If it spikes higher, open the case and clean the dust from the GPU fans and heatsink with compressed air, make sure the fans actually spin, and check that case intake and exhaust airflow are not blocked. On a laptop, lift the rear for airflow or use a cooling pad, and check power settings — a GPU starved of power or throttled by a failing fan corrupts video memory the same way a bad driver does.
- Roll back or stop recent graphics software changes. If 0x0000010E appeared after a Windows update, a new game, a screen recorder, or an overclocking utility, that change is your prime suspect. Press Win + X and open Device Manager, expand Display adapters, right-click your GPU, open Properties, go to the Driver tab, and click Roll Back Driver if the option is available. Also remove GPU overclocks — utilities like MSI Afterburner, EVGA Precision, or AMD Adrenalin's performance tuning can push memory clocks past stability; reset them to stock defaults. Temporarily disable screen overlays and recorders (Discord overlay, GeForce Experience overlay, OBS) and see if the crashes stop: anything that hooks into the graphics pipeline can trip the video memory manager.
- Run SFC and DISM to repair system files. The video memory manager is part of Windows itself, and corrupted system files can make it misbehave even with a good driver. Open an admin Terminal (right-click Start > Terminal (Admin)) and run
sfc /scannow, letting it finish completely. Then runDISM /Online /Cleanup-Image /RestoreHealth, which repairs the component store SFC depends on, and run SFC once more if it found anything it could not fix the first time. Restart the PC after both finish. This combination fixes the "Windows files quietly damaged by a failed update or a hard shutdown during a crash loop" version of this error. - Stress-test the video memory with OCCT or MemTestG80. If the driver and temperatures are fine, the VRAM chips on the graphics card may be failing — video memory errors are a signature cause of 0x0000010E. Run OCCT's VRAM test (or MemTestG80) for at least 30 minutes; any reported errors mean the GPU's memory is faulty and no driver fix will save it. Also run Windows Memory Diagnostic (Win + R, type
mdsched.exe, choose "Restart now and check for problems") since bad system RAM can feed corrupted data to the GPU as well. Failing VRAM means the graphics card itself needs repair or replacement — try reseating the card and its power cables first, and if you have a second PCIe slot or another GPU to test with, swap to confirm. - Update the BIOS and Windows, then reset as a last resort. Check your PC or motherboard maker's support page for a BIOS/UEFI update — newer firmware fixes PCIe and memory-controller compatibility bugs that can trigger this bug check on new GPUs and CPUs. Install any pending Windows cumulative updates too (Settings > Windows Update), since Microsoft periodically patches the video memory manager itself. If every hardware test passes and crashes persist, back up your files and use Settings > System > Recovery > Reset this PC ("Keep my files" first). A clean Windows that still blue-screens with 0x0000010E on stock clocks and clean drivers is a hardware verdict: GPU first, then the motherboard's PCIe slot or power supply.
Did this fix it? Quick checklist
- The graphics driver was fully wiped with DDU and reinstalled from the manufacturer's site — not over the old install
- All GPU overclocks are reset to stock and screen overlays are disabled
- GPU temperature stays under ~85°C under load and all fans spin
- OCCT's VRAM test ran 30+ minutes with zero errors
If crashes continue after all six steps, the crash dump has the answer. Open C:\Windows\Minidump, note the newest .dmp file, and open it with WinDbg (free from the Microsoft Store) — the "Probably caused by" line often names the driver directly. Reseat the graphics card and its power cables, try the card in another PC if you can, and consider a warranty claim if the VRAM test reported errors. A fresh Windows that still crashes with 0x0000010E on stock settings points squarely at the GPU hardware.
Frequently asked questions
What does VIDEO_MEMORY_MANAGEMENT_INTERNAL (0x0000010E) mean?
It means the part of Windows that manages the graphics card's memory (the video memory manager inside the kernel) detected internal corruption and blue-screened to protect the system. The name points at video memory — not a website video or a media player. Almost always the trigger is a faulty graphics driver, an overheating or unstable GPU, or failing VRAM chips on the card itself.
Is 0x0000010E always the graphics card's fault?
The fault is almost always in the graphics subsystem, but not always the physical card: a bad graphics driver, a GPU overclock, overheating, corrupted Windows system files, and even bad system RAM can all cause it. That is why the fix order starts with a clean driver reinstall (DDU) and temperature checks before suspecting the hardware. If a clean driver on stock clocks still crashes and the VRAM test reports errors, then yes — the card itself is failing.
Can an overclock cause 0x0000010E?
Yes, very commonly — especially memory-clock overclocks on the GPU. Pushing VRAM past its stable limit corrupts exactly the structures the video memory manager guards, so the very first fix for this error on an overclocked system is to reset everything to stock in your tuning utility (MSI Afterburner, AMD Adrenalin, or similar). If the crashes stop at stock settings, your overclock was unstable for that card.
Why does 0x0000010E only happen during games?
Games hammer the GPU hard: maximum clock speeds, heavy VRAM usage, and maximum heat — exactly the conditions that expose an unstable driver, a dirty cooler, a marginal overclock, or dying VRAM. A PC that idles fine but crashes under load is the textbook signature of a heat or stability problem. Clean the GPU, watch temperatures with HWMonitor, reset overclocks, and run OCCT's VRAM test to confirm.