Blackmagic Forum

I've tried to use DaVinci Resolve for over 6 months and every new update I hope that the bug is fixed but Its still causing me issues.

I have tried everything I can find online to try and resolve the issue, I have even replaced the GPU for a different unit, 3 times.

Started with a EVGA Kingpin 2080TI (11GB) and was told that maybe because it was a gaming card it might be causing an issue, so I stepped upto a RTX Titan (24GB!!), had the very same issues, I kinda gave up and sold both and purchased a Quadro RTX 6000 with 48GB of ram!!! Sold the 6000 a few days ago and put a 2060 KO in there with like 6GB and crashes at identical points.

Don't know what to do next,

Tell me what GPU I need to buy to make this problem go away?

Running the latest version of DV.

Windows 10 pro (upto date)

Ram DDR4 32GB 4000mhz (two matched sticks)
EVGA Z390 Dark motherboard, I9 9900k 5.3GHz (No AVX offset)
1000w EVGA psu
4x SSD m.2

Watercooled to extera Mora3 420 Pro with allot of fans (next room)

Not that it would matter but the monitor is a Eizo C319x.

I have no other issues with this computer, all other programs run flawlessly, CAD software etc.

If you can help I would appreciate it,

All I can suggest is to make sure you're using the latest version of the Studio drivers for your GPU.

I'm doing some pretty heavy 4K timelines at the moment with multiple video tracks, stabilization, color correction/grading, temporal noise reduction and retiming with optical-flow and I'm only very rarely having issues -- with a GTX1060/6 card that has just 6GB of VRAM!

My secret?

I'm using Resolve 15.3

I think the latest versions of resolve (ie: 16.x) are far more demanding of GPU VRAM than the previous version and since the previous version does *everything* I need (even if it doesn't do everything I *want*), that's where I'm staying for now.

RCModelReviews wrote:All I can suggest is to make sure you're using the latest version of the Studio drivers for your GPU.

I'm doing some pretty heavy 4K timelines at the moment with multiple video tracks, stabilization, color correction/grading, temporal noise reduction and retiming with optical-flow and I'm only very rarely having issues -- with a GTX1060/6 card that has just 6GB of VRAM!

My secret?

I'm using Resolve 15.3

I think the latest versions of resolve (ie: 16.x) are far more demanding of GPU VRAM than the previous version and since the previous version does *everything* I need (even if it doesn't do everything I *want*), that's where I'm staying for now.

Thanks for your reply, I can confirm I'm using the latest studio drivers (456.71), and the monitors is running 10bit.

Unsure how much more memory you need then 48GB

My PC is overclocked, I should just point out that I've also tried it bone stock without any OC settings applied, tried different memory and even done fresh installs of DV. I even changed the SSD on the MB.

The best bit was because at first I was editing H.265 files, and I was told I had to purchase DV to be able to use that function I never got to try how badly it constantly crashes.

I normally get 1 to 2 clips in, do some basic corrections, then anything above that get GPU faults.

Same here. I can't render at 4k anymore. GPU memory running out and GPU errors.

My system is drastically slower than yours and 4K editing was not slow but worked. So I don't think that is your issue. GPU errors are new for me with recent DR updates.

Windows task mgr performance tab shows the moment the render fails. The instant "dedicated GPU memory" began to climb, it immediately crashed.

https://pasteboard.co/JxnqJt4.png

Half a day later and a successful 4K render. After tons of ineffective debugging attempts, I finally deleted all of the OFX "object removals" and used "patch replacer" instead. Good lord it worked!

The only time i had GPU memory full on my 1080Ti while editing 4K video from Sony A7III (light color grade) was when i used some bad Nvidia drivers ... i rolled back to an older driver and everything went back to normal ..

I`m currently using the latest gaming driver and it`s also good ... i didn`t had luck with the Studio drivers from them though ... i find them just placebo and at times with issues ....

Can`t remember which driver was the one giving me Memory full but for sure it was something wrong with it ... usually i have ~ 4-6 GB VRAM used while editing 4K .. with this bad driver i was constantly sitting at 9GB without doing anything to the footage.

This is the most annoying problem DR has. Also LinusTechTips brought up as a showstopper not changing from PremierePRO to DR. As a SW Developer I think this should be managed by DR way better (like fall back, or organize GPU mem differently). This is a bit ridiculous 24 GB GPU mem is still not enough. In my case using one plugin (deflicker) caused this issue on a 4k timeline.

Anyway, as others stated, falling back to 15.x could be a solution if you want to use it for serious production. Other solution could be to use a FHD timeline and render to 4K at the end. Also, try to find the plugin which eats up your memory and last, do not let your machine go sleep/hibernation! It can cause GPU problems as well.

I have never, ever encountered a memory full problem with my 8 GB VRAM in UHD timelines, even with complex filters like NR.
I can even feed 8K Red stuff to my humble machine. I'd still assume this is a wrong error message or a driver issue.
It's impossible that 24 GB VRAM is not enough (as long as we don't all work in 12K timelines).

Uli,
You are working with a Mac, the others all have Windows! Thats perhaps the difference.
I've the same problem, not always, and use the latest Studiodriver.

Dirk PEL

Uli, are you on Mac, right?
It seems to be a Cuda problem

For all of you that are experiencing this issue, do you have only Edit + Color or also a Fusion effect on your image pipeline?

A workaround that a user suggested (cant remember who it is) is to isolate the problematic point if possible, and render it in OpenCL mode
It will slowly crawl sure, but will go thru the problematic spot without the dreaded Memory full error

24GB GPU memory should not be the issue unless you are working on 12K x 12k files.. id check gpu driver options and then try isolate what operation is the issue.
if you can repo, generate diagnostic logs with repo steps, images if needed, drp, etc and system specs and put them all on a dropbox to pass a link here..

So are You using the latest drivers?

Two very daft questions, but I often find going back to the beginning helps with triage

1) you are using Studio and not the free version - yes?

