What does HRESULT 0x8004029E (VFW_E_DVD_NON_EVR_RENDERER_IN_FILTER_GRAPH) mean?

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

AM_DVD_EVR_ONLY cannot be passed to RenderDvdVideoVolume if the graph.

Previous	Next
VFW_E_DVD_TOO_MANY_RENDERERS_IN_FILTER_GRAPH	VFW_E_DVD_RESOLUTION_ERROR

VFW_E_DVD_NON_EVR_RENDERER_IN_FILTER_GRAPH

Exact result and bit fields

VFW_E_DVD_NON_EVR_RENDERER_IN_FILTER_GRAPH has the unsigned HRESULT value 2147746462 (0x8004029E) and the signed 32-bit representation -2147220834. AllStat describes it as “AM_DVD_EVR_ONLY cannot be passed to RenderDvdVideoVolume if the graph builder's filter graph contains a renderer which is not the EVR”. In the operation that produces this result, RenderDvdVideoVolume is called with AM_DVD_EVR_ONLY while the graph already contains a renderer other than EVR.

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

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.

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: graph-builder flags.
Evidence 2 for this HRESULT: existing renderer CLSIDs.
Evidence 3 for this HRESULT: filter insertion order and cleanup trace.

Conditions that can produce it

Cause 1 for this HRESULT: a legacy Video Renderer or VMR was pre-added.
Cause 2 for this HRESULT: partial graph construction left a non-EVR filter.
Cause 3 for this HRESULT: renderer policy changed without recreating the graph.

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: RenderDvdVideoVolume is called with AM_DVD_EVR_ONLY while the graph already contains a renderer other than EVR.
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 after the graph is free of non-EVR renderers or after removing the EVR-only flag. 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: remove the non-EVR renderer before requesting EVR-only mode.
Action 2 for this HRESULT: build a fresh graph for a renderer-policy change.
Action 3 for this HRESULT: avoid mixing manual renderer insertion with EVR-only graph-builder ownership.

Example incident

A player switches its setting from VMR-9 to EVR but reuses the old graph; rebuilding it 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

VFW_E_DVD_TOO_MANY_RENDERERS_IN_FILTER_GRAPH concerns multiple renderers, while it specifically violates the EVR-only request. 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.