| Previous | Next |
| EVENT_E_CANT_MODIFY_OR_DELETE_CONFIGURED_OBJECT | EVENT_E_INVALID_EVENT_CLASS_PARTITION |
VFW_E_BADALIGN
Meaning and numerical form
VFW_E_BADALIGN is HRESULT 2147746318 (0x8004020E; signed -2147220978). AllStat records its meaning as “An invalid alignment was specified”. In practical terms, it is returned when DirectShow allocator negotiation receives a buffer-alignment requirement that is invalid or cannot be honored.
The severity bit in 0x8004020E is set, so this result is a failure result rather than a success or informational status. Its facility is 4 (FACILITY_ITF) and its low 16-bit code is 526 (0x020E). Those fields classify the value but do not identify the component instance, call, object or input that produced it.
Where the failure belongs
This result belongs to DirectShow filter-graph processing. DirectShow is a legacy, component-based media pipeline. Graph state, pin transport, negotiated media types, allocators, clocks, samples, renderers and source filters contribute separate contracts to the operation. The decisive condition is this: DirectShow allocator negotiation receives a buffer-alignment requirement that is invalid or cannot be honored. Record the first native producer instead of relying only on a framework exception translated several layers later.
Do not infer from this result alone that reinstalling, rebooting or repeating the whole workflow is appropriate. Because it can cross process and language boundaries, its correction depends on the object identity, lifecycle generation, input and state at the first failing call.
Diagnostic sequence
- Capture this result at the first native return and identify the exact object and method.
- Confirm that the observed path matches this the condition: DirectShow allocator negotiation receives a buffer-alignment requirement that is invalid or cannot be honored.
- compare the live state with the method contract before changing configuration.
- collect the code-specific evidence listed above and preserve any more specific preceding error.
- change one evidence-backed cause at a time, then repeat the smallest operation that can prove the correction.
- Add a regression check that distinguishes it from the related outcomes described below.
Likely causes
- Possible cause 1 for it: cbAlign is zero or not supported by the allocator.
- Possible cause 2 for it: upstream and downstream filters require incompatible alignment.
- Possible cause 3 for it: a custom allocator reports properties different from those it actually provides.
Evidence to collect
A useful it record includes the native API or interface method, component or CLSID, process and thread IDs, architecture, apartment where relevant, operation correlation ID, elapsed time, input identity, and the first state-changing event before failure. When diagnosing it, preserve IErrorInfo, an inner HRESULT, Win32 status, device event or provider message when available.
- Capture 1 for it: requested and actual ALLOCATOR_PROPERTIES values.
- Capture 2 for it: the filter that proposed each alignment.
- Capture 3 for it: buffer addresses and SetProperties return data.
Telemetry for it should retain types, lengths, hashes, stable opaque identifiers and lifecycle generations while redacting content and credentials. This makes repeated incidents comparable without exposing media content, file paths, device identifiers or credentials.
Correction and retry boundary
- Corrective action 1 for it: supply a valid nonzero alignment supported by both pins.
- Corrective action 2 for it: honor the actual properties returned by the allocator.
- Corrective action 3 for it: correct custom allocator calculations for prefix, size and alignment together.
Retry guidance for it. Retry after renegotiating allocator properties while the allocator is decommitted and buffers are released. A it retry must avoid this hazard: replay obsolete samples, duplicate graph changes or reuse interfaces from an earlier topology generation. It must also preserve the evidence needed to locate the original producer of it.
Practical scenario
A hardware transform requires 16-byte buffers but a custom allocator advertises an impossible alignment value; correcting cbAlign resolves it. The result scenario narrows the result to a reproducible contract boundary and supplies a concrete before-and-after test.
Developer and operational guidance
Code handling it should log the failed stage before cleanup, keep ownership and lifecycle transitions explicit, and avoid converting every failure into a generic message. Tests for it should cover the primary cause, one adjacent HRESULT and the retry boundary so a future change cannot turn a deterministic contract failure into an uncontrolled loop.
Operational repair for it should use supported filter installation, device, graph-building and renderer configuration paths. Avoid unsupported configuration edits or component replacement unless evidence identifies that layer. Retain the original trace and a post-fix trace so the result can be attributed and the change reversed.
Difference from nearby HRESULTs
VFW_E_SIZENOTSET concerns missing buffer size, while it concerns the alignment constraint on those buffers. Keep these outcomes separate in logs, exception mappings, user messages, dashboards and automated retry policy.
Official Microsoft references
- Microsoft: DirectShow error and success codes
- Microsoft: media samples and allocators
- Microsoft: DirectShow media samples
Looking for a different code? Search another status or error code.