FACILITY_GRAPHICS: the graphics drivers.
The source of the error code is the graphics drivers.[1][2]
0x80260001: {Display Driver Stopped Responding} The %hs display driver has stopped working normally. Save your work and reboot the system to restore full display functionality. The next time you reboot the machine a dialog will be displayed giving you a chance to report this failure to Microsoft.[2]0x80263001: {Desktop composition is disabled} The operation could not be completed because desktop composition is disabled.[2]0x80263002: {Some desktop composition APIs are not supported while remoting} The operation is not supported while running in a remote session.[2]0x80263003: {No DWM redirection surface is available} The DWM was unable to provide a redireciton surface to complete the DirectX present.[2]0x80263004: {DWM is not queuing presents for the specified window} The window specified is not currently using queued presents.[2]0x80263005: {The adapter specified by the LUID is not found} DWM can not find the adapter specified by the LUID.[2]0x00263005: {GDI redirection surface was returned} GDI redirection surface of the top level window was returned.[2]0x80263007: {Redirection surface can not be created. The size of the surface is larger than what is supported on this machine} Redirection surface can not be created. The size of the surface is larger than what is supported on this machine.[2]0x00263008: {GDI redirection surface is either on a different adapter or in system memory. Perform blt via GDI} GDI redirection surface is either on a different adapter or in system memory. Perform blt via GDI.[2]0x00261001: Monitor descriptor could not be obtained.[2]0x00261002: Format of the obtained monitor descriptor is not supported by this release.[2]0xC0261003: Checksum of the obtained monitor descriptor is invalid.[2]0xC0261004: Monitor descriptor contains an invalid standard timing block.[2]0xC0261005: WMI data block registration failed for one of the MSMonitorClass WMI subclasses.[2]0xC0261006: Provided monitor descriptor block is either corrupted or does not contain monitor's detailed serial number.[2]0xC0261007: Provided monitor descriptor block is either corrupted or does not contain monitor's user friendly name.[2]0xC0261008: There is no monitor descriptor data at the specified (offset, size) region.[2]0xC0261009: Monitor descriptor contains an invalid detailed timing block.[2]0xC026100A: Monitor descriptor contains invalid manufacture date.[2]0xC0262000: Exclusive mode ownership is needed to create unmanaged primary allocation.[2]0xC0262001: The driver needs more DMA buffer space in order to complete the requested operation.[2]0xC0262002: Specified display adapter handle is invalid.[2]0xC0262003: Specified display adapter and all of its state has been reset.[2]0xC0262004: The driver stack doesn't match the expected driver model.[2]0xC0262005: Present happened but ended up into the changed desktop mode[2]0xC0262006: Nothing to present due to desktop occlusion[2]0xC0262007: Not able to present due to denial of desktop access[2]0xC0262008: Not able to present with color convertion[2]0xC0262009: The kernel driver detected a version mismatch between it and the user mode driver.[2]0x4026200A: Specified buffer is not big enough to contain entire requested dataset. Partial data populated up to the size of the buffer. Caller needs to provide buffer of size as specified in the partially populated buffer's content (interface specific).[2]0xC026200B: Present redirection is disabled (desktop windowing management subsystem is off).[2]0xC026200C: Previous exclusive VidPn source owner has released its ownership[2]0xC026200D: Window DC is not available for presentation[2]0xC026200E: Windowless present is disabled (desktop windowing management subsystem is off).[2]0xC0262100: Not enough video memory available to complete the operation.[2]0xC0262101: Couldn't probe and lock the underlying memory of an allocation.[2]0xC0262102: The allocation is currently busy.[2]0xC0262103: An object being referenced has reach the maximum reference count already and can't be reference further.[2]0xC0262104: A problem couldn't be solved due to some currently existing condition. The problem should be tried again later.[2]0xC0262105: A problem couldn't be solved due to some currently existing condition. The problem should be tried again immediately.[2]0xC0262106: The allocation is invalid.[2]0xC0262107: No more unswizzling aperture are currently available.[2]0xC0262108: The current allocation can't be unswizzled by an aperture.[2]0xC0262109: The request failed because a pinned allocation can't be evicted.[2]0xC0262110: The allocation can't be used from its current segment location for the specified operation.[2]0xC0262111: A locked allocation can't be used in the current command buffer.[2]0xC0262112: The allocation being referenced has been closed permanently.[2]0xC0262113: An invalid allocation instance is being referenced.[2]0xC0262114: An invalid allocation handle is being referenced.[2]0xC0262115: The allocation being referenced doesn't belong to the current device.[2]0xC0262116: The specified allocation lost its content.[2]0xC0262200: GPU exception is detected on the given device. The device is not able to be scheduled.[2]0x40262201: Skip preparation of allocations referenced by the DMA buffer.[2]0xC0262300: Specified VidPN topology is invalid.[2]0xC0262301: Specified VidPN topology is valid but is not supported by this model of the display adapter.[2]0xC0262302: Specified VidPN topology is valid but is not supported by the display adapter at this time, due to current allocation of its resources.[2]0xC0262303: Specified VidPN handle is invalid.[2]0xC0262304: Specified video present source is invalid.[2]0xC0262305: Specified video present target is invalid.[2]0xC0262306: Specified VidPN modality is not supported (e.g. at least two of the pinned modes are not cofunctional).[2]0x00262307: No mode is pinned on the specified VidPN source/target.[2]0xC0262308: Specified VidPN source mode set is invalid.[2]0xC0262309: Specified VidPN target mode set is invalid.[2]0xC026230A: Specified video signal frequency is invalid.[2]0xC026230B: Specified video signal active region is invalid.[2]0xC026230C: Specified video signal total region is invalid.[2]0xC0262310: Specified video present source mode is invalid.[2]0xC0262311: Specified video present target mode is invalid.[2]0xC0262312: Pinned mode must remain in the set on VidPN's cofunctional modality enumeration.[2]0xC0262313: Specified video present path is already in VidPN's topology.[2]0xC0262314: Specified mode is already in the mode set.[2]0xC0262315: Specified video present source set is invalid.[2]0xC0262316: Specified video present target set is invalid.[2]0xC0262317: Specified video present source is already in the video present source set.[2]0xC0262318: Specified video present target is already in the video present target set.[2]0xC0262319: Specified VidPN present path is invalid.[2]0xC026231A: Miniport has no recommendation for augmentation of the specified VidPN's topology.[2]0xC026231B: Specified monitor frequency range set is invalid.[2]0xC026231C: Specified monitor frequency range is invalid.[2]0xC026231D: Specified frequency range is not in the specified monitor frequency range set.[2]0x0026231E: Specified mode set does not specify preference for one of its modes.[2]0xC026231F: Specified frequency range is already in the specified monitor frequency range set.[2]0xC0262320: Specified mode set is stale. Please reacquire the new mode set.[2]0xC0262321: Specified monitor source mode set is invalid.[2]0xC0262322: Specified monitor source mode is invalid.[2]0xC0262323: Miniport does not have any recommendation regarding the request to provide a functional VidPN given the current display adapter configuration.[2]0xC0262324: ID of the specified mode is already used by another mode in the set.[2]0xC0262325: System failed to determine a mode that is supported by both the display adapter and the monitor connected to it.[2]0xC0262326: Number of video present targets must be greater than or equal to the number of video present sources.[2]0xC0262327: Specified present path is not in VidPN's topology.[2]0xC0262328: Display adapter must have at least one video present source.[2]0xC0262329: Display adapter must have at least one video present target.[2]0xC026232A: Specified monitor descriptor set is invalid.[2]0xC026232B: Specified monitor descriptor is invalid.[2]0xC026232C: Specified descriptor is not in the specified monitor descriptor set.[2]0xC026232D: Specified descriptor is already in the specified monitor descriptor set.[2]0xC026232E: ID of the specified monitor descriptor is already used by another descriptor in the set.[2]0xC026232F: Specified video present target subset type is invalid.[2]0xC0262330: Two or more of the specified resources are not related to each other, as defined by the interface semantics.[2]0xC0262331: ID of the specified video present source is already used by another source in the set.[2]0xC0262332: ID of the specified video present target is already used by another target in the set.[2]0xC0262333: Specified VidPN source cannot be used because there is no available VidPN target to connect it to.[2]0xC0262334: Newly arrived monitor could not be associated with a display adapter.[2]0xC0262335: Display adapter in question does not have an associated VidPN manager.[2]0xC0262336: VidPN manager of the display adapter in question does not have an active VidPN.[2]0xC0262337: Specified VidPN topology is stale. Please reacquire the new topology.[2]0xC0262338: There is no monitor connected on the specified video present target.[2]0xC0262339: Specified source is not part of the specified VidPN's topology.[2]0xC026233A: Specified primary surface size is invalid.[2]0xC026233B: Specified visible region size is invalid.[2]0xC026233C: Specified stride is invalid.[2]0xC026233D: Specified pixel format is invalid.[2]0xC026233E: Specified color basis is invalid.[2]0xC026233F: Specified pixel value access mode is invalid.[2]0xC0262340: Specified target is not part of the specified VidPN's topology.[2]0xC0262341: Failed to acquire display mode management interface.[2]0xC0262342: Specified VidPN source is already owned by a DMM client and cannot be used until that client releases it.[2]0xC0262343: Specified VidPN is active and cannot be accessed.[2]0xC0262344: Specified VidPN present path importance ordinal is invalid.[2]0xC0262345: Specified VidPN present path content geometry transformation is invalid.[2]0xC0262346: Specified content geometry transformation is not supported on the respective VidPN present path.[2]0xC0262347: Specified gamma ramp is invalid.[2]0xC0262348: Specified gamma ramp is not supported on the respective VidPN present path.[2]0xC0262349: Multi-sampling is not supported on the respective VidPN present path.[2]0xC026234A: Specified mode is not in the specified mode set.[2]0x0026234B: Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) is empty.[2]0x0026234C: Specified data set (e.g. mode set, frequency range set, descriptor set, topology, etc.) does not contain any more elements.[2]0xC026234D: Specified VidPN topology recommendation reason is invalid.[2]0xC026234E: Specified VidPN present path content type is invalid.[2]0xC026234F: Specified VidPN present path copy protection type is invalid.[2]0xC0262350: No more than one unassigned mode set can exist at any given time for a given VidPN source/target.[2]0x00262351: Specified content transformation is not pinned on the specified VidPN present path.[2]0xC0262352: Specified scanline ordering type is invalid.[2]0xC0262353: Topology changes are not allowed for the specified VidPN.[2]0xC0262354: All available importance ordinals are already used in specified topology.[2]0xC0262355: Specified primary surface has a different private format attribute than the current primary surface[2]0xC0262356: Specified mode pruning algorithm is invalid[2]0xC0262357: Specified monitor capability origin is invalid.[2]0xC0262358: Specified monitor frequency range constraint is invalid.[2]0xC0262359: Maximum supported number of present paths has been reached.[2]0xC026235A: Miniport requested that augmentation be cancelled for the specified source of the specified VidPN's topology.[2]0xC026235B: Specified client type was not recognized.[2]0xC026235C: Client VidPN is not set on this adapter (e.g. no user mode initiated mode changes took place on this adapter yet).[2]0xC0262400: Specified display adapter child device already has an external device connected to it.[2]0xC0262401: Specified display adapter child device does not support descriptor exposure.[2]0x4026242F: Child device presence was not reliably detected.[2]0xC0262430: The display adapter is not linked to any other adapters.[2]0xC0262431: Lead adapter in a linked configuration was not enumerated yet.[2]0xC0262432: Some chain adapters in a linked configuration were not enumerated yet.[2]0xC0262433: The chain of linked adapters is not ready to start because of an unknown failure.[2]0xC0262434: An attempt was made to start a lead link display adapter when the chain links were not started yet.[2]0xC0262435: An attempt was made to power up a lead link display adapter when the chain links were powered down.[2]0xC0262436: The adapter link was found to be in an inconsistent state. Not all adapters are in an expected PNP/Power state.[2]0x40262437: Starting the leadlink adapter has been deferred temporarily.[2]0xC0262438: The driver trying to start is not the same as the driver for the POSTed display adapter.[2]0x40262439: The display adapter is being polled for children too frequently at the same polling level.[2]0x4026243A: Starting the adapter has been deferred temporarily.[2]0xC026243B: An operation is being attempted that requires the display adapter to be in a quiescent state.[2]0x4026243C: We can depend on the child device presence returned by the driver.[2]0xC0262500: The driver does not support OPM.[2]0xC0262501: The driver does not support COPP.[2]0xC0262502: The driver does not support UAB.[2]0xC0262503: The specified encrypted parameters are invalid.[2]0xC0262505: The GDI display device passed to this function does not have any active video outputs.[2]0xC026250B: An internal error caused this operation to fail.[2]0xC026250C: The function failed because the caller passed in an invalid OPM user mode handle.[2]0xC026250E: A certificate could not be returned because the certificate buffer passed to the function was too small.[2]0xC026250F: A video output could not be created because the frame buffer is in spanning mode.[2]0xC0262510: A video output could not be created because the frame buffer is in theater mode.[2]0xC0262511: The function failed because the display adapter's Hardware Functionality Scan failed to validate the graphics hardware.[2]0xC0262512: The HDCP System Renewability Message passed to this function did not comply with section 5 of the HDCP 1.1 specification.[2]0xC0262513: The video output cannot enable the High-bandwidth Digital Content Protection (HDCP) System because it does not support HDCP.[2]0xC0262514: The video output cannot enable Analogue Copy Protection (ACP) because it does not support ACP.[2]0xC0262515: The video output cannot enable the Content Generation Management System Analogue (CGMS-A) protection technology because it does not support CGMS-A.[2]0xC0262516: The IOPMVideoOutput::GetInformation method cannot return the version of the SRM being used because the application never successfully passed an SRM to the video output.[2]0xC0262517: The IOPMVideoOutput::Configure method cannot enable the specified output protection technology because the output's screen resolution is too high.[2]0xC0262518: The IOPMVideoOutput::Configure method cannot enable HDCP because the display adapter's HDCP hardware is already being used by other physical outputs.[2]0xC026251A: The operating system asynchronously destroyed this OPM video output because the operating system's state changed. This error typically occurs because the monitor PDO associated with this video output was removed, the monitor PDO associated with this video output was stopped, the video output's session became a non-console session or the video output's desktop became an inactive desktop.[2]0xC026251B: The method failed because the session is changing its type. No IOPMVideoOutput methods can be called when a session is changing its type. There are currently three types of sessions: console, disconnected and remote.[2]0xC026251C: Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use a COPP specific command while the video output has OPM semantics only.[2]0xC026251D: The IOPMVideoOutput::GetInformation and IOPMVideoOutput::COPPCompatibleGetInformation methods return this error if the passed in sequence number is not the expected sequence number or the passed in OMAC value is invalid.[2]0xC026251E: The method failed because an unexpected error occurred inside of a display driver.[2]0xC026251F: Either the IOPMVideoOutput::COPPCompatibleGetInformation, IOPMVideoOutput::GetInformation, or IOPMVideoOutput::Configure method failed. This error is returned when the caller tries to use an OPM specific command while the video output has COPP semantics only.[2]0xC0262520: The IOPMVideoOutput::COPPCompatibleGetInformation or IOPMVideoOutput::Configure method failed because the display driver does not support the OPM_GET_ACP_AND_CGMSA_SIGNALING and OPM_SET_ACP_AND_CGMSA_SIGNALING GUIDs.[2]0xC0262521: The IOPMVideoOutput::Configure 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.[2]0xC0262580: The monitor connected to the specified video output does not have an I2C bus.[2]0xC0262581: No device on the I2C bus has the specified address.[2]0xC0262582: An error occurred while transmitting data to the device on the I2C bus.[2]0xC0262583: An error occurred while receiving data from the device on the I2C bus.[2]0xC0262584: The monitor does not support the specified VCP code.[2]0xC0262585: The data received from the monitor is invalid.[2]0xC0262586: The function failed because a monitor returned an invalid Timing Status byte when the operating system used the DDC/CI Get Timing Report & Timing Message command to get a timing report from a monitor.[2]0xC0262587: The monitor returned a DDC/CI capabilities string which did not comply with the ACCESS.bus 3.0, DDC/CI 1.1, or MCCS 2 Revision 1 specification.[2]0xC0262588: An internal Monitor Configuration API error occurred.[2]0xC0262589: An operation failed because a DDC/CI message had an invalid value in its command field.[2]0xC026258A: An error occurred because the field length of a DDC/CI message contained an invalid value.[2]0xC026258B: An error occurred because the checksum field in a DDC/CI message 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.[2]0xC026258C: This function failed because an invalid monitor handle was passed to it.[2]0xC026258D: The operating system asynchronously destroyed the monitor which 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, the monitor PDO associated with this handle was stopped, or a display mode change occurred. A display mode change occurs when windows sends a WM_DISPLAYCHANGE windows message to applications.[2]0xC02625D8: A continuous VCP code's current value is greater than its maximum value. This error code indicates that a monitor returned an invalid value.[2]0xC02625D9: The monitor's VCP Version (0xDF) VCP code returned an invalid version value.[2]0xC02625DA: The monitor does not comply with the MCCS specification it claims to support.[2]0xC02625DB: The MCCS version in a monitor's mccs_ver capability does not match the MCCS version the monitor reports when the VCP Version (0xDF) VCP code is used.[2]0xC02625DC: The Monitor Configuration API only works with monitors which support the MCCS 1.0 specification, MCCS 2.0 specification or the MCCS 2.0 Revision 1 specification.[2]0xC02625DE: The monitor returned an invalid monitor technology type. CRT, Plasma and LCD (TFT) are examples of monitor technology types. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.[2]0xC02625DF: SetMonitorColorTemperature()'s caller passed a color temperature to it which the current monitor did not support. This error implies that the monitor violated the MCCS 2.0 or MCCS 2.0 Revision 1 specification.[2]0xC02625E0: This function can only be used if a program is running in the local console session. It cannot be used if the program is running on a remote desktop session or on a terminal server session.[2]0xC02625E1: This function cannot find an actual GDI display device which corresponds to the specified GDI display device name.[2]0xC02625E2: The function failed because the specified GDI display device was not attached to the Windows desktop.[2]0xC02625E3: This function does not support GDI mirroring display devices because GDI mirroring display devices do not have any physical monitors associated with them.[2]0xC02625E4: The function failed because an invalid pointer parameter was passed to it. A pointer parameter is invalid if it is NULL, points to an invalid address, points to a kernel mode address, or is not correctly aligned.[2]0xC02625E5: The function failed because the specified GDI device did not have any monitors associated with it.[2]0xC02625E6: An array passed to the function cannot hold all of the data that the function must copy into the array.[2]0xC02625E7: An internal error caused an operation to fail.[2]0xC02605E8: The function failed because the current session is changing its type. This function cannot be called when the current session is changing its type. There are currently three types of sessions: console, disconnected and remote.[2]
Sources
- https://msdn.microsoft.com/en-us/library/cc231198.aspx
- winerror.h from Windows SDK 10.0.14393.0