The VIDEO_MEMORY_MANAGEMENT_INTERNAL error is a Windows Blue Screen of Death (BSOD) associated with the operating system's graphics/video-memory management subsystem.

The bug check is commonly identified as:

VIDEO_MEMORY_MANAGEMENT_INTERNAL

Bug Check Code: 0x0000010E

This stop error indicates that Windows detected a serious problem involving its video memory manager. The underlying cause can range from a corrupted or incompatible graphics driver to unstable GPU/VRAM hardware, system memory problems, overclocking, firmware issues, or other low-level graphics subsystem failures.

The error may occur occasionally or repeatedly. Some computers crash only while gaming or performing GPU-intensive work, while others experience the BSOD during startup, normal desktop operation, video playback, sleep/resume, or shortly after installing a graphics driver or Windows update.

This guide explains how to systematically diagnose and resolve the VIDEO_MEMORY_MANAGEMENT_INTERNAL error in Windows 11 and Windows 10.

What Is VIDEO_MEMORY_MANAGEMENT_INTERNAL?

Windows uses a sophisticated graphics memory-management system to coordinate memory resources used by the GPU, applications, drivers, DirectX, and the Windows graphics subsystem.

Graphics processing does not involve only the dedicated VRAM installed on a graphics card. Depending on the hardware configuration, Windows may manage:

• Dedicated GPU memory (VRAM)
• Shared system memory
• Integrated graphics memory
• Graphics memory allocations
• DirectX resources
• GPU paging operations
• Video-memory mapping
• Graphics-driver memory requests

If Windows detects an unrecoverable inconsistency or violation while managing these resources, it may intentionally stop the operating system to prevent further corruption.

The resulting BSOD can display:

Your device ran into a problem and needs to restart.

Stop code: VIDEO_MEMORY_MANAGEMENT_INTERNAL

What Does Bug Check 0x0000010E Mean?

VIDEO_MEMORY_MANAGEMENT_INTERNAL corresponds to bug check 0x10E.

The bug check indicates that the video memory manager encountered a condition from which it could not safely recover.

The parameters recorded with a 0x10E crash provide additional diagnostic information. Their meaning depends on the specific subtype recorded in the first parameter.

For technicians, this is important because two computers displaying the same VIDEO_MEMORY_MANAGEMENT_INTERNAL stop code may have completely different root causes.

A crash dump should therefore be examined before assuming that the graphics card itself has failed.

Common Symptoms

A system affected by VIDEO_MEMORY_MANAGEMENT_INTERNAL may show one or more of the following symptoms:

• Random Windows blue screens
• BSOD immediately after starting a game
• Crash during gaming
• Crash during GPU rendering
• Crash while watching videos
• BSOD during video editing
• Crash when connecting an external monitor
• BSOD after installing a GPU driver
• Crash after Windows Update
• Black screen followed by a restart
• Display driver repeatedly crashing
• Screen flickering before the BSOD
• Graphical artifacts
• Colored blocks or lines on the display
• Applications unexpectedly closing
• Games freezing
• GPU-intensive applications crashing
• BSOD when waking from Sleep or Hibernate
• System instability after GPU overclocking

The exact symptoms can provide useful clues about the underlying problem.

Common Causes of VIDEO_MEMORY_MANAGEMENT_INTERNAL

1. Corrupted Graphics Driver

A damaged NVIDIA, AMD, or Intel graphics driver is one of the most common software-related causes.

Driver corruption can occur because of:

• Interrupted driver installation
• Failed Windows Update
• Incomplete driver upgrade
• Third-party driver utilities
• Previous GPU drivers remaining installed
• Unexpected shutdown during an update

2. Incompatible Graphics Driver

The newest driver is not necessarily the most stable driver for every computer.

Problems can occur when:

• A newly released driver contains a bug
• Windows automatically replaces an OEM driver
• A generic GPU driver conflicts with laptop-specific graphics management
• An older GPU is used with a newer driver
• Hybrid graphics drivers are installed in the wrong order

If the problem started immediately after a graphics-driver update, driver rollback should be considered early in the troubleshooting process.

3. Faulty Graphics Card

