DaVinci Resolve Crashes When Rendering: Why It Happens and How to Fix It

DaVinci Resolve crashing mid-render is one of the most frustrating problems an editor can face, especially with a deadline close. The good news is that the cause is almost always one of a handful of fixable issues: GPU drivers, memory settings, a bad codec, or corrupted cache data. This guide walks through every proven fix in order of likelihood so you can get back to rendering without wasting time on the wrong solution.

Why DaVinci Resolve Crashes During Rendering

Rendering puts your system under sustained, full-load stress in a way that casual playback never does. When something in your hardware or software configuration cannot handle that load, the application crashes. Before diving into fixes, it helps to know which root cause you are likely dealing with.

The six most common reasons DaVinci Resolve crashes during a render:

• GPU driver conflict or outdated driver: The single most frequent cause; an unstable or incompatible driver fails under encode load. Jump to Fix 1

• Insufficient VRAM or RAM: DaVinci Resolve is memory-intensive; running out of VRAM or system RAM mid-render causes an immediate crash. Jump to Fix 2

• Corrupted render cache: Old or damaged cache files produce errors when Resolve tries to read them during export. Jump to Fix 3

• Codec or hardware encoder incompatibility: H.265 (HEVC) hardware encoding is especially prone to crashing on mismatched driver and GPU combinations. Jump to Fix 4

• Corrupted clip, broken Fusion node, or unsupported OFX plugin: A single problematic element in the timeline can reliably crash the render at the same point every time. Jump to Fix 5

• Full render drive or thermal throttling: Less common but easy to overlook; an overheating GPU or a nearly full drive can trigger a crash with no clear error message. Jump to Quick Checks

Most users resolve the issue within the first two or three fixes. A reinstall is almost never necessary.

Run These Quick Checks First

Before making any configuration changes, run through these three fast checks. Each takes less than two minutes and could save you significant troubleshooting time.

1. Verify free disk space on your render drive. DaVinci Resolve needs room to write temporary files during export. If your render drive has less than 15 to 20 percent free space, the render will fail. Delete unneeded files or point the render output to a drive with more headroom.

2. Check your DaVinci Resolve version. Open DaVinci Resolve > Help > About. Blackmagic Design releases updates specifically to fix stability bugs. If you are more than one minor version behind, for example running 18.1 when 18.6 is available, update before trying anything else. Download the latest installer directly from the Blackmagic Design support page.

3. Monitor GPU and CPU temperatures during a render attempt. Use GPU-Z or HWiNFO64 on Windows, or iStatMenus on macOS, to watch temperatures while a render runs. If your GPU reaches 90°C or higher, thermal throttling or a thermal shutdown is likely the cause. Check fan curves and case airflow before proceeding.

Fix 1 — Update or Rollback Your GPU Drivers

Outdated, corrupted, or poorly matched GPU drivers are the most common cause of DaVinci Resolve render crashes. This fix should be your first serious troubleshooting step.

1. Identify your current driver version. On Windows, open Device Manager > Display Adapters, right-click your GPU, and select Properties > Driver tab. On macOS, go to Apple menu > About This Mac > System Report > Graphics/Displays.

2. Download the correct driver. Visit the NVIDIA driver download page or the AMD Adrenalin download page. For NVIDIA, select Studio Driver rather than Game Ready Driver (see the section below). For AMD, choose the latest stable Adrenalin release, not a beta or optional build.

3. Perform a clean install on Windows using DDU. Download Display Driver Uninstaller (DDU) from Wagnardsoft. Boot into Safe Mode, run DDU to fully remove the existing driver, then reboot normally and install the new driver. A clean install removes leftover files that cause persistent instability.

4. Consider rolling back if the crash started after a recent driver update. In Device Manager > Display Adapters > Properties > Driver tab, click Roll Back Driver to return to the previous version. This is often the fastest fix if your setup was stable before a recent update.

5. Retest with a short render on a simple timeline before attempting your full project.

NVIDIA vs. AMD — Which Driver Type to Use for Video Editing

For DaVinci Resolve on NVIDIA hardware, always install the Studio Driver rather than the Game Ready Driver. Studio Drivers are tested against creative applications including DaVinci Resolve and are released on a slower, more stable update cycle. AMD does not separate its drivers into distinct game and studio branches, but sticking to the latest recommended Adrenalin release rather than optional or beta versions gives you the same benefit of a validated, stable build.

Fix 2 — Adjust Memory and GPU Settings Inside DaVinci Resolve

DaVinci Resolve’s default memory and GPU settings are not always optimized for your specific hardware. Incorrect settings can push the GPU or RAM past its limits during a render.

