Resolve Studio 19v6 problems

I am running Studio version on windows 11 (128GB memory, RTX 3080 10GB, and with the latest update 19 v6 I get message that GPU memory is full and when I select a clip on edit page the audio comes through, the playhead moves but no video. I restarted pc and changed timeline resolution to HD from UHD 4K and problem persists. I uninstalled 19v6 and reloaded 19v5 and all is well. How does this happen? Also I got message with v6 that USD plug-in cannot be loaded so I deleted the USD plug-in folder and message went away but not the problem.


Sent from my iPad using Tapatalk

[Dwaine Maggart]

In the Resolve Help menu, select "Create Diagnostics Log on Desktop"

Open the Windows System Information app and select its File - Save menu to create a .NFO file.

Put both those files on a file sharing site and provide links to the files here.

I am running Studio version on windows 11 (128GB memory, RTX 3080 10GB, and with the latest update 19 v6 I get message that GPU memory is full and when I select a clip on edit page the audio comes through, the playhead moves but no video. I restarted pc and changed timeline resolution to HD from UHD 4K and problem persists. I uninstalled 19v6 and reloaded 19v5 and all is well.

I have the same issue. Sadly I can't create a Diagnostics Log on Desktop since I uninstalled it and returned to beta 5, because I was getting that message even with a 720p clip, so was totally unusable.

I am running Studio version on windows 11 (128GB memory, RTX 3080 10GB, and with the latest update 19 v6 I get message that GPU memory is full and when I select a clip on edit page the audio comes through, the playhead moves but no video. I restarted pc and changed timeline resolution to HD from UHD 4K and problem persists. I uninstalled 19v6 and reloaded 19v5 and all is well.

I have the same issue. Sadly I can't create a Diagnostics Log on Desktop since I uninstalled it and returned to beta 5, because I was getting that message even with a 720p clip, so was totally unusable.

My experience exactly, I tried 720p and no help. Since I reinstalled v5 it’s too much work to create a diagnostic log, I’ll have to wait for next release and maybe then.


Sent from my iPad using Tapatalk

Diagnostic logs and NFO files help the Blackmagic developers pinpoint and fix problems.
" it’s too much work to create a diagnostic log, I’ll have to wait for next release and maybe then" is not exactly helpful.

[Dwaine Maggart]

Unless you've restarted and crashed Resolve multiple times since reverting to 19b5, the 19b6 crash logs will still be available. That's why I've asked you to create a diagnostics log even though you are now using 19b5.

I am also experiencing crashes every time that Davinci opens: Python issue.
Log attached

[Dwaine Maggart]

I don't see such an issue in your logs. You had a project open today. Last crash log is from July 29.

But it also appears you have Resolve 19b3 installed, not 19b6.

Unless you've restarted and crashed Resolve multiple times since reverting to 19b5, the 19b6 crash logs will still be available. That's why I've asked you to create a diagnostics log even though you are now using 19b5.

But the error isn't a crash (I think). Davinci loads fine, you place a video in the timeline and get the popup window with "gpu memory is full, try changing timeline resolution" or something like that, but the program keeps running (without video preview, just black video and only audio).

My computer is under the minimum requirements to run davinci (only 1Gb of VRAM) but enough for what I do with it. I know the fix will be "get a better machine, yours is not supported". I was not going to make a thread about that error, but since the OP has a good computer and has my same error, just added to the cause.

Anyway, if the OP doesn't make the diagnostic log and you are still interested on it and think it could help (even knowing my computer is under the minimum requirements), tell me and I will reinstall Beta 6 and produce the diagnostic with it.

I reinstalled studio 19v6 with same problem but I created diagnostics and the link to the logs is

https://www.dropbox.com/scl/fo/m8wzabda ... ep9v0&dl=0


Sent from my iPad using Tapatalk

[Dwaine Maggart]

@Lee: Please send a proper Resolve diagnostics log created from the Resolve Help menu.

Also send a Windows System Information .NFO file.

I’m sorry but what is a proper Resolve diagnostics log?


Sent from my iPad using Tapatalk

I’m sorry but what is a proper Resolve diagnostics log?


Sent from my iPad using Tapatalk

I did create NPO file and it’s on the link I posted


Sent from my iPad using Tapatalk

All the info you need. viewtopic.php?f=21&t=90190

[Dwaine Maggart]

A proper Resolve diagnostics log is one generated using the Resolve Help menu: Create Diagnostics Log on Desktop. Please provide that.

If your current issue is that Resolve won't even start, then generate a log with this process:

In a File Explorer window, go to:

C:\Program Files\Blackmagic Design\DaVinci Resolve

and run CaptureLogs

This will place a Resolve log file named similar to this on your Windows Desktop: DaVinci-Resolve-logs-20181228_140434.zip (You may not see the .zip extension if your system is set to hide known extensions).



Can you confirm exactly what happened in todays crash?

I see in the NFO that Resolve crashed accessing this file: gio-2.0-0.dll

The only other time I've seen that error was from someone with a Resolve startup crash, and it was caused by a third party utility they had added to the system.

Is your crash today a startup crash, or still related to selecting a file in an active project?

I included the NPO file and the log files created and they are in the link I posted, is that everything you need? No crashes, just GPU memory full message.

[Dwaine Maggart]

What's on your Dropbox link is just a Resolve logs folder. I need a Resolve diagnostics log file with a .zip extension, looking something like this: DaVinci-Resolve-logs-20181228_140434.zip

I have the NFO file as well, thanks.

I just did that now, thx.


Sent from my iPad using Tapatalk

[Dwaine Maggart]

You have selected OpenCL GPU processing mode in Resolve Preferences - System - Memory and GPU.

Enable the GPU Processing mode "Auto" checkbox, save the prefs and restart Resolve. Only CUDA processing mode works with NVIDIA GPU's, and the Auto mode will select that.

Yes, thx, it all works now, I had to update the Nvidia driver. Thanks for such a prompt reply and fix!


Sent from my iPad using Tapatalk

You have selected OpenCL GPU processing mode in Resolve Preferences - System - Memory and GPU.

Enable the GPU Processing mode "Auto" checkbox, save the prefs and restart Resolve. Only CUDA processing mode works with NVIDIA GPU's, and the Auto mode will select that.

So as I understand, with Beta6 the OpenCL support was removed for Nvidia GPUs? Don't understand why, since my Nvidia GPU doesn't support the current CUDA version in Davinci and OpenCL allowed me to keep using it.

At least now I know why I was getting the memory full message with Beta6. Are there plans to revert the support of OpenCL with Nvidia cards or should stick to Beta5 forever (until I update my computer)?

[Dwaine Maggart]

We've never provided OpenCL support on NVIDIA GPU's. It may sort of work, in scenarios where you don't have a GPU that supports CUDA Computer 3.5 or higher, or where you don't have a current NVIDIA driver installed. But if it works at all, it will work very poorly.

Resolve has always required CUDA processing for NVIDIA GPUs.

Francisco, what GPU do you have?

Francisco, what GPU do you have?

A really old one, a Nvidia GTX 650 TI. I am waiting for RTX 5000 series to upgrade.

[Dwaine Maggart]

And that GPU only has CUDA Compute 3.0 support and Resolve requires a minimum of 3.5 support.

Thus the Resolve Auto GPU processing mode will select OpenCL, which will work very poorly if at all. Same as it's ever been.

You mentioned 19b5 worked better? It shouldn't. It also should have been using OpenCL, which should have worked just as poorly.

Resolve 14 was the last version that supported that GPU. Any newer Resolve version should work poorly with that GPU.

And that GPU only has CUDA Compute 3.0 support and Resolve requires a minimum of 3.5 support.

Thus the Resolve Auto GPU processing mode will select OpenCL, which will work very poorly if at all. Same as it's ever been.

You mentioned 19b5 worked better? It shouldn't. It also should have been using OpenCL, which should have worked just as poorly.

Resolve 14 was the last version that supported that GPU. Any newer Resolve version should work poorly with that GPU.

No, what I mean is, with 19b5 I can use OpenCL (bad performance, but works), with 19b6 with OpenCL I get the error "GPU memory is full, try change the timeline resolution" (or similar one, I write it by memory) and no video preview (same video works with 19b5 without video memory full error).

- 19b5 with OpenCL: bad performance, but works.
- 19b6 with OpenCL: error "GPU memory is full"

[Dwaine Maggart]

It's possible that 19b6 is doing something more with the GPU that's causing that to happen.

But since it's an unsupported GPU, there's not much to be done. It is what it is. If you are going to continue to try to use the GTX650, then I guess you'll have to stick with 19b5. But I really expect there'll be more bad things that happen, even with that. I would expect GPU artifacts or failures at some point.

It's possible that 19b6 is doing something more with the GPU that's causing that to happen.

But since it's an unsupported GPU, there's not much to be done. It is what it is. If you are going to continue to try to use the GTX650, then I guess you'll have to stick with 19b5. But I really expect there'll be more bad things that happen, even with that. I would expect GPU artifacts or failures at some point.

Ok, thanks, I will stick to 19b5 until I upgrade the GPU.

It's possible that 19b6 is doing something more with the GPU that's causing that to happen.

But since it's an unsupported GPU, there's not much to be done. It is what it is. If you are going to continue to try to use the GTX650, then I guess you'll have to stick with 19b5. But I really expect there'll be more bad things that happen, even with that. I would expect GPU artifacts or failures at some point.

Ok, thanks, I will stick to 19b5 until I upgrade the GPU.

Decided to try with 19.0 Build 69 version (not beta) an it works again. Thanks.