| Previous | Next |
| STATUS_GRAPHICS_I2C_NOT_SUPPORTED | STATUS_GRAPHICS_I2C_ERROR_TRANSMITTING_DATA |
STATUS_GRAPHICS_I2C_DEVICE_DOES_NOT_EXIST
STATUS_GRAPHICS_I2C_DEVICE_DOES_NOT_EXIST is narrower than I2C-not-supported. The selected path has an I2C bus, but no device exists at the address requested by the operation. That can expose a wrong bus/address assumption or a control path that does not reach the intended monitor.
It is not a VCP capability result. The transaction did not reach a device that could interpret a DDC/CI feature code, so changing the feature code alone is not a valid remedy.
What to correlate
- Map the application’s display and physical-monitor handle to the actual connector and active sink.
- Check whether docks, adapters, KVMs, or display paths alter the control bus independently of the pixel path.
- Keep the requested I2C address and operation in diagnostics; this helps distinguish a missing device from a later transmit or receive failure.
References
- Microsoft: low-level monitor configuration
- VESA free DDC/CI and MCCS standards
- MS-ERREF: NTSTATUS values
Looking for a different code? Search another status or error code.