Edit

Bug Check 0x10E: VIDEO_MEMORY_MANAGEMENT_INTERNAL

  • Article

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

This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

VIDEO_MEMORY_MANAGEMENT_INTERNAL Parameters

Parameter 1 describes the type of video memory error. 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.
Parameter 1 Cause of Error

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.

0x1C

VidMm is trying to rotate an allocation back from the frame buffer but the VA isn't rotated where it was expected.

0x1D

VidMm is trying to use paging buffer that have been unmapped.

0x1E

VidMm is trying to do an operation from the wrong process context.

0x1F

VidMm is trying to mark an allocation with a lower fence than it is currently marked with.
Parameter 1 Cause of Error

0x20

VidMm is trying to manipulate an allocation is assumed was idle but isn't.

0x21

VidMm is trying to flush the paging buffer outside of preparation or unflushed data was found in the paging buffer at the start of a preparation.

0x22

VidMm is trying to rotate a VA to an invalid range.

0x23

The scheduler wake up a thread before the wait was completed.

0x24

An allocation is being destroyed which has outstanding references to its backing store... physical memory will be leaked.

0x25

The GPU attempted to write over an undefined area of the aperture.

0x26

A VIDMM_LOCAL_ALLOC was closed from a process other than its owner.

0x27

A VIDMM_ALLOC was not reprogrammed at the current split point.

0x28

An unexpected exception happened when referencing a global allocation.

0x29

An overflow or an underflow was detected when manipulating a VIDMM_ALLOC DMA reference count.

0x2A

VidMm is trying to free the last reference to the currently displaying allocation.

0x2B

VidMm is trying to free the an invalid Cpu Host Aperture page range.

0x2C

VidMm is trying to map a page range to the Cpu Host Aperture which was previously already mapped. Best case memory leak.

0x2D

Call to DdiMapCpuHostAperture failed, but was expected to succeed.

0x2E

Call to DdiUnmapCpuHostAperture failed, but was expected to succeed.

0x2F

Reported range size does not match the number of elements allocated for the array.
Parameter 1 Cause of Error

0x30

An error occurred during a GPU virtual address operation.

0x31

The paging queue being deleted is still being processed by the VidMm worker thread.

0x32

The paging queue being deleted still contains running packets.

0x33

The device is being destroyed but there are still allocations resident on it.

0x34

A heap allocation has received a state transition event incompatible with current state.

0x35

The paging request failed at default paging queue.

0x36

The paging request failed on a paging packet or device resume that was previously marked as unrecoverable, and was expected to succeed subsequent calls.

0x37

VidMm failed to lock pages of an allocation during TDR.

0x38

VidMm is freeing an allocation that still has paging packets referencing it.

0x39

VidMm is putting a device to the indefinite penalty box, but it has paging packets.

0x3A

VidMm worker thread is running a paging queue that became suspended.

0x3B

Memory is still rotated to the frame buffer during D3 transition.

0x3C

Memory is still allocated or mapped to the CPU host aperture. This indicates memory may still be rotated to the frame buffer during a D3 transition.

0x3D

An invalid segment group was specified during an operation.

0x3E

Failed to acquire the VIDMM_ALLOC rundown protection.

0x3F

Resuming the scheduler device during a move or defragment operation conflicts with the penalty box state. This implies we will be resuming the scheduler for a device whose memory is not accessible yet.
Parameter 1 Cause of Error

0x40

Attempting to start a preparation bracket while another operation is already in progress.

0x41

Deleting a VIDMM_CROSSADAPTER_ALLOC that has non-zero residency or adapter count.

0x42

Deleting a VIDMM_CROSSADAPTER_ALLOC that has a negative residency or adapter count.

0x43

While saving or restoring the reserved frame buffer content, we were unable to map at least one page of the section object to make forward progress.

0x44

Memory budget bookkeeping ended up in an underflow.

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.