HRESULT 0x887A0024 (DXGI_ERROR_REMOTE

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

The device has been removed during a remote session because the remote computer ran out of memory.

Previous	Next
DXGI_ERROR_REMOTE_CLIENT_DISCONNECTED	DXGI_ERROR_MODE_CHANGE_IN_PROGRESS

DXGI_ERROR_REMOTE_OUTOFMEMORY

What Windows rejected: remote outofmemory

DXGI_ERROR_REMOTE_OUTOFMEMORY (0x887A0024) belongs to the dxgi error layer. It marks the remote computer could not retain the device because its memory budget was exhausted, rather than a generic rendering failure. The object that owns the decision is remote-session graphics memory budget.

DXGI_ERROR_REMOTE_OUTOFMEMORY: Do not erase all shader caches or recreate every graphics object before preserving the first failing call. For DXGI_ERROR_REMOTE_OUTOFMEMORY, Cache, policy, remote-session and device-lifetime failures have different recovery rules. For DXGI_ERROR_REMOTE_OUTOFMEMORY, the built-in one-line message identifies the immediate result; diagnosis also needs the producing API, object ownership and the display generation current at the time.

Build a useful diagnostic record

Capture item	Why it matters for `DXGI_ERROR_REMOTE_OUTOFMEMORY`
Object identity	remote-session graphics memory budget
Rejected boundary	the remote computer could not retain the device because its memory budget was exhausted
Decisive capture	remote host commit charge, GPU and system budgets, resource sizes, adapter identity, session count and removed reason
Current graph state	DXGI factory, adapter, device, resource or cache session
Supporting trace	DXGI debug messages, adapter LUID, driver version, device-removal reason where applicable and the exact API parameters

For DXGI_ERROR_REMOTE_OUTOFMEMORY, preserve the unsigned HRESULT, symbolic name, first failing API and timestamp in one record. If cleanup later fails too, keep that secondary result separately from DXGI_ERROR_REMOTE_OUTOFMEMORY.

Separate state from capability

Freeze the DXGI_ERROR_REMOTE_OUTOFMEMORY generation. Record remote host commit charge, GPU and system budgets, resource sizes, adapter identity, session count and removed reason. Before diagnosing DXGI_ERROR_REMOTE_OUTOFMEMORY, do not resize, hot-plug, recreate or release the object under examination.
Run the narrow DXGI_ERROR_REMOTE_OUTOFMEMORY comparison. reduce render-target and texture allocations on a controlled remote host and compare the removal threshold. During the DXGI_ERROR_REMOTE_OUTOFMEMORY comparison, keep every driver, monitor, resource format and unrelated policy unchanged.
Observe the layer after DXGI_ERROR_REMOTE_OUTOFMEMORY. For DXGI_ERROR_REMOTE_OUTOFMEMORY, if the exact check passes, record the next HRESULT or visible outcome. A different downstream result shows that the DXGI_ERROR_REMOTE_OUTOFMEMORY boundary was crossed.
Repeat DXGI_ERROR_REMOTE_OUTOFMEMORY through a lifecycle transition. For DXGI_ERROR_REMOTE_OUTOFMEMORY, exercise one relevant resize, mode switch, device recreation, hot-plug or session change and confirm that this result does not reuse stale handles.

The comparison with DXGI_ERROR_REMOTE_CLIENT_DISCONNECTED is especially useful: DXGI_ERROR_REMOTE_CLIENT_DISCONNECTED is driven by session connectivity rather than memory pressure. For DXGI_ERROR_REMOTE_OUTOFMEMORY, recording both names prevents a broad “graphics error” label from merging distinct ownership, capability and lifetime problems.

Verify the repaired path

Shrink or stream resources, release unused allocations and recreate the device only after the remote budget recovers. Repair of DXGI_ERROR_REMOTE_OUTOFMEMORY is complete only when the original call succeeds or returns its documented nonfatal status and the same lifetime test remains correct after a second display transition.

The DXGI_ERROR_REMOTE_OUTOFMEMORY trace identifies one producing API and one current graphics object, rather than only the final UI symptom.
The passing run changes exactly the condition described for DXGI_ERROR_REMOTE_OUTOFMEMORY; unrelated adapter, monitor and application state remains unchanged.
For DXGI_ERROR_REMOTE_OUTOFMEMORY, debug-layer, ETW or driver diagnostics no longer report the rejected remote-session graphics memory budget contract during the same scenario.
The application handles recurrence of DXGI_ERROR_REMOTE_OUTOFMEMORY without an unbounded retry loop, leaked resource, duplicate composition target or stale topology handle.

Implementation notes for `DXGI_ERROR_REMOTE_OUTOFMEMORY`

For DXGI_ERROR_REMOTE_OUTOFMEMORY, log DXGI debug messages, adapter LUID, driver version, device-removal reason where applicable and the exact API parameters. When the DXGI_ERROR_REMOTE_OUTOFMEMORY path returns a count, size, status flag or replacement object, retain it even on a nonfatal result because it can direct the next call.

A production fallback for DXGI_ERROR_REMOTE_OUTOFMEMORY should be explicit: pause rendering, re-enumerate, rebuild one cache entry, recreate a device, or decline a protected path only when this layer calls for that action. Reinstalling every display component, deleting all caches or forcing a resolution change is not an evidence-based fix for DXGI_ERROR_REMOTE_OUTOFMEMORY.

Technical references

Microsoft: DXGI error codes — background for the remote-session graphics memory budget boundary involved in DXGI_ERROR_REMOTE_OUTOFMEMORY.
Microsoft: DXGI overview — background for the remote-session graphics memory budget boundary involved in DXGI_ERROR_REMOTE_OUTOFMEMORY.
Microsoft: Direct3D 12 shader cache StoreValue — background for the remote-session graphics memory budget boundary involved in DXGI_ERROR_REMOTE_OUTOFMEMORY.
Microsoft: Handle device-removed scenarios — background for the remote-session graphics memory budget boundary involved in DXGI_ERROR_REMOTE_OUTOFMEMORY.

Looking for a different code? Search another status or error code.