A physically failing GPU can produce memory-management errors.

Possible indications include:

• Frequent crashes under GPU load
• Graphical artifacts
• Random black screens
• Driver resets
• Games crashing across different installations
• Problems continuing after clean Windows installation
• Failure during GPU diagnostics

A hardware problem becomes more likely if software troubleshooting does not change the behavior.

4. Faulty VRAM

Dedicated graphics cards contain their own video memory.

Defective or unstable VRAM can cause:

• Texture corruption
• Artifacts
• Driver crashes
• Application failures
• GPU compute errors
• VIDEO_MEMORY_MANAGEMENT_INTERNAL BSODs

VRAM instability can also be caused by aggressive memory overclocking rather than permanent hardware failure.

5. GPU Overclocking

Overclocking the GPU core or VRAM can introduce instability even if normal desktop usage appears stable.

A configuration that passes a short benchmark may still fail during:

• Long gaming sessions
• Video rendering
• AI workloads
• High-resolution gaming
• Multi-monitor usage
• Rapid changes in GPU load

Return the GPU to manufacturer-default frequencies during troubleshooting.

6. GPU Undervolting

Undervolting is commonly used to reduce temperature and power consumption.

However, an excessively low GPU voltage can cause instability.

Temporarily restore the GPU voltage and frequency settings to default values and test the computer again.

7. GPU Overheating

Excessive GPU temperature can destabilize the graphics subsystem.

Common causes include:

• Dust buildup
• Blocked ventilation
• Failed GPU fan
• Poor case airflow
• Deteriorated thermal compound
• Laptop cooling-system problems
• Excessive overclocking

If crashes occur primarily during gaming or rendering, monitor GPU temperatures.

8. System RAM Problems

VIDEO_MEMORY_MANAGEMENT_INTERNAL does not automatically mean that dedicated graphics memory is defective.

Windows graphics operations can use system RAM, particularly with integrated graphics and shared graphics memory.

Defective RAM can therefore create symptoms that appear to be GPU-related.

9. Power Supply Problems

Desktop graphics cards can consume significant power, especially during sudden changes in workload.

A weak, deteriorating, incorrectly connected, or inadequate power supply can cause:

• Black screens
• GPU resets
• Unexpected restarts
• System freezes
• BSODs

Check that all required GPU PCIe power connectors are securely installed.

10. BIOS/UEFI Problems

Older motherboard firmware can sometimes cause compatibility problems involving:

• PCI Express
• GPU initialization
• Resizable BAR
• Memory mapping
• Integrated graphics
• Dedicated graphics
• Power management

Check the computer or motherboard manufacturer's support page for BIOS/UEFI updates applicable to your exact model.

11. Chipset Driver Problems

The graphics card communicates with the rest of the system through the motherboard platform.

Outdated or corrupted chipset drivers can contribute to PCIe, power-management, and hardware communication problems.

Install the correct chipset package from the PC or motherboard manufacturer, or from the platform vendor when appropriate.

12. Windows System File Corruption

Corrupted Windows system components can affect graphics operations and driver interaction.

System corruption can occur because of:

• Improper shutdowns
• Storage errors
• Failed Windows updates
• Malware
• Disk corruption
• Incomplete servicing operations

Windows provides built-in SFC and DISM utilities for checking and repairing many of these problems.

How to Fix VIDEO_MEMORY_MANAGEMENT_INTERNAL

Follow the troubleshooting methods below in a logical order.

Method 1: Restart the Computer

If the BSOD occurred only once, restart Windows and observe the computer.

A single crash does not automatically indicate hardware failure.

If the error repeatedly returns, continue with the following troubleshooting.

Method 2: Identify Recent Changes

Determine what changed shortly before the BSOD started.

Examples include:

• New GPU driver
• Windows Update
• New graphics card
• RAM upgrade
• BIOS update
• New game
• GPU tuning software
• Overclocking
• Undervolting
• New monitor
• New docking station
• New PCIe hardware

Recent changes can significantly narrow the investigation.

Method 3: Update the Graphics Driver

Install the appropriate driver for your graphics hardware.

Determine whether your computer uses:

