- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
System Setup Information:
-----------------------------------------
System Used: GIGABYTE Z170N-WIFI
CPU SKU: Intel Core i3-7100 (Kaby Lake-S, S0)
GPU SKU: Intel HD Graphics 630 (Kaby Lake-S GT2) - Integrated Graphics Controller [GIGABYTE]
Processor Line: 7th Generation Intel Core i3 Processor
System BIOS Version: "American Megatrends Inc. F20i , 03/09/2018 12:00 AM"
CMOS settings: -
Graphics Driver Version: 25.20.100.6519
GOP/VBIOS Version: 1046.0
Operating System: Windows 10
OS Version: Pro (10.0.17763)
API: OpenCL
Occurs on non-Intel GPUs?: -
Steps to Reproduce:
-------------------------------
Try to run OpenCL app on i3-7100 (CPU and IGP).
Expected Results:
-------------------------------
To be able to select Intel OpenCL platform and to choose between CPU OpenCL device and GPU (Intel integrated gfx) device.
Actual Results:
-------------------------------
No Intel OpenCL platform found (no additional discrete GPU installed in the system).
Additional Information:
-------------------------------
It seems that Display Driver Uninstaller (DDU) messed up the ICD Loader, after adding registry references, the Intel OpenCL plaform is back, but only OCL CPU device.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Installed the latest driver - 26.20.100.6709. Before the install, I run DDU, and it seems that DDU removes the ICD registry references because after installing the driver no OpenCL platform was available. The Intel_OpenCL_ICD.dll is now resides in a slightly different location and adding the recommended REG_DWORD objects in the registry crash OpenCL applications on startup.
My ICD location: C:\windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_...\Intel_OpenCL_ICD(32/64).dll
Tutorial ICD location: C:\windows\System32\DriverStore\FileRepository\ig<path_on_your_system>\IntelOpenCL(32/64).dll
Any help would be appreciated!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi TiborN,
Addressing this issue here where more OpenCL stakeholders have more visibility.
Thanks,
-MichaelC

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page