Navigate to: DaVinci Resolve > Preferences > Memory and GPU (keyboard shortcut: Ctrl+, on Windows or Cmd+, on macOS).

1. Set the system RAM allocation. In the Memory Configuration section, set Limit Resolve memory usage to no more than 70 to 75 percent of your total installed RAM. On a 32 GB system, cap Resolve at 22 to 24 GB. This leaves headroom for the operating system and background processes, which prevents mid-render memory exhaustion.

2. Assign a specific GPU instead of using Auto. Under GPU configuration, change the setting from Auto to your specific GPU by name. When set to Auto, DaVinci Resolve may attempt to use integrated graphics or split tasks in unstable ways, particularly on laptops.

3. Limit to a single GPU if you have multiple cards. Multi-GPU setups can introduce synchronization issues during a render. Deselect all but your primary GPU in the GPU list and retest.

4. Disable GPU decoding for problem codecs. If your crashes are tied to H.264 or H.265 source footage, go to Decode Options and uncheck Decode H.264/H.265 using hardware acceleration. This moves decoding to the CPU, which is slower but more stable on certain driver and hardware combinations.

5. Click Save and restart DaVinci Resolve fully before attempting another render.

Fix 3 — Clear the Render Cache and Delete Optimized Media

Corrupted render cache files are a silent and frequent crash source. DaVinci Resolve builds a render cache in the background during editing, and if any of those files become corrupted, the render process will fail when it tries to read them.

1. Delete the render cache. Go to Playback > Delete Render Cache > All. Confirm the deletion when prompted.

2. Delete optimized media. Go to Playback > Delete Optimized Media. This removes any pre-transcoded versions of your source clips.

3. Check where your cache is stored.Open Project Settings → Master Settings → Working Folders → Cache Files Location. Verify that it points to a drive with at least 20 percent free space. If it's set to a nearly full drive, redirect it now. 

4. Let DaVinci Resolve rebuild the cache before exporting. Go to Playback > Render Cache > Smart, then wait for the rebuild to complete before starting the export. Watch for errors during this step, as they can flag specific problem clips.

Note: Clearing the render cache does not delete your project or source media. It only removes temporary processing files that DaVinci Resolve regenerates automatically on the next render or playback session.

Fix 4 — Change Your Export Codec or Format

The codec you export to has a direct impact on render stability. H.265 (HEVC) hardware encoding is the most crash-prone option in DaVinci Resolve, especially on older GPUs or systems where the driver does not fully support the hardware encoder.

Try these codec changes in order:

1. Switch from H.265 to H.264 as a test. In the Deliver tab, change the format to H.264. If the render completes successfully, H.265 hardware encoding is confirmed as the problem.

2. Switch H.265 from Hardware to Software encoding. On the Deliver page, in the Render Settings panel, set your Codec to H.265. Change the Encoder dropdown from "Auto" to "Native". In the free version of Resolve, selecting "Native" forces software (CPU) processing, which is slower but bypasses the hardware encoder entirely.

3. Export to DNxHR or ProRes for intermediate deliverables. If you are creating a master file for further editing rather than a final upload, use DNxHR (cross-platform) or ProRes (preferred on macOS). Both are far more stable under heavy load.

Fix 5 — Isolate Corrupted Clips or Problematic Effects

If DaVinci Resolve crashes at the same point in the timeline on every render attempt, the cause is almost certainly a specific clip, Fusion composition, or third-party OFX plugin at that position. Use the binary search method to find it efficiently.

1. Note the approximate timeline position where the crash occurs. Use the render progress percentage as a guide to identify the rough location.

2. Set In and Out points to cover only the first half of the timeline. Attempt a render of that range. If it completes, the problem is in the second half.

3. Move the In/Out points to the half that contains the crash and split it in half again. Continue narrowing until you isolate the problem to a range of a few clips.

4. Disable effects on suspect clips one at a time. Use the Inspector panel to bypass clip effects. Right-click any Fusion composition in the timeline and select Bypass to skip it during the render.

5. Disable third-party OFX plugins. Go to DaVinci Resolve > Preferences > Effects and turn off OFX plugins, or disable them individually from the Effects panel. Third-party plugins frequently break after a DaVinci Resolve version update.

6. Relink or re-export the problem clip. If a specific source file is identified as the cause, re-export it from its original application or transcode it to ProRes or DNxHR using HandBrake before relinking it in DaVinci Resolve.

Fix 6 — Generate Optimized Media or Use a Proxy Workflow

High-bitrate or exotic source formats such as RED RAW, Blackmagic RAW (BRAW), 4K H.265, or high-frame-rate footage can overwhelm the GPU decoder during a render, especially on systems without dedicated hardware decoding support for those formats. Transcoding source files to a friendlier format before rendering removes that pressure.

