| Previous | Next |
| VFW_E_CODECAPI_NO_CURRENT_VALUE | VFW_E_BAD_KEY |
VFW_E_DVD_CHAPTER_DOES_NOT_EXIST
Exact result and bit fields
VFW_E_DVD_CHAPTER_DOES_NOT_EXIST has the unsigned HRESULT value 2147746581 (0x80040315) and the signed 32-bit representation -2147220715. AllStat describes it as “The operation failed since the chapter does not exist”. In the operation that produces this result, a chapter-specific DVD command names a chapter outside the current title’s authored chapter range.
The high bit is set, so this value is a failure HRESULT. Its facility field is 4 (FACILITY_ITF) and its low code is 789 (0x0315). 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 it: the chapter number is zero or above the title count.
- Cause 2 for it: cached chapter data belongs to another title.
- Cause 3 for it: the disc uses a different title layout than the application expected.
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 it 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: a chapter-specific DVD command names a chapter outside the current title’s authored chapter range.
- compare the live object state, topology and input with the documented interface preconditions.
- Before changing filters, drivers, registry data or media for it, 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 it: requested title and chapter.
- Evidence 2 for it: GetNumberOfChapters result.
- Evidence 3 for it: title-change events and UI selection source.
Correction strategy
- Action 1 for it: validate chapter numbers against the current title.
- Action 2 for it: refresh chapter lists on every title change.
- Action 3 for it: handle titles with unusual or zero chapter counts.
Example incident
A saved shortcut points to chapter 12, but a replacement disc edition has only ten chapters; validating the current title prevents 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 it: Retry after choosing a valid chapter in the current title. 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_DVD_TITLE_UNKNOWN means no current title context exists, while it rejects a specific chapter in a known title. 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 it should favor supported component installation, device configuration and documented DirectShow calls. Manual registry or driver changes are appropriate only when the collected evidence for it points to that layer and a rollback is available.
Official Microsoft references
Looking for a different code? Search another status or error code.