Tweet
Customer reported this problem and the solution (Thanks to Nico for this).
Symptom:
Running PerformanceTest V11 on Windows 11, there is a crash during the 3D test suite in mandelbrot benchmark test.
3rda party software, Davinci Resolve, also had problems running.
Video card was a AMD RX6600, but CPU also had integrated graphics.
Integrated graphics worked OK, if AMD GPU was removed.
Crash dump was generated when the crash happened.
Crash dump showed that the crash was due to a Access violation (code: c0000005), within the file, igdrclneo64.dll. So most likely a video card device driver bug resulting in an invalid memory being read.
Stack trace:
00000000`0014ac40 00000000`3eef4c40 igdrclneo64+0x30819
00000000`0014ac48 00000000`00000001 0x3eef4c40
00000000`0014ac50 00000001`40187ac7 0x1
00000000`0014ac58 00000001`4018a087 PerformanceTest64+0x187ac7
00000000`0014ac60 00000000`3e883150 PerformanceTest64+0x18a087
ExceptionAddress: 00007ff8eda00819 (igdrclneo64+0x0000000000030819)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000020
Attempt to read from address 0000000000000020
What is igdrclneo64:
Seems to be a binary library file (DLL) from Intel for OpenCL. OpenCL is a framework for writing programs which run on video cards.
The file gets installed with a related file, igdrcl64.dll.
Solution:
It seems to be two bugs. One AMD and one Intel.
So it seems some AMD video card drivers ship with OpenCL libraries as DLLs (as they should), but don't register the DLLs in the Windows registry.
It isn't totally clear if this was an AMD bug, of if AMD, kind of, dropped support for OpenCL. Given it seemed to work in the past I am thinking it is a bug.
To register them, open the Registry Editor (aka regedit.exe), navigate to the key HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors (if the key does not exist, create it), and create a new DWORD of Value 0. Now rename the DWORD to be the path to your amdocl64.dll. Mine is C:\Windows\System32\DriverStore\FileRepository\u03 44717.inf_amd64_d38cec78c83eee99\B343886\amdocl64. dll. Search C:\Windows\System32\ for amdocl64.dll to find the correct path on your computer.
Thanks to Bastian at Bastian.de for this registry information.
And I think there is a 2nd Intel video card driver bug. Where if a AMD video card in installed, but that card isn't advertising support for OpenCL, then the integrated card gets used for OpenCL, even though it likely has no monitor connected, which results in it crashing.
Fixing the registry entry bug means the AMD card gets used so the Intel bug never gets exposed.
Symptom:
Running PerformanceTest V11 on Windows 11, there is a crash during the 3D test suite in mandelbrot benchmark test.
3rda party software, Davinci Resolve, also had problems running.
Video card was a AMD RX6600, but CPU also had integrated graphics.
Integrated graphics worked OK, if AMD GPU was removed.
Crash dump was generated when the crash happened.
Crash dump showed that the crash was due to a Access violation (code: c0000005), within the file, igdrclneo64.dll. So most likely a video card device driver bug resulting in an invalid memory being read.
Stack trace:
00000000`0014ac40 00000000`3eef4c40 igdrclneo64+0x30819
00000000`0014ac48 00000000`00000001 0x3eef4c40
00000000`0014ac50 00000001`40187ac7 0x1
00000000`0014ac58 00000001`4018a087 PerformanceTest64+0x187ac7
00000000`0014ac60 00000000`3e883150 PerformanceTest64+0x18a087
ExceptionAddress: 00007ff8eda00819 (igdrclneo64+0x0000000000030819)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000020
Attempt to read from address 0000000000000020
What is igdrclneo64:
Seems to be a binary library file (DLL) from Intel for OpenCL. OpenCL is a framework for writing programs which run on video cards.
The file gets installed with a related file, igdrcl64.dll.
Solution:
It seems to be two bugs. One AMD and one Intel.
So it seems some AMD video card drivers ship with OpenCL libraries as DLLs (as they should), but don't register the DLLs in the Windows registry.
It isn't totally clear if this was an AMD bug, of if AMD, kind of, dropped support for OpenCL. Given it seemed to work in the past I am thinking it is a bug.
To register them, open the Registry Editor (aka regedit.exe), navigate to the key HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL\Vendors (if the key does not exist, create it), and create a new DWORD of Value 0. Now rename the DWORD to be the path to your amdocl64.dll. Mine is C:\Windows\System32\DriverStore\FileRepository\u03 44717.inf_amd64_d38cec78c83eee99\B343886\amdocl64. dll. Search C:\Windows\System32\ for amdocl64.dll to find the correct path on your computer.
Thanks to Bastian at Bastian.de for this registry information.
And I think there is a 2nd Intel video card driver bug. Where if a AMD video card in installed, but that card isn't advertising support for OpenCL, then the integrated card gets used for OpenCL, even though it likely has no monitor connected, which results in it crashing.
Fixing the registry entry bug means the AMD card gets used so the Intel bug never gets exposed.