Blackmagic Forum

I keep getting this message on 4k 10bit h265 footage using optimized media with a very light white balance and contrast on each clip. This is seriously impeding my work. Can someone help out please? I was really hoping that the upgrade would fix my constant crashing issues.


System NFO - https://we.tl/t-TqLjbpmHu9

This shows the GPU isn't full?

If this were my problem, there are two paths I would try to go down for long term solution. The first and best is to change cameras to one that records a proper editing format - RAW, DNx, ProRes. My second option would be to find a reliable method of converting the footage to one of those formats.

I have done so many things to make Resolve work. I have bought a new laptop, bought an internal SSD so I can store optimized media, I have upgraded and downgraded. As a paying customer, why do I have to keep changing things that work on ever other NLE out there? Why can't BM just fix these issues in their software? (not to take away from your suggestion, but your suggestion adds quite a lot to my team's workflow)

NVIDIA driver 442.59 is a gaming driver. Try driver version 442.19, the "studio" and not the "gaming" driver.

Michael_Andreas wrote:NVIDIA driver 442.59 is a gaming driver. Try driver version 442.19, the "studio" and not the "gaming" driver.

Thanks Michael, I actually just upgraded from that version to see if would help, but it is the same problem with both drivers unfortunately.

One issue that I've seen others have is using both a motherboard GPU and an NVIDIA GPU. On a desktop moving the GUI connection to the NVIDIA card often solves the problem. But on a laptop that's rather hard to do. Look in the "DaVinci Resolve" drop-down menu Preferences, Memory and GPU panel to see if there's a setting option that has the motherboard GPU being used and try changing it.

After similar nonsense with 16.2- System Threadripper 3960X, 128GB ram, Nvidia 2080ti with latest studio drivers, Windows 10- I found the easiest and best solution was to roll back to 16.1.2. I don't need the drama and don't like to waste my time spending hours on silly bugs in improperly vetted software updates. Since rolling back, I don't have to deal with this nonsense.

2D3D4K wrote:After similar nonsense with 16.2- System Threadripper 3960X, 128GB ram, Nvidia 2080ti with latest studio drivers, Windows 10- I found the easiest and best solution was to roll back to 16.1.2. I don't need the drama and don't like to waste my time spending hours on silly bugs in improperly vetted software updates. Since rolling back, I don't have to deal with this nonsense.

Thanks for this. I would do that, but my logic for upgrading was that it couldn't get any worse. I had other problems which also made it very difficult to work. Sigh....

Sorry to hear that everything is so bad for you. That really sucks! I'm fairly new to Resolve having done most of my work with GV Edius for that past several years. Edius has a few quirks too, but is basically rock solid and VERY HARD to crash. It's primary user base is TV news rooms and documentary makers. Daily news operations would never put up with Resolve's instability. The reason why I'm now using Resolve for certain projects is that Edius at the moment doesn't do 8K, and doesn't make use of GPU resources. Hopefully, the next upgrade version will.

Also must say that Resolve's GUI reminds me of the old saying that a camel is a horse designed by a committee. No user movable windows, no option in dual monitor setup to move timeline to one monitor while viewing full screen on the second. Second monitor in dual monitor configuration displaying full screen items which I have no interest in seeing or using. I'm just not used to this!

I had to revert to 16.1 to have a useable system when working with h.264 and h.265 source material. The suggestion to transcode all such material does not solve the root cause. I never had issues on 15.3 which makes me suspect software bugs are the cause.

MikeMeagher wrote:I had to revert to 16.1 to have a useable system when working with h.264 and h.265 source material. The suggestion to transcode all such material does not solve the root cause. I never had issues on 15.3 which makes me suspect software bugs are the cause.

Thanks Mike. I had no issues whatsoever with 15.3, but I did have lot's of problems with 16.1. Can someone from BM check the logs I posted please to help out?

Please download 16.2 again and check it’s build 55.

Peter Chamberlain wrote:Please download 16.2 again and check it’s build 55.

Thank you for the response. Will try that and report back!

Peter Chamberlain wrote:Please download 16.2 again and check it’s build 55.

I downloaded the new build, and reverted back to the studio drivers, but sadly I am still getting the GPU full message. My logs are posted here:



Could you please help me? I am having a lot of trouble delivering to my clients.

Thanks in advance

Peter Chamberlain wrote:Please download 16.2 again and check it’s build 55.

Good Day,
How does one download build 55?

My version downloaded from the prompt when opening Resolve.
Under "About Davinci Resolve" I see version 16.2.0.054. Is that build 54?

Experiencing the same GPU Memory Full error at times. Working with RED Gemini 5K FF video in a 4K timeline. I use 2x NVIDIA 11GB 1080 and rolled back to NVIDIA's GeForce Game Ready Driver 436.48.

When I updated to the latest NVIDIA Studio Driver 442.19 at the time of installing 16.2, I experienced a playback error. I don't recall if it was the GPU Memory Full or poor playback performance. I found a user's post on this forum that shared a similar experience and recommended the 436.48 driver. Since, reverting to 436.48 playback is stable, but at times, I receive the GPU Memory Full.

In 16.1 using the 436.48 driver, I had no issues.

