Davinci resolve ошибка dll opencl

I guess I do need the above runtime, because otherwise there is no opencl.dll in the Windows system directories. I tried the other Intel OpenCL installer, but that appears to be for Intel CPU’s with onboard Graphics. The OpenCL test/benchmark program ViennaCLBench fails to run with that, but runs with the runtime that I linked in the post above this one.

The MESA docs say that it should be completely overriding all OpenCL calls anyway. I can’t test MESA with ViennaCLBench because it’s a 32 bit program, and the x86 builds of clover have failed so far in MESA.

Here’s Resolve 15.3.1 free/trial if you want to test it.

Just to experiment, I renamed OpenCL.dll to OpenCL.dll.bak and MesaOpenCL.dll to OpenCL.dll.

That’s a bad idea because MesaOpenCL.dll is an ICD that needs to be loaded by official Khronos OpenCL runtime.

You can register MesaOpenCL.dll with Khronos OpenCL runtime by adding it in registry like this

Don’t forget to remove Mesa DLLs from program folder otherwise it won’t pick it up.

Hey! Thanks for the reply!

Unfortunately, I couldn’t get it to work. Resolve now starts like there is no OpenCL on the system, and gives the message, «»DaVinci Resolve could not find any OpenCL capable GPUs.»

What files should not be in the program directory?

Here’s what I’ve got so far:

Made directory C:Program FilesMESA

Copied in the following:

MesaOpenCL.dll
OpenCL.dll
clon12compiler.dll
pipe_swrast.dll

Created Dword32 entry C:Program FilesMESAMesaOpenCL.dll under key HKEY_LOCAL_MACHINESOFTWAREKhronosOpenCLVendors, set to 0. Like your screenshot I also have an entry for intelocl64.dll.

In the Resolve application directory, I have:

libgallium_wgl.dll
libglapi.dll
opengl32.dll
vulkan-1.dll

All MESA files from 21.3.5 MSVC release. Vulkan-1.dll from VulkanRT-1.2.198.1-Components.zip.

I checked resolve.exe with x64dbg and created a log file. Looking at the file, I can see that it loads all four MESA OpenGL files listed above from the application directory. It doesn’t load opengl32.dll from the Windows System directory.

With OpenCL, it loads:

C:WindowsSystem32OpenCL.dll
C:Program Files (x86)Common FilesIntelOpenCLwindowscompilerlibintel64_winintelocl64.dll
C:Program Files (x86)Common FilesIntelOpenCLwindowscompilerlibintel64_wintask_executor64.dll
C:Program Files (x86)Common FilesIntelOpenCLwindowscompilerlibintel64_wincpu_device64.dll
C:Program FilesMESAMesaOpenCL.dll

That’s everything I noticed. MesaOpenCL.dll does throw numerous exceptions in the log file.

Here’s the entire x64dbg log file: https://pastebin.com/bWPY9aaW

Resolve does appear to be looking for a hardware GPU, so maybe it just simply won’t work with MESA. Or it could be something stupid like a file needing to be named something specific. I remember when I was trying to get Topaz applications to run with MESA and had just about given up, thinking it wasn’t possible, and I have no idea what made me think to try this, but I made a second copy of MESA’s opengl32.dll in the application directory and named it opengl32sw.dll, and that actually worked. I was shocked when I saw the application run. I discovered that it would only work if both opengl32.dll (MESA) and opengl32sw.dll (duplicate copy of MESA opengl32.dll) were present in the application directory. Delete one, and it no longer works. There was NOTHING from looking at any debugger, logs, or otherwise to lead anyone to think that that would be what makes it work. So it’s possible there’s something like that going on here. (I have no idea, just guessing.)

Copy libgallium_wgl.dll and libglapi.dll in C:Program FilesMESA and then remove those 4 files from Dvinci Resolve folder. If this still doesn’t work we are kind of screwed.

It didn’t work. Oh well, thanks for trying! :

It gives this error:

If I click «Update Configuration» it shows this:

I believe that’s the problem. It should list an entry in there for the «GPU» which is the Intel CPU runtime for OpenCL, like it shows here in ViennaCLBench:

I mean, MESA shouldn’t really be necessary, since the Intel drivers I have installed are supposed to be a complete software rendering runtime. So it must mean Resolve 15 is coded in such a way as to need to see a physical GPU card. The reason I tried at all is that I’ve heard of people running Resolve 15 on Linux using MESA, so I thought it should work for Windows, since OpenCL is now part of the Windows build here (at least for x64 so far). It must be that the Linux version of Resolve is coded without the limitation of needing a physical GPU. I suppose I could try older versions of Resolve, but I think I’ve spent too much time on this so far!

Thanks again for the replies.

I tried running this:

http://wiki.luxcorerender.org/LuxMark_v3
https://github.com/LuxCoreRender/LuxMark/releases/download/luxmark_v3.1/luxmark-windows64-v3.1.zip

