Vulkan errors in games

🖥 DirectX, drivers and GPU VK_ERROR_* ⏱ 7 steps · ≈77 min
Takes some timeSeveral possible causes — work through the steps top to bottom
Vulkan errors come in two groups. At launch (VK_ERROR_INCOMPATIBLE_DRIVER, VK_ERROR_INITIALIZATION_FAILED, “vkCreateInstance failed”) — a driver without Vulkan or the game on integrated graphics: install the vendor’s driver and select the discrete GPU. During play (VK_ERROR_DEVICE_LOST) — the Vulkan equivalent of DXGI_ERROR_DEVICE_REMOVED: driver, overclock, power, overheating.
✔ Facts and links checked:

What this error means

Vulkan runs “closer to the metal” than DirectX 11, so driver bugs and GPU instability surface earlier. Vulkan is not installed separately — only with the GPU driver. Overlays that hook in as “Vulkan layers” (screen recording, monitoring) can also break start-up.

Where exactly the chain breaks

Causes — most common first

A Windows Update driver without Vulkan, or an old version
most common
The game starts on integrated graphics
common
Overlay Vulkan layers (recording, monitoring)
common
DEVICE_LOST: overclock, power, overheating
common

Step-by-step fix: from simple to advanced

Test the game after each step — only move on if the error is still there.

  1. Update your GPU driver from the vendor’s site easy ≈10 min

    The driver installed by Windows Update is often old and stripped down. Download the current one from the official NVIDIA, AMD or Intel site for your model and Windows version. Your GPU model is shown in Task Manager → Performance → GPU.

  2. Check the power plan and GPU selection easy ≈5 min

    Laptop: plug in the charger (on battery the GPU cuts power) and pick the “Best performance” mode. Settings → System → Display → Graphics: set the game exe to “High performance” so it runs on the discrete GPU, not the integrated one. Desktop: the monitor must be plugged into the graphics card, not the motherboard port.

  3. Disable overlays and on-top tools easy ≈5 min

    Overlays inject into the game process and hook frame presentation — a frequent cause of launch crashes and black screens. For the test, turn off: Discord overlay, Steam overlay (game Properties → “Enable the Steam Overlay”), NVIDIA App / GeForce Experience, AMD Adrenalin, Xbox Game Bar, MSI Afterburner + RivaTuner, screen recorders and “FPS boosters”.

  4. Do a clean driver reinstall medium ≈20 min

    Profiles and caches left from the old driver keep failing. NVIDIA: pick custom install and tick “Perform a clean installation”. AMD: the Adrenalin installer has a “Factory Reset” option, or remove the driver with the official AMD Cleanup Utility. If the error appeared right after an update, roll back to the previous stable version from the same site instead.

  5. Return to stock clocks (overclock, XMP/EXPO, undervolt) medium ≈15 min

    An overclock that passes stress tests can still fail in a specific game or shader load. Reset the profile in MSI Afterburner / Adrenalin, remove the undervolt and, to test memory, temporarily disable XMP/EXPO in BIOS. If the error disappears at stock, lower clocks or improve stability.

  6. Check temperatures under load medium ≈20 min

    GPU temperature is shown in Task Manager (Performance → GPU) and in the NVIDIA/AMD panels; CPU temperature — in the motherboard or CPU vendor’s utility. If after 10–20 minutes of play the values hit the limit (GPU and CPU start throttling, a laptop runs fans at maximum), clean the cooling, check the fans and do not put a laptop on soft surfaces.

  7. Switch the game to DirectX easy ≈2 min

    If the game supports several APIs, pick DirectX 11/12 in the settings. It is a workaround until a fixed driver arrives.

Diagnostics for your PC

Enter your GPU, RAM and game — we will compare them with the requirements and point out what matters for your PC. If you are signed in and saved a PC, it is filled in automatically.

This is a hint based on specs, not a measurement. Browsers cannot see your driver version or power supply model: the FPSHQ app for Windows shows your driver version and real FPS.

Key figures

Unique FPSHQ metrics from this page's data

7
steps in the guide
77min
minutes for all steps
2/5
error severity
3
primary sources (Microsoft, NVIDIA, AMD, Steam)
Oct 2, 2026
guide verified

How long each step takes

Time estimate from the guide: 7 steps, about 77 minutes. Steps go from simple to complex — the error usually disappears on the first ones.

1. Update your GPU driver from the vendor’s site1. Update your GPU driver from t…10 min2. Check the power plan and GPU selection2. Check the power plan and GPU …5 min3. Disable overlays and on-top tools3. Disable overlays and on-top t…5 min4. Do a clean driver reinstall4. Do a clean driver reinstall20 min5. Return to stock clocks (overclock, XMP/EXPO, undervolt)5. Return to stock clocks (overc…15 min6. Check temperatures under load6. Check temperatures under load20 min7. Switch the game to DirectX7. Switch the game to DirectX2 min1. Update your GPU driver from the vendor’s site1. Update your GPU driver from the…10 min2. Check the power plan and GPU selection2. Check the power plan and GPU sel…5 min3. Disable overlays and on-top tools3. Disable overlays and on-top tools5 min4. Do a clean driver reinstall4. Do a clean driver reinstall20 min5. Return to stock clocks (overclock, XMP/EXPO, undervolt)5. Return to stock clocks (overclo…15 min6. Check temperatures under load6. Check temperatures under load20 min7. Switch the game to DirectX7. Switch the game to DirectX2 min
In short

Vulkan errors in games

Vulkan errors come in two groups. At launch (VK_ERROR_INCOMPATIBLE_DRIVER, VK_ERROR_INITIALIZATION_FAILED, “vkCreateInstance failed”) — a driver without Vulkan or the game on integrated graphics: install the vendor’s driver and select the discrete GPU. During play (VK_ERROR_DEVICE_LOST) — the Vulkan equivalent of DXGI_ERROR_DEVICE_REMOVED: driver, overclock, power, overheating.

steps in the guide
7
minutes for all steps
77 min
guide verified
Oct 2, 2026
updated · source: NVIDIA, AMD, Intel, FPSHQ model estimate

FAQ

What is vulkan-1.dll and where do I get it?

It is the Vulkan loader installed with the GPU driver. See our separate vulkan-1.dll guide.

What does VK_ERROR_DEVICE_LOST mean?

The GPU stopped responding while working — the Vulkan equivalent of DXGI_ERROR_DEVICE_REMOVED in DirectX. Causes are the same: driver, unstable overclock, overheating or insufficient power. Start with a clean driver install and resetting the overclock.

What does VK_ERROR_INCOMPATIBLE_DRIVER mean?

The driver does not support the Vulkan version the game requires, or the GPU does not support Vulkan at all. Update the driver; if the GPU is old (before GeForce 600 / Radeon HD 7000), Vulkan is not available on it.

Do overlays interfere with Vulkan?

Yes: overlays and capture tools register Vulkan “layers”, and an outdated layer can break start-up. Disable overlays (Discord, MSI Afterburner/RTSS, OBS, old capture utilities) and try again.

🧭 Nothing helped?

Write down the exact error text and the faulting module from Event Viewer (Windows Logs → Application) and contact the game developer’s support — attach the crash report if the game created one. Also check our related errors.

Related errors

Games where this error occurs

Official sources

Facts and links checked: 2026-10-02