What does HRESULT 0xC00D36F7 (MF_E_RT_OUTOFMEMORY) mean?

MF_E_RT_OUTOFMEMORY

Locate the failing boundary

MF_E_RT_OUTOFMEMORY (0xC00D36F7) is a failure result from Windows Media Foundation. The generated section above already contains the platform message; the useful extra information is that this result isolates the real-time media path exhausted the memory budget or pool reserved for time-sensitive processing.

The producer is the real-time work queue, allocator, or hardware pipeline rather than ordinary process heap allocation, so diagnosis should begin with that object and its state rather than with a broad reinstall or an unrelated codec change. A representative occurrence is a video path retains surfaces across callbacks until the real-time allocator cannot satisfy the next sample request.

Read the call sequence as a timeline. First, the application reaches the real-time work queue, allocator, or hardware pipeline rather than ordinary process heap allocation. Next, the component evaluates the real-time media path exhausted the memory budget or pool reserved for time-sensitive processing. Only after the MF_E_RT_OUTOFMEMORY checkpoint can a wrapper, user interface, or fallback path emit a less specific message.

Evidence that survives retries

• Exact request: method name, all identifiers, units, flags, stream number, requested action, and MF_E_RT_OUTOFMEMORY.
• Object state: sample counts, buffer sizes, outstanding references, allocator limits, queue depth, frame dimensions, and the point where samples stop being released.
• Correlation for MF_E_RT_OUTOFMEMORY: callback cookie, object generation, URL or file identity, device identity, and timestamps from the same attempt.
• Underlying cause: the first Win32, COM, network, driver, policy, or component error reported before 0xC00D36F7.

A controlled verification sequence

Use one controlled experiment: reduce queue depth or frame size in one controlled run and verify that sample references return to the allocator. A useful MF_E_RT_OUTOFMEMORY comparison changes exactly that variable; changing content, account, proxy, device, components, and version together makes attribution impossible.

Nearby results that mean something else

The important distinction is this: E_OUTOFMEMORY can describe general allocation failure, while this code points to Media Foundation real-time resources. For MF_E_RT_OUTOFMEMORY, searching only for the visible English message collapses different states; the constant and 0xC00D36F7 retain the boundary.

Repair at the owning layer

Apply the narrow remedy: release retained samples, bound queues, and configure realistic allocator capacity; adding unrelated virtual memory may not fix a real-time pool. Then discard stale media objects, pending callbacks, cached provider sessions, or installer state as appropriate and rerun the exact request that originally returned MF_E_RT_OUTOFMEMORY.

A confirmed MF_E_RT_OUTOFMEMORY repair produces the requested stream, attribute, state transition, license decision, store callback, or setup result. Suppressing MF_E_RT_OUTOFMEMORY, broadly enabling legacy controls, or falling back to unrelated content is not proof of repair.

References

• Media Foundation architecture — reference used for the MF_E_RT_OUTOFMEMORY checkpoint.
• Media Foundation error codes — reference used for the MF_E_RT_OUTOFMEMORY checkpoint.
• Media samples — reference used for the MF_E_RT_OUTOFMEMORY checkpoint.
• IMFVideoSampleAllocator interface — reference used for the MF_E_RT_OUTOFMEMORY checkpoint.

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