DXVK errors and log messages, decoded

Likely causes, most likely first

1. The GPU driver is missing or broken
2. A very old GPU with no Vulkan driver
3. A virtual machine or remote-desktop session

Fixes

1. Install the GPU vendor's driver from the vendor's own site, not from Windows Update. (not tested by us)
2. Check your GPU against the requirements page. (not tested by us)

Likely causes, most likely first

1. No Vulkan driver installed for the GPU
2. Wine with no Vulkan driver (ICD)
3. A virtual display or remote-desktop session
4. A broken driver install

Fixes

1. Update or reinstall the GPU driver. On laptops make sure the driver for the dedicated GPU is installed. (not tested by us)
2. Virtual machines and remote desktop sessions are not supported. (not tested by us)

Likely causes, most likely first

1. See the line above this one

Fixes

1. Fix the error that comes before it. (not tested by us)

Likely causes, most likely first

1. DXVK_FILTER_DEVICE_NAME, DXVK_FILTER_DEVICE_UUID or dxvk.deviceFilter excludes every GPU
2. No GPU meets DXVK's requirements (old GPU or driver)
3. 32-bit games under Linux without the 32-bit graphics drivers

Fixes

1. Remove the filter or correct it: it matches a substring of the Vulkan device name (tested: a matching name works, a non-matching one breaks Direct3D 11). (tested in our lab)
2. Update the driver, or use an older DXVK line for an old GPU. (not tested by us)

Likely causes, most likely first

1. An old driver
2. A GPU too old for this DXVK line

Fixes

1. Update the driver; if the GPU is old, pick an older DXVK line with the Version Picker. (not tested by us)

Likely causes, most likely first

1. Overlay hooking the window
2. Exclusive full-screen

Fixes

1. Close overlays; use borderless windowed. (not tested by us)

Likely causes, most likely first

1. No Vulkan or no usable driver (E01, E02)
2. A device filter that excludes every GPU (E04)

Fixes

1. Follow the earlier error. (not tested by us)

Likely causes, most likely first

1. Only d3d11.dll was copied

Fixes

1. Copy DXVK's dxgi.dll next to d3d11.dll (tested). (tested in our lab)

Likely causes, most likely first

1. dxgi.dll missing from the game folder

Fixes

1. Copy DXVK's dxgi.dll (tested). (tested in our lab)

Likely causes, most likely first

1. See E07 and E06

Fixes

1. Open the DXVK log next to the game's .exe and read the error before these codes. (not tested by us)

Likely causes, most likely first

1. Driver bug
2. Overclock or undervolt
3. An overlay
4. A DXVK regression

Fixes

1. Update or roll back the driver, remove any overclock, close overlays, try the previous DXVK. (not tested by us)

Likely causes, most likely first

1. VRAM exhausted
2. 32-bit address-space limit

Fixes

1. Lower texture quality; for 32-bit games check Large Address Aware and the memory settings. (not tested by us)

Likely causes, most likely first

1. Wine has no real monitor data to give

Fixes

1. Ignore them. (tested in our lab)

Likely causes, most likely first

1. No VR runtime installed

Fixes

1. Ignore them. (tested in our lab)

Likely causes, most likely first

1. The game probes for optional features

Fixes

1. Ignore it unless the game then fails. (tested in our lab)

Likely causes, most likely first

1. Software or minimal drivers

Fixes

1. Ignore it. (tested in our lab)

Likely causes, most likely first

1. Virtual displays

Fixes

1. Ignore it unless the game cannot find its monitor. (not tested by us)

Likely causes, most likely first

1. Old DXVK line

Fixes

1. Nothing to do. DXVK 3.x uses a different shader cache. (tested in our lab)

Likely causes, most likely first

1. DXVK's default for GPUs that are not AMD, NVIDIA or Intel

Fixes

1. Nothing to do; the GPU selection guide explains how to override. (tested in our lab)

Likely causes, most likely first

1. You set a frame rate limit in dxvk.conf

Fixes

1. Nothing wrong; see the FPS limit page for alternatives. (tested in our lab)

Likely causes, most likely first

1. Normal operation

Fixes

1. Nothing to do. (tested in our lab)