To generate optimized media:

1. Select all clips in the Media Pool (Ctrl+A on Windows or Cmd+A on macOS).

2. Right-click and choose Generate Optimized Media. DaVinci Resolve will transcode source clips to the format defined in Preferences > Master Settings > Optimized Media. DNxHR SQ or ProRes Proxy are reliable default choices.

3. Once generation is complete, attempt the render again.

For very long timelines or very large source files, a full proxy workflow using offline-resolution proxies is more practical. Enable proxy mode from the Playback menu or the proxy toggle in the timeline toolbar, edit at proxy resolution, then disable proxies before the final render.

Fix 7 — Disable Hardware Acceleration Temporarily

This step is a diagnostic tool rather than a permanent fix. Disabling GPU processing tells you definitively whether the crash is GPU-related.

1. Go to DaVinci Resolve > Preferences > Memory and GPU.

2. Under GPU Processing Mode, change the setting from CUDA (NVIDIA), Metal (Apple Silicon or macOS), or OpenCL (AMD) to Software (CPU).

3. Attempt a render. If it completes without crashing, the problem is confirmed as a GPU driver or VRAM issue. Return to GPU processing mode and focus on Fix 1 and Fix 2.

Do not leave DaVinci Resolve in software processing mode for regular work, as render times will increase significantly.

Fix 8 — Render the Timeline in Segments

When a deadline cannot wait and isolating the crashing clip will take too long, rendering in sections is a practical workaround.

1. Set In and Out points in the timeline to define a short segment, for example the first 20 percent of the project.

2. In the Deliver tab, select In/Out Range rather than Entire Timeline.

3. Add each segment to the render queue and render them sequentially.

4. Join the completed segments in a separate DaVinci Resolve project or another editing application using the same codec settings to avoid a quality-degrading re-encode.

When Reinstalling DaVinci Resolve Is the Right Call

A reinstall should be treated as a last resort. It rarely fixes issues rooted in GPU drivers or hardware configurations, but it can resolve corrupted application files or broken plugin registrations.

1. Export a project archive first. Go to File > Export Project Archive to save your project, media references, and grade data as a single package before uninstalling anything.

2. Uninstall DaVinci Resolve fully. On Windows, uninstall through Settings > Apps, then manually delete the leftover folders at C:Design and C:[Username]Design. On macOS, delete the application and remove ~/Library/Application Support/Blackmagic Design.

3. Download a fresh installer from the Blackmagic Design support page.

4. Reinstall and restore your project via File > Restore Project Archive.

FAQ: DaVinci Resolve Crashes When Rendering

Q: Why does DaVinci Resolve crash only when rendering and not during playback?

Rendering puts sustained, full-load stress on the GPU and VRAM simultaneously, while playback often streams at reduced quality using cached frames. A GPU that handles playback without issue can still crash under full encode load due to thermal limits, VRAM overflow, or a hardware encoder fault that never gets triggered during normal playback.

Q: Does DaVinci Resolve Free crash more than Studio during rendering?

Free and Studio share the same core rendering engine. DaVinci Resolve Studio adds hardware acceleration for certain codecs including H.265 and HEVC. Render crashes are almost always caused by driver or hardware issues rather than the license tier, so the troubleshooting process is identical for both versions.

Q: Can RAM cause DaVinci Resolve to crash when rendering?

Yes. If DaVinci Resolve is allocated more RAM than the system can deliver, particularly when other applications are open simultaneously, it will crash mid-render. Set the RAM allocation in Preferences > Memory and GPU to no more than 70 to 75 percent of your total installed RAM to prevent this.

Q: DaVinci Resolve crashes at a specific percentage during rendering — what does that mean?

A crash at a consistent percentage almost always points to a specific clip, effect, or Fusion node at that position in the timeline. Convert the percentage to a rough timeline position and use the binary search method in Fix 5 to isolate and disable the problematic element.

Q: Why does DaVinci Resolve crash when rendering H.265 but not H.264?

H.265 hardware encoding requires specific driver and GPU firmware support. When that support is incomplete or mismatched, the hardware encoder fails under sustained load. Switching to software-based H.265 encoding or to H.264 removes the dependency on the hardware encoder, which is frequently the unstable component in a crashing render.

Conclusion

Work through the fixes in order: start with GPU drivers and memory settings (Fix 1 and Fix 2), then clear the render cache and test a different codec (Fix 3 and Fix 4), and isolate problem clips if the crash persists (Fix 5). Most render crashes are resolved within those first three steps. Bookmark this guide for future projects, and check our related articles on fixing DaVinci Resolve running slow and choosing the best export settings for DaVinci Resolve.