GPU failed (Error 702)

I've been getting the 702 error also here and there. pretty frustrating. I've re installed current driver but drive going back on the driver. went back and forth game ready drivers and clean install. nothing works. I still get it from time to time.

Is there an idea what is sorta causing it at least?

[Dwaine Maggart]

No idea without the information requested in my message just prior to yours in this thread.

And add to those requests additionally a project export .drp of the project that the error occurred in.

Hope this sheds some light why its happening. i have a hunch that it's either with my graphics card or the nvme dedicated scratch drive. but i've tried everything and can't prevent it. it happens when i'm rendering cache.

https://www.dropbox.com/scl/fo/dlkxfwtn ... f7qvi9826m

[Dwaine Maggart]

The issue is with the amount of VRAM on your 1080Ti GPU (11 GB) and the VRAM requirements of your UHD timeline project with 8K Red media. Also possible that the 525 clips in the timeline are using a lot of VRAM when they are deinterlaced.

You also are using a Color Intelligence Look Designer plugin. I don't have that, so I don't know what kind of VRAM requirements that might need.

Simple solutions are reducing timeline resolution from UHD to HD, or getting a GPU with more VRAM.

You can monitor your VRAM use by using the Windows Task Manager on Performance tab, and monitoring the Dedicated GPU memory usage. If that goes up to 11GB, you are probably going to get a GPU memory error in Resolve. That might give you a clue as to what areas of the timeline are using lots of VRAM, and maybe you can modify the grades/effects in those areas to use less VRAM. Temporal NR is a typical high VRAM use grade. The higher the Frames number, the more VRAM it uses.

Note that VRAM usage might appear low when you have caching enabled, since once a VRAM heavy clip is cached, it won't use much VRAM. So you should check VRAM use with cache off. Because when you render the timeline, caching isn't going to help you (unless you enable rendering using cache) and it's most likely you'll run into GPU mem issues when rendering.

ok thank you. I'll examine it further. I have shared memory usage as well and was wondering could that be a factor or you think strictly dedicated memory? I do kinda wish there were some parameters in resolve or nvidia drivers side to know what's happening and prevent the crash. let the snake slow down and not chew all at once.. at rather cashe render and work slower than get a crash.

[Dwaine Maggart]

Resolve on NVIDIA relies on the dedicated GPU VRAM. The shared GPU VRAM is not used, unfortunately.