| 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
Meaning
Windows documents VFW_E_DVD_NON_EVR_RENDERER_IN_FILTER_GRAPH 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”. Here, RenderDvdVideoVolume is called with AM_DVD_EVR_ONLY while the graph already contains a renderer other than EVR.
Relevant contract
Code-specific boundary: VFW_E_DVD_NON_EVR_RENDERER_IN_FILTER_GRAPH narrows the investigation to the renderer already present in the graph; DVD playback cannot proceed with an incompatible non-EVR topology. Preserve the DVD domain, title/menu location and graph topology from the same attempt so a later navigation error is not mistaken for the original condition.
Start with the DVD Navigator, graph builder, decoder inventory and renderer topology.
Evidence worth preserving
- Evidence 1: graph-builder flags.
- Evidence 2: existing renderer CLSIDs.
- Evidence 3: filter insertion order and cleanup trace.
Conditions that can produce it
- Cause 1: a legacy Video Renderer or VMR was pre-added.
- Cause 2: partial graph construction left a non-EVR filter.
- Cause 3: renderer policy changed without recreating the graph.
Retry and recovery
Retry rule: Retry after the graph is free of non-EVR renderers or after removing the EVR-only flag.
Correction strategy
- Action 1: remove the non-EVR renderer before requesting EVR-only mode.
- Action 2: build a fresh graph for a renderer-policy change.
- Action 3: 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.
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.
Official Microsoft references
Looking for a different code? Search another status or error code.