DaVinci Resolve Not Working on Windows 10 Machine

Hello, new user here.

I have installed the free version of DaVinci Resolve on my PC and I can't get it working. I have gotten as far as the welcome screen, and when I continue, the program does not open. Now when I open the program, it always gets suspended and closes. I have tried everything from deleting the AppData for BlackMagicDesign, reinstalling the program over and over, updating my AMD graphics driver, but no dice. Can you help me figure out what is going on? I have attached the latest log files and the NFO file to this post for reference. Any help would be appreciated.

Log and NFO files: https://drive.google.com/drive/folders/ ... sp=sharing

Just a chance. Did you disable all virus programs when you installed. Usually a good idea as these often interfere with installs. Defender is usually OK.

I don't think your AMD Radeon RX 580 GPU w/ 1GB VRAM is compatible with Resolve.

SkierEvans wrote:
Just a chance. Did you disable all virus programs when you installed. Usually a good idea as these often interfere with installs. Defender is usually OK.

I tried reinstalling the program with my Avast shields off and that didn't seem to help. The program is still in a suspending state whenever I start it.

Gary Hango wrote:
I don't think your AMD Radeon RX 580 GPU w/ 1GB VRAM is compatible with Resolve.

That would suck if that's the case. I have no idea why the NFO file lists the graphics card as just 1 GB. The graphics card is an 8 GB model and it says so in the task manager.

By the way, I also tried removing all USB devices other than the mouse and keyboard and turning off Bluetooth, but no dice there either.

Couple things you might try.

1. Fully uninstall Avast. Windows Security is sufficient.

2. Make sure you're using an Admin level account for Installation and running of Resolve. Don't use a limited Guest account.

I uninstalled Avast and tried reinstalling DaVinci. Still doing the same thing. Will try reinstalling by running as admin.

I also tried installing and running as admin. That didn't help either.

OK.

At this point you may have to waif for staff to review the logs.