The “Unsupported GPU Processing Mode” error means DaVinci Resolve started up and couldn’t find a graphics card that meets its driver, memory, or processing API requirements. The fix is almost always one of three things: update or cleanly reinstall your graphics driver, manually pick the right GPU and processing mode in preferences, or reset Resolve’s saved configuration so it re-detects your hardware from scratch.
This guide walks through why the error happens and how to clear it on Windows, Mac, and Linux, in the order that actually works, plus how to tell whether your GPU is simply too old for the version of Resolve you’re running.
What does this error mean?
Resolve leans on your graphics card for nearly everything it does: playback, color grading, noise reduction, Fusion effects, and rendering. When the app launches, it runs a hardware check called GPUDetect before the interface even appears. If that check can’t find a supported GPU, or finds one but can’t confirm it supports a processing API Resolve can use, you get the warning along with two options: “Update Configuration” or “Quit.”
The three processing modes are CUDA (Nvidia only), OpenCL (Nvidia, AMD, and Intel), and Metal (Mac only, built into macOS). Resolve needs to confirm at least one of these is genuinely working, not just that a card is physically installed. A GPU that’s present in Device Manager but running on a generic or mismatched driver often reports zero compute support to Resolve, which is exactly what produces this message. The software isn’t guessing about your hardware; it’s reading back whatever the driver tells it, and a broken or incomplete driver answer looks identical to no GPU at all.
What causes it?
A handful of situations account for nearly every case people run into.
The driver is missing, outdated, or the wrong type. This is the single most common cause. Windows Update sometimes replaces a dedicated Nvidia or AMD driver with a generic Microsoft basic display driver during a system update, and Resolve can’t extract any processing capability from that generic driver.
Two driver versions are fighting each other. Installing a new AMD Adrenalin or Nvidia driver directly on top of an older one, without a clean uninstall first, can leave conflicting DLLs and registry entries behind. Resolve then queries the GPU and gets an inconsistent or incomplete answer about what it supports.
The GPU no longer meets the minimum for your installed Resolve version. Blackmagic raises the hardware floor with major releases. A card that ran Resolve 17 without issue can fall below the requirement after you update to a newer version, even though nothing about the card itself has changed.
Resolve’s saved configuration file has a bad or leftover entry. Settings left behind from a previous GPU, a previous driver, or an interrupted install can point Resolve at hardware or a mode that no longer matches your current setup. This is common after swapping a graphics card without reinstalling Resolve.
A laptop is defaulting to the wrong GPU. Many laptops pair a low-power integrated chip with a discrete GPU. If Windows or macOS routes Resolve to the integrated chip by default and that chip falls short of the requirement, you’ll see this error even though a perfectly capable discrete GPU sits right next to it, unused.
The GPU’s compute capability is too low. This applies mainly to older Nvidia cards. Resolve versions from 16.2.7 onward require CUDA 11, which in turn requires a compute capability of 3.5 or higher. A card below that line cannot pass the check no matter what driver you install, because the hardware itself lacks the required instruction set.
Check your GPU actually meets the requirements first
Before touching drivers or digging through settings, confirm your hardware is actually in range for your installed Resolve version. Requirements shift with nearly every release, and the readme packaged with your specific installer is the only fully current source, so check Blackmagic’s support and download page for the exact build if any of the numbers below look borderline for your setup.
As of Resolve 21.0.4, the official minimums are:
| Platform | Minimum GPU | Driver / API |
| Windows | Integrated or discrete, 4 GB VRAM | OpenCL 1.2 or CUDA 12.8; Nvidia Studio driver 581.57 or newer |
| macOS | Apple Silicon only (Intel Macs unsupported) | Metal, macOS 15 Sequoia or later |
| Linux | Discrete GPU, 4 GB VRAM | OpenCL 1.2 or CUDA 12.8; Nvidia driver 580.119.02 or newer |
If you’re running an older Resolve version, the numbers will be lower. Releases before version 18 asked for only 2 GB of VRAM and accepted CUDA 11 instead of 12.8. If your card sits below both the OpenCL and CUDA lines for the Resolve version you have installed, no driver update will fix the error, because the limitation is the silicon itself, not the software talking to it. At that point your realistic options are installing an older Resolve build with a lower hardware floor, or moving to a newer GPU. Downgrading Resolve is a legitimate short-term fix if you’re on a laptop you can’t easily upgrade.
| If Resolve opens fine on a blank project but throws a GPU error only once you add certain effects, noise reduction, or 4K media, that’s a separate performance or memory issue, not a detection failure. This guide covers the startup error, where Resolve can’t confirm any working GPU at all before you’ve even opened a project. |
Fix it on Windows
Windows has the most documented fixes for this error, in large part because it’s the platform with the widest range of GPU brands and driver combinations. Work through these in order; most people are fixed by the first two.
1. Install the correct driver, cleanly
Download the latest driver straight from the manufacturer’s site rather than trusting whatever Windows Update installed.
Nvidia: get the Studio Driver, not Game Ready, from the Nvidia driver download page. Studio drivers go through additional validation specifically against creative applications like Resolve, Premiere, and Photoshop, and Blackmagic’s own driver recommendations reference Studio driver versions rather than Game Ready ones.
AMD: get the latest Adrenalin or Radeon Pro driver from AMD’s website, matched to your card’s generation.
If you already have a driver installed and simply changing versions hasn’t helped, do a clean removal first. Boot into Windows Safe Mode and run Display Driver Uninstaller (DDU) to strip out every trace of the old driver, then reboot normally and install the fresh one on a clean base. This clears leftover files that a standard reinstall or update leaves behind, and it’s one of the more consistently reported fixes for this exact error across both AMD and Nvidia setups. Some AMD driver packages also include a factory reset option during installation that achieves a similar result without a separate uninstaller tool.
2. Set the GPU manually instead of Auto
Leaving GPU selection on Auto is normally fine, but on a system with two GPUs or a flaky driver, it can pick the wrong one or fail to pick anything.
- Open DaVinci Resolve and go to DaVinci Resolve > Preferences.
- Click the System tab, then Memory and GPU.
- Under GPU Configuration, uncheck Auto next to GPU Processing Mode.
- Choose CUDA for an Nvidia card or OpenCL for AMD.
- Uncheck Auto under GPU Selection and manually tick your dedicated GPU. Untick any integrated graphics chip if one appears in the list.
- Save the settings and restart Resolve.
If Resolve crashes or shows the error before you can even reach Preferences, force the assignment from Windows itself instead: open Settings > System > Display, scroll to Graphics settings, add DaVinci Resolve as a desktop app, and set its GPU preference to “High performance.” This solves the specific case where a laptop silently routes Resolve to integrated graphics rather than the dedicated card.
3. Reset Resolve’s saved configuration
A stale configuration entry can override a perfectly functional GPU. Open Resolve, go to Preferences, and use the Reset option under Advanced Settings. This returns the app to its defaults and forces a fresh hardware detection the next time it launches. If Resolve won’t open far enough to reach that menu, you can locate and rename the configuration folder directly instead, typically found under your Windows user profile’s AppData directory, so Resolve rebuilds a clean one automatically on the next launch.
4. Reinstall Resolve as a last resort
If none of the steps above resolve it, uninstall Resolve completely, restart the PC, and install it fresh from the official download. Interrupted or partial installs occasionally skip a required component silently, and a clean reinstall is the most reliable way to catch that.
Fix it on Mac
Mac troubleshooting is narrower than Windows because Apple controls both the hardware and the graphics stack end to end, which removes a lot of the driver-mismatch scenarios that cause this error elsewhere.
Confirm you’re on a supported machine and OS version. Current Resolve releases require an Apple Silicon Mac; Intel Macs are no longer supported by the newest builds. If you’re on an Intel Mac and this error appeared after updating Resolve, the fix isn’t a setting change, it’s staying on (or rolling back to) an older Resolve version whose own readme still lists Intel Mac support.
Update macOS fully. Apple bundles graphics driver improvements into system updates rather than shipping them as a separate download the way Nvidia and AMD do, so running an outdated macOS version is functionally the same problem as running an outdated GPU driver on Windows. Check for updates under System Settings > General > Software Update before anything else.
Check the Preferences setting the same way you would on Windows. Go to DaVinci Resolve > Preferences > Memory and GPU, uncheck Auto, and explicitly select Metal as the processing mode.
Rule out an eGPU conflict. If you’re using an external GPU enclosure over Thunderbolt, disconnect it and test with the built-in GPU only. External GPU support in professional creative apps has always been inconsistent across macOS versions, and Resolve has a documented history of struggling to detect eGPUs cleanly on startup, particularly right after a macOS update changes how the OS reports connected displays and devices.
Fix it on Linux
Linux has the most moving parts of the three platforms, mainly because the OpenCL and CUDA runtime aren’t bundled with the operating system the way graphics drivers are on Windows or Mac.
Install the proprietary driver, not the open-source one. On Nvidia hardware, the open-source Nouveau driver that ships by default with many distributions does not expose CUDA and only has limited, unreliable OpenCL support. Resolve will report no usable GPU even though one is physically installed and working for everything else on the desktop. Install Nvidia’s proprietary driver package built for your distribution and reboot before trying Resolve again.
Match the driver version to your Resolve build. Current Resolve releases expect Nvidia driver 580.119.02 or newer on Linux, while older Resolve versions tolerated older driver branches. Updating Resolve without updating the driver to match, or the reverse, is a common and easy-to-miss trigger for this exact error.
Confirm the OpenCL runtime is actually present. For AMD and Intel GPUs on Linux, you need the correct OpenCL implementation package installed and visible to the system; the exact package name varies by distribution and GPU vendor. After installing it, run clinfo from a terminal. If it returns no platforms at all, Resolve won’t find a usable GPU either, regardless of what hardware is physically connected.
Check for a duplicate or malformed configuration entry. Resolve’s Linux config file can end up with a duplicate or conflicting GPU mode line after a botched update, which produces the same blank, greyed-out GPU selection screen reported across Arch, Fedora, and Manjaro forums. Backing up and then deleting the configuration directory forces Resolve to regenerate a clean one from scratch on next launch, which resolves this specific variant more often than adjusting driver settings does.
When the GPU selection screen is empty or greyed out
A specific and very common variant of this error shows the Preferences screen with no GPUs listed at all, and both the processing mode and GPU selection dropdowns greyed out and unclickable. This means Resolve’s detection step found zero compatible devices during startup, not that it found your GPU and specifically rejected it.
This almost always comes down to one of two things: the driver genuinely isn’t installed, isn’t loaded, or is a stripped-down version missing compute support, or the GPU itself falls below the compute or memory floor for the Resolve version you’re running. You can check driver status directly rather than guessing: on Windows, Device Manager will flag a driver problem with a warning icon next to the GPU entry; on Linux, nvidia-smi for Nvidia cards will either report your card’s details or fail outright if the driver isn’t loaded correctly. Confirming which situation you’re in first saves real time, since a driver problem is usually fixable within minutes and a hardware floor problem is not fixable through settings at all.
Preventing it after you’ve fixed it once
Once the error is cleared, a few habits keep it from coming back. Avoid letting Windows Update silently push a driver update to a GPU that Resolve depends on; check what changed if the error reappears after any Windows update. Keep a record of the driver version that works with your current Resolve version before you update either one, so you have a known-good rollback point. And treat a Resolve version update the same way you’d treat any driver update: check the current readme for that build’s specific requirements before installing, rather than assuming last month’s compatible setup still applies.
Frequently asked questions
Why does DaVinci Resolve say my GPU is unsupported when it worked fine before?
An update to Resolve, your graphics driver, or your operating system likely changed what’s required. Check your current driver version against Resolve’s minimum for your platform and update or reinstall it.
Can I run DaVinci Resolve with only integrated graphics?
Yes, as long as the integrated GPU meets the current VRAM and processing API minimum for your Resolve version. Performance will be limited beyond basic HD editing without a dedicated card.
Should I use CUDA or OpenCL on an Nvidia card?
CUDA is generally faster and more stable for Nvidia hardware inside Resolve. Use OpenCL only if CUDA isn’t available on your driver or is causing instability on your specific setup.
Does resetting Resolve’s preferences delete my projects?
No. Preferences and project files are stored completely separately. Resetting preferences only clears app settings like GPU configuration, window layout, and playback options.
Why is my GPU selection screen completely empty with nothing to click?
This means Resolve detected zero usable graphics devices at startup, usually because the driver isn’t installed or loaded correctly, or because the card falls below the compute requirement for your installed Resolve version.
Conclusion
The Unsupported GPU Processing Mode error comes down to Resolve failing to detect a graphics card that meets its current driver and processing API requirements. On Windows and Linux, a clean driver install paired with manually selecting your GPU and processing mode in Preferences clears it in most cases. On Mac, confirm your hardware and macOS version are still supported by your Resolve build. If the problem persists after that, resetting Resolve’s saved configuration forces a fresh hardware check that resolves most remaining cases.
Related Post:
Is 70°C Too Hot for a GPU? What the Number Really Means
Red Light on GPU When PC Is Off: What It Means and When to Worry
Client Server Runtime Process High GPU Usage: Why It Happens and How to Fix It
How to Know If Your GPU Is Failing: 7 Warning Signs and How to Test It
Satisfactory “GPU Crash Dump Triggered”: What It Means and How to Fix It