• NVIDIA graphics
• AMD Radeon graphics
• Intel graphics
• Hybrid Intel + NVIDIA graphics
• Hybrid AMD + NVIDIA graphics

Avoid relying exclusively on Windows Update when troubleshooting persistent GPU crashes.

For laptops and systems with switchable graphics, first check the computer manufacturer's recommended graphics packages because they may contain OEM-specific configurations.

After installing the driver, restart Windows.

Method 4: Roll Back the Graphics Driver

If VIDEO_MEMORY_MANAGEMENT_INTERNAL started immediately after a graphics-driver update, the new driver may be responsible.

Open:

Device Manager → Display adapters

Right-click the graphics adapter and select:

Properties → Driver → Roll Back Driver

If Roll Back Driver is unavailable, manually install an earlier stable driver from the GPU or computer manufacturer's support source.

Method 5: Perform a Clean Graphics Driver Reinstallation

If normal driver updates do not help, reinstall the graphics driver.

Open:

Device Manager → Display adapters

Right-click the graphics adapter and choose:

Uninstall device

Restart Windows and install the correct graphics driver again.

For persistent problems, technicians may choose to perform a more thorough clean-driver installation. Before using third-party driver-removal utilities, create a restore point or backup and understand that Safe Mode may be required.

Method 6: Install Windows Updates

Open:

Settings → Windows Update

Install applicable:

• Quality updates
• Security updates
• Reliability fixes
• Driver updates where appropriate

Restart Windows afterward.

If the BSOD started immediately after a specific update, however, investigate that update rather than blindly installing additional changes.

Method 7: Reset GPU Overclocking

If you use GPU tuning software such as manufacturer utilities or overclocking tools, restore:

• GPU core clock
• VRAM clock
• Voltage
• Power limit

to their default values.

Restart Windows and test again.

This step is particularly important if the error occurs during gaming.

Method 8: Disable CPU and RAM Overclocking Temporarily

GPU-related crashes can sometimes originate elsewhere.

Temporarily return the entire computer to stable/default settings, including:

• CPU overclock
• RAM overclock
• XMP/EXPO settings
• GPU overclock
• GPU undervolt

This provides a clean baseline for troubleshooting.

Do not change BIOS settings unless you understand their effect and know how to restore the previous configuration.

Method 9: Check GPU Temperature

Monitor GPU temperature while reproducing the workload that normally causes the crash.

If the temperature rises abnormally:

• Clean dust from the computer
• Check GPU fans
• Improve airflow
• Check laptop vents
• Avoid using a laptop on soft surfaces
• Verify cooling-system operation

Do not disassemble a graphics card or laptop cooling assembly unless you are qualified to do so.

Method 10: Run System File Checker

Open Command Prompt or Windows Terminal as Administrator.

Run:

sfc /scannow

Allow the scan to reach 100%.

SFC checks protected Windows system files and attempts to repair corrupted copies.

Restart Windows after repairs are completed.

Method 11: Repair Windows Using DISM

Open an elevated Command Prompt or Terminal.

Run:

DISM /Online /Cleanup-Image /ScanHealth

Then run:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM finishes successfully, run:

sfc /scannow

again.

Restart the computer.

Method 12: Check System RAM

Press:

Windows + R

Type:

mdsched.exe

Press Enter.

Select:

Restart now and check for problems

Windows will restart and perform a memory test.

If memory errors are reported, investigate the RAM before replacing the GPU.

For persistent or intermittent hardware problems, a more extensive memory diagnostic may be required.

Method 13: Reseat the RAM

For desktop computers, poorly seated RAM can cause unpredictable BSODs.

If you are comfortable servicing hardware:

1. Shut down the computer.
2. Disconnect power.
3. Follow appropriate anti-static precautions.
4. Remove the RAM modules.
5. Inspect the slots and modules.
6. Reinstall the RAM firmly.
7. Test the computer.

If multiple RAM modules are installed, a technician can test modules individually when investigating suspected memory failure.

Method 14: Reseat the Graphics Card

On a desktop PC with a discrete GPU:

