Existing issue from Premiere Pro CC 2015 to 2017
Copy link to clipboard
Copied
Now that Premiere CC 2017 came out, I decided to see if I can upgrade from Premiere CC 2014. I am running into the same issue with versions 2015, 2016, and now 2017. It starts up and I get the following error (see screenshot). I am taking that error with a gain of salt, because I have a NVIDA GeForce GTX 950 from EVGA with the latest drivers. If I un-install 2017 and re-install 2014, Premiere Pro opens up just fine without any issues.
Messing with "running as Administrator" does not help either. To me the real problem is dynamiclinkmanager.exe and here is why. If I decide to run GPUSniffer in the Premiere folder, the program errors out. If I go to Adobe Audition and run the GPUSniffer there, no problems
I strongly believe the root of the issue is the Adobe Dynamic Link Manager that comes with the latest version. GPUSniffer uses the Adobe Dynamic Link Manager to run. Since GPU Sniffer fails, we get the
could not find any capable video play modules"
Adobe Dynamic Link Manager has problems and it will fail but I do not know what are the conditions that is causing the failure.
Does anyone have any ideas, otherwise I am going back CC 2014?
thanks,
Jaime
Copy link to clipboard
Copied
I have same issue with multiple GPUs,
keeping one and disabling all others seems solve the problem
Copy link to clipboard
Copied
I have tried disabling my other GPU but the error still happens. What is weird, Premiere CC 2014 doesn't have an issue with two GPUs. Still believe the issue has to do with Dynamic Link Manager (DLM) and GPUSniffer is not able to execute to locate any GPUs. I have noticed that the DLM is a different version in CC 2014 than CC 2015-2017. I'll have time this weekend to explore this.
Copy link to clipboard
Copied
Sam here,
I have 3 GPUs, one of them is Tesla K40 GPU accelerator, disabling this card while keeping the other two seems working,
also this error impacted all Applications (Premiere , Media Encoder and After Effects). even photoshop didn't run in CUDA mode.
Please keep my updated with your findings.
Thanks
![](/skins/images/EAF9F7E131C5D03B206D7C6CFC7D852B/responsive_peak/images/icon_anonymous_message.png)
![](/skins/images/EAF9F7E131C5D03B206D7C6CFC7D852B/responsive_peak/images/icon_anonymous_message.png)