WDDM CCD Test for verifying only one internal target active on GPU

This automated queries all display devices and ensures that only one internal device is actively driving an output. Having two displays marked as internal is not supported.

Test details

Associated requirements


See the system hardware requirements.


Windows 7 (x64) Windows 7 (x86) Windows RT (ARM-based) Windows 8 (x64) Windows 8 (x86) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86

Expected run time

~1 minutes


Certification Functional



Running the test

Before you run the test, complete the test setup as described in the test requirements: System Client Testing Prerequisites.


For troubleshooting information, see Troubleshooting System Client Testing.

More information

In order for this test to complete successfully, the following must be true:

  • Windows must be able to drive any target from any source, although there may be constraints on which target may be driven in combination.

  • When Windows asks for the EDID, the driver must provide the most current EDID. If there's been an interruption (sleep/resume, PnP stop/start) in the drivers ability to detect connection state, the driver must re-query the display device.

  • For each DVI-I connector on the system, the graphics adapter or chipset driver must expose one target of type D3DKMDT_VOT_DVI and one target of type D3DKMDT_VOT_HD15.

  • The graphics adapter or chipset driver must not use D3DKMDT_VOT_OTHER as target type for any target type already defined in D3DKMDT_VIDEO_OUTPUT_TECHNOLOGY.

  • The graphics adapter or chipset driver must accurately report the result of the connection state request based on the display device being physically connected. If the driver doesn't have this information it must return STATUS_GRAPHICS_UNKNOWN_CHILD_STATUS when the operating system invokes the DXGKDDI_QUERY_CHILD_STATUS DDI. On systems with multiple GPUs, the laptop lid target must not be reported as 'connected' on more than one graphics adapter at any given time.

Send comments about this topic to Microsoft