Error Code: 77.

The GPU failed to perform image processing because of an error.

This has just started to happen today when using the stabilizer on an HD timeline.

Windows10

GTX1080ti

391.35 WHQL Driver

Did you find a solution to the problem?

It happened to me as well. I'm on Davinci Resolve Studio 15 Beta4. Funny thing is, beta3 gave me no errors when stabilizing footage.


Windows 10
32GB Ram
nVidia GTX 1060
Davinci Resolve Studio 15b4

[Peter Chamberlain]

Hi, could you PM a link to a sample clip so we can try to repo?

Hi, could you PM a link to a sample clip so we can try to repo?

Got this error too. It doesn’t seem to be linked to the clip because I’ve made another attempt after rebooting resolve and the stabilization went ok. It looks like it is only happening when I use the new stabilizer. If I switch to the classic stabilizer I never get any error.

[Peter Chamberlain]

If you see this error again please make a diagnostic log and post a link here.
We cant see this or repo.

viewtopic.php?f=21&t=69837

I'm having this Error 77 sporadically too and sent several Logfiles to Rohit Singhal.

The error occurs in different HD-Timelines with different videofiles. I'm preferably using MOV-H.264 1920x1080 50p video. Till now I haven't been able to figure out which action could have caused this error. Although the errormessage can be quit and DR says it analyzes for stabilisation it does not do nothing and has to be closed by the OS' task manager. After Restart the timeline is untouched if Autosave is enabled.

(15b4 Studio - Win 10/64 1803 - 32GB RAM - HP Z420 - GTX1080 Driver-Version 23.21.13.8846 - Computer from setup used for Davinci Resolve only)

Best Regards

Josef

If you see this error again please make a diagnostic log and post a link here.
We cant see this or repo.

viewtopic.php?f=21&t=69837

err77.PNG (455.52 KiB) Viewed 29556 times

Just stumbled upon the error this morning. I've made a stabilize and it went fine. Few seconds later, I was scrubbing the timeline and the error popped up. I had to resart Resolve as all the viewers were freezed.

Here is the log: https://we.tl/ipJ9NsI4Nw

The GPU failed to preform image processing because of an error: Error Code: 77

This has happened twice during stabilizing footage with the Camera Lock checkbox. Sometimes it does not fail. After the dialog box error comes up the program freezes.

Using Sony XAVCS footage at 1080.

Error log:
https://drive.google.com/file/d/1PF7wc- ... sp=sharing

Happen to me too, the first time today. I actually did some stabilization with the Beta 4 - but with other footage. No problem back then.

Now with "RAW" from a Sony Alpha DSLR I get this 10/10 times I try to stabilize. Resolve also freezes / crashes. Please fix!

p.s. no other issues with this footage and Beta 4. I also tried optimized media but the result is the same. I guess it could also be related to an Nvidia driver update maybe? Do you guys all use Nvidia GPUs?

[Peter Chamberlain]

Can you post a link to the clip that 'always' makes this happen?
thanks

Hi
I keep getting the same error. I originally had GPU memory full errors popping up in version 14, running a GTX1080, I knew this was a glitch, so I decided to downgrade to the lite version of beta 15.0.0B.046 and now I keep getting error 77 crashes. This is my first time using this program and its now taken me days to just start the project. Any help would be amazing!

[Shrinivas Ramani]

Could you try the new 15.0 beta 5 version to see if you face the same issues?

Thanks
Shrinivas

Hi, I installed Version 15 beta 6 and get the Error Code 77 during stabilizing a clip with GPU acceleration enabled. With CPU acceleration disabled, no problems. The same impact with with Version 15 beta 5. Version 14 works fine.

Version 15 Beta 5
GTX 1080 Ti with 11GB

I have this error 100% of the time when changing the working resolution to 6K (6144x3240).
It is a show stopper as I can't add any nodes to the time line.

Please fix.

Resolve 15 Beta 5
GTX 1080 Ti 11GB