1. Shut down Windows.
2. Disconnect power.
3. Follow anti-static precautions.
4. Remove and reinstall the graphics card.
5. Verify that the PCIe slot connection is secure.
6. Reconnect all required GPU power cables.
7. Start the computer and test.

Do not attempt this on equipment covered by warranty if opening the system would conflict with the manufacturer's service requirements.

Method 15: Check GPU Power Connections

Modern graphics cards may require one or more dedicated power connections.

Inspect:

• PCIe power connectors
• 6-pin/8-pin connectors
• Modern high-power GPU connectors where applicable
• Loose connections
• Damaged connectors
• Excessive cable bending near the connector

Use the power-supply and GPU manufacturer's recommended connection method.

Method 16: Check the Power Supply

Consider PSU problems if crashes occur mainly when the GPU suddenly enters a high-load state.

Check:

• PSU wattage
• PSU age
• GPU power requirements
• Cable condition
• Power connectors
• PSU quality
• Other high-power components

Do not open a power supply. Internal PSU components can retain dangerous electrical energy even after the unit is disconnected.

Method 17: Update Chipset Drivers

Install the correct motherboard/chipset drivers.

Chipset updates may improve:

• PCIe communication
• Power management
• Device enumeration
• System stability
• CPU/GPU interaction

Restart the computer after installation.

Method 18: Check BIOS/UEFI Updates

Check whether the system manufacturer has released a newer BIOS/UEFI version addressing:

• Stability
• Graphics compatibility
• Memory compatibility
• PCIe behavior
• CPU microcode
• Power management

BIOS updates should be performed carefully. An interrupted or incorrect firmware update can prevent the computer from booting.

Always follow the manufacturer's instructions for the exact computer or motherboard model.

Method 19: Test Without Hardware Acceleration in Applications

If crashes occur primarily while using Chrome, Edge, Discord, Teams, media applications, or other GPU-accelerated software, temporarily disable hardware acceleration in the affected application.

If the crashes stop, this does not necessarily prove the application is defective. It can indicate a graphics driver, GPU, or graphics-acceleration compatibility issue.

Use this test diagnostically rather than treating it as the final solution.

Method 20: Check for Graphics Artifacts

Watch for:

• Colored dots
• Checkerboard patterns
• Strange polygons
• Texture corruption
• Horizontal or vertical lines
• Flashing blocks
• Random colors

Artifacts that appear during GPU load can indicate:

• GPU instability
• VRAM instability
• Excessive temperature
• Overclocking
• Hardware degradation

Artifacts appearing before Windows loads are especially important because they are less likely to be caused by a normal Windows graphics driver.

Method 21: Test the GPU Under Controlled Load

A technician may use a reputable GPU diagnostic or benchmark to determine whether the problem consistently occurs under graphics load.

Do not perform aggressive stress testing if:

• GPU temperature is already excessive
• Fans are malfunctioning
• Power connectors are damaged
• The computer shuts down under load

Stress testing an already unstable component can worsen thermal or electrical problems.

Method 22: Test Integrated Graphics

If the desktop processor provides integrated graphics and the motherboard supports display output, a technician can temporarily remove or disable the dedicated graphics card and test using integrated graphics.

If the system becomes stable without the dedicated GPU, investigate:

• Dedicated GPU
• VRAM
• GPU driver
• PCIe slot
• GPU power cables
• Power supply

This is one of the most useful isolation tests for desktop systems.

Method 23: Test With Another Graphics Card

If compatible hardware is available, install a known-good graphics card.

If the VIDEO_MEMORY_MANAGEMENT_INTERNAL error disappears completely, the original GPU or its associated power/driver configuration becomes a primary suspect.

Conversely, if the replacement GPU produces the same problem, investigate RAM, motherboard, PSU, Windows, BIOS, and chipset configuration.

Method 24: Check Reliability Monitor

Windows Reliability Monitor provides a useful timeline of crashes.

Search Windows for:

View reliability history

Look for:

• Windows failures
• Hardware errors
• Application crashes
• Driver failures
• Windows updates
• Software installations

Compare their timestamps with the VIDEO_MEMORY_MANAGEMENT_INTERNAL crashes.

Method 25: Check Event Viewer

Open:

Event Viewer → Windows Logs → System

