| Previous | Next |
| MF_E_NO_BITPUMP | MF_E_RT_WORKQUEUE_CLASS_NOT_SPECIFIED |
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 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 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 for it: 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 this result comparison changes exactly that variable; changing content, account, proxy, device, components, and version together makes attribution impossible.
| Outcome | Interpretation |
|---|---|
| The same checkpoint now succeeds | The changed condition belongs to the producing boundary for it. |
| 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 result 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; compare this boundary specifically with it. |
MF_E_MEDIAPROC_WRONGSTATE | MediaProc is in the wrong state; compare this boundary specifically with it. |
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; compare this boundary specifically with it. |
The important distinction is this: E_OUTOFMEMORY can describe general allocation failure, while this code points to Media Foundation real-time resources. 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 it.
A confirmed it repair produces the requested stream, attribute, state transition, license decision, store callback, or setup result. Suppressing it, broadly enabling legacy controls, or falling back to unrelated content is not proof of repair.
References
- Media Foundation architecture — reference used for the checkpoint.
- Media Foundation error codes — reference used for the checkpoint.
- Media samples — reference used for the checkpoint.
- IMFVideoSampleAllocator interface — reference used for the checkpoint.
Looking for a different code? Search another status or error code.