Resolve worked yesterday. Today, after updating Resolve - or after Windows quietly changed something - it refuses CUDA mode and blames the driver. Here is why that pairing breaks, and the clean way to fix it.
Every version of DaVinci Resolve is built against a certain generation of GPU technology, and it checks your driver version at startup. When Blackmagic raises the floor in a new release, a driver that was perfectly fine last month suddenly fails the check. The card has not changed and nothing is broken - the software and driver are simply out of step. The fix is almost always to bring the driver up to the version your Resolve expects.
Messages in this family include Unable to run in CUDA mode as the installed NVIDIA driver is incompatible and the general GPU Configuration Warning right after a Resolve upgrade. Both point the same way: Resolve can see the card, but cannot use it through the driver that is installed. Note what changed most recently - a Resolve update, a Windows update, or a driver change - because that is the side of the pair that moved.
Do not guess. On Windows, open the NVIDIA App (or the older NVIDIA Control Panel, under Help then System Information) to see the installed driver version, or run dxdiag and read the Display tab. AMD users can read the version inside the AMD Software app. Write the number down - you will want it to prove the update actually landed.
Honest note: the Game Ready and Studio branches come from the same family, and Game Ready usually works too - but when a creator app complains, Studio is the branch to be standing on before you troubleshoot anything else.
A driver that Windows Update half-replaced, or that survived several in-place upgrades, can report the right version yet behave like a broken one. Symptoms: the warning persists on the newest driver, or the card vanishes from Resolve's GPU list entirely. That is the case for a clean driver installation - removing every trace of the old driver before installing fresh. It is a bigger hammer, so keep it for exactly this situation; the clean-install guide on this site walks through it safely.
Treat Resolve and its GPU driver as a matched pair. Update Resolve, then check the driver. Update the driver, then expect one clean Resolve restart to re-detect everything. And when a brand-new Resolve release lands, give it a few days before updating your production machine - if Blackmagic or the GPU vendors find a pairing problem, it surfaces fast and gets patched.
The video shows the incompatible-driver message being cleared with the correct Studio Driver - including how to confirm the new driver version actually installed.
▶️ Watch Full VideoNew Resolve versions raise the minimum GPU driver and CUDA requirements. Your driver did not change, but the bar moved - so a setup that passed last week fails the check today. Updating the driver to the current release closes the gap.
Studio. NVIDIA tests the Studio branch specifically against creative applications and holds it on proven versions, which is what you want under an editor. Game Ready targets day-one game releases and usually works, but Studio is the safer default for a Resolve machine.
Yes - the warning tests the driver, not the card's power. A flagship GPU on a two-year-old driver will fail where a modest card on a current driver passes. That is why the driver step comes before any hardware conclusion.