LLVM Error while opening igdclbif.bin when running clBuildProgram

LLVM Error while opening igdclbif.bin when running clBuildProgram

Hi all,

Recently I bought a new laptop.

I get the following error after starting clBuildProgram when running any of OpenCL code in GPU.

It's OK in CPU.

LLVM ERROR: Unknown error while opening the igdclbif.bin

clGetPlatformIDs, clGetDeviceIDs, clCreateContext, clCreateProgramWithSource all work well.

I assume the complicated kernel code is cause and change it to the following simply

void a() {

}

But the problem is not disappeared.

I think the graphics driver has a problem.

When I try to update a graphics driver, I can see the message that the most recent driver available is already installed.

Does anyone have any idea to solve it?

Thanks all.

<Specification>

OS : Windows 10 64bit

OS Version : 1607

Model : LG 22V270-BZ10K

CPU : Celeron N3450 

GPU : HD Graphics 500

Driver Vesion : 21.20.16.4494

<Log>

clBuildProgram start
LLVM ERROR: Unknown error while opening the igdclbif.bin
0x7742CFD6 (0x00000000 0x00EFF4AC 0x62405580 0x62405580), RtlDllShutdownInProgress() + 0x76 bytes(s)
0x7744A38A (0x00000039 0x00EFF440 0x623DD27F 0x62405580), RtlEnterCriticalSection() + 0x17A bytes(s)
0x7744A259 (0x62405580 0x00EFF4D4 0x623E0C2D 0x03260000), RtlEnterCriticalSection() + 0x49 bytes(s)
0x623DD27F (0x00EFF600 0x05CEEE30 0x00000000 0x077A7E98), Register() + 0xB9A8 bytes(s)
0x623D9C33 (0x00EFF4D4 0x00000001 0x623F8BE8 0x00B607D0), Register() + 0x835C bytes(s)
0x623D9C6A (0x623F8BE8 0x00000001 0x00EFF6C0 0x05CEEE30), Register() + 0x8393 bytes(s)
0x623D552F (0x00EFF600 0x077BE768 0x00EFF6C0 0x077BE8C8), Register() + 0x3C58 bytes(s)
0x623D271B (0x00EFF6C0 0x077BE8C8 0x00EFF7A8 0x05CEEE30), Register() + 0xE44 bytes(s)
0x623D2B1E (0x07235FB0 0x0000001C 0x077BE768 0x077BE8C8), Register() + 0x1247 bytes(s)
0x623D30AD (0x00EFF7A8 0x077BE8E8 0x077BE8E8 0x00000000), Register() + 0x17D6 bytes(s)
0x624BAF11 (0x00EFF7A8 0x077BE8E8 0x00040001 0x00000000), clGetCLObjectInfoINTEL() + 0x22771 bytes(s)
0x624B2859 (0xFFFFFFF5 0x07231BC0 0x00080001 0x00EFF858), clGetCLObjectInfoINTEL() + 0x1A0B9 bytes(s)
0x624B15BE (0x07231C68 0x776F76A0 0x05BFEE48 0x00000000), clGetCLObjectInfoINTEL() + 0x18E1E bytes(s)
0x624A3B41 (0x072E67E8 0x00000001 0x00EFF8F0 0x00000000), clGetCLObjectInfoINTEL() + 0xB3A1 bytes(s)
0x62440854 (0x072E67E8 0x00000001 0x00EFF8F0 0x00000000)
0x6249417E (0x072E67E8 0x00000001 0x00EFF8F0 0x00000000), clBuildProgram() + 0x7E bytes(s)
0x0028C8F9 (0x00DC2000 0x76498630 0x41A31DB1 0x00EFFB6C), __tmainCRTStartup() + 0xFD bytes(s), f:\dd\vctools\crt\crtw32\dllstuff\crtexe.c, line 626 + 0x17 byte(s)
0x76498654 (0x00DC2000 0x324F59D4 0x00000000 0x00000000), BaseThreadInitThunk() + 0x24 bytes(s)
0x77464A77 (0xFFFFFFFF 0x77489EE5 0x00000000 0x00000000), RtlGetAppContainerNamedObjectPath() + 0x137 bytes(s)
0x77464A47 (0x0028C961 0x00DC2000 0x00000000 0x00000000), RtlGetAppContainerNamedObjectPath() + 0x107 bytes(s)
0x77464A47 (0x0028C961 0x00DC2000 0x00000000 0x00000000), RtlGetAppContainerNamedObjectPath() + 0x107 bytes(s)

 

2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

This sounds like a driver install problem.  Could you try completely uninstalling your current driver - check the box to "delete the driver software for this device" - then reinstalling?

I suspect that will fix the problem, but if it doesn't, can you check that you have an igdclbif.bin installed on your machine?  It'll probably be in your Windows/System32 directory, but if you don't see it there, check that it didn't get installed somewhere else.

Hi, Ben Ashbaugh

Reinstalling can't fix the problem and there is a igdclbif.bin in Windows/System32 directory.

I thought the driver problem and updated it.

Version was changed 21.20.16.4494 to 22.20.16.4718, it's fixed.

I could see below in new driver version.

igdclbif.bin was removed in system32 directory and it was included in ki123253.inf_amd64_c98021945dc61ed.

I want to know why the problem occurs and what has been changed to fix it and there is a solution to fix it without updating driver.

Thank you.

 

Leave a Comment

Please sign in to add a comment. Not a member? Join today