What does HRESULT 0x80040294 (VFW_E_PIN_ALREADY_BLOCKED) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

IPinFlowControl::Block() has been called on another thread. The current thread cannot make.

Previous	Next
VFW_E_PIN_ALREADY_BLOCKED_ON_THIS_THREAD	VFW_E_CERTIFICATION_FAILURE

VFW_E_PIN_ALREADY_BLOCKED

Exact result and bit fields

VFW_E_PIN_ALREADY_BLOCKED has the unsigned HRESULT value 2147746452 (0x80040294) and the signed 32-bit representation -2147220844. AllStat describes it as “IPinFlowControl::Block() has been called on another thread. The current thread cannot make any assumptions about this pin's block state”. In the operation that produces this result, IPinFlowControl::Block finds that another thread has already established the pin block, so the current thread cannot assume or replace that state.

The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 660 (0x0294). These fields classify this result, but they do not identify which filter, thread, device, file or graph generation returned it.

Contract boundary

This result is a DirectShow contract failure whose owner must be identified from the exact interface, filter instance, graph generation and operation stage.

The practical owner to locate for this HRESULT is the filter graph, device or persisted configuration that first returned the result. When handling this result, capture the native result before a wrapper replaces it with a generic exception, and keep the graph generation or object identity with the record.

Evidence worth preserving

Log the interface and method, filter CLSID and friendly name, process and thread, graph state, connected pin names, media-type summary, renderer or device identity where relevant, and the first preceding HRESULT. Record lengths and hashes instead of raw content when the incident includes media paths, device identifiers, registry values and stream metadata.

Evidence 1 for this HRESULT: pin identity, owning and calling thread IDs.
Evidence 2 for this HRESULT: block event handle and operation correlation IDs.
Evidence 3 for this HRESULT: graph lock order and outstanding reconfiguration.

Conditions that can produce it

Cause 1 for this HRESULT: two reconfiguration controllers race for the same pin.
Cause 2 for this HRESULT: stop and dynamic reconnect paths use separate locks.
Cause 3 for this HRESULT: the owning thread is delayed or abandoned without cleanup.

Step-by-step diagnosis

Capture it at the first native return, not only at the top-level playback failure.
identify the exact graph stage described here: IPinFlowControl::Block finds that another thread has already established the pin block, so the current thread cannot assume or replace that state.
compare the live object state, topology and input with the documented interface preconditions.
Before changing filters, drivers, registry data or media for this HRESULT, collect the code-specific evidence below.
Test one evidence-backed the correction on the smallest reproducible graph.
Verify that the corrected run no longer returns it and does not merely replace it with a nearby HRESULT.

Retry and recovery

Retry rule for this HRESULT: Retry only after the owning thread releases the block and the graph generation is revalidated. A safe it retry must use a changed capability, state, object generation or input. While recovering from it, preserve cancellation and avoid replaying side effects when the original operation may have partially completed.

Correction strategy

Action 1 for this HRESULT: serialize topology changes through one coordinator.
Action 2 for this HRESULT: wait for the owner to complete rather than issuing a second block.
Action 3 for this HRESULT: provide cancellation and cleanup for abandoned reconfiguration.

Example incident

A UI reconnect and a device-change handler both block the same output pin; a single graph-operation queue prevents it. This example keeps the diagnosis at the specific the boundary instead of treating every DirectShow failure as a codec reinstall problem.

Implementation notes

Code that handles it should preserve the original HRESULT, the failed stage and an opaque correlation identifier. After it, do not infer success from partial graph construction, and do not continue using interfaces retained from a graph or device generation that has already changed.

Operational remediation for this HRESULT should favor supported component installation, device configuration and documented DirectShow calls. Manual registry or driver changes are appropriate only when the collected evidence for this HRESULT points to that layer and a rollback is available.

How it differs from nearby results

This result_ON_THIS_THREAD reports duplicate acquisition by one thread; it reports conflicting ownership by another thread. Keep those cases separate in telemetry, UI messages and retry policy because their next actions are different.

Official Microsoft references

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