DXGI_ERROR
Error codes that can be returned by a DXGI function.
| Constant/value | Description |
|---|---|
|
You tried to use a resource to which you did not have the required access privileges. This error is most typically caused when you write to a shared resource with read-only access. |
|
The desktop duplication interface is invalid. The desktop duplication interface typically becomes invalid when a different type of image is displayed on the desktop. |
|
The desired element already exists. This is returned by DXGIDeclareAdapterRemovalSupport if it is not the first time that the function is called. |
|
DXGI can't provide content protection on the swap chain. This error is typically caused by an older driver, or when you use a swap chain that is incompatible with content protection. |
|
The application's device failed due to badly formed commands sent by the application. This is an design-time issue that should be investigated and fixed. |
|
The video card has been physically removed from the system, or a driver upgrade for the video card has occurred. The application should destroy and recreate the device. For help debugging the problem, call ID3D10Device::GetDeviceRemovedReason. |
|
The device failed due to a badly formed command. This is a run-time issue; The application should destroy and recreate the device. |
|
The driver encountered a problem and was put into the device removed state. |
|
An event (for example, a power cycle) interrupted the gathering of presentation statistics. |
|
The application attempted to acquire exclusive ownership of an output, but failed because some other application (or device within the application) already acquired ownership. |
|
The application provided invalid parameter data; this must be debugged and fixed before the application is released. |
|
The buffer supplied by the application is not big enough to hold the requested data. |
|
The supplied name of a resource in a call to IDXGIResource1::CreateSharedHandle is already associated with some other resource. |
|
A global counter resource is in use, and the Direct3D device can't currently use the counter resource. |
|
The resource or request is not currently available, but it might become available later. |
|
When calling IDXGIObject::GetPrivateData, the GUID passed in is not recognized as one previously passed to IDXGIObject::SetPrivateData or IDXGIObject::SetPrivateDataInterface. When calling IDXGIFactory::EnumAdapters or IDXGIAdapter::EnumOutputs, the enumerated ordinal is out of range. |
|
Reserved |
|
Reserved |
|
The DXGI output (monitor) to which the swap chain content was restricted is now disconnected or changed. |
|
The operation depends on an SDK component that is missing or mismatched. |
|
The Remote Desktop Services session is currently disconnected. |
|
The requested functionality is not supported by the device or the driver. |
|
The time-out interval elapsed before the next desktop frame was available. |
|
The GPU was busy at the moment when a call was made to perform an operation, and did not execute or schedule the operation. |
|
The method succeeded without an error. |
Remarks
You may be interested only in whether the method succeeded or failed. The best way to test whether an HRESULT value indicates success or failure is to pass the value to the one of the following macros, defined in WinError.h:
- The SUCCEEDED macro returns TRUE for a success code and FALSE for a failure code.
- The FAILED macro returns TRUE for a failure code and FALSE for a success code.
The HRESULT value for each DXGI_ERROR value is determined from this macro that is defined in DXGItype.h:
#define _FACDXGI 0x87a
#define MAKE_DXGI_HRESULT(code) MAKE_HRESULT(1, _FACDXGI, code)
For example, DXGI_ERROR_INVALID_CALL is defined as 0x887A0001:
#define DXGI_ERROR_INVALID_CALL MAKE_DXGI_HRESULT(1)
Requirements
| Requirement | Value |
|---|---|
| Header |
|
See also