It’s your decision.
Most often, the problem is not the hardware, but the drivers – see the MS OpenCL Compatibility Pack below. There is very little darktable’s developers can do there, if a broken driver causes a fatal error even when just checking for what is available. That said, there have been many enhancements.
The normal troubleshooting steps involve:
- opening a command prompt (Windows key + R, type cmd, press Enter – alternatively, select command prompt from the start menu);
- running darktable-cltest and darktable from that command prompt (enter the command
cd "\program files\darktable\bin"
, then executedarktable-cltest
anddarktable -d common -d opencl
); - checking the logs and sharing them here;
- trying launching darktable with
darktable --disable-opencl
from the command prompt (if it is an OpenCL problem, that will solve it 100% of the time); - often, uninstalling the Microsoft OpenCL Compatibility Pack helps (Darktable not opening - #6 by kofa, I can't get Darktable to work anymore - #4 by kofa).