Page 11 of 17 FirstFirst ... 910111213 ... LastLast

  1. Joined : Oct 2013
    Posts : 17,438
    64-bit Windows 10 Pro build 15014
       2015-12-24 #100

    Hello VBs,

    The hash mismatch for the opencl.dll file found by SFC is only a bug for the NIVIDIA driver. It's safe to ignore until NIVIDIA fixes it in the next driver release.
      My System SpecsSystem Spec


  2. Joined : Aug 2015
    Posts : 47
    Microsoft Windows 10 Enterprise 64-bit 10586 Multiprocessor Free
       2015-12-24 #101

    Brink said: View Post
    Hello VBs,

    The hash mismatch for the opencl.dll file found by SFC is only a bug for the NIVIDIA driver. It's safe to ignore until NIVIDIA fixes it in the next driver release.
    But he did say that his GPU is not NVIDIA but Intel, so how come he still has that problem?
      My System SpecsSystem Spec


  3. Joined : Oct 2013
    Posts : 17,438
    64-bit Windows 10 Pro build 15014
       2015-12-24 #102

    He may have an Intel graphic chip, but he may also have NVIDIA as well like mine.

    Either way, there's no need to do anything to fix it.
      My System SpecsSystem Spec


  4. Joined : Aug 2015
    Posts : 47
    Microsoft Windows 10 Enterprise 64-bit 10586 Multiprocessor Free
       2015-12-24 #103

    Oh ok, got it. Thanks for the clarification.
      My System SpecsSystem Spec


  5. Joined : Oct 2013
    Posts : 17,438
    64-bit Windows 10 Pro build 15014
       2015-12-24 #104

    Anytime.
      My System SpecsSystem Spec


  6. Joined : Oct 2014
    Posts : 83
    Windows 10 x64 Insider
       2015-12-25 #105

    Brink said: View Post
    He may have an Intel graphic chip, but he may also have NVIDIA as well like mine.

    Either way, there's no need to do anything to fix it.
    Thank you for fast response.

    PC that has error definitely doesn't have any GPU other than one integrated with Intel CPU. It's operating as headless server (mostly for running hyper-v and storage spaces), so no other graphics card is necessary (it's not laptop with hybrid graphics). Scan was performed in RDP connection from PC with nVidia card, but strangely enough that PC with nvidia card shows no errors when running sfc /scannow. Does running sfc /scannow when connected in RDP has anything to do with errors?
      My System SpecsSystem Spec


  7. Joined : Oct 2013
    Posts : 17,438
    64-bit Windows 10 Pro build 15014
       2015-12-25 #106

    It shouldn't. The main issue is a has mismatch with the opencl.dll file.

    This was an issue recently from NIVIDIA, but was fixed in the current driver release. Maybe Intel has the issue now?

    Hopefully the latest Intel graphics driver or next will sort it.
      My System SpecsSystem Spec


  8. Joined : Aug 2015
    Maine
    Posts : 20,966
    Windows10Pro 64Bit on 2 DeskTop Computers
       2015-12-25 #107

    Brink said: View Post
    It shouldn't. The main issue is a has mismatch with the opencl.dll file.

    This was an issue recently from NIVIDIA, but was fixed in the current driver release. Maybe Intel has the issue now?

    Hopefully the latest Intel graphics driver or next will sort it.
    Really the opencl.dll issue was fixed by Nvidia in the latest release?? If you run sfc /verify its still shows the same error. I used that command 1st, because I didn't want Windows to remove 1 of the opencl.dll files. like it would if I ran sfc / scannow are you sure its fixed Shawn???
      My System SpecsSystem Spec


  9. Joined : Aug 2015
    Maine
    Posts : 20,966
    Windows10Pro 64Bit on 2 DeskTop Computers
       2015-12-25 #108

    I did see where in one of the new releases of the Insider builds it WAS fixed, by Microsoft, but I don't run any of the Insider builds.

    Update: After I read where one of the folks who are in the Insider program, reported this issue was fixed in one of the new Insider releases, It made me VERY happy knowing that at some point MS will release a future update that will fix this issue.
    Last edited by OldMike65; 2015-12-25 at 11:19.
      My System SpecsSystem Spec


  10. Joined : Oct 2013
    Posts : 17,438
    64-bit Windows 10 Pro build 15014
       2015-12-25 #109

    Hey Mike,

    I just ran SFC /SCANNOW as a test using the latest 361.43 NIVIDIA driver, and SFC came back with no issues. Looks like it's sorted now.
      My System SpecsSystem Spec


 
Page 11 of 17 FirstFirst ... 910111213 ... LastLast


Similar Threads
Tutorial Category
Elevated Command Prompt - Open in Windows 10
How to Open an Elevated Command Prompt in Windows 10 A command prompt is an entry point for typing computer commands in the Command Prompt window. By typing commands in an elevated command prompt, you can perform tasks that require...
Tutorials
Show Us Your Command Centre
This is my study. Also my office when I am working. I call it Sanctuary. 327 328
Chillout Room
Command Prompt at Boot - Open in Windows 10
How to Open a Command Prompt at Boot in Windows 10 A command prompt is an entry point for typing computer commands in the Command Prompt window. By typing commands at the command prompt, you can perform tasks on your computer without using the...
Tutorials
Command Prompt - Open in Windows 10
How to Open a Command Prompt in Windows 10 A command prompt is an entry point for typing computer commands in the Command Prompt window. By typing commands at the command prompt, you can perform tasks on your computer without using the Windows...
Tutorials
Command Prompt gets welcome improvements in Windows 10
Read more...
Windows 10 News
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 06:56.
Find Us
Twitter Facebook Google+



Windows 10 Forums