… and the culprit is … intelopencl32.dll and intelopencl64.dll which were supposed to be removed in a windows update.
See the link below for solution.
Just removing the files enabled all the Deep Learning fx’s without going into the Registry. I did though just to make sure.
As an aside, for some time now Vegas would not load with Intel UHD Graphics 630 Enabled. It just triggered an OpenCL fault so I disabled it to carry on with Nvenc. It now loads with it enabled and I now have my QSV options to Render back again.
Hope this helps anyone suffering this problem.
See
Copy of the link:
10-19-2018 06:16 PM
1,142 Views
[Announcement][Windows* OS] Intel® CPU Runtime for OpenCL™ Applications 16.1.2 to 18.1 upgrade path, troubleshooting, and fixes
Hello Windows* OS OpenCL™ users,
*Update 20181025*
Some users have reported platform interrogation discrepancies when:
installing Intel® CPU Runtime for OpenCL™ Applications 18.1 for Windows* OS over a 16.1.2 installation
after uninstalling version 16.1.2.
OpenCL™ programs are said to observe an extra, non-existant CPU platform and/or device. Uninstallation of 16.1.2 may leave assets on disk... the following system alterations should help complete uninstallation procedure for 16.1.2:
1) Remove following registry keys:
On 32-bit OS:
HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors\intelopencl32.dll
On 64-bit OS:
HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors\intelopencl64.dll
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Khronos\OpenCL\Vendors\intelopencl32.dll
2) (optional) Remove following files if they exist:
On 32-bit
OS: C:\Windows\System32\intelopencl32.dll
On 64-bit
OS: C:\Windows\System32\intelopencl64.dll
C:\Windows\SysWOW64\intelopencl32.dll
*End update 20181025*
For more information on manual installation of runtimes, users should refer to the guidance in section 5.1 of the release notes.
See full 18.1 release notes