2) is DRS configured to use the GPU in settings, or is it using the discrete GPU built into your processor?

You can select the GPU being used in the Studio version in settings.

I’ve only ever had GPU memory problems when DRS insisted on using an onboard GPU instead of the external / add on GPU interface.


Sent from my iPhone using Tapatalk

Get a dirt cheap RX580 with 8 GB (~ $180) or wait for the upcoming RX6000 serie.
Only use hardware h265 encoding when you want bad quality and are in a hurry.

Peter Chamberlain wrote:24GB GPU memory should not be the issue unless you are working on 12K x 12k files.. id check gpu driver options and then try isolate what operation is the issue.
if you can repo, generate diagnostic logs with repo steps, images if needed, drp, etc and system specs and put them all on a dropbox to pass a link here..

I can't see it being a genuine out of memory issue, I had 48GB, When errors happened it was hardly using the card...

I have been back and forth trying to resolve the issue with cards, I have tried 3 different cards they can't all be faulty.

As for the questions about am I using the paid version, yes I am, as I wanted to edit h.265 files and was told I had to get paid version for that.

I have selected the card and in the settings, I've tried OpenCL and CUDA options also.

Everytime I sit down to try and use this software it just crashes and I'm forced to abandon it.

Yes I'm editing a 4k UHD timeline, 10bits H.265, can't see why my machine shouldn't be able to run this.

I've since purchased a Ninja V (junk) to try different recording formats, all breaks the software the same.

I purchased the dongle in release 16, so I've had the problem the whole time. Never experiences purchasing software and it just being a brick I can't use.

I will be really annoyed if I purchase the new Quadro that is coming out and it doesn't work with that.

It is a DR 16.x + NVidia bug. It does not matter how many nodes you have, GPU drivers or GPU VRAM. It randomly pops up.

It almost never happens with DR 15 + Nvidia or DR 16 + AMD.

It is the single error that has prevented us from migrating to DR16.

mpetech wrote:It is a DR 16.x + NVidia bug. It does not matter how many nodes you have, GPU drivers or GPU VRAM. It randomly pops up.

It almost never happens with DR 15 + Nvidia or DR 16 + AMD.

It is the single error that has prevented us from migrating to DR16.

What are alternative GPU’s that are in the same pro class? Only have somewhat of an understanding of Nvida GPU.

Was tempted to try a 3090 to see if it helped but I don’t like to be an early adopter on anything as that brings its own issues.

Glad in away its not only me that is having these issues.

Our ecosystem consists of HP z8 systems with Titan cards, some with 2080Ti and iMac Pros.
The DR16 with Titan cards or 2080ti always gets the error at least 2-3 times a day. DR15 systems get the error maybe once or twice a month.

The iMac Pros with AMD GPU never get it.

We were planning to move to DR16 and 3090. But for now, DR16 migration is on hold. We will upgrade to 3090 once it is available.

We will also see what AMD releases this week.

mpetech wrote:Our ecosystem consists of HP z8 systems with Titan cards, some with 2080Ti and iMac Pros.
The DR16 with Titan cards or 2080ti always gets the error at least 2-3 times a day. DR15 systems get the error maybe once or twice a month.

The iMac Pros with AMD GPU never get it.

We were planning to move to DR16 and 3090. But for now, DR16 migration is on hold. We will upgrade to 3090 once it is available.

We will also see what AMD releases this week.

I think I will just sell the dongle to someone else as I can’t wait for software to be out of testing stages.

I really wouldn’t mind, but I’m not trying to produce films with this just do basic edits, I do really like the colour correction (well technical grading in DR) but its not worth all this hassle.

Either way tried everything to get this to work.

Thanks for everyones help, cheers.

superclarkey wrote:

mpetech wrote:Our ecosystem consists of HP z8 systems with Titan cards, some with 2080Ti and iMac Pros.
The DR16 with Titan cards or 2080ti always gets the error at least 2-3 times a day. DR15 systems get the error maybe once or twice a month.

The iMac Pros with AMD GPU never get it.

We were planning to move to DR16 and 3090. But for now, DR16 migration is on hold. We will upgrade to 3090 once it is available.