The same problem, reproducible 100% of the time (in fact I can't avoid it in any way) as soon as I increase project resolution to 6K DCI (6144x3240). Working with 6K RED RAW.

Beta 15.beta 6 we continue with the same error
Beta 15.beta 6 seguimos con el mismo error

In 15b6 it happened today after a long time without when I tried to stabilize a clip which I previously reversed at 100% speed using the Retime Controls. No error if I stabilize the same clip in normal direction and speed. No problem to reverse the clip after stabilization.

I don't do that again....

Regards

Josef

Happened to me today too (Beta 6) without even doing the editing, just importing footage (4K HEVC 10bit - normally no issues at all). Windows updated last night though to April version, that killed OpenCL (which I've fixed) but now this error too.

I've kinda - but not completely - solved the problem, well at least for my scenario.

Turns out the most recent Nvidia driver is incompatible with Resolve 15.X driver version 24.21.13.9836 (398.36). I rolled back the driver to 23.21.13.9077 (390.77) and the GPU error has gone.

HOWEVER....

I did get a BSOD about 20-minutes later. I wasn't using Resolve at the time (but was open in the background) so it may or may not be related. I blame Windows April 2018 update - nothing but trouble.

I started getting this error today too on a project I've been working on for a week or more. I created the project using 15 B4, updated to 15 B6 a few days ago.

Same issues as above in that crash was not related to a specific clip or operation. Rebooting did not fix the issue, however (so far so good) reinstalling the 398.11 Nvidia drivers has stopped. See how it goes.

Hi again, I now installed Version 15 beta 7 and get the Error Code 77 during stabilizing a clip with GPU acceleration enabled. (Latest NVIDIA Driver 398.82 as well 398.36 and 398.11).With GPU acceleration disabled, no problems. The same impact with with Version 15 beta 5 and 6. Version 14 works fine.

I have just swapped back to beta 6, as there are few things that I am doing with a project where issues with beta 7 (lost ability to shuffle clips between other clips along time line) and beta 8 (issue with JKL in Color page) get in the way somewhat.

So, with beta 6, I every now and again get this issue with Code 77 The GPU failed to perform image processing because of an error, and then unable to close the Analyzing... window, necessitating I force-close using Windows End Task.

I see some people have reported this with beta 7. Does anyone experience this issue with beta 8?

Hello, now I have installed version 15 beta 8. The problem is solved! I was unable to reproduce the error again. The stabilization works perfectly with GPU acceleration enabled. Many thanks to Blackmagic!

Hello, now I have installed version 15 beta 8. The problem is solved! I was unable to reproduce the error again. The stabilization works perfectly with GPU acceleration enabled. Many thanks to Blackmagic!

Thank you so much for the information...

Hi, I´ve got just that error now, using Resolve Studio 15 (full). I was trying to use the stabilizer with 1920x1080 XAVCs files (of a Sony A7s). Now is hanged

I upgraded from Studio 14.3 to Studio 15 the day it was released and have had no problems. Today I noticed that most of the stabilization that I had done on a 55 minute long project using DR 14.3 had disappeared. When I tried to re-stabilize one of the clips, I received the Error Code 77 and the machine locked up. I haven't tried again. Files are from a Sony FS700 AVCHD codec.

Had another go at stabilizing a clip. I am using DR 15 Studio. First attempt the stabilization was not good. (This clip had been stabilized previously in DR 14.3 Studio and worked perfectly but the stabilization disappeared when I changed to DR 15 Studio) Tried again and received the Error Code 77 and the computer locked up. Had another attempt and the program crashed. I used the stabilizer on a lot of clips with perfect results in DR 14.3 Studio but in DR 15 Studio my experience has not been good. Am I the only one having this problem?

I'm currently working on a project where I need to stabilize dozens of clips from a Sony A6500 and they all work fine. I re-wrapped them from mp4 to mov, though.

I am wondering if it is because they were originally stabilized with DR 14.3 Studio. When I switched to DR 15 Studio most of the clips that had been stabilized lost the stabilization. The problem is happening when I try to re-stabilize the clips.

Can you try to reset the stabilization data (upper right in stabilizer, clear all tracking points), even if there is none?

Sometimes it works for me after I trim a clip a bit.


Sent from my iPhone using Tapatalk Pro

Thanks Uli and Pavel for your advice. Tried your methods and DR 15 still crashed however it did give me the idea to reinsert the clip into the timeline and try again. This time the stabilization worked perfectly. What I can deduce is that when I upgraded to DR 15 Studio the stabilization disappeared on most of the clips that I had stabilized when the project was completed using DR 14.3 Studio. For projects started on DR 15 the stabilization works well.
Even though there was no sign of stabilization having been done to the clip, there must be some hidden data referring to the clip even after clearing (resetting). This then corrupts the new attempt to re-stabilize with DR 15. This may turn out to be a pain for users down the track if they need to revisit a project completed on an earlier Davinci version.
Thanks for your help.

Also for anyone else having same error, try copy pasting (or Alt + Drag ) to duplicate the clip and then stabilize it.


Sent from my iPhone using Tapatalk Pro

Having this happen on every clip I enable GPU stabilization on. Working around by using cpu or the legacy stabilizer.

Any known fixes yet?

I am not stabilizing any footage, doing an export I am at %68 export and I am having this problem.

I figured out what my issue was, something I will chop up to a rookie mistake. I was overwhelming my ASUS Nvidia 1070 by using the Red Denoiser and the Davinci Denoiser. Once I turned the Red Denoiser to the minimum from Maximum the file encoded fine.

Hey Peter, I'm working on a broadcast show and I cannot get Resolve 15 to stabilise *any* clip without throwing an error 77 and freezing. Is there anything I can provide to help get this bug fixed?

Im getting the error 77 code aswell when adding the noisereduction (some times have worked). I have only 8k and 6k .r3d ith the project and apart from render out clips with noisereduction everything is quiet fast and responsive in terms of playback experience.

Im running
windows 10 pro. Version 10.0.17763 Build 17763
Name NVIDIA GeForce GTX 1080 Ti 11GB ram.
Driver Version 419.17
Davinci Resolve Studio 15.4.006

The workstation is from supermicro with dual cpu's and 64gb ram working with the footage of an local qnap server.

Seams like there have been some slowdowns on the Davinci 15.3 so I have not installed that yet.
Do you think that might fix this issue?

I have the same problem with all last version of Resolve.
I have one Quadro M5000 and two GTX 1080 Titan Black; if I use the GTX for rendering Resolve and system goes to crash (also with 2k project); if I use only the Quadro M5000 (rendering Cuda manual option on the preference) I haven't issue.

Resolve 15.3 Studio, Windows 10 Pro, Nvidia 419.67 (...but same issue with other driver), Desktop Video 11.1, Intensity Pro 4K.

alessandro

Resurrecting this issue.

We have this happening on all of our machines that are using 2080ti's. The only system that seems to be immune is one running a single P5000. It occurs when both rendering from the deliver page and caching. It has been an absolute pain.

It happens on a variety of different shots but you can guarantee it will happen on 4K shots with both dissolves and noise reduction.

Our Nvidia drivers are up to date and we are on Resolve 15.3.

Thank you for your time.

Just updated from 15.2.3 to 16 b3, due to the need to work with BRAW. Can't use fusion to key anymore, always getting Error 77. Tried Chroma Key and Ultra Key.

Win 10, i7 5960X, GTX970, 32GB RAM, Intensity Pro 4K - All up to date.

Ok! This is a known issue and I have a 28 minute GH5 footage in timeline. So has anyone got any solution?
On DR 16 beta 6.

I keep getting this code randomly with Red r3d files.

Just got it myself when trying to apply an OFX Color Transform effect to a 5K R3D clip. The message popped up when trying to scrub the clip on the color page.

I just upgraded to 16.1.2 and enabled the "Decompression and Debayer" option in the preferences - decode options settings. When I try and play sample red footage, I get the Error 77 message and the picture locks up until Resolve is restarted. The footage was downloaded from the red.com/sample-r3d-files page and is the HELIUM 8K S35 footage. I am running a Windows 10 box with an RTX 2080ti and a Blackmagic Decklink 4k 12G Extreme video card.

[Rohit Singhal]

can you post the logs from 16.1.2?

I just upgraded to 16.1.2 and enabled the "Decompression and Debayer" option in the preferences - decode options settings. When I try and play sample red footage, I get the Error 77 message and the picture locks up until Resolve is restarted. The footage was downloaded from the red.com/sample-r3d-files page and is the HELIUM 8K S35 footage. I am running a Windows 10 box with an RTX 2080ti and a Blackmagic Decklink 4k 12G Extreme video card.

There are 8 different files on that webpage identified as "HELIUM 8K S35". I happened to have 3 of them, which I loaded into the Media page and played without failure with the settings you mention, this on my lower-spec'd GPU. It may be necessary to know
(1) exactly which ONE of the EIGHT did you have problems with?
(2) what is your system configuration, including NVIDIA driver?

updated the software, first time user and getting the error code above

I just upgraded to 16.1.2 and enabled the "Decompression and Debayer" option in the preferences - decode options settings. When I try and play sample red footage, I get the Error 77 message and the picture locks up until Resolve is restarted. The footage was downloaded from the red.com/sample-r3d-files page and is the HELIUM 8K S35 footage. I am running a Windows 10 box with an RTX 2080ti and a Blackmagic Decklink 4k 12G Extreme video card.

There are 8 different files on that webpage identified as "HELIUM 8K S35". I happened to have 3 of them, which I loaded into the Media page and played without failure with the settings you mention, this on my lower-spec'd GPU. It may be necessary to know
(1) exactly which ONE of the EIGHT did you have problems with?
(2) what is your system configuration, including NVIDIA driver?

Apologies for the delayed response, holidays.

1. The ONE of EIGHT files was named H001_C001_1215VG_001.R3D and was in a folder titled "epicw8k-standard-24fps-7to1redcode_16x9". It's the city skyline to the right of the snow covered monkey in the pool clip. The similarity in specs for the other clips fooled me in to thinking this wasn't necessary info.

2. Computer specs: 7980xe Skylake X 18-Core on a ROG Rampage VI Extreme with 64 gb of Corsair dominator platinum 64gb (4x16gb) ddr4 3200mhz ram. The media drive is a 1TB Samsung 970 pro NVME and the system drive is a Crucial MX500 2TB. I am running Windows 10 with an RTX 2080ti card running driver 26.21.14.4166. The video card is a Blackmagic Decklink 4k 12G Extreme video card going sdi to an FSI broadcast monitor and and HDMI to a UHD LG OLED client montior. I have an XMP profile setup in my bios, but otherwise stock.

Additional info: My timeline settings are set to the 8k resolution of the source clip. The 12G Extreme is sending a UHD signal to the client monitor and a real time down convert to 1080p for the FSI. There is no scaling on the output so there is cropping to the UHD resolution. I have no color grade on the clip and was only testing the new driver for playback performance at this point.

Some new info I came across is in the article from Puget systems that seems to suggest the "Decompression and Debayer" setting can actually cause worse performance on multi-core machines. Their tests were on an 24 core AMD TR 3960X.

https://www.pugetsystems.com/labs/artic ... ents-1645/

I have dropped my setting back to "Debayer" and so far the issue is resolved and the system is stable.