nvidia driver problems

After updating the driver for my GTX Titan Pascal (381.65) I'm seeing issues in Pro Res 422 HQ quicktime and DNxHD 185X MXF opt1a files. A blue/purple vertical line appears on the right side of the image, as well 'some other stuff' on the very right edge of the frame.

Verifying the same material, on the same machine, in Adobe Premiere does not give the blue line glitch. Also in Assimilate Scratch this issue does not occur. Pro res 4444 footage looks like normal.

WIN10, Resolve 12.5.5.026

ps. I rolled back to 373.06 and problems are gone.

Same with cineform 10 bit on my system.

381.65 with Dual GTX 1080ti with Resolve 12.5.5 on Win 10.

I have the same issue as I have the same setup (dual 1080ti). What solved it was changing CUDA to OpenCL.

Also, I haven't tested it on older drivers, but I get faster FPS on graded Red 6K footage on openCL with the current setup.

In openCL, graded Red footage will play back at 17.5fps, and in CUDA, it was around 14.5 fps.

Sent from my XT1563 using Tapatalk

Same here,

I have the same problem as Pepijn. After updating to 381.65 blue/purple vertical line appears on the right side of the image and at the right edge there is also a thin vertical line of random noise.I tried many different Prores422HQ files that I have.
Trying to render to h264 or other codecs burns the problem to the new file.

Switching to OpenCl as Roger mentioned solves the problem.
For the time being I am rolling back to my previous drivers 378.86 that fix the problem.

I am on Windows 10 Pro, Titan X + GTX 1080. Resolve 12.5.5.026

New drivers, new adventures every time..

Hey gang, i am having the same issue, as soon as i put in my new GTX 1080TI im getting that wierd blue sometimes yellow line on the right side of the screen, AND.. sometimes the video on the right side flickers, just on the right side, what gives?

Did you see one or more times a popup where "display driver stopped responding and has recovered" was displayed? (Apart from the use of Davinci Resolve)

This bug seems to appears only with 10bit files.

No issue on résolve 14.