Community
cancel
Showing results for 
Search instead for 
Did you mean: 
MSchm21
Valued Contributor I
1,002 Views

HD Graphics 630 - No OpenCL in newest drivers

There is no OpenCL support detected in all the latest drivers, to be specific: 21.20.16.4565, 21.20.16.4574, 21.20.16.4589

Build 4589 is the latest from Microsoft, still no support. Here is a screen from GPUz: http://fs5.directupload.net/images/170201/ocdbk96w.png

The latest driver with OpenCL support is 21.20.16.4551: http://fs5.directupload.net/images/170201/6kz5of6u.png

What is wrong?

0 Kudos
12 Replies
Jeffrey_M_Intel1
Employee
1,002 Views

The team is looking into this now. The issue may be similar to this post:

https://software.intel.com/en-us/forums/opencl/topic/710194

The newest build #s available at downloadcenter.intel.com are 4542 (latest) and 4552 (beta).  The  driver version you have may be from your OEM.

 

 

MSchm21
Valued Contributor I
1,002 Views

Intel doesn't support my HD 630 with their drivers at downloadcenter. The drivers I have been using are from the Microsoft update catalog therefore. They are generic. I don't use OEM drivers.

MSchm21
Valued Contributor I
1,002 Views

Control panel reports OpenCL version 0.0: http://fs5.directupload.net/images/170202/bppfcqoi.png

There is no driver support from Intel itself which is bizarre but a different topic. All the latest drivers I did try were generic, it should work. I never had such issues with these.

MSchm21
Valued Contributor I
1,002 Views

I've tried a dozen of drivers, including old drivers, only one driver gives me OpenCL support for my HD 630, as mentioned 21.20.16.4551. Previously with my HD 530 on the same system all these drivers worked fine. And by the way Vulkan support is effected as well from this issue. Drivers that should give me Vulkan support doesn't give me Vulkan.

Jeffrey_M_Intel1
Employee
1,002 Views

Thanks for reporting the results of your search.  We are investigating.  

MSchm21
Valued Contributor I
1,002 Views

Interesting news on this matter. I've tried 21.20.16.4590 on Friday and Saturday which didn't gave me OpenCL and Vulkan support either. Today I looked into GPUz and suddenly OpenCL support is back. Also Vulkan support is back. I didn't change anything on my side but there were some silent updates from Microsoft which are Intel related. In particular Management Engine version looks interesting, it might be the culprit. Management engine version previously on my system was 11.6.0.1032, that's the newest from Asus for my board on their support page. The silent update from Microsoft installed version 11.6.0.1039. Here is a screen: http://fs5.directupload.net/images/170205/yhxzc3ab.png

I'm going to install driver 21.20.16.4589 to see if OpenCL support remain in effect.

MSchm21
Valued Contributor I
1,002 Views

OpenCL remain in effect with 21.20.16.4589: http://fs5.directupload.net/images/170205/fgktgwvx.png

So it possibly was somehow related to the Management Engine.

MSchm21
Valued Contributor I
1,002 Views

Something is unreliable, I lost OpenCL and Vulkan support once again after I tested some drivers back and forth. Only 4551 isn't affected.

MSchm21
Valued Contributor I
1,002 Views

I removed all Intel display driver related stuff with display driver uninstaller and finally I have Vulkan and OpenCL support with the newest 21.20.16.4590 driver.

MSchm21
Valued Contributor I
1,002 Views

Jeffrey_M_Intel1
Employee
1,002 Views

Thank you for the additional details.  Do I understand correctly that you have found a driver that works?

We appreciate your help with reporting the problem.  As we've traced this so far it looks like the cause of the glitch has already been taken care of.  The latest driver updates (after 4589) should be OK but we are continuing to investigate.

MSchm21
Valued Contributor I
1,002 Views

All driver are working for me now after I did use DDU and then a clean install of the driver, so there may be was something corrupted that prevented to properly install/detect OpenCL and Vulkan. Before I did use DDU the only driver with OpenCL support was Build 4551. Build 4590 wasn't OK either and in my link I posted there is another one who encountered this issue with Build 4590. We can also see that not all systems are affected.