It crashed.

I then removed the registry entry of C:Program FilesMESAMesaOpenCL.dll under key HKEY_LOCAL_MACHINESOFTWAREKhronosOpenCLVendors.

After doing that, LuxMark now runs.

So I guess Resolve is hard coded not to use a software renderer for OpenCL.

Faulting application name: luxmark.exe, version: 0.0.0.0, time stamp: 0x55e59579
Faulting module name: MSVCR120.dll, version: 12.0.40660.0, time stamp: 0x577e0cc7
Exception code: 0x40000015
Fault offset: 0x00000000000748a6
Faulting process id: 0x4220
Faulting application start time: 0x01d81fb22e7f7654
Faulting application path: E:luxmark-windows64-v3.1LuxMark-v3.1luxmark.exe
Faulting module path: C:Windowssystem32MSVCR120.dll
Report Id: 6d10ad07-8ba5-11ec-a7fb-0050560334cc

So it must mean Resolve 15 is coded in such a way as to need to see a physical GPU card.

Precisely, it demands a CL GPU type device, see pal1000/save-legacy-intel-graphics#4.
It might work with Mesa clover (MesaOpenCL.dll) or CLonD3D12.
You don’t seam to have much luck with former and judging by this

Oh s**t, I probably should have mentioned this is Windows Server 2008 R2 (equivalent to Windows 7).

you are way bellow the requirements for latter.

I tested ViennaCLBench but it’s not relevant to this issue because it’s a 32-bit program so it can’t use Mesa clover and it also uses CL CPU type devices if available.

I tested LuxMark and I got the same crash you reported. CLonD3D12 crashes too but at least it let us in enough so we can disable it from right pane if we are fast enough. You should report crashes like this upstream for better visibility.

I keep trying new MESA versions, including the latest 22 r2, and so far I have not found a single thing working with OpenCL. Same crash on Luxmark, etc. The release notes seem to indicate changes and such for clover… is ANYTHING supposed to be working for OpenCL? If not, what is the point of these non working builds? Not trying to sound insulting or anything… just confused.

Well, clond3d12 is also available for Windows 10 and 11 and it works even without a D3D12 graphics driver by using the CPU. I may give up on clover if I keep getting reports that is so broken.

At this point I’m just trying Luxmark with new releases to see if it will start.

Still crashes with mesa3d-22.1.0-release-msvc. 😞

MESA folder contains MesaOpenCL.dll, libgallium_wgl.dll, and libglapi.dll. Registry key HKEY_LOCAL_MACHINESOFTWAREKhronosOpenCLVendors has 32 bit Dword C:Program FilesMESAMesaOpenCL.dll in it. Luxmark crashes. Delete that Dword, and it runs with Intel CPU OpenCL drivers (intelocl64.dll is in above registry key).

also please notice this

The OpenCL CPU runtimes will be installed to the following directory:
C:Program Files (x86)Common FilesIntelShared Libraries

Known Issues and Limitations
A known-issue in the installer of previous version of Intel® OpenCL driver for Intel® Graphics for Windows that removes one registray key, so the OpenCL application will fail to run on Intel CPU processor.

Workaround: this issue can be fixed with the method below.

Manually update the registry key:
run «Registry Editor» program
go to
for x32
HKEY_LOCAL_MACHINESOFTWAREKhronosOpenCLVendors

for x64
HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeKhronosOpenCLVendors

add a new key with following key-value pair:

for x64
«C:Program Files (x86)Common FilesIntelShared Librariesintelocl64.dll»=dword:0
this file dont showng up at inside regedit or the folder intelocl64_emu.dll

for x32
«C:Program Files (x86)Common FilesIntelShared Librariesia32intelocl32.dll»=dword:0
«C:Program Files (x86)Common FilesIntelShared Librariesia32intelocl32_emu.dll»=dword:0

the file named C:Windowssystem32MSVCR120.dll
its from the Microsoft Visual C++ Redistributable

that file is for
Visual C++ Redistributable Packages for Visual Studio 2013

Visual Studio 2015, 2017, 2019, and 2022
docs.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170

Architecture Link
ARM64 https://aka.ms/vs/17/release/vc_redist.arm64.exe Permalink for latest supported ARM64 version
X86 https://aka.ms/vs/17/release/vc_redist.x86.exe Permalink for latest supported x86 version
X64 https://aka.ms/vs/17/release/vc_redist.x64.exe Permalink for latest supported x64 version.

                 Notes
                 The X64 Redistributable package contains both ARM64 and X64 binaries. 
                 This package makes it easy to install required Visual C++ ARM64 binaries when the X64 Redistributable is 
                 installed on an ARM64 device

