DaVinci Resolve is a high end post production software available for free.
But crashing randomly or frequently can be a frustrating experience. (Though it is not applicable to everyone)
I can relate to the feeling of starting the render, going to sleep and waking up the next day only to find out Resolve crashing on me!
Especially, when you thought you got the best desktop/laptop meeting the recommended system requirements, crashing or freezing can give a horrible feeling.
Sometimes Resolve can crash during startup, editing, opening Fusion, etc.
Today, let’s see how to overcome this frustration and save you a lot of effort, time and finally get some…
Let’s get started right away!
DaVinci Resolve Minimum System Requirements
The first step is to look into the minimum system requirements as suggested by BlackMagic Design.
|OS||64 bit||Windows 10, macOS 10.12.6, Linux CentOS|
|CPU||Quad Core (4 Core) or more||Intel, AMD|
|GPU||4 GB VRAM or more||NVidia (CUDA 3.0), AMD (OpenCL 1.2), Metal (from Apple)|
|Memory||16 GB RAM or more|
|Storage||Internal Storage for Application and Projects,|
Permanently Connected Storage for Cache, Optimized Media, Stills
|SSD, RAID Configuration|
Meeting the minimum system requirements should solve most of the crashing problems.
Despite meeting minimum requirements (and sometimes exceeding requirements), there are crashes and freezes.
Why Does my DaVinci Resolve Keep Crashing
DaVinci Resolve keeps crashing, mainly because of
- Incompatible or unstable Graphics card drivers (like some Nvidia gaming and studio drivers).
- Not using dedicated graphics card (and relying on integrated graphics card),
- Insufficient system memory RAM (8 GB or less),
- Insufficient GPU VRAM (2 GB or less),
- DaVinci Resolve Beta version, which could be riddled with bugs.
People who custom built their systems to meet recommended system requirements, still face random crashes!
No matter if you’re a beginner who doesn’t have the budget needed to upgrade your system,
You already have a powerful system (desktop or laptop) with sufficient CPU cores, GPU VRAM, System Memory and Fast Storage…
It’s good to have an understanding of different system components and how they coordinate among themselves.
This knowledge could equip you with better judgement on troubleshooting the crashes with the existing system.
Help you make wise decisions on choosing the best system components, fitting your budget.
Potentially save you from shelling out huge loads of money needed for a system upgrade (which otherwise could be resolved with simple fixes!)
DaVinci Resolve Crashing on Startup
Many users face crashes after launching Resolve – during splash screen which loads different modules like Edit, Color, looking for control surface, etc.
Either DaVinci Resolve doesn’t respond or closes unexpectedly.
|No dedicated Graphics Card, system runs only on Integrated Graphics Card||Integrated Graphics card is not sufficient to run DaVinci Resolve. Need to have a dedicated GPU.|
|Have Graphics Card but Resolve recognises only Integrated Graphics Card||Either disable Integrated Graphics Card or update Video Card Driver which will make Resolve recognize the GPU.|
|Have a good GPU with sufficient VRAM but still crashing.||Update the Video Card Driver to the correct version – not necessarily the latest one. Revert to the previous version if needed.|
|My system meets minimum system requirements but still crashing||Roll back to the previous stable version of Resolve.|
1. Use Dedicated Graphics Card
System which runs only on Integrated Graphics card and doesn’t have dedicated GPU can cause crashing during startup.
Sometimes, if you’re lucky, you can get away with importing footages inside “Media” tab of Resolve with the integrated graphics card.
But when you start editing, Resolve can crash on you.
It is better to install a dedicated GPU (if you don’t have one). Make sure the minimum onboard memory or VRAM has 4GB.
If you have one, be sure to make the dedicated graphics card as the default display adapter.
How to set Nvidia or AMD GPU as Default Display Adapter
- Right click on your desktop -> Click on Nvidia Control Panel (or AMD Catalyst Control Center).
- Click on “Manage 3D Settings” under “3D Settings”
- Under “Global Settings” -> Preferred Graphics Processor -> Select “High Performance NVidia Processor”
- Click on “Apply”
- Now click on “Set PhysX Configuration” under “3D Settings”.
- “Select a PhysX Processor” -> Select the dedicated graphics card listed.
- Click on “Apply”
Now try to launch DaVinci Resolve.
From the menu bar, click on “DaVinci Resolve” -> “Preferences“, you should be able to see the name of your dedicated graphics card against “Video card 1” under GPU configuration.
If the above still doesn’t display the GPU, go to “Device Manager” -> “Display Adapters“, you will see:
Right Click on the Integrated Graphics (in this case, Intel(R) HD Graphics 5500) and disable the driver.
Now this will force the system to use only the dedicated graphics driver.
(I am assuming here that you are powering the monitor through your dedicated graphics card like NVidia GeForce GTX 1050 and not from the motherboard integrated graphics card. Laptops, by default, will have a connection from dedicated GPU to the display monitor.)
If the above doesn’t solve the issue, then it’s time to update the correct video driver.
2. Install the Correct Video Driver for Nvidia or AMD Graphics Card
NVidia comes with Gaming drivers as well as Studio drivers.
As the name suggests, Gaming drivers are released frequently to support new and high end games.
Whereas, Nvidia Studio Drivers are aimed at creative application works like editing, grading, content creation, animation, etc.
Nvidia states studio drivers are more stable.
So, if you are in the habit of automatically updating gaming drivers through “GeForce Experience” app, and find Resolve crashing on you, then it’s time to switch over to Studio driver.
- Launch GeForce Experience app.
- Click on the 3 dots (More) option.
- Click on Studio driver.
- If not displayed then, head over to Nvidia Official website and select your GPU from the list and download it.
- Click on Search.
- Click on Download!
If Studio driver is not available for your GPU, then update the Gaming driver to latest version.
If the latest versions (of gaming or studio) drivers crash, then roll back to the previous ones, which are stable.
Correct version of either the Gaming or Studio version of Nvidia should run DaVinci Resolve with no crashes.
It is up to you to decide which one fits you.
After successfully launching Resolve, importing media, creating a timeline and start editing…
There come’s a time to add some 3d Fusion titles which might need a lot of customizing, or…
You might need to do some green screen keying, or other compositing.
So, when you click on “Fusion” tab,
DaVinci Resolve Fusion Crashing
Most of the users who can work with no issues in other tabs like Edit, Fairlight, Color, etc, might face a crash on clicking the Fusion tab.
Or sometimes after clicking on Fusion tab, during the building of node-based compositions (which might involve tracking operations, painting, etc), Resolve can crash.
DaVinci Resolve Fusion tab crashes mainly because of:
- Insufficient System Memory – Fusion requires more than 16 GB RAM (32 GB recommended by Blackmagic Design)
- Insufficient Graphics Card VRAM – 2 to 4GB for 1080p, 6 to 8GB for 4K
- No discrete or dedicated GPU (Integrated Graphics is NOT sufficient to run Fusion)
- Incompatible Video driver
1. Insufficient System Memory:
You might get away with simple editing, audio and color correction work with 8GB or less RAM (if you are lucky), but working inside Fusion will demand more RAM.
That’s where Resolve can crash on you.
If you have insufficient RAM, please upgrade to 16 GB. If you are going to do a lot of VFX work and graphics work, 32 GB RAM and more should be your target.
What if you have sufficient RAM, but still Resolve crashes?
A very frustrating one! Follow the next step.
2. Insufficient Graphics Card Onboard Memory (VRAM)
When you work with 1080p h.264, a minimum of 2 to 4GB GPU VRAM is necessary. Anything below than that might crash Resolve.
But if you’re working with 4K h.264 or h.265 (heavily compressed codec), a 2 to 4 GB RAM is insufficient and can crash on you.
Fusion (or for that matter Resolve) is very GPU hungry. The more VRAM – the better.
If the problem persists, then try updating the Video card driver to the appropriate version (as discussed above).
If you still face the same issue, then try the below:
Memory and GPU Configuration inside Resolve
From the menu bar, click on “DaVinci Resolve” -> “Preferences“, then click on “Memory and GPU” -> “System”.
Under “Memory Configuration”:
Try increasing the memory for “Limit Fusion Memory Cache to“, which will take the memory from “Limit Resolve Memory Usage to” which is 75% of the total system RAM.
For example, if you have 16 GB total RAM, “Limit Resolve Memory Usage to” will be defaulted to 75%, which is “12 GB”. If your “Limit Fusion Memory Cache to” is set around 4 GB, then try to increase beyond 4GB, say 8 GB.
Give “Save” and restart Resolve.
See if it solves the issue, if not revert the changes.
Under GPU Configuration:
“GPU Processing Mode” -> Instead of “Auto”, try selecting “CUDA” for NVidia GPUs or “OpenCL” for AMD GPUs. Give “Save” and restart Resolve.
If the above doesn’t solve your issue, then see that your System managed Paging file size is sufficient.
Virtual Memory, Swap File or Paging File:
A Paging file is an area on the hard disk that Windows uses as if it were RAM.
Generally, the operating system decides its own paging file size based on the amount of RAM installed.
Typically, it selects the drive where the OS is installed and allocates a portion of hard disk as virtual memory or paging file size.
The most important point here is : Don’t cram your C: disk. Leave some breathing space. I mean to tell, have sufficient free space. (Let the strip be blue instead of red).
There is no need to alter the paging file size (let it be system managed).
But if you would like to manually define the paging file size, then proceed at your own risk (changing the values could make your system unstable).
- Go to “Control Panel” -> “System” -> “Advanced System Settings” -> Click on “Settings” under “Performance” – > Click on “Advanced” -> Click on “Change” under “Virtual Memory”.
- Uncheck “Automatically manage paging file size for all drives”, Click on “Custom Size” radiobutton -> Enter “Initial Size” and “Maximum Size”.
Based on the “Currently Allocated” size, you can define the “Initial Size” which in this case will be more than the currently allocated one. (Again reminding – please be very careful here, this could make your system unstable. Do your own research before committing the numbers.)
Most of the crashes happen during rendering.
Most users have the experience of render crashing at around 20% to 30%, 50% to 60% and…
Around 95% to 99% as well!!!
Sometimes during editing you add simple transitions with no crashing issues. But the same transitions can cause crashes during rendering!
Basically Resolve can crash at any point while rendering.
DaVinci Resolve Crashes While Rendering
DaVinci Resolve crashes while rendering because of:
|Incompatible Graphics Driver||Certain Nividia Cuda, AMD OpenCL Drivers|
|Insufficient GPU VRAM||Less than 4GB|
|Insufficient System Memory (RAM)||Less than 8GB|
|Unstable DaVinci Resolve version||Beta versions are known to have bugs|
Solution for Render Crashing
1. Incompatible Graphics Driver
Choosing the correct graphics driver for your GPU is VERY critical.
It need not be the latest one.
(Refer the above section on Video drivers on how to select the correct driver).
2. Insufficient GPU VRAM:
As Blackmagic claims, rendering required resolution (frame size) like 1080p, 4K etc, and image processing (like temporal noise reduction, motion effects, OpenFX plugins, etc) mainly depend on GPU and its onboard memory.
A minimum of 4GB VRAM is recommended.
3. DaVinci Resolve Beta Version:
Beta version, as the name suggests, is released to test out new features, bug fixes, support new camera codecs, enhancements by the public. If there are bugs reported by the public, then Blackmagic will reproduce the bugs from their side and then fix them through future beta or public beta versions.
Unstable beta version of Resolve along with incompatible GPU video drivers can cause random crashes not only during rendering but also during editing, audio, fusion and color grading works.
It’s always a best practise to roll back to the previous STABLE version, let’s say, from 16.3.1 beta to 16 (or 15 if needed!)
4. Insufficient system memory (RAM) will also cause crashes during rendering. Hence a minimum of 8GB or more than that is recommended.
Apart from doing all the above, if you still face issues, try out the below workarounds.
Workarounds for Render Crashing
1. Render Speed = Set the value other than Maximum
- Go to “Delivery” tab -> Choose “Custom” -> Click on “File” out of Video, Audio, File -> Scroll down.
- Render Speed -> Set it to 100 or 75 or 50.
Essentially, we are trying to reduce the render speed.
A setting of “Maximum” will put more demand on your system’s resources like CPU, GPU and RAM.
Let’s reduce the stress. Let the system take more time to render with less stress.
2. Disabling Viewer Updates during Render
- Go to “Delivery” tab -> Click on the 3 dots above the viewer -> “Updates During Renders” -> Select “Off” or “Minimal”
- Choosing “Off” or “Minimal” will speed up rendering with less stress on your system’s resources.
For some users, sometimes minimizing DaVinci Resolve during render has finished the render without crashing!
3. Export “Optimized Media” or “Render Cached Images”
If you optimized your media or render cached your timeline, you can check either of these 2 options. Sometimes, this setting can save Resolve from crashing.
- Go to “Deliver” tab.
- Click on “Custom? -> “Video” -> “Advanced Settings”
- Check either “Use Optimized Media” or “Use Render Cached Images”
But keep in mind that the video settings for optimized media or render cache should be of high quality.
If you were following offline editing or proxy workflow, then this step shouldn’t be followed. Because checking this option during export will result in lower resolution file.
4. Uncheck”Reload Last Working Project”
Uncheck this option, if you’re directly taken to the last project after launching Resolve. If the project that you were working crashed and when you again launch, then you’ll be forced to open the same project.
- From the menu bar, go to “DaVinci Resolve” -> “Preferences” -> “User”
- Uncheck “Reload last working project when logging in” (if already checked).
But always keep in mind that a stable version of Resolve coupled with compatible graphics driver will never crash on you (given that you have sufficient RAM and GPU memory)!
You have come a long way in troubleshooting DaVinci Resolve crashes.
But if you are still facing issues, then it’s time to follow the below steps (not necessarily in the same order):
- Completely uninstall DaVinci Resolve (and all the relevant DLLs), then either again download the latest version from the website or roll back to the previous best version and re-install.
- Over-clocked CPU can also cause issues.
- Disable your antivirus and see if Resolve works with no issue. Or..
- Disable firewall and check if there are any crashes.
- Try disabling both antivirus and firewall and see Resolve is crashing or not.
The above is to make sure that other softwares are not interfering with Resolve.
If the issue is persistent, then…
It’s time to capture logs immediately after the crash and submit to Blackmagic Design for further analysis.
Blackmagic Design would require the following from you:
- Your System Information – system brand, model, year, OS version, your DaVinci Resolve version number, etc.
- Your Project Export (.drp format) = “File” -> “Export Project”
2 Ways to Generate Logs Immediately after DaVinci Resolve Crash
- Restart Resolve -> From Menu bar, go to “Help” -> Click on “Create Diagnostics Log on Desktop“. Or..
- If Resolve doesn’t launch, then go to “C:/Program Files/Blackmagic Design/DaVinci Resolve” for Windows or “/Library/Application Support/Blackmagic Design/DaVinci Resolve” for Mac. Run CaptureLogs.bat application.
This is how the log will be generated:
Head over to “https://forum.blackmagicdesign.com/” -> “DaVinci Resolve” and search for relevant topics on troubleshooting. (Be sure to read the forum rules before posting your queries).
While working inside DaVinci Resolve, crashes can also occur because of external factors like laptop battery dying, hard disk crashing, power outage, OS issues, or similar other reasons which are out of our hands.
Read the below posts for more actionable information:
- How to recover and restore accidentally deleted or crashed projects in DaVinci Resolve.
- Tips to Save Your Precious Work in DaVinci Resolve (IMPORTANT!)
After you have successfully sorted out the crash issue, now it’s time to make sure DaVinci’s performance is optimised to run smoothly in your system – desktop or laptop.
Getting smooth “REAL-TIME PLAYBACK” speeds up your editing and grading works.
Click on “Easy fixes for lagging DaVinci Resolve”.
Not only lower end systems, even powerful systems with 6/8 cores CPU (Intel or Ryzen), 16/32GB RAM, Nvidia RTX 2080Ti, SSD/RAID storage, can crash.
For most of the cases, the main culprit is not installing the correct version of graphics driver of your GPU.
As discussed several times above, the unstable beta version of DaVinci Resolve and incompatible graphics driver can cause crashes.
So spend some time and follow this guide to troubleshoot your issue.
This guide can not guarantee 100% of crash fix, but it still covers solution for most of the commonly occurring crashes.