TL;DR: Update GPU drivers first — it solves more DaVinci Resolve problems than any other single fix. For crashes on startup: delete the preference file and let Resolve rebuild it.
I’ve evaluated a lot of video editing software over the years, and DaVinci Resolve is genuinely impressive — free tier does things competitors charge hundreds of dollars for. But it’s also a demanding application that doesn’t hold your hand when things go wrong. When it breaks, it tends to break hard, and the error messages are often cryptic. I’ve seen teams waste half a day on issues that had a two-minute fix. These are those fixes.
Fix 1: Crashes on Launch
Resolve won’t open at all, or it opens briefly and immediately crashes. This is almost always one of two things: GPU drivers or a corrupt preference file.
Step one: update your GPU drivers. Not “check if there’s an update” — actually go do it now before anything else.
- NVIDIA: Open GeForce Experience > Drivers tab > Check for Updates > Download and install. If you don’t have GeForce Experience, go to nvidia.com/drivers, enter your GPU model, and download the latest Game Ready Driver.
- AMD: Open AMD Radeon Software > Home > Check for Updates. Or go to amd.com/en/support, enter your GPU, and download the latest Adrenalin driver.
- Intel Arc: Open Intel Arc Control or go to intel.com/content/www/us/en/download-center/ and get the latest graphics driver.
Outdated or partially corrupted GPU drivers are the single most common cause of DaVinci Resolve startup crashes. Blackmagic Design updates Resolve frequently, and new versions regularly require newer driver features.
If updating drivers doesn’t fix it: delete the preference file. Resolve’s preferences can become corrupted after a bad shutdown, a failed update, or even a hardware change. Deleting the file forces Resolve to rebuild it fresh.
On Windows: Press Win+R, type %appdata%\Blackmagic Design\DaVinci Resolve\Support and hit Enter. Delete the file named Resolve Disk Database (it may appear as just the database file with no extension). On Mac: Open Finder, press Cmd+Shift+G, navigate to ~/Library/Application Support/Blackmagic Design/DaVinci Resolve. Look for the preferences file and delete it. Resolve will regenerate everything on next launch.
One more thing: if you’re on Windows and Resolve crashes immediately at the splash screen, try right-clicking the Resolve shortcut > Run as administrator. Some Windows configurations restrict GPU access for non-admin processes in ways that specifically break Resolve.
Fix 2: GPU Error / Unsupported GPU
You see an error like “Unsupported GPU processing mode,” “Could not find any GPU,” or Resolve launches but everything is slow and the GPU indicator shows nothing.
First, let’s confirm what Resolve thinks it has access to. If you can get Resolve open (even in a degraded state), go to DaVinci Resolve > Preferences > System (on Mac it’s the menu bar > DaVinci Resolve > Preferences; on Windows it’s the top-left DaVinci Resolve menu). Click the Memory and GPU tab.
Under GPU configuration: set GPU processing mode to match your hardware. CUDA for NVIDIA cards, OpenCL for AMD and Intel. Don’t leave it on “Auto” — Auto sometimes picks the wrong GPU, especially on laptops with both integrated and discrete graphics. Under GPU selection, click “Use selected GPU” and manually select your discrete GPU from the list.
Click Save and restart Resolve completely.
If your GPU isn’t appearing in the list at all: It may be unsupported. Resolve’s minimum GPU requirements are an NVIDIA GPU with CUDA 11 support (GTX 600 series or newer, practically speaking) or an AMD GPU with OpenCL 1.2 or higher. Very old cards won’t work. If your GPU is borderline, check Blackmagic Design’s official system requirements page.
Fallback to CPU mode: If you need Resolve working right now and can’t resolve the GPU issue, go back to Preferences > Memory and GPU and set GPU processing mode to CPU. This disables hardware acceleration. Everything will be slow — real-time playback will suffer on anything but simple timelines — but Resolve will at least function while you sort out the GPU situation.
Fix 3: Project Won’t Open
You open Resolve, click a project, and nothing happens. Or you get a database error. Or Resolve opens but the project is empty.
Check the Project Manager. In Resolve’s Project Manager (the home screen when you launch), look at which database is selected in the top left dropdown. If you’re connected to a local database and your project isn’t showing up, check whether you accidentally switched to a different database. Resolve can have multiple local databases, and it’s easy to accidentally create a new blank one.
Try restoring from backup. Resolve automatically backs up projects. On Windows, backups live at: %appdata%\Blackmagic Design\DaVinci Resolve\Support\Backup. On Mac: ~/Library/Application Support/Blackmagic Design/DaVinci Resolve/Backup. You’ll find timestamped .drp files. In Resolve’s Project Manager, right-click in the project list > Restore Project Backup and point it at one of these files.
If the project was exported as a .drp file: File > Import Project in Resolve’s Project Manager. Browse to the .drp file. If the file is corrupted, you’ll get an error here — at that point, you’re relying on the automatic backups above.
Database corruption (serious case). If the entire Resolve database is corrupted — not just a single project — you’ll see errors at launch or the Project Manager will show an empty list with errors. In this scenario: close Resolve, navigate to the database folder (same location as above), and look for the Resolve Project folder. There’s a SQLite database file in there. You can try opening it with a SQLite tool to check for corruption. Usually at this point though, restoring from the most recent backup is faster than attempting database repair.
Fix 4: Audio Sync Issues
You export your edit and the audio is out of sync. Or it starts in sync and drifts progressively worse over time. This is almost always a frame rate problem.
Check your timeline frame rate. In Resolve, go to File > Project Settings (or Shift+9) > Master Settings. Look at Timeline frame rate. This needs to match the frame rate of your primary footage — if your camera shot at 23.976fps and your timeline is set to 24fps, you’ll get sync drift.
Check your clips’ actual frame rate. In the Media Pool, right-click a clip and look at Properties, or enable the FPS column in the list view. If you have mixed frame rates in one timeline (say, some 30fps clips mixed with 60fps clips), the conforming process can misalign audio. Resolve handles mixed frame rates, but it helps to make sure your timeline is set to the frame rate that matches the majority of your footage.
Check your timeline audio sample rate. File > Project Settings > Master Settings. The Timeline audio sample rate must match your audio files. If your audio was recorded at 48kHz and your timeline is set to 44.1kHz (more common in music production), you’ll get desync on export even though it looks fine in the timeline. Set this to 48kHz for most video work.
Enable audio waveform sync check. In the Edit page, look at a clip’s audio waveform and compare it to adjacent clips after the point where sync looks off. Resolve’s Fairlight page (the dedicated audio tab) gives you a much better view of any timing discrepancies. If audio is shifted by exactly one second or a specific frame count, it may be a source file issue rather than a project settings issue.
Fix 5: Performance / Lag on Playback
Resolve plays back stuttering, dropping frames, or just crawling. Common on underpowered machines, but even beefy systems can run into this with demanding timelines.
Generate optimized media. In the Media Pool, select your clips > right-click > Generate Optimized Media. This creates lower-resolution proxy files that Resolve uses during editing. You still export from the original files, but playback is dramatically smoother. Optimized media settings are at File > Project Settings > Master Settings > Optimized Media and Render Cache.
Use proxy mode. At the top right of the timeline viewer, there’s a small rocket/gauge icon. Click it and set Playback > Proxy Mode to “Half Resolution” or even “Quarter Resolution” for very complex timelines. This reduces rendering quality for real-time playback only — exports are still full quality.
Set your cache location to an SSD. This matters more than people realize. Go to File > Project Settings > Master Settings > Working Folders. Make sure the Cache files location is pointing to an SSD, not a spinning hard drive. On editing workstations I’ve set up for teams, moving the cache to an NVMe drive has sometimes tripled playback performance on complex timelines.
Reduce timeline resolution for editing. Under File > Project Settings > Master Settings, there’s a Proxy media resolution setting. For 4K timelines, editing at 1/2 resolution (1080p) is nearly indistinguishable in the edit and much faster.
Render cache. Go to Playback > Render Cache > Smart. With Smart mode enabled, Resolve will automatically render cache frames in the background for complex segments of your timeline, significantly reducing stutter on future playback passes.
Fix 6: Render Failures
You hit Deliver, the render starts, and then it fails — sometimes immediately, sometimes 90% through. Infuriating.
Check disk space first. This is the most common cause and the easiest to overlook. A 4K ProRes file can easily be 50-100GB or more. If your output drive doesn’t have enough space, the render will fail partway through with an unhelpful error. In Resolve’s Deliver page, the output path shows where the file is going — confirm that drive has adequate free space.
Codec issues. H.265 (HEVC) encoding fails on systems that lack hardware H.265 support. This affects older NVIDIA cards (pre-GTX 1000 series) and some AMD configurations. To isolate: change your export format in the Deliver page to H.264 or to QuickTime > ProRes 422 and re-attempt the render. If those succeed and H.265 doesn’t, it’s a codec capability issue, not a general Resolve problem.
Memory exhaustion on complex timelines. Timelines with heavy Fusion effects, many color grades, or lots of nested nodes can exhaust RAM during renders. Go to DaVinci Resolve > Preferences > Memory and GPU and look at System memory to use for caching. If it’s set very high (close to your total RAM), other processes can’t run and Resolve itself can destabilize. Try setting it to 50-60% of your total RAM and re-rendering. On Windows, also close all other applications before rendering complex timelines.
Permissions on the output path. On both Windows and Mac, if Resolve doesn’t have write permission to the output folder, renders will fail with cryptic errors. Right-click the destination folder, check Properties (Windows) or Get Info (Mac), and confirm your user account has write permission.
Fix 7: DaVinci Crashing During Editing
Resolve was working fine but keeps crashing mid-edit. Not at launch — during use.
Set the Fusion memory limit. Fusion (Resolve’s visual effects compositor) is a known memory hog. Go to DaVinci Resolve > Preferences > Memory and GPU. Find Fusion Memory Cache and reduce it. The default is often too high for systems with less than 32GB RAM. Try setting it to 4GB or 8GB if you’re running 16GB RAM total. Click Save and restart Resolve.
Move your cache to a faster drive. Covered in Fix 5, but worth repeating here: if your cache drive fills up or is slow, Resolve will crash mid-edit. Go to File > Project Settings > Master Settings > Working Folders and verify the cache location is on a fast, non-full drive.
Check GPU temperature. Crashes during complex operations are sometimes thermal throttling. Use GPU-Z (Windows) or iStat Menus (Mac) to monitor GPU temperature while you work. If it’s hitting 90°C+ and then crashing, that’s a cooling issue — clean the fans, reapply thermal paste, or improve case airflow.
Purge the render cache. Go to Playback > Delete Render Cache > All. A corrupted render cache can cause intermittent crashes on specific sections of a timeline.
Update Resolve. Blackmagic Design releases updates fairly regularly, often specifically addressing stability issues. Help > Check for Updates inside Resolve, or check blackmagicdesign.com/support for the latest version.
Fix 8: Color Page Not Showing Properly
The Color page loads but looks wrong — scopes are blank, the viewer shows incorrect colors, or the entire color grade environment looks off.
Check GPU acceleration settings. Go to DaVinci Resolve > Preferences > Memory and GPU. Look at the GPU selection section. If Resolve is running with CPU fallback (which you might have set in Fix 2), the Color page scopes and real-time processing will be significantly degraded. Confirm your GPU is selected and working.
Verify your display color profile. The viewer in the Color page is affected by your operating system’s display color profile. On Windows: right-click desktop > Display Settings > Advanced Display Settings > Display adapter properties > Color Management tab. Confirm your monitor’s ICC profile is selected. On Mac: System Settings > Displays > Color Profile. Use the profile recommended for your monitor, not a generic sRGB profile — the difference matters on the Color page.
Check Color Management settings in the project. File > Project Settings > Color Management. If “Color science” is set to DaVinci YRGB Color Managed but your input and output color spaces don’t match your footage and monitor, colors will look wrong in the viewer while the actual grade is fine. For most straightforward editing work, set Color Science to “DaVinci YRGB” (not color managed) and handle color spaces manually.
Scope settings. If scopes (histogram, waveform, parade) are blank: click the scope panel, look for a small settings icon (three dots or gear), and confirm the scope is set to show the current timeline signal, not an empty input. Sometimes scopes disconnect from the viewer after a Resolve crash. Closing and reopening the Color page panel can reset the connection.
DaVinci Resolve has a steeper troubleshooting curve than a lot of editing software. But the fixes above cover the overwhelming majority of what goes wrong in practice. Update drivers, clear preferences when needed, manage memory settings, and make sure your cache is on fast storage.
If you’re evaluating whether Resolve is the right tool for your team or workflow, it’s worth checking our roundup of the best AI video editing tools in 2026 — a few of them handle the GPU management and proxy workflows more transparently than Resolve does, which matters when you’re onboarding non-technical editors.