Thank you.

They've done a "silent" upgrade. Download again 16.2 from the BMD product page, install it, and verify that it shows build 055 on the "DaVinci Resolve" dropdown About option.

Michael_Andreas wrote:They've done a "silent" upgrade. Download again 16.2 from the BMD product page, install it, and verify that it shows build 055 on the "DaVinci Resolve" dropdown About option.

Thank you, Michael. That updated Resolve to build 55.

Peter Chamberlain wrote:Please download 16.2 again and check it’s build 55.

Hi Peter, is there any chance you can check out the new logs that I posted? I upgraded as you mentioned and the issue is still persisting.

WesKane wrote:

Michael_Andreas wrote:They've done a "silent" upgrade. Download again 16.2 from the BMD product page, install it, and verify that it shows build 055 on the "DaVinci Resolve" dropdown About option.

Thank you, Michael. That updated Resolve to build 55.

Update to build 55 did not fix the issue of GPU Memory Full. That was using NVIDIA's 436.48 GeForce Game Ready Driver. As previously mentioned, if I upgrade to 442.19 the error continues. At this time, I have found build 16.1 with 436.48 as the most stable configuration for me.

Thank you.

Peter Chamberlain wrote:Please download 16.2 again and check it’s build 55.

Please Peter can you look at my logs?

Joshua Morin wrote:I downloaded the new build, and reverted back to the studio drivers, but sadly I am still getting the GPU full message.
Could you please help me? I am having a lot of trouble delivering to my clients.
Thanks in advance

Hi Joshua,

Can you please also send us a test project which shows this issue for you? and detail the steps you need to run into it.

Rohit Singhal wrote:

Joshua Morin wrote:I downloaded the new build, and reverted back to the studio drivers, but sadly I am still getting the GPU full message.
Could you please help me? I am having a lot of trouble delivering to my clients.
Thanks in advance

Hi Joshua,

Can you please also send us a test project which shows this issue for you? and detail the steps you need to run into it.

Thank you for helping out Rohit. It happens quite often, but it is not something that is reproduceable every time. It happens in all of my projects. I attached a sample project. I would say that it happens around 6-10 times per day. Does this help?

https://we.tl/t-s27jtG6Hn8

Thanks in advance...

Your signature says that you're using build 054.

What build number is in the pop-up panel resulting from the pull-down menu DaVinci Resolve --> About DaVinci Resolve?

Yes thank you I will update that. If this problem is happening with anyone else, I think what has solved my problem was turning off GPU scopes. Thanks for the helping out BM support! (they DMed me to help out)

Look, all kinds of "tips" that suggest replacing your graphic card, updating/ downgrading drivers, transcoding clips, using a proper camera that produces the "right" kind of clips, bla bla bla does not address the fundamental fact:

This wasn't a problem in 16.1.
It is a problem in 16.2.
Including in build 055.

There is something wrong with the update, not people's setup.

I find that if I save and close Resolve, then reopen the project, at least I can see my clips - for a while. But opening Resolve takes quite a bit of time on my PC. Is there another workaround that doesn't involve restarting Resolve?

Confirming this, the update just installed (even though I only pressed Download, I didn't want to install while in the middle of a project).

Got a similar setup as most people here, RTX 2080, 64GB ram, Ryzen 3900x - on my laptop with RTX 2060 it's the same...

No matter what I do this st** notice pops up over and over "You GPU Memory is full", starting a Fusion clip, importing mkv, .. things that weren't an issue before. And Resolve then doesn't do these things instead it crashes reproducably.

Try adding a Fusion clip and in the Fusion tab drag an image from the media library to the nodes section. While this image is loading quickly drag the next image - crash.

Every other move - crash.

Manuel Geissinger wrote:Try adding a Fusion clip and in the Fusion tab drag an image from the media library to the nodes section. While this image is loading quickly drag the next image - crash.

As a general piece of advice, don't use MediaIn nodes for loading still images. Use Loader nodes instead, loading the same images direct from disk.

More info: Fusion page: Major performance issue with MediaIn v Loader

It's known that MediaIn nodes loading still images will often use more GPU VRAM, result in lower performance, and can lead to out-of-VRAM and other GPU-related error messages.

Your issues sound pretty severe so I don't think this is the only explanation. But it's worth trying to see if it might help get you further.

Haavard Pettersen wrote:Look, all kinds of "tips" that suggest replacing your graphic card, updating/ downgrading drivers, transcoding clips, using a proper camera that produces the "right" kind of clips, bla bla bla does not address the fundamental fact

It's the old men from Hollywood keeping the cargo cult ******** wheel rolling till the sun burns out. They can't do a single reply without disqualifying you, your camera or your editing setup. It's a weird superiority complex these poor souls developed. Even in 2020 they can't deal with the fact that their elite $100,000 grading suite is now available to any youtuber.

Hey friends, I'm having the same issue with Davinci Resolve Studio 17.1.1 Build 9.

I'm getting the GPU Memory is full while editing a 2 minute 1080p video without any effect or color grading... and my GPU memory is not full, is at 20-28%.

My GPU is a AMD Radeon RX 3700xt.

Any fix?