It was also discovered that this issue only affects Windows 10 users who have NVIDIA GPUs. What happens is that, whenever an NVIDIA GPU user installs or updates NVIDIA drivers for their graphics card, regardless of whether they do it via NVIDIA GeForce or Windows Update, the NVIDIA driver installer automatically overwrites the existing opencl.dll file from Windows with its own, corrupting it as a consequence. Until NVIDIA deploys a fix to resolve this issue, this is going to happen every time you install or update NVIDIA drivers. Fortunately, you can determine whether or not your computer’s opencl.dll file is corrupt and then repair/replace it to resolve this problem. Even though a corrupt opencl.dll file will not hinder your everyday use of your computer, it is always better to be safe than to be sorry.
How to Determine Whether or Not Your Opencl.dll File is Corrupt
There are a couple of ways you can find out if your computer’s opencl.dll file is corrupt – you can either use the System File Checker (SFC) utility or the Deployment Image Servicing and Management (DISM) utility. Both of these utilities are built-in Windows utilities that are designed to scan for, detect and try to repair integrity violations such as the corruption of system files like the opencl.dll file.
Option 1: Run an SFC Scan and Check Its Log File
To run an SFC scan and then use the results to find out whether or not your computer’s opencl.dll file is corrupt, you need to:
Option 2: Run a DISM Scan and Check Its Log File
If you would rather run a DISM scan and use its results to determine whether or not your computer is affected by this issue, you need to: Found: {l:32 EbG6RAK4saLIYu69FF29XF3DXk+hFjNQz45caiKP3Ng=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=} 2015-12-13 04:11:37, Info CSI 00004a0d [SR] Cannot repair member file [l:10]”opencl.dll” of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-12-13 04:11:37, Info CSI 00004a0e@2015/12/13:12:11:37.574 Primitive installers committed for repair 2015-12-13 04:11:37, Info CSI 00004a0f Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]”opencl.dll” : Found: {l:32 EbG6RAK4saLIYu69FF29XF3DXk+hFjNQz45caiKP3Ng=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=} 2015-12-13 04:11:37, Info CSI 00004a10 [SR] Cannot repair member file [l:10]”opencl.dll” of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, version 10.0.10586.0, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch 2015-12-13 04:11:37, Info CSI 00004a11 [SR] This component was referenced by [l:125]”Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10586.0.RemoteFX clientVM and UMTS files and regkeys” 2015-12-13 04:11:37, Info CSI 00004a12 Hashes for file member ??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]”opencl.dll” : Found: {l:32 EbG6RAK4saLIYu69FF29XF3DXk+hFjNQz45caiKP3Ng=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=} 2015-12-13 04:11:37, Info CSI 00004a13 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]”opencl.dll” : Found: {l:32 EbG6RAK4saLIYu69FF29XF3DXk+hFjNQz45caiKP3Ng=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=} 2015-12-13 04:11:37, Info CSI 00004a14 [SR] Could not reproject corrupted file [l:23 ml:24]”??\C:\WINDOWS\SysWOW64″[l:10]”opencl.dll”; source file in store is also corrupted If nothing has worked for you, you should either perform a system restore or reset Windows. Repair failed: Missing replacement payload.
How to Recover and Repair Corrupt Microsoft Word FileHow to Fix Corrupt Bootres.dll File on Windows 10?Fix: DCIMAN32.DLL is Missing or CorruptFix: Windows Resource Protection Found Corrupt Files but was Unable to Fix
