Windows 10: SFC some corrupt files can not be fixed Solved

Page 15 of 21 FirstFirst ... 51314151617 ... LastLast
  1.    22 Nov 2015 #141

    I can't reproduce this success story.
    1) I have 27kb opencl.dll in WinSxS and 103kb opencl.dll in SysWoW64
    2) I run sfc /scannow and got
    "Windows Resource Protection found corrupt files and successfully repaired them."
    3) Now have 27kb opencl.dll in both directories (as hardlink).
      My ComputerSystem Spec

  2.    22 Nov 2015 #142

    Ache said: View Post
    I can't reproduce this success story.
    1) I have 27kb opencl.dll in WinSxS and 103kb opencl.dll in SysWoW64
    2) I run sfc /scannow and got
    "Windows Resource Protection found corrupt files and successfully repaired them."
    3) Now have 27kb opencl.dll in both directories (as hardlink).
    Yup, that IS the SAME problem we both have.....exactly.....
      My ComputersSystem Spec

  3.    23 Nov 2015 #143

    Ratbone said: View Post
    SFC is not able to fix it I still got the same error.

    took a copy of \wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll


    Attachment 50009



    took ownership of the containing folder \wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\

    took a copy of the new opencl.dll and renamed it to opencl_New_NVidia.dll

    Attachment 50011

    Prompt path How do I find these two files
      My ComputerSystem Spec


  4. Posts : 23
    Windows 10 Professional
       23 Nov 2015 #144

    right let's clarify what my issue was.

    I was having a problem with the opencl.dll in
    C:\Windows\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll

    Microsoft was not happy with the NVidia (103 KB) version and wanted to replace it with the Microsoft version (27 KB) but failed.

    running both

    SFC /scannow

    and

    DISM.exe /Online /Cleanup-image /Restorehealth /Source:wim:K:\sources\install.wim:1 /limitaccess

    did not fix the corruption
    the version in SysWOW64 was never my issue because DISM health check did not take issue with the NVidia (103 KB) version and did NOT report any corruption. That was fine by me.

    BUT if you ignore DISM not finding any corruption and do run SFC /scannow anyway, the file in SysWOW64 will be replaced.

    I tend not to use SFC (I only use it as the "last chance saloon" for file corruption prior to re-imaging my OS). From my experience if DISM fails to fix corrupted files then SFC will also fail.

    So as long as DISM health Check does not report corruption I am happy to stop there and leave things alone.

    Now regarding the Opencl.dll in SysWOW64 and WinSxS I suspect (but I stand to be corrected) NVidia driver does not even use them and quite possibly might call them from C:\Program Files\NVIDIA Corporation\OpenCL.

    If you use a program like process hacker or System Information\Loaded modules, it appears the Opencl.dll in SysWOW64 (or anywhere else) is not actively used.

      My ComputerSystem Spec

  5.    23 Nov 2015 #145

    You need 32bit application or game which directly use OpenCL API to see this dll loaded. The driver itself does not need it.
    This demo for example: Scenic by UnRAVeL :: pouët.net
      My ComputerSystem Spec

  6.    23 Nov 2015 #146

    Ratbone said: View Post
    right let's clarify what my issue was.
    BUT if you ignore DISM not finding any corruption and do run SFC /scannow anyway, the file in SysWOW64 will be replaced.
    Well what I found out that Opencl.dll is not just replaced from this folder, but it IS REMOVED. After you run SFC this file is removed from the SysWow64 folder.
      My ComputersSystem Spec


  7. Posts : 23
    Windows 10 Professional
       23 Nov 2015 #147

    Ache said: View Post
    You need 32bit application or game which directly use OpenCL API to see this dll loaded. The driver itself does not need it.
    This demo for example: Scenic by UnRAVeL :: pouët.net
    OK I 'll give it a try and see

    did you try running the demo with both versions? any difference?
      My ComputerSystem Spec

  8.    23 Nov 2015 #148

    This is scene demo, designed to work on bare minimum of OpenCL API, so MS one works too.
      My ComputerSystem Spec


  9. Posts : 23
    Windows 10 Professional
       23 Nov 2015 #149

    Ache said: View Post
    This is scene demo, designed to work on bare minimum of OpenCL API, so MS one works too.
    yep it's being used

    Click image for larger version. 

Name:	NVOpencl.PNG 
Views:	51 
Size:	16.5 KB 
ID:	50060Click image for larger version. 

Name:	process hacker.PNG 
Views:	51 
Size:	11.5 KB 
ID:	50061

    So If you want to run the Nvidia version just replace it with the 103 KB version and do not run SFC.

    I suspect there will be a lag before Microsoft - NVidia agree on a version to be defaulted on the OS don't forget the Windows Update of the Nvidia driver is always older than the Nvidia current WHQL release.
      My ComputerSystem Spec


  10. Posts : 5
    win 10 pro x64
       25 Nov 2015 #150

    I've read the entire thread, i also have win 10 build 10586, and in sfcdetails i have this line:
    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-11-25 07:48:37, Info CSI 00003c6b [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-11-25 07:48:37, Info CSI 00003c6c [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-11-25 07:48:37, Info CSI 00003c6f [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\Windows\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted


    I have the gtx 970 with 359.00 driver and i've reinstaled this windows 3 times. The opencl.dll file has 103 kb.
    Is this normal or do i have a hardware problem?
      My ComputerSystem Spec


 
Page 15 of 21 FirstFirst ... 51314151617 ... LastLast

Related Threads
Solved SFC Corrupt Files on CBS.Log in Performance & Maintenance
Trying to run down some error codes in the admin log I decided to run the SFC scan to see if any files were corrupt and many were which were fixed except for 2 and was wondering if anyone here knows how to read and make fixes to the CBS.log, thanks
Solved SFC Corrupt Files in Performance & Maintenance
Windows search doesn't work. I ran SFC /scannow and there is corrupt files, the log is attached.
repairing corrupt files in Performance & Maintenance
After running sfc /scannow on my windows 10 installation I have been advised tthat there are corrupt files. I have viewed the log and would like to know what these messages mean. " 000010fd Warning - Overlap: Duplicate ownership for directory...
Is this possible ? Ran both programs multiple times .. Ran cc cleaner to get rid of bad registry entries . Nothing is working . Used the media creator and burnt a USB stick . Is there a way to fix corruption with this ? The drive letter for the USB...
fix corrupt files in General Support
I apparently got one or some corrupted files during last update... Computer Win 7 Pro works fine but sfc/scannow etc including install repair wont fix.... will Windows 10 install fix these?? thanks toim

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 16:10.
Find Us