Inspect events around the time of the BSOD.

Useful events may involve:

• Display driver
• WHEA hardware errors
• Kernel-Power
• BugCheck
• PCI Express
• Device-driver failures

Do not assume that a Kernel-Power event identifies the cause. It often records that Windows restarted unexpectedly rather than explaining why it crashed.

Method 26: Analyze Windows Minidump Files

Windows may create crash dumps under:

C:\Windows\Minidump

Typical filenames look similar to:

082926-12345-01.dmp

These files can provide considerably more information than the BSOD screen itself.

Microsoft WinDbg can be used for detailed dump analysis.

A common starting command is:

!analyze -v

Review information such as:

• Bugcheck code
• Bugcheck parameters
• Faulting module
• Call stack
• Driver names
• Process involved
• Failure bucket
• Graphics-related modules

Do not automatically delete or replace a driver merely because its filename appears in the stack. A component can appear in the crash path without being the original cause.

dxgkrnl.sys and dxgmms2.sys

Graphics-related BSOD dumps may reference files such as:

dxgkrnl.sys

or

dxgmms2.sys

These are Windows graphics components.

Seeing one of these files in a crash dump does not automatically mean that the Windows file itself is defective.

The underlying problem could still be:

• NVIDIA/AMD/Intel driver
• GPU hardware
• VRAM
• System RAM
• PCIe instability
• Overclocking
• Power instability

Dump analysis should therefore consider the complete call stack and system configuration.

VIDEO_MEMORY_MANAGEMENT_INTERNAL While Gaming

If the BSOD occurs primarily while gaming, prioritize:

1. Restore GPU settings to default.
2. Monitor GPU temperature.
3. Clean-install or roll back the graphics driver.
4. Disable RAM/CPU overclocking for testing.
5. Check GPU power connections.
6. Test system RAM.
7. Test another GPU if available.
8. Investigate the PSU.

Gaming places substantially more load on the GPU, VRAM, power supply, and cooling system than normal desktop operation.

VIDEO_MEMORY_MANAGEMENT_INTERNAL After a Driver Update

If the problem started immediately after updating NVIDIA, AMD, or Intel graphics drivers:

1. Roll back the driver.
2. Restart Windows.
3. Test the system.
4. If necessary, uninstall the current driver.
5. Install a previous known-stable version.

For laptops, consider the OEM-provided driver if generic graphics drivers cause problems.

VIDEO_MEMORY_MANAGEMENT_INTERNAL After Windows Update

If the error started immediately after Windows Update:

Check:

Settings → Windows Update → Update history

Determine whether Windows installed:

• A graphics driver
• A cumulative update
• A firmware update
• Another hardware driver

If a graphics driver was automatically replaced, reinstall the appropriate OEM/GPU manufacturer driver.

VIDEO_MEMORY_MANAGEMENT_INTERNAL on Laptops

Laptop troubleshooting requires additional consideration because many notebooks use hybrid graphics.

For example:

Intel integrated GPU + NVIDIA dedicated GPU

or

AMD integrated GPU + NVIDIA/AMD dedicated GPU

The integrated and dedicated graphics drivers may depend on OEM-specific configurations.

For laptops:

• Check the laptop manufacturer's support page first.
• Install chipset and graphics drivers appropriate for the exact model.
• Check BIOS updates.
• Monitor GPU and CPU temperatures.
• Test with and without external displays.
• Investigate docking stations if crashes occur while docked.

When Should You Suspect GPU Hardware Failure?

Hardware failure becomes more likely when several of these conditions are present:

• BSOD continues after clean driver installation
• Multiple driver versions produce the same error
• Windows has been clean-installed and the problem remains
• GPU produces visible artifacts
• GPU fails under load
• Crashes occur in multiple games
• Another GPU works correctly in the same PC
• Original GPU fails in another compatible system
• VRAM diagnostics report errors
• Problems occur outside Windows

No single symptom should be treated as absolute proof. Hardware should ideally be isolated through substitution testing.

Recommended Troubleshooting Order

For most systems, use this order:

