What is the output of darktable-cltest?
I run that in which console ? cmd does not know that command.
It is in darktable\bin.
hehe Linux reflex 
I’m really newb on Windows.
[defaults] setting very high quality defaults
0.062488 [opencl_init] opencl related configuration options:
0.062488 [opencl_init]
0.062488 [opencl_init] opencl: 1
0.062488 [opencl_init] opencl_library: ''
0.062488 [opencl_init] opencl_memory_requirement: 768
0.078109 [opencl_init] opencl_memory_headroom: 300
0.078109 [opencl_init] opencl_device_priority: '*/!0,*/*/*'
0.078109 [opencl_init] opencl_mandatory_timeout: 200
0.078109 [opencl_init] opencl_size_roundup: 16
0.078109 [opencl_init] opencl_async_pixelpipe: 0
0.078109 [opencl_init] opencl_synch_cache: 0
0.078109 [opencl_init] opencl_number_event_handles: 25
0.078109 [opencl_init] opencl_micro_nap: 1000
0.078109 [opencl_init] opencl_use_pinned_memory: 0
0.078109 [opencl_init] opencl_use_cpu_devices: 0
0.078109 [opencl_init] opencl_avoid_atomics: 0
0.093730 [opencl_init]
0.093730 [opencl_init] found opencl runtime library 'OpenCL.dll'
0.093730 [opencl_init] opencl library 'OpenCL.dll' found on your system and loaded
Then it crashes with the same backtrace.
It is an OpenCL crash upon initialization inside IntelOpenCL64.dll and igdrclneo64.dll, so the problem is in the Intel OpenLC implementation.
You have mentioned that you have an Nvidia Quadro M2200 in the machine: IMHO you should install the Nvidia driver, and that is providing OpenCL and should work.
Is there any specific reason why you installed this Intel OpenCL?
My machine is a Thinkpad mobile workstation and the drivers are in factory state. I never bothered to inspect them in Windows actually, I use it only for CAD softwares and Photoshop. Nvidia drivers are installed. I do everything else on Debian. If it’s a problem of driver on my side, I will let it rest then. I develop and use dt on Linux 
FWIW: on linux the intel opencl drivers are actually filtered out and you cant enable opencl with them. something similar is missing for windows I guess.
1 Like
src/common/opencl_drivers_blacklist.h
I see there only two blacklistd: beignet and pocl. Are you sure the Intel OpenCL is also blacklisted?
If I remember correctly the beignet driver is the Intel driver (at least under Linux)
yes, beignet is intel but on linux probably not on windows.
There is a new Intel OpenCL called Neo : https://software.intel.com/en-us/forums/opencl/topic/758168
That’s what crashes on my system:
00007FFB16320819 000000000061E638 00007FFB164DCD00 0000000000000001 igdrclneo64.dll!clGetKernelSubGroupInfoKHR
00007FFB1630C4A7 00007FFB1BE13277 0000000000000001 0000000000000001 igdrclneo64.dll!0x7ffb0001c4a7
00007FFB1635CEDA 0000C5E2DD34F521 0000000000000000 0000000000000000 igdrclneo64.dll!clGetKernelSubGroupInfoKHR
00007FFB1630D10E 0000000006C93250 0000000000000000 0000000000000000 igdrclneo64.dll!clGetPlatformIDs
00007FFB163141E9 0000000006C93270 00007FFB16313C80 0000000006C93250 igdrclneo64.dll!clEnqueueTask
00007FFB1BE132B5 00007FFB26784C08 0000000000000000 0000000000000000 IntelOpenCL64.dll!clEnqueueWriteBufferRect
00007FFB1BDDC85B 00007FFB1BDD48A9 00007FFB2679AEB0 00007FFB1BDD0000 IntelOpenCL64.dll!clEnqueueWriteBufferRect
“this driver replaces both the SRB5 closed-source driver (aka Classic) and the Beignet open-source driver.”
It looks to me which also deserves the blacklisting: how can an OpenCL call result in a crash in a driver?
1 Like
Black magic ? I have no idea…
Non compatible API?
It seems darktable for Windows doesn’t support network shares? Even when I map them to Windows drive letters, darktable still doesn’t see them.
Could someone please tell me what the Windows equivalent of the ~/.local/share/lensfun directory is for darktable purposes (if there is one)? Thanks.
darktable\share\lensfun
2 Likes