also notice
The current installed version number is stored in the HKEY_LOCAL_MACHINESOFTWARE[Wow6432Node]MicrosoftVisualStudio14.0VCRuntimes{x86|x64|ARM} key.

every visual studio got it version number for the

The version number is 14.0 for Visual Studio 2015, 2017, 2019, and 2022 because the latest Redistributable is binary compatible with previous versions back to 2015

Yeah, that’s fine, I have that registry key and OpenCL for Intel CPU works fine. It’s the MESA Clover OpenCL GPU software emulation that is not working… yet. Hopefully it will, someday? :p

The upstream was closed with «Closing now that Clover’s probably going away.»

Not sure if that means that Windows will not support OpenCL at all for the future, or if Clover will be replaced with something else.

Not sure if that means that Windows will not support OpenCL at all for the future

Windows has CLonD3D12 driver but it may have stopped working with switch to LLVM/Clang 15.

or if Clover will be replaced with something else.

It’s being replaced by Rusticl, but this new driver doesn’t build for Windows yet.

As usual, please forgive my ignorance…

How does one go about configuring the system for openclon12 / CLonD3D12?

I tried the simple «copy all dll’s from the latest release into the application directory,» but that didn’t work for Luxmark. I tried both MSVC and MingW.

Using CLonD3D12 works the same way it worked with clover ICD (MesaOpenCL.dll).
CLonD3D12 ICD name is openclon12.dll.

What other files should be in the directory that contains openclon12.dll?

Registering OpenCL or Vulkan drivers in general doesn’t involve copying files over to program folder at all, instead it works by writing to registry or setting environment variables that point to driver full path.
I already gave you an example with registry here. Also don’t forget CLonD3D12 requires Windows 10.0.19041.488 or newer.

I understand that, what I am asking is, what files other than openclon12.dll need to be in the driver full path folder? openclon12.dll is under 2 MB so there must be other files that need to be in the driver path folder, right? 😕

I recommend you to just extract mesa-dist-win release package somewhere and then the paths to CLonD3D12 driver would be <path-to-mesa-dist-win>binx64openclon12.dll and <path-to-mesa-dist-win>binx86openclon12.dll respectively.

For Vulkan and OpenCL drivers you don’t have to copy any files to program directory. OpenCL ICD loader and Vulkan runtime respectively handle finding drivers’ depending DLLs for us.

To satisfy your curiosity openclon12.dll depends on dxil.dll, clon12compiler.dll and on x64 only, WinPixEventRuntime.dll.

OK, thanks very much for the clarification.

Again (sorry for so many basic questions), does the Vulcan runtime need to be in the driver path folder along with MESA, or does the Vulcan runtime go in its own driver path? (Or in the WindowsSystem32 directory)?

Remember, I’m attempting to get a MESA to run as GPU MESA, on a system that does not have a GPU, which I’m assuming should be possible in the same way that OpenGL is able to run OpenGL dependent applications on a system without a GPU (i.e., a VPS).

Vulkan runtime is packaged an excusable installer. Just run it as it’s unpacked in WindowsSystem32.

Hello again and Happy Holidays!

I finally had time to try openclon12.dll. It didn’t work, Luxmark still crashes, but it looks a bit different now. It appears to crash at the point where it would start drawing onscreen. Event log just shows Luxmark crashing itself (luxmark.exe), so that isn’t really useful.

Here’s what I did (Windows 10 x64 2004 final build 19041.1415):

1 — System path environment variable added C:Program FilesMESA

2 — Place all files from mesa3d-22.3.1-release-msvc.7zx64 into C:Program FilesMESA. (Also tried with mesa3d-22.3.1-release-mingw.7zx64, this had no effect.)

3 — Create zero value DWORD registry entry openclon12.dll under ComputerHKEY_LOCAL_MACHINESOFTWAREKhronosOpenCLVendors.

4 — Install Vulkan runtime VulkanRT-1.3.236.0-Installer.7z. (Also tried manually copy + pasting files from VulkanRT-1.3.236.0-Components.zip into C:WindowsSystem32 and C:WindowsSysWOW64, this had no effect.)

I think that should be everything?

So this is what happens when I try to run Luxmark:

Unfortunately, since it crashes nearly right away, I cannot scroll down the log text on the bottom, or export it since the application is in a crashed state.

Does this require a GPU to work? The Vulkan runtime is for a GPU, and this is a system with no GPU. If it does need a GPU, then I wonder what is the point, as I thought this was supposed to be a GPU software renderer for OpenCL, unless I am misunderstanding something. (Should I be doing anything with Swiftshader?)

I got crash with Luxmark 3.1 and CLonD3D12 as well so it’s not just you. Try collecting a call stack (MSVC) or backtrace (MinGW). Help yourself with debug packages. Report the crash to Mesa3D CLC or CLonnD3D12 ICD depending on module crashing clon12compiler.dll or openclon12.dll respectively.