1. Check what changed before the error started.
2. Install or roll back the graphics driver.
3. Restore GPU settings to default.
4. Install Windows updates where appropriate.
5. Run SFC.
6. Run DISM.
7. Test system RAM.
8. Monitor GPU temperature.
9. Update chipset drivers.
10. Check BIOS/UEFI updates.
11. Check GPU power connections.
12. Investigate PSU stability.
13. Analyze minidump files.
14. Test integrated graphics or another GPU.
15. Investigate GPU/VRAM hardware failure.

This approach reduces unnecessary hardware replacement.

Commands Quick Reference

System File Checker

sfc /scannow

Check Windows Component Store

DISM /Online /Cleanup-Image /ScanHealth

Repair Windows Component Store

DISM /Online /Cleanup-Image /RestoreHealth

Windows Memory Diagnostic

mdsched.exe

DirectX Diagnostic Tool

dxdiag

System Information

msinfo32

Event Viewer

eventvwr.msc

These commands should normally be run from an administrator account where elevated privileges are required.

Important Technician Note

Never diagnose VIDEO_MEMORY_MANAGEMENT_INTERNAL solely from the stop-code name.

"VIDEO MEMORY" can lead users to immediately conclude that the graphics card's VRAM has failed. That conclusion can be incorrect.

The failure may originate from:

• Graphics driver
• GPU
• VRAM
• RAM
• Motherboard
• PCIe interface
• Power supply
• Firmware
• Windows corruption
• Overclocking

For repeated BSODs, crash-dump analysis combined with hardware isolation is significantly more reliable than replacing components based solely on the stop code.

Frequently Asked Questions (FAQ)

1. What is VIDEO_MEMORY_MANAGEMENT_INTERNAL?

VIDEO_MEMORY_MANAGEMENT_INTERNAL is a Windows BSOD indicating that the operating system detected a serious internal error while managing graphics/video memory.

2. What is the bug check code for VIDEO_MEMORY_MANAGEMENT_INTERNAL?

The associated bug check is:

0x0000010E

It is commonly shortened to 0x10E.

3. Does VIDEO_MEMORY_MANAGEMENT_INTERNAL mean my graphics card is faulty?

Not necessarily.

A faulty GPU or VRAM can cause the error, but graphics drivers, RAM, overclocking, overheating, BIOS issues, power instability, and other problems can produce similar symptoms.

4. Can NVIDIA drivers cause VIDEO_MEMORY_MANAGEMENT_INTERNAL?

Yes.

Corrupted, incompatible, or unstable NVIDIA graphics drivers can contribute to this BSOD.

However, the presence of an NVIDIA GPU does not prove that its driver is responsible.

5. Can AMD graphics cause this BSOD?

Yes.

AMD graphics hardware or drivers can be involved, just as NVIDIA or Intel graphics components can.

6. Can Intel graphics cause VIDEO_MEMORY_MANAGEMENT_INTERNAL?

Yes.

Systems using Intel integrated graphics can experience graphics-memory-related BSODs because integrated graphics relies heavily on shared system memory and graphics drivers.

7. Can faulty RAM cause VIDEO_MEMORY_MANAGEMENT_INTERNAL?

Yes.

System RAM participates in many graphics-memory operations, particularly with integrated graphics.

Testing RAM is therefore an important troubleshooting step.

8. Can overheating cause this error?

Yes.

GPU overheating can cause graphics instability and may contribute to driver crashes or BSODs.

Check temperatures if the problem appears during gaming or rendering.

9. Why does VIDEO_MEMORY_MANAGEMENT_INTERNAL happen only while gaming?

Gaming heavily stresses:

• GPU core
• VRAM
• System RAM
• Cooling
• Power supply

A marginally unstable component may therefore work normally on the desktop but fail during gaming.

10. Can GPU overclocking cause 0x10E?

Yes.

GPU core or VRAM overclocking can create memory errors and graphics instability.

Restore factory/default settings while troubleshooting.

11. Can undervolting cause the error?

Yes.

An unstable undervolt can prevent the GPU from receiving sufficient voltage under certain workloads.

Restore default settings and retest.

12. Should I reinstall Windows?

Usually not as the first troubleshooting step.

