| Previous | Next |
| VFW_E_DVD_NON_EVR_RENDERER_IN_FILTER_GRAPH | VFW_E_CODECAPI_LINEAR_RANGE |
VFW_E_DVD_RESOLUTION_ERROR
Exact result and bit fields
VFW_E_DVD_RESOLUTION_ERROR has the unsigned HRESULT value 2147746463 (0x8004029F) and the signed 32-bit representation -2147220833. AllStat describes it as “DVD Video Output is not at a proper resolution”. In the operation that produces this result, the DVD playback graph produces or requests video output at a resolution that is not valid for the selected DVD rendering path.
The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 671 (0x029F). These fields classify this result, but they do not identify which filter, thread, device, file or graph generation returned it.
Conditions that can produce it
- Cause 1 for this HRESULT: decoder output dimensions are inconsistent with DVD video attributes.
- Cause 2 for this HRESULT: renderer configuration forces an unsupported surface size.
- Cause 3 for this HRESULT: display-mode or scaling negotiation produces an invalid output.
Contract boundary
This result belongs to the legacy DirectShow DVD Navigator contract. DVD state is authored and stateful: domains, user-operation controls, titles, menus, streams, command objects and graph construction each impose different preconditions.
The practical owner to locate for this HRESULT is the DVD Navigator, graph builder, decoder inventory and renderer topology. 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.
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: the DVD playback graph produces or requests video output at a resolution that is not valid for the selected DVD rendering path.
- 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.
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 disc identifiers, navigation state, parental settings and media paths.
- Evidence 1 for this HRESULT: DVD_VideoAttributes dimensions and aspect ratio.
- Evidence 2 for this HRESULT: decoder output media type.
- Evidence 3 for this HRESULT: renderer destination size and graph-builder status.
Correction strategy
- Action 1 for this HRESULT: allow DVD-native dimensions through decoder negotiation.
- Action 2 for this HRESULT: remove unsupported forced-resolution settings.
- Action 3 for this HRESULT: select a renderer and display mode that can scale the DVD output.
Example incident
A custom decoder advertises a non-DVD output size to the EVR-only graph builder; negotiating a valid DVD resolution removes it. This example keeps the diagnosis at the specific the boundary instead of treating every DirectShow failure as a codec reinstall problem.
Retry and recovery
Retry rule for this HRESULT: Retry after correcting the decoder output or renderer configuration. 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.
How it differs from nearby results
VFW_E_OUT_OF_VIDEO_MEMORY is a resource failure at an otherwise valid size, while it says the output resolution itself is inappropriate. Keep those cases separate in telemetry, UI messages and retry policy because their next actions are different.
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.
Official Microsoft references
Looking for a different code? Search another status or error code.