Page 14 of 21 FirstFirst ... 41213141516 ... LastLast
  1.    22 Nov 2015 #131
    Join Date : Aug 2015
    Maine
    Posts : 36,346
    Windows10Pro 64Bit

    Quote Originally Posted by Ratbone View Post
    what do you suggest we do, re-install 359.00 and do not run DISM and FSC until it is fixed?
    Well you have a couple choices, don't do anything right now, unless you are having problems. OR run SFC / Scannow under admin command prompt and that should fix your errors. Running dism command won't do much unless you run sfc 1st.
    What I did was re-installed 359 update, and left it that way for a few days, didn't run sfc and waited to find a solution, but didn't find any. So I ran sfc this morning, and it repaired the corrupt files, removed two of the Nvidia opencl drivers, and going to leave it like this for now. My display seems to be working ok right now and I have no corrupt files in Windows. I can not find any fix for this problem right now. I still think its a Microsoft issue, but unless MS gives us a NEW update, not much else can be done. Unless someone else figures out how to solve this issue.
      My ComputersSystem Spec
  2.    22 Nov 2015 #132
    Join Date : Aug 2015
    Hampshire
    Posts : 23
    Windows 10 Professional

    Think I fixed it.


    SFC is not able to fix it I still got the same error.

    This is how i fixed it:
    I rolled back to the clean image (pre-359.00 update)
    ran windows update.
    went to the Winsxs folder
    took a copy of \wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
    kept the copy safe for future use when required.

    Click image for larger version. 

Name:	Opencl.dll master.PNG 
Views:	45 
Size:	13.7 KB 
ID:	50009

    Installed 359.00 and ran DISM health check and got the same error as before.

    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

    Click image for larger version. 

Name:	Opencl.dll NVidia.PNG 
Views:	44 
Size:	14.8 KB 
ID:	50011

    deleted it form the folder
    and replaces it with the original one.

    ran DISM and No corruption detected.

    I can't see any ill effects from the change so I think this could be a solution.

    I will run a few games just to see if I have created any issues. I suspect not. but I will report back if I do.

    Just ran a few games no difference of performance issues looks good.
    Last edited by Ratbone; 22 Nov 2015 at 18:33.
      My ComputerSystem Spec
  3.    22 Nov 2015 #133
    Join Date : Nov 2015
    Posts : 54
    Windows 10

    Then run sfc /scannnow and see corruption again (fixable by sfc, i.e. Nvidia opencl.dll will be overwritten after that in your case).
      My ComputerSystem Spec
  4.    22 Nov 2015 #134
    Join Date : Aug 2015
    Hampshire
    Posts : 23
    Windows 10 Professional

    just checked nothing's changed.... I've still got the Microsoft 27KB version in the folder no corruption. keeping the original does not affect the NVidia driver in any perceivable way.

    I do not need to run SFC I run this instead:

    DISM.exe /Online /Cleanup-image /Scanhealth

    I only check for corruption first and not attempt to fix something which is not broken.

    Deployment Image Servicing and Management tool
    Version: 10.0.10586.0


    Image Version: 10.0.10586.0

    [==========================100.0%==========================]
    No component store corruption detected.
    The operation completed successfully.

    always run a component clean-up prior to trying to restore health

    Dism.exe /online /Cleanup-Image /StartComponentCleanup

    finally if there are corrupt files then you will need to mount a Win 10 Installation disk prior to running;

    DISM.exe /Online /Cleanup-image /Restorehealth /Source:wim:%OSSource%:1 /limitaccess

    The Variable %OSSource% (I use a batch script) is the path to the install.wim: e.g. D:\sources\install.wim
    Last edited by Ratbone; 22 Nov 2015 at 18:59.
      My ComputerSystem Spec
  5.    22 Nov 2015 #135
    Join Date : Nov 2015
    Posts : 54
    Windows 10

    If WinSxS contains MS version while SysWOW64 have Nvidia version, SysWOW64 will be overwritten with MS one after sfc /scannow.
    Check sizes, since WinSxS file is hardlink after sfc, not two separate files.
      My ComputerSystem Spec
  6.    22 Nov 2015 #136
    Join Date : Aug 2015
    Maine
    Posts : 36,346
    Windows10Pro 64Bit

    Quote Originally Posted by Ratbone View Post
    just checked nothing's changed.... I've still got the Microsoft 27KB version in the folder no corruption. keeping the original does not affect the NVidia driver in any perceivable way.
    Take a look at the pic's I posted on post # 106 in here. 2nd pic is what mine looked like BEFORE running sfc /scannow. 1st pic is what it looked like AFTER running sfc
      My ComputersSystem Spec
  7.    22 Nov 2015 #137
    Join Date : Aug 2015
    Hampshire
    Posts : 23
    Windows 10 Professional

    Quote Originally Posted by OldMike65 View Post
    Take a look at the pic's I posted on post # 106 in here. 2nd pic is what mine looked like BEFORE running sfc /scannow. 1st pic is what it looked like AFTER running sfc
    I did not have any corruption in the SYSWOW64 folder I only had an issue with

    WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll

    we might have different problems. sfc /scannow could not fix my problem anyway.

    In my case the MS version was overwritten by the NVidia 350.00 driver and sfc could not fix it
      My ComputerSystem Spec
  8.    22 Nov 2015 #138
    Join Date : Nov 2015
    Posts : 54
    Windows 10

    If you have no corruption after sfc /scannow it means Nvidia opencl.dll from SysWOW64 is damaged and not 103kb size, but 27kb.
      My ComputerSystem Spec
  9.    22 Nov 2015 #139
    Join Date : Aug 2015
    Hampshire
    Posts : 23
    Windows 10 Professional

    Quote Originally Posted by Ache View Post
    If you have no corruption after sfc /scannow it means Nvidia opencl.dll from SysWOW64 is damaged and not 103kb size, but 27kb.


    Nope looks fine to me:

    Click image for larger version. 

Name:	SYSWOW64.PNG 
Views:	4 
Size:	12.2 KB 
ID:	50012
      My ComputerSystem Spec
  10.    22 Nov 2015 #140
    Join Date : Aug 2015
    Maine
    Posts : 36,346
    Windows10Pro 64Bit

    So when you run sfc /scannow it reports no errors??? If so great job...Ratbone.
      My ComputersSystem Spec

 
Page 14 of 21 FirstFirst ... 41213141516 ... LastLast


Similar Threads
Thread Forum
Solved SFC Corrupt Files on CBS.Log
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
Performance & Maintenance
Solved SFC Corrupt Files
Windows search doesn't work. I ran SFC /scannow and there is corrupt files, the log is attached.
Performance & Maintenance
repairing corrupt files
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...
Performance & Maintenance
Any way to fix corrupt files from USB stick ?
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...
General Support
fix corrupt files
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
General Support
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 21:05.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums