| Previous | Next |
| MF_E_NO_BITPUMP | MF_E_RT_WORKQUEUE_CLASS_NOT_SPECIFIED |
MF_E_RT_OUTOFMEMORY
Where the result originates
MF_E_RT_OUTOFMEMORY means the real-time media path exhausted the memory budget or pool reserved for time-sensitive processing.
The result comes from the real-time work queue, allocator, or hardware pipeline rather than ordinary process heap allocation. A representative case 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. A wrapper, user interface, or fallback path can report a less specific message afterward.
Evidence that survives retries
- Exact request: method name, all identifiers, units, flags, stream number, requested action, and this result.
- Object state: sample counts, buffer sizes, outstanding references, allocator limits, queue depth, frame dimensions, and the point where samples stop being released.
- Correlation: callback cookie, object instance, 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 comparison for this result changes exactly that variable; changing content, account, proxy, device, components, and version together makes attribution impossible.
| Outcome | Interpretation |
|---|---|
| The same operation now succeeds | The changed precondition was relevant to the failure. |
| A more specific earlier HRESULT appears | Preserve it; this result was probably a wrapper or terminal state. |
| The operation advances and fails later | The condition is fixed even though the complete workflow still has another defect. |
| No behavior changes | Restore the original baseline and test another documented prerequisite instead of stacking workarounds. |
Nearby results that mean something else
| Related code | Why it is not interchangeable |
|---|---|
MF_E_NO_BITPUMP | Internal; Bitpump not found. |
MF_E_MEDIAPROC_WRONGSTATE | MediaProc is in the wrong state. |
MF_E_FORMAT_CHANGE_NOT_SUPPORTED | The data specified for the media type is supported, but would require a format change, which is not supported by this object. |
The important distinction is this: E_OUTOFMEMORY can describe general allocation failure, while this code points to Media Foundation real-time resources. Use the symbolic constant and 0xC00D36F7 value to distinguish states that share a similar visible message.
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 it.
References
Looking for a different code? Search another status or error code.