We will also see what AMD releases this week.

I think I will just sell the dongle to someone else as I can’t wait for software to be out of testing stages.

I really wouldn’t mind, but I’m not trying to produce films with this just do basic edits, I do really like the colour correction (well technical grading in DR) but its not worth all this hassle.

Either way tried everything to get this to work.

Thanks for everyones help, cheers.

You really give up fast... get a $180 rx580 with 8 GB and you can run DR with no problems.
And when you want something faster wait for the RX6000 series, they are just around the corner.
You can always rent a colorist when you have more money than..

superclarkey wrote:I think I will just sell the dongle to someone else as I can’t wait for software to be out of testing stages.

I really wouldn’t mind, but I’m not trying to produce films with this just do basic edits, I do really like the colour correction (well technical grading in DR) but its not worth all this hassle.

Either way tried everything to get this to work.

Thanks for everyones help, cheers.

Just use version 15.3, it's robust as hell and super-reliable.

Don't make the mistake of thinking that you *must* use the latest version just because it's the latest.

Smart folk are always just behind the bleeding edge because they prefer reliability and robustness to bugs and problems.

I've been using this philosophy for many years and never seem to have any of the problems that others (who prefer the bleeding edge) are complaining about. Resolve 15.3 is a *very* capable editor with unrivaled reliability.

Not that it matters in this case, but I'd like to mention that VRAM doesn't add up, so you never had 48 GB.

Uli Plank wrote:Not that it matters in this case, but I'd like to mention that VRAM doesn't add up, so you never had 48 GB.

Original post: "I kinda gave up and sold both and purchased a Quadro RTX 6000 with 48GB of ram!"

Ah, OK, I saw 24 mentioned so often in the thread that I got confused.

My attitude might be I’ve given up quickly and not willing to resolve it, but I’ve spent allot of money and time trying to resolve the problem... over six months. So you guys/girls are seeing me at the end of my patience with this issue.

I agree its fantastic software and when I use it and it works its so logical and powerful I don’t wish to give up.

Where do you draw the line?

How do you roll back to version 15 when I have a 16 dongle? Lol

The point is if 48GB causes these issues then its nothing to do with memory issues... could be nvida I get that but main reason for ising nvida was studio drivers giving 10bit per channel colour depth.

I bought the Kingpin 2080ti because it has binned memory as other 2080ti’s had memory issues...

The Titan RTX was not that much better tbh, the real difference was the quadro.

No problem going back, your dongle will work.
Don't know if it'll fix things, I'd assume a driver issue.

Anyone tried a Amd card? Thought i should never sat that on a Windows 10 setup.


Sent from my iPhone using Tapatalk

SylvestCorp wrote:Anyone tried a Amd card? Thought i should never sat that on a Windows 10 setup.


Sent from my iPhone using Tapatalk

Never a frown with...err, never a GPU memory full error with AMD RX580 8 GB...4K footage, HD and UHD projects...

Same here. It’s not very fast, but very reliable.

Mario Kalogjera wrote:

SylvestCorp wrote:Anyone tried a Amd card? Thought i should never sat that on a Windows 10 setup.


Sent from my iPhone using Tapatalk

Never a frown with...err, never a GPU memory full error with AMD RX580 8 GB...4K footage, HD and UHD projects...

Hi
Good to hear it works for you. You can see the dual radeon vii threads where I come from. I currently run a RTX 2080 Super no memory issue in my workflow. I do not see what the others see. Sorry for generalizing
kind regards
HC

Uli Plank wrote:Same here. It’s not very fast, but very reliable.

It's somewhere between 1060 and 1070 in it's current state with the latest drivers, the GPU originally being designed for compute rather than gaming helps it a bit with Resolve.

I'd take a look at your gpu settings... RUnning a 2080Ti and work and deliver 4k almost daily (except for today... sick in bed).

SylvestCorp wrote:

Mario Kalogjera wrote:

SylvestCorp wrote:Anyone tried a Amd card? Thought i should never sat that on a Windows 10 setup.


Sent from my iPhone using Tapatalk

Never a frown with...err, never a GPU memory full error with AMD RX580 8 GB...4K footage, HD and UHD projects...

Hi
Good to hear it works for you. You can see the dual radeon vii threads where I come from. I currently run a RTX 2080 Super no memory issue in my workflow. I do not see what the others see. Sorry for generalizing
kind regards
HC

Sadly i have the memory bug too now AI scaling might be the issue and a can’t find the Audio devise issue(restart resolve resolved it). Version 17b3 and 4.
/HC


Sent from my iPhone using Tapatalk

I have uninstalled R17b4, it exhibits all kind of weird stuff, UI and viewer playback flickering, often failing to initialize clips for playback etc with RX 580. I went back to R16 which is rock solid. I am also very displeased with the "advances" in Radeon software, except the looks. It breaks HDCP 2.2 and pervents me from watching Netflix in 4K. It worked before with the previous unfriendly UI.

Sent from my Mi 9T using Tapatalk