| Previous | Next |
| VFW_E_NO_TRANSPORT | VFW_E_OUT_OF_VIDEO_MEMORY |
VFW_E_BAD_VIDEOCD
Exact result and bit fields
VFW_E_BAD_VIDEOCD has the unsigned HRESULT value 2147746409 (0x80040269) and the signed 32-bit representation -2147220887. AllStat describes it as “The Video CD can't be read correctly by the device or is the data is corrupt”. In the operation that produces this result, the Video CD source cannot read valid MPEG data from the disc or device 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 617 (0x0269). These fields classify this result, but they do not identify which filter, thread, device, file or graph generation returned it.
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 media paths, device identifiers, registry values and stream metadata.
- Evidence 1 for it: drive model, media identifier and read error.
- Evidence 2 for it: failing logical block and retry count.
- Evidence 3 for it: raw sector sample and parser offset.
Contract boundary
This result is a DirectShow contract failure whose owner must be identified from the exact interface, filter instance, graph generation and operation stage.
The practical owner to locate for it is the filter graph, device or persisted configuration that first returned the result. 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.
Conditions that can produce it
- Cause 1 for it: the disc has unreadable sectors.
- Cause 2 for it: the drive returns inconsistent sector data.
- Cause 3 for it: the Video CD filesystem or MPEG sequence is corrupt.
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 Video CD source cannot read valid MPEG data from the disc or device path.
- 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.
Correction strategy
- Action 1 for it: clean or replace the disc and verify it in another drive.
- Action 2 for it: copy the readable content with error reporting before playback.
- Action 3 for it: treat repeated sector corruption as media failure rather than a codec problem.
Example incident
A Video CD stalls at the same chapter in two players and the drive logs uncorrectable sectors; replacing the disc resolves 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 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.
Retry and recovery
Retry rule for it: Retry is reasonable for transient drive reads, but stop after bounded attempts or when the same sectors remain unreadable. 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_INVALID_FILE_FORMAT concerns malformed file structure, while it also covers device-level inability to read valid Video CD data. Keep those cases separate in telemetry, UI messages and retry policy because their next actions are different.
Official Microsoft references
- Microsoft: DirectShow error and success codes
- Microsoft: IGraphBuilder::RenderFile
- Microsoft: overview of DirectShow graph building
Looking for a different code? Search another status or error code.