Investigate drivers, RAM, temperatures, GPU settings, Windows integrity, and crash dumps first.

A Windows reinstall is more appropriate after reasonable software and hardware diagnostics have failed to identify the problem.

13. Should I replace my graphics card?

Do not replace the GPU based solely on the VIDEO_MEMORY_MANAGEMENT_INTERNAL stop code.

GPU replacement becomes more reasonable when hardware testing and substitution strongly indicate that the graphics card is defective.

14. What is dxgkrnl.sys?

dxgkrnl.sys is a Microsoft Windows DirectX graphics kernel component.

If it appears in a dump, investigate the entire graphics stack rather than assuming that dxgkrnl.sys itself is damaged.

15. What is dxgmms2.sys?

dxgmms2.sys is associated with Windows graphics memory management.

Its appearance in a crash dump can be related to graphics drivers, GPU hardware, memory instability, or other graphics subsystem problems.

16. Where are Windows BSOD dump files stored?

Small crash dumps are commonly stored in:

C:\Windows\Minidump

The system may also create:

C:\Windows\MEMORY.DMP

depending on the configured crash-dump settings.

17. Can WinDbg diagnose VIDEO_MEMORY_MANAGEMENT_INTERNAL?

Yes.

WinDbg can analyze Windows crash dumps and provide bugcheck parameters, call stacks, module information, and other diagnostic evidence.

A commonly used command is:

!analyze -v

18. Can a bad power supply cause graphics BSODs?

Yes.

An inadequate or failing PSU can destabilize a high-power graphics card, particularly during sudden load changes.

19. Can BIOS updates fix VIDEO_MEMORY_MANAGEMENT_INTERNAL?

Potentially.

BIOS/UEFI updates can resolve hardware compatibility, memory, PCIe, and power-management issues.

Only install firmware intended for the exact computer or motherboard model.

20. What should I do if VIDEO_MEMORY_MANAGEMENT_INTERNAL keeps returning?

If the error persists:

• Analyze the crash dumps.
• Test RAM.
• Test the GPU.
• Check GPU temperature.
• Check the power supply.
• Restore default clock settings.
• Try another graphics driver.
• Update chipset/BIOS where appropriate.
• Test with another GPU or integrated graphics.

Repeated 0x10E crashes should be investigated systematically instead of repeatedly reinstalling the same graphics driver.

Conclusion

The VIDEO_MEMORY_MANAGEMENT_INTERNAL (0x0000010E) BSOD indicates that Windows encountered a serious problem within the graphics/video-memory management subsystem.

Although graphics drivers are a common starting point, the stop code should not automatically be interpreted as proof of a defective graphics card.

Possible causes include graphics-driver corruption, GPU or VRAM instability, faulty system RAM, excessive temperatures, unstable overclocking or undervolting, PCIe problems, power-supply instability, BIOS/UEFI issues, chipset drivers, and Windows system corruption.

Start with driver and software troubleshooting, restore the hardware to default settings, check RAM and temperatures, and analyze Windows crash dumps. If the error continues, use hardware substitution testing to isolate the GPU, RAM, PSU, and motherboard.

A methodical diagnosis is the safest way to find the actual cause and avoid unnecessary replacement of expensive hardware.

#VIDEO_MEMORY_MANAGEMENT_INTERNAL #VideoMemoryManagement #BSOD #BlueScreen #Windows11 #Windows10 #WindowsBSOD #StopCode #Error0x10E #0x0000010E #GPU #GraphicsCard #GPUError #GPUCrash #GPUMemory #VRAM #VRAMError #GraphicsDriver #DisplayDriver #NVIDIA #AMD #Radeon #IntelGraphics #DirectX #dxgkrnl #dxgmms2 #WindowsTroubleshooting #PCRepair #ComputerRepair #WindowsRepair #TechSupport #ITSupport #HardwareTroubleshooting #DriverTroubleshooting #GPUDriver #GraphicsCardError #GamingPC #GamingBSOD #GPUOverheating #GPUOverclocking #MemoryError #WindowsMemoryDiagnostic #SFC #DISM #WinDbg #CrashDump #Minidump #WindowsError #ComputerTroubleshooting #BSODFix