SFC some corrupt files can not be fixed

Page 17 of 21 FirstFirst ... 71516171819 ... LastLast

  1. Posts : 68
    Microsoft Windows 10 Enterprise 64-bit 10586 Multiprocessor Free
       #161

    Is this opencl.dll issue with NVIDIA and Microsoft already fixed? Are Microsoft and NVIDIA even aware?
      My Computer


  2. Posts : 134,237
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #162

    kevindd992002 said:
    Is this opencl.dll issue with NVIDIA and Microsoft already fixed? Are Microsoft and NVIDIA even aware?
    Yes Nvidia knows for sure, if they read their own forums. 1 or 2 people here have reported it to MS, how much good that will do is anybody's guess.
      My Computers


  3. Posts : 68
    Microsoft Windows 10 Enterprise 64-bit 10586 Multiprocessor Free
       #163

    Just as I thought. But using the opencl.dll from NVIDIA doesn't really do any harm, does it?
      My Computer


  4. Posts : 134,237
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #164

    kevindd992002 said:
    Just as I thought. But using the opencl.dll from NVIDIA doesn't really do any harm, does it?
    That is the correct one to use. You would have to go back 3 or 4 pages on here to understand what is happening.
      My Computers


  5. Posts : 384
    Window 10
       #165

    kevindd992002 said:
    Is this opencl.dll issue with NVIDIA and Microsoft already fixed? Are Microsoft and NVIDIA even aware?
    I'm not sure it's just with NVIDIA. My Surface Pro 4 (Intel HD graphics) throws the same errors for the opencl.dll file.

    Interestingly, my desktop machine with an NVidia card does not.
      My Computer


  6. Posts : 134,237
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #166

    PJLLB said:
    I'm not sure it's just with NVIDIA. My Surface Pro 4 (Intel HD graphics) throws the same errors for the opencl.dll file.

    Interestingly, my desktop machine with an NVidia card does not.
    That does make sense because I think its mainly a Microsoft problem. Not AMD, Nvidia, or in your case Intel. How long it is going to take Microsoft to admit this and fix their problem thou, could be a while. Hopefully the Graphic card companies will contact Microsoft and report these problems.
      My Computers


  7. Posts : 134,237
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #167

    Just to add another idea on this issue, I have turned OFF, Device Driver Updates, so this is suppose to stop MS from updating any of our drivers. Don't know how well this will really work, but I thought its worth a shot.
      My Computers


  8. Posts : 54
    Windows 10
       #168

    Device Driver Updates have nothing common with this bug. MS install (and not update yet) x86 part of their Remote FX driver (without x64 part). MS do it in any case, independently of Device Driver Updates on/off.
      My Computer


  9. Posts : 134,237
    Windows 11 Pro (x64) 23H2 Build 22631.3296
       #169

    Ache said:
    Device Driver Updates have nothing common with this bug. MS install (and not update yet) x86 part of their Remote FX driver (without x64 part). MS do it in any case, independently of Device Driver Updates on/off.
    Ok well that's ok, MS still replaced 3 of my device drivers, that I had the factory drivers loaded with. And replaced them with MS drivers. I had to re-install 3 different device drivers after MS messed them up!
      My Computers


  10. Posts : 459
    Windows 8&10
       #170

    I am not sure why folks are having problems with this. I have not seen it so far and am running the 353.82 version of the Nvidia drivers. My install is an updated 10240 version which hasn't been used much.

    Since the opencl.dll file seems to be part of the WDDM driver which update apart from the Nvidia drivers, has anyone seen one of those drivers being installed? Nvidia is using an nvopencl.dll file on my system although I cannot be sure it doesn't interact with the other one.

    We have seen SFC errors like this before. When Microsoft was changing the servers around we have several files which showed the problem, but one update cleared that up. I am still seeing Metadata errors and DeviceSetup warning messages in Event Viewer.

    Has anyone with a problematic system checked the DISM log after trying that fix. Maybe it would yield more info about the situation. I know there are some listings in this thread so I will go back and check if any of them come from the dism.log file.
      My Computer


 

  Related Discussions
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 20:58.
Find Us




Windows 10 Forums