Video imports but is black with broken thumbnails and audio

My System:
MSI B450-A Pro
AMD Ryzen 7 2700
Radeon RX580 8gb
Windows 10

Everything but Resolve is running fine. No issues with other programs. I have been using Resolve for several projects when last night I got an alert from Windows Security saying it had prevented divincipaneldaemon.exe from accessing public networks. I didn't think anything of it until I had this issue. When I try to import mp4 video AND when I open projects from before the problem started now the video doesn't appear to be recognized in the timeline and it's black in the previewer. The timeline thumbs look like like B&W snow on an old TV with some random pixels of color interspersed.

I changed the settings in Windows to allow the file to access any network and I don't know if that solved the problem but I was able to work on a project last night. Just now I am trying to start a new project and am having the issue again. So I went to see if the setting had changed but it did not. So I don't think it is related and last night was a fluke perhaps. IDK.

I tried also to reopen a couple projects that never had the problem and now they have the problem too. So it's not just a failed import. But I don't know what to do. I don't see anyone else having this problem.

Please advise.

[Peter Chamberlain]

Are you on beta 4?

I included some images for reference. Thanks.

Bump - still broken

Try updating to beta 4. Might make a difference (you never know). Your screen capture shows that you are running an earlier beta (build should be at least 033).

Updated to latest. Problem persists.

Joel I am running 16 Beta on 4 different computers and I have had that same problem on two of my workstations both of which run AMD cards. One is the 560 and the other is the 580. I had to do a lot of uninstalling and reinstalling of the AMD drivers to get it to work correctly.

It was one of those situations where I was doing so many things that I am not sure exactly which step fixed it but the thing that I did on both computers around the time that i got it to render thumbnails and video correctly was to use DDU to remove the latest AMD drivers (19.5.2 brand new at the time) and re-install the prior release (19.5.1). On the rare occasion that the thumbnails brake again (rare on 5.1) I can reboot and that would take care of it each time. Prior to that I couldn't get thumbnails or video to show correctly no matter how much rebooting or reinstalling I did.

So although I can't be 100% sure it seemed that the 19.5.2 drivers were the problem and just uninstalling with AMD's uninstaller didn't fix it. I had to use DDU to get rid of it completely. And I am now running 6.1 and I don't think I have had an issue with it since.

@Buck Thanks for that info. I went into preferences and setup a new media storage location and then restarted Resolve and was able to import a video that did show video and thumbnails correctly. So for a minute I thought maybe there was some issue with the hard drive that the original media storage location was set to use. But when I closed and re-opened Resolve it went back to being broke again while using the new location on a different HD. I'm going to try to re-install the RX580 drivers now to see if that makes any difference. This is frustrating because I built this AMD machine specifically to run Resolve as I'm trying to get out of the MAC world.

Resolve will not open now. It gets stuck "loading waveform". I have to kill the process with task manager. I rolled back the RX580 driver but that doesn't make any difference. I was going to just reinstall the previous version I had running but the website is trying to get me to signup again. I don';t know what to do. Please advise.

I completely removed the Radeon Drivers using DDU in safe mode and then downloaded an older version (Radeon Software Version 19.1.1) and now Resolve opens and at least for now my video has come back to life. All later driver versions cause the original problem FYI.

Having exactly the same problem, started randomly on a newer driver. Occasionally worked for a few reboots but now nothing is bringing it back. Not even the 19.1.1 driver.
Has the issue come back on your system yet?

Adrian, did you use DDU to remove the bad driver? You have to use it to do a full low-level driver delete. Download 19.1.1 to your desktop as you have to unplug internet and enter safe mode when using DDU. Just opened Resolve to test it's still working for me and, yes it is. Hope that helps. https://www.wagnardsoft.com/

Adrian, did you use DDU to remove the bad driver? You have to use it to do a full low-level driver delete. Download 19.1.1 to your desktop as you have to unplug internet and enter safe mode when using DDU. Just opened Resolve to test it's still working for me and, yes it is. Hope that helps. https://www.wagnardsoft.com/

Thanks for the suggestion but I've already tried that, even the WHQL driver Windows 10 immediately installs (if you don't disable it) doesn't work. At this point, I've tried so many drivers that I think BlackMagic should (and hopefully already did) take a very close look at how their software interacts with AMD (drivers) on Polaris.

