| Previous | Next |
| MF_E_RT_WOULDBLOCK | MF_E_RT_OUTOFMEMORY |
MF_E_NO_BITPUMP
Interpret the result in the pipeline
MF_E_NO_BITPUMP means an internal data-pumping component required by the selected Media Foundation path could not be located or created.
The result comes from the internal pipeline assembly step rather than the application media data itself. A representative case is a damaged platform component or incompatible custom media component prevents creation of the internal pump during graph setup.
Key observations
| Observation | What to capture |
|---|---|
| Primary discriminator | the topology, source and sink types, installed component versions, first preceding activation error, and whether the failure reproduces in a stock pipeline |
| Owning object | the internal pipeline assembly step rather than the application media data itself, including its object identity and generation |
| Timeline marker | the call immediately before an internal data-pumping component required by the selected Media Foundation path could not be located or created and the completion event, callback, or state change that followed |
| Comparison artifact | one known-good run that changes only this condition: rebuild a minimal topology with system components and compare it with the failing custom-component graph |
An internal data-pumping component required by the selected Media Foundation path could not be located or created. Preserve the original internal pipeline assembly step rather than the application media data itself and the first result in the chain: a later UI message can replace this precise code with a generic playback, setup, network, or device failure.
Minimal experiment
- Record this result,
0xC00D36F6, the returning method, process architecture, Windows build, and component version. - Capture the topology, source and sink types, installed component versions, first preceding activation error, and whether the failure reproduces in a stock pipeline before retry logic changes the object.
- Perform this narrow comparison: rebuild a minimal topology with system components and compare it with the failing custom-component graph.
- Keep the input, account, URL, device, media type, and requested action unchanged unless one is the single tested variable.
- After correcting this result, create a fresh object or process where lifecycle state may have been retained, then repeat the original call.
What the result does not prove
This result does not by itself prove a machine-wide media-platform failure. In this case, a missing decoder normally yields a topology or codec error, not this internal bit-pump result. The result evidence does not justify deleting license stores, clearing every proxy setting, installing codec packs, or rewriting media files before its producer is identified.
Similar messages, different conditions
| Result | Different condition |
|---|---|
MF_E_RT_OUTOFMEMORY | No more RT memory available. |
MF_E_MEDIAPROC_WRONGSTATE | MediaProc is in the wrong state. |
MF_E_DISABLED_IN_SAFEMODE | The Media Foundation platform is disabled when the system is running in Safe Mode. |
Targeted recovery
The supported corrective direction is to repair or update the component installation and remove the custom element that prevents pipeline assembly; applications should not instantiate undocumented internals.
For an incident, keep the symbolic constant together with 0xC00D36F6. That pairing preserves the exact failure identity when signed integer fields or wrapper logs obscure the original Media Foundation or Windows Media facility.
Technical references
Looking for a different code? Search another status or error code.