Bug Check 0x10E: VIDEO_MEMORY_MANAGEMENT_INTERNAL
The VIDEO_MEMORY_MANAGEMENT_INTERNAL bug check has a value of 0x0000010E. This indicates that the video memory manager has encountered a condition that it is unable to recover from.
Important Info If You Have Received a STOP Code
If you received a blue screen error, or stop code, the computer has shut down abruptly to protect itself from data loss. A hardware device, its driver, or related software might have caused this error. If your copy of Windows came with your computer, call the manufacturer of your computer. If you purchased Windows separately from your computer, Microsoft provides support. To find contact info for Microsoft or your computer manufacturer, Contact Support.
If you have experience with computers and want to try to recover from this error, follow the steps provided in the Microsoft article Resolving STOP (Blue Screen) Errors in Windows.
These actions might prevent an error like this from happening again:
- Download and install updates and device drivers for your computer from Windows Update.
- Scan your computer for computer viruses.
- Check your hard disk for errors.
VIDEO_MEMORY_MANAGEMENT_INTERNAL Parameters
The following parameters are displayed on the blue screen. Parameter 1 is the only parameter of interest; this identifies the exact violation. Values for Parameter 1 that do not appear in this table must be individually examined.
| Parameter 1 | Cause of Error |
|---|---|
|
0x1 |
An attempt was made to rotate a non-rotate range. |
|
0x2 |
An attempt was made to destroy a non-empty process heap. |
|
0x3 |
An attempt to unmap from an aperture segment failed. |
|
0x4 |
A rotation in a must-succeed path failed. |
|
0x5 |
A deferred command failed. |
|
0x6 |
An attempt was made to reallocate resources for an allocation that was having its eviction canceled. |
|
0x7 |
An invalid attempt was made to defer free usage. |
|
0x8 |
The split direct memory access (DMA) buffer contains an invalid reference. |
|
0x9 |
An attempt to evict an allocation failed. |
|
0xA |
An invalid attempt to use a pinned allocation was made. |
|
0xB |
A driver returned an invalid error code from BuildPagingBuffer. |
|
0xC |
A resource leak was detected in a segment. |
|
0xD |
A segment is being used improperly. |
|
0xE |
An attempt to map an allocation into an aperture segment failed. |
|
0xF |
A driver returned an invalid error code from AcquireSwizzlingRange. |
|
0x10 |
A driver returned an invalid error code from ReleaseSwizzlingRange. |
|
0x11 |
An invalid attempt to use an aperture segment was made. |
|
0x12 |
A driver overflowed the provided DMA buffer. |
|
0x13 |
A driver overflowed the provided private data buffer. |
|
0x14 |
An attempt to purge all segments failed. |
|
0x15 |
An attempt was made to free a virtual address descriptor (VAD) that was still in the rotated state |
|
0x16 |
A driver broke the guaranteed DMA buffer model contract. |
|
0x17 |
An unexpected system command failure occurred. |
|
0x18 |
An attempt to release a pinned allocation's resource failed. |
|
0x19 |
A driver failed to patch a DMA buffer. |
|
0x1A |
The owner of a shared allocation was freed. |
|
0x1B |
An attempt was made to release an aperture range that is still in use. |
|
0x25 |
The GPU attempted to write over an undefined area of the aperture. |
Cause
This bug check is usually caused by a video driver behaving improperly.
Resolution
If the problem persists, check Windows Update for an updated video driver.
Send comments about this topic to Microsoft
Build date: 4/9/2013
