| Previous | Next |
| ERROR_GRAPHICS_I2C_NOT_SUPPORTED | ERROR_GRAPHICS_I2C_ERROR_TRANSMITTING_DATA |
ERROR_GRAPHICS_I2C_DEVICE_DOES_NOT_EXIST
The bus exists, but the addressed device did not answer
ERROR_GRAPHICS_I2C_DEVICE_DOES_NOT_EXIST is more specific than lack of I²C support. The controller attempted a transaction, but no device responded at the requested address. In I²C terms, the address phase was not acknowledged; in a monitor path this can result from selecting the wrong bus, a disconnected sink, a phantom DDC channel, or an intervening device that does not forward control traffic.
Re-enumerate the physical monitor after hot-plug and mode changes instead of reusing a stale handle. Verify that the bus corresponds to the connector carrying the monitor's EDID and DDC/CI channel. Do not scan arbitrary addresses on production display hardware when the documented API can identify the physical monitor object.
Evidence for an address-phase failure
- Connector and physical-monitor identity at the time of the call.
- Whether the monitor acknowledged after a fresh enumeration.
- Presence of duplicate or phantom I²C buses for the same EDID.
- Hot-plug, sleep, or input-source changes immediately before the error.
References
- Linux kernel: I²C address and ACK/NACK phases
- ddcutil: phantom display buses and response timing
- Microsoft: physical-monitor enumeration and control functions
Looking for a different code? Search another status or error code.