I had the same issue on Win10 with the latest Radeon WX 4100 driver, downgraded to 24.20.13028.22 and now it's normal.

I had a lot of troubles with this card in general. It simply does not work with video within Lightroom: full system crashes all the time. Also sleep function is not healthy.

However Resolve 16 keeps causing system crash, so I went back to 15.

[Peter Chamberlain]

However Resolve 16 keeps causing system crash, so I went back to 15.

Could you review this and provide details so we could try to assist?
viewtopic.php?f=21&t=90190

I have solved it yesterday. I am not sure if it works for everybody.

1.DDU to uninstall gpu driver and turn on Windows driver pushing in DDU
2.Reboot and wait for Windows pushing driver, can also manually check update in Device Manager if no automatic pushing
3.Reboot and DR16 should be fine, run it to check
4.Download driver from AMD and install it directly, DR16 can work with new driver. (Mine is newest recommend version 19.5.2)

So my finding is install older version (should better with windows pushing version) and update without uninstall older version should be fine.

I tried DDU and install new 19.x.x driver, none of them can works. (including 19.7.5 / 19.5.2 / 19.4.x / 19.1.1 / 18.10.1)

I am afraid pervious posts can solve it by install some versions is not the key. At least to me I can run with 19.5.2 and not too. Just depends on if I cleanned windows driver.

I have tested DR16 for editing and grading with reboots many times, very stable without any crash or black thumbnail. I think it is done.

I hope this can help. Anyone who overcome it can leave comments.

I hope this can help. Anyone who overcome it can leave comments.

So I uninstalled using DDU and just let windows install a driver, all right? Then, when I startup R16, it says it cannot find an OpenCL capable CPU, so for me it stops. Unless I install the latest driver, and then I am back to the pixel problem.

BTW the official 16 gives the same problem

Could you review this and provide details so we could try to assist?
viewtopic.php?f=21&t=90190

I added my system setup to my signature. Is that enough for now? The broken thumbnail issue is back in 16.

I hope this can help. Anyone who overcome it can leave comments.

So I uninstalled using DDU and just let windows install a driver, all right? Then, when I startup R16, it says it cannot find an OpenCL capable CPU, so for me it stops. Unless I install the latest driver, and then I am back to the pixel problem.

BTW the official 16 gives the same problem

No. Don't choose the option in DDU to let Windows install the driver. Download the driver, let DDU clean up old drivers and install the downloaded drivers manually.

No. Don't choose the option in DDU to let Windows install the driver. Download the driver, let DDU clean up old drivers and install the downloaded drivers manually.

Well, what happens when I remove the driver by DDU, at startup Windows has to install some basic driver in order to get an image on the screen, as far as I understand. From there I manually installed the ADM driver, but no success.

No. Don't choose the option in DDU to let Windows install the driver. Download the driver, let DDU clean up old drivers and install the downloaded drivers manually.

Well, what happens when I remove the driver by DDU, at startup Windows has to install some basic driver in order to get an image on the screen, as far as I understand. From there I manually installed the ADM driver, but no success.

It installs some basic "VGA" driver (like in the od days) that makes desktop very slow and low res, otherwise it always tries to be smart and install some windows-bundled driver for the specific vendor/GPU...AFAIK...

I hope this can help. Anyone who overcome it can leave comments.

So I uninstalled using DDU and just let windows install a driver, all right? Then, when I startup R16, it says it cannot find an OpenCL capable CPU, so for me it stops. Unless I install the latest driver, and then I am back to the pixel problem.

BTW the official 16 gives the same problem

No. Don't choose the option in DDU to let Windows install the driver. Download the driver, let DDU clean up old drivers and install the downloaded drivers manually.

I thought like you, do not let windows to install. But in my case, this doesn't work. I have to install AMD driver over the windows auto driver. Anyway, this just my solution.
This is still should be a problem to BMD or AMD. Because I do not see any other program issue with clean installed new driver. Hope they fix it soon.

I hope this can help. Anyone who overcome it can leave comments.

So I uninstalled using DDU and just let windows install a driver, all right? Then, when I startup R16, it says it cannot find an OpenCL capable CPU, so for me it stops. Unless I install the latest driver, and then I am back to the pixel problem.

BTW the official 16 gives the same problem

So my soultion may not work for you.
Windows pushing driver can run DR16 in my machine. Just make sure you install DR16 to default C drive. I get opencl fault before due to this.