The operating system asynchronously destroyed this OPM-protected output because the operating system state changed. This error typically occurs because the monitor PDO associated with this protected output was removed or stopped, the protected output's session became a nonconsole session, or the protected output's desktop became inactive.
The DxgkDdiOPMGetCOPPCompatibleInformation, DxgkDdiOPMGetInformation, or DxgkDdiOPMConfigureProtectedOutput function failed. This error is returned only if a protected output has OPM semantics.
DxgkDdiOPMGetCOPPCompatibleInformation always returns this error if a protected output has OPM semantics.
DxgkDdiOPMGetInformation returns this error code if the caller requested COPP-specific information.
DxgkDdiOPMConfigureProtectedOutput returns this error when the caller tries to use a COPP-specific command.
The DxgkDdiOPMGetInformation and DxgkDdiOPMGetCOPPCompatibleInformation functions return this error code if the passed-in sequence number is not the expected sequence number or the passed-in OMAC value is invalid.
The function failed because an unexpected error occurred inside a display driver.
The DxgkDdiOPMGetCOPPCompatibleInformation, DxgkDdiOPMGetInformation, or DxgkDdiOPMConfigureProtectedOutput function failed. This error is returned only if a protected output has COPP semantics.
DxgkDdiOPMGetCOPPCompatibleInformation returns this error code if the caller requested OPM-specific information.
DxgkDdiOPMGetInformation always returns this error if a protected output has COPP semantics.
DxgkDdiOPMConfigureProtectedOutput returns this error when the caller tries to use an OPM-specific command.
The DxgkDdiOPMGetCOPPCompatibleInformation and DxgkDdiOPMConfigureProtectedOutput functions return this error if the display driver does not support the DXGKMDT_OPM_GET_ACP_AND_CGMSA_SIGNALING and DXGKMDT_OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs.
The DxgkDdiOPMConfigureProtectedOutput function returns this error code if the passed-in sequence number is not the expected sequence number or the passed-in OMAC value is invalid.
The monitor connected to the specified video output does not have an I2C bus.
No device on the I2C bus has the specified address.
An error occurred while transmitting data to the device on the I2C bus.
An error occurred while receiving data from the device on the I2C bus.
The monitor does not support the specified VCP code.
A function call failed because a monitor returned an invalid timing status byte when the operating system used the DDC/CI get timing report and timing message command to get a timing report from a monitor.
A monitor returned a DDC/CI capabilities string that did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification.
An internal error caused an operation to fail.
An operation failed because a DDC/CI message had an invalid value in its command field.
This error occurred because a DDC/CI message had an invalid value in its length field.
This error occurred because the value in a DDC/CI message's checksum field did not match the message's computed checksum value. This error implies that the data was corrupted while it was being transmitted from a monitor to a computer.
This function failed because an invalid monitor handle was passed to it.
The operating system asynchronously destroyed the monitor that corresponds to this handle because the operating system's state changed. This error typically occurs because the monitor PDO associated with this handle was removed or stopped, or a display mode change occurred. A display mode change occurs when Windows sends a WM_DISPLAYCHANGE message to applications.
This function can be used only if a program is running in the local console session. It cannot be used if a program is running on a remote desktop session or on a terminal server session.
The function failed because the specified GDI display device was not attached to the Windows desktop.
This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them.
The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is null, is not correctly aligned, or points to an invalid address or to a kernel mode address.
This function failed because the GDI device passed to it did not have a monitor associated with it.
An array passed to the function cannot hold all of the data that the function must copy into the array.
An internal error caused an operation to fail.
The function failed because the current session is changing its type. This function cannot be called when the current session is changing its type. Three types of sessions currently exist: console, disconnected, and remote (RDP or ICA).
The volume must be unlocked before it can be used.
The volume is fully decrypted and no key is available.
The control block for the encrypted volume is not valid.
Not enough free space remains on the volume to allow encryption.
The partition cannot be encrypted because the file system is not supported.
The file system is inconsistent. Run the Check Disk utility.
The file system does not extend to the end of the volume.
This operation cannot be performed while a file system is mounted on the volume.
BitLocker Drive Encryption is not included with this version of Windows.
The requested action was denied by the FVE control engine.
The data supplied is malformed.
The volume is not bound to the system.
The volume specified is not a data volume.
A read operation failed while converting the volume.
A write operation failed while converting the volume.
The control block for the encrypted volume was updated by another thread. Try again.
The volume encryption algorithm cannot be used on this sector size.
BitLocker recovery authentication failed.
The volume specified is not the boot operating system volume.
The BitLocker startup key or recovery password could not be read from external media.
The BitLocker startup key or recovery password file is corrupt or invalid.
The BitLocker encryption key could not be obtained from the startup key or the recovery password.
The TPM is disabled.
The authorization data for the SRK of the TPM is not zero.
The system boot information changed or the TPM locked out access to BitLocker encryption keys until the computer is restarted.
The BitLocker encryption key could not be obtained from the TPM.
The BitLocker encryption key could not be obtained from the TPM and PIN.
A boot application hash does not match the hash computed when BitLocker was turned on.
The Boot Configuration Data (BCD) settings are not supported or have changed because BitLocker was enabled.
Boot debugging is enabled. Run Windows Boot Configuration Data Store Editor (bcdedit.exe) to turn it off.
The BitLocker encryption key could not be obtained.
The metadata disk region pointer is incorrect.
The backup copy of the metadata is out of date.
No action was taken because a system restart is required.
No action was taken because BitLocker Drive Encryption is in RAW access mode.
BitLocker Drive Encryption cannot enter RAW access mode for this volume.
This feature of BitLocker Drive Encryption is not included with this version of Windows.
Group policy does not permit turning off BitLocker Drive Encryption on roaming data volumes.
Bitlocker Drive Encryption failed to recover from aborted conversion. This could be due to either all conversion logs being corrupted or the media being write-protected.
The requested virtualization size is too big.
The drive is too small to be protected using BitLocker Drive Encryption.
The callout does not exist.
The filter condition does not exist.
The filter does not exist.
The layer does not exist.
The provider does not exist.
The provider context does not exist.
The sublayer does not exist.
The object does not exist.
An object with that GUID or LUID already exists.
The object is referenced by other objects and cannot be deleted.
The call is not allowed from within a dynamic session.
The call was made from the wrong session and cannot be completed.
The call must be made from within an explicit transaction.
The call is not allowed from within an explicit transaction.
The explicit transaction has been forcibly canceled.
The session has been canceled.
The call is not allowed from within a read-only transaction.
The call timed out while waiting to acquire the transaction lock.
The collection of network diagnostic events is disabled.
The operation is not supported by the specified layer.
The call is allowed for kernel-mode callers only.
The call tried to associate two objects with incompatible lifetimes.
The object is built-in and cannot be deleted.
The maximum number of boot-time filters has been reached.
The maximum number of callouts has been reached.
A notification could not be delivered because a message queue has reached maximum capacity.
The traffic parameters do not match those for the security association context.
The call is not allowed for the current security association state.
A required pointer is null.
An enumerator is not valid.
The flags field contains an invalid value.
A network mask is not valid.
An FWP_RANGE is not valid.
The time interval is not valid.
An array that must contain at least one element has a zero length.
The displayData.name field cannot be null.
The action type is not one of the allowed action types for a filter.
The filter weight is not valid.
A filter condition contains a match type that is not compatible with the operands.
An FWP_VALUE or FWPM_CONDITION_VALUE is of the wrong type.
An integer value is outside the allowed range.
A reserved field is nonzero.
A filter cannot contain multiple conditions operating on a single field.
A policy cannot contain the same keying module more than once.
The action type is not compatible with the layer.
The action type is not compatible with the sublayer.
The raw context or the provider context is not compatible with the layer.
The raw context or the provider context is not compatible with the callout.
The authentication method is not compatible with the policy type.
The Diffie-Hellman group is not compatible with the policy type.
An IKE policy cannot contain an Extended Mode policy.
The enumeration template or subscription will never match any objects.
The provider context is of the wrong type.
The parameter is incorrect.
The maximum number of sublayers has been reached.
The notification function for a callout returned an error.
The IPsec authentication configuration is not compatible with the authentication type.
The IPsec cipher configuration is not compatible with the cipher type.
A policy cannot contain the same auth method more than once.
The TCP/IP stack is not ready.
The injection handle is being closed by another thread.
The injection handle is stale.
The classify cannot be pended.
The binding to the network interface is being closed.
An invalid version was specified.
An invalid characteristics table was used.
Failed to find the network interface or the network interface is not ready.
Failed to open the network interface.
The network interface has encountered an internal unrecoverable failure.
The multicast list on the network interface is full.
An attempt was made to add a duplicate multicast address to the list.
At attempt was made to remove a multicast address that was never added.
The network interface aborted the request.
The network interface cannot process the request because it is being reset.
An attempt was made to send an invalid packet on a network interface.
The specified request is not a valid operation for the target device.
The network interface is not ready to complete this operation.
The length of the buffer submitted for this operation is not valid.
The data used for this operation is not valid.
The length of the submitted buffer for this operation is too small.
The network interface does not support this object identifier.
The network interface has been removed.
The network interface does not support this media type.
An attempt was made to remove a token ring group address that is in use by other components.
An attempt was made to map a file that cannot be found.
An error occurred while NDIS tried to map the file.
An attempt was made to map a file that is already mapped.
An attempt to allocate a hardware resource failed because the resource is used by another component.
The I/O operation failed because the network media is disconnected or the wireless access point is out of range.
The network address used in the request is invalid.
The offload operation on the network interface has been paused.
The network interface was not found.
The revision number specified in the structure is not supported.
The specified port does not exist on this network interface.
The current state of the specified port on this network interface does not support the requested operation.
The miniport adapter is in a lower power state.
The network interface does not support this request.
The TCP connection is not offloadable because of a local policy setting.
The TCP connection is not offloadable by the Chimney offload target.
The IP Path object is not in an offloadable state.
The wireless LAN interface is in auto-configuration mode and does not support the requested parameter change operation.
The wireless LAN interface is busy and cannot perform the requested operation.
The wireless LAN interface is power down and does not support the requested operation.
The list of wake on LAN patterns is full.
The list of low power protocol offloads is full.
The SPI in the packet does not match a valid IPsec SA.
The packet was received on an IPsec SA whose lifetime has expired.
The packet was received on an IPsec SA that does not match the packet characteristics.
The packet sequence number replay check failed.
The IPsec header and/or trailer in the packet is invalid.
The IPsec integrity check failed.
IPsec dropped a clear text packet.
IPsec dropped an incoming ESP packet in authenticated firewall mode. This drop is benign.
IPsec dropped a packet due to DOS throttle.
IPsec Dos Protection matched an explicit block rule.
IPsec Dos Protection received an IPsec specific multicast packet which is not allowed.
IPsec Dos Protection received an incorrectly formatted packet.
IPsec Dos Protection failed to lookup state.
IPsec Dos Protection failed to create state because there are already maximum number of entries allowed by policy.
IPsec Dos Protection received an IPsec negotiation packet for a keying module which is not allowed by policy.
IPsec Dos Protection failed to create per internal IP ratelimit queue because there is already maximum number of queues allowed by policy.
The system does not support mirrored volumes.
The system does not support RAID-5 volumes.
A virtual disk support provider for the specified file was not found.
The specified disk is not a virtual disk.
The chain of virtual hard disks is inaccessible. The process has not been granted access rights to the parent virtual hard disk for the differencing disk.
The chain of virtual hard disks is corrupted. There is a mismatch in the virtual sizes of the parent virtual hard disk and differencing disk.
The chain of virtual hard disks is corrupted. A differencing disk is indicated in its own parent chain.
The chain of virtual hard disks is inaccessible. There was an error opening a virtual hard disk further up the chain.