Page 1 of 2 12 LastLast
  1.    12 Feb 2016 #1
    Join Date : Nov 2015
    Posts : 10
    windows 10 ent x64

    SFC /SCANNOW shows opencl.dll bad


    My box is windows 10 pro x64 and I tried to "SFC /SCANNOW", and got "opencl.dll bad" message as follows.

    2016-02-12 11:46:45, Info CSI 00004f51 [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
    2016-02-12 11:46:45, Info CSI 00004f5b [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
    2016-02-12 11:46:45, Info CSI 00004f5c [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"
    2016-02-12 11:46:45, Info CSI 00004f5f [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
    2016-02-12 11:49:06, Info CSI 00006527 [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
    2016-02-12 11:49:06, Info CSI 0000652a [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
    2016-02-12 11:49:06, Info CSI 0000652b [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"
    2016-02-12 11:49:06, Info CSI 0000652e [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted

    Please let me know how to resolve this.

    Thanks in advance.
      My ComputerSystem Spec
  2.    12 Feb 2016 #2
    Join Date : May 2015
    Central IL
    Posts : 3,971
    Mac OS Sierra

    Have you tried searching for solutions yet, or just wanting us to walk you through the easy steps to fix this issue. Your problem is not with Windows 10, it is with your Video Chipset driver.
      My ComputerSystem Spec
  3.    13 Feb 2016 #3
    Join Date : Feb 2015
    Posts : 1
    Dual Boot 10 Pro v1607 10 Pro rs2 build 14971

    Opencl.dll hash mismatch is a known problem with Nvidia drivers. See the SFC command tutorial here SFC Command - Run in Windows 10 - Page 12 - Windows 10 Forums . The advice has been to ignore it when running the SFC command.
      My ComputerSystem Spec
  4.    13 Feb 2016 #4
    Join Date : Nov 2015
    Posts : 10
    windows 10 ent x64
    Thread Starter

    /bro67
    I've googled and found this link, but not solved.
    SFC SCANNOW report opencl.dll bad - Microsoft Community

    JohnC/

    Yhakns a lot for your kind comment. I'll try the thread you linked.
      My ComputerSystem Spec
  5.    13 Feb 2016 #5
    Join Date : May 2015
    Central IL
    Posts : 3,971
    Mac OS Sierra

    Quote Originally Posted by windstory View Post
    /bro67
    I've googled and found this link, but not solved.
    SFC SCANNOW report opencl.dll bad - Microsoft Community

    JohnC/

    Yhakns a lot for your kind comment. I'll try the thread you linked.
    Again your problem is not with SFC or Windows. It is with OpenCL.dll which is caused by the Video Drivers. Try using the correct search, instead of the command that gave you the error.
      My ComputerSystem Spec
  6.    20 Feb 2016 #6
    Join Date : Aug 2015
    Maine
    Posts : 36,191
    Windows10Pro 64Bit

    Just a little NEW information on the Opencl.dll issue's After downloading the latest drivers from Nvidia few days ago, Version 361.91
    Then running sfc /scannow after installing the latest drivers, for the 1st time in the last 4 months, sfc found NO ERRORS!! Then I went and looked at my Opencl.dll drivers and location of them. Nvidia has changed how they install and where they place their drivers in this latest update. They do not replace the MS Opencl drivers like they did in the past with their updates, so looks like Nvidia has fixed the problem with Opencl errors .... at least for THIS latest update. I was VERY surprised to see this, as I kept thinking it was a problem from MS, not Nvidia.

    Just thought I would post my results on the Opencl.dll errors that lots of us USED to get ... Until THIS new update.
      My ComputersSystem Spec
  7.    20 Feb 2016 #7
    Join Date : May 2015
    Central IL
    Posts : 3,971
    Mac OS Sierra

    Everyone has known about the opencl-dll problem since 7, because it has been mainly with NVidia. When 10 came out, NVidia was late on putting the latest drivers in Microsoft's repository, so Microsoft used the drivers from Windows 8.1, until NVidia released updated the drivers aprox. 2 weeks after 10 was released out to the wild in Aug.
      My ComputerSystem Spec
  8.    21 Feb 2016 #8
    Join Date : Aug 2015
    Maine
    Posts : 36,191
    Windows10Pro 64Bit

    Quote Originally Posted by bro67 View Post
    Everyone has known about the opencl-dll problem since 7, because it has been mainly with NVidia. When 10 came out, NVidia was late on putting the latest drivers in Microsoft's repository, so Microsoft used the drivers from Windows 8.1, until NVidia released updated the drivers aprox. 2 weeks after 10 was released out to the wild in Aug.
    That's not correct as Windows 7 did not have issues with Nvidia drivers. Windows 10 the early version 10240 also had no problems with Nvidia drivers. I ran both versions on 2 computers, never had problems with any Nvidia drivers, until the release of Windows 1511, then lots of people starting have problems with any Nvidia driver, or updates. Until this latest release of 361.91 just recently.
      My ComputersSystem Spec
  9.    21 Feb 2016 #9
    Join Date : May 2015
    Central IL
    Posts : 3,971
    Mac OS Sierra

    Quote Originally Posted by OldMike65 View Post
    That's not correct as Windows 7 did not have issues with Nvidia drivers. Windows 10 the early version 10240 also had no problems with Nvidia drivers. I ran both versions on 2 computers, never had problems with any Nvidia drivers, until the release of Windows 1511, then lots of people starting have problems with any Nvidia driver, or updates. Until this latest release of 361.91 just recently.
    Not to argue, but it is correct. You will find a lot of Linux posts about the NVidia driver issues, same as some people were having issues with 7. It was more of a smaller percentage then what happened with 10.
      My ComputerSystem Spec
  10.    22 Feb 2016 #10
    Join Date : Aug 2015
    Maine
    Posts : 36,191
    Windows10Pro 64Bit

    Quote Originally Posted by bro67 View Post
    Not to argue, but it is correct. You will find a lot of Linux posts about the NVidia driver issues, same as some people were having issues with 7. It was more of a smaller percentage then what happened with 10.
    Yes I did hear of Linux having issues with Nvidia cards, which was a Linux issue, not Nvidia's . Also heard Linux fixed this issue a while back......not just recently. But this being more of a Windows forum then Linux, we never discussed it as much in here. Windows 7 never had any issue with Nvidia drivers, as I ran it for a long time on both computers. Actually still got a 3rd computer with Windows 7 still installed, but I don't use that one anymore, its stored and offline. All my versions of Windows 7 was either Pro or Ultimate versions.
      My ComputersSystem Spec

 
Page 1 of 2 12 LastLast


Similar Threads
Thread Forum
Solved SFC Corrupt Issue Regarding OpenCl.dll
Hi guys. I am hoping you can help me as i don't wish to do a full reinstall. Spoke to Microsoft who couldn't help. I have looked through the excellent tutorial posted on here with regards to SFC issues but i'm unsure if i am doing something...
Performance & Maintenance
Solved Opencl.dll on sfc /scannow
hey guys long time lurker here, usually i find solutions on my problem but this time around, i have no idea what to do! Short story: ran sfc /scannow and got the message "found corrupt files but cannot repair," specifically regarding Opencl.dll....
General Support
Solved Failed to Initialize OpenCL
First error in a program after the Windows 10 Fall Upgrade... I'm using Adobe After Effects CC 2015. ...
Software and Apps
Solved Running sfc /scannow shows that there are errors
Things are not going well for me. Multiple system issues are being reported in the Reliability Monitor although these are not obvious while using the OS. One of the things I have now tried is sfc /scannow from a command prompt in both normal and...
Performance & Maintenance
Solved Missing OpenCL.dll
Hi All, So, I upgraded to Windows 10 a day back using the media creation tool, and the install went fine. After I restarted the PC for the first time, I got an error saying that OpenCL.dll is missing. I searched online forums and it said that it...
Drivers and Hardware
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:07.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums