Page 2 of 2 FirstFirst 12
  1.    26 Nov 2015 #11
    Join Date : Nov 2015
    Posts : 11
    windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.
    As expected, I got the following message:
    Windows Resource Protection found corrupt files but was unable to fix some
    of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
    example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
    supported in offline servicing scenarios.
    I've uploaded the file to my G Drive, please check it here. Also to add, restarting time was still around 10-15 minutes.
    Thanks again.
      My ComputerSystem Spec
  2.    26 Nov 2015 #12
    Join Date : Jun 2015
    Posts : 12,673
    Windows 10 Pro

    The file opencl.dll and the source are corrupted.
    Code:
    2015-11-26 17:06:35, Info                  CSI    000058b1 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-11-26 17:06:35, Info                  CSI    000058b2 [SR] This component was referenced by [l:258{129}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.RemoteFX clientVM and UMTS files and regkeys"
    2015-11-26 17:06:35, Info                  CSI    000058b3 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
      Found: {l:32 b:49za8C5TRgSaDSUdC64s2a49uEKeT5hcOPrm/k5k1Lk=} Expected: {l:32 b:3nQy34XEqrcTm+le3PyhNMbyrGuxiT2D5+L7RJQKKgM=}
    2015-11-26 17:06:35, Info                  CSI    000058b4 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10240.16384_none_b928dea146e73395\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
      Found: {l:32 b:49za8C5TRgSaDSUdC64s2a49uEKeT5hcOPrm/k5k1Lk=} Expected: {l:32 b:3nQy34XEqrcTm+le3PyhNMbyrGuxiT2D5+L7RJQKKgM=}
    2015-11-26 17:06:35, Info                  CSI    000058b5 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted
    Please try following command in admin command prompt
    Code:
    DISM /Online /Cleanup-Image /RestoreHealth
    If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial
      My ComputersSystem Spec
  3.    27 Nov 2015 #13
    Join Date : Nov 2015
    Posts : 11
    windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    The file opencl.dll and the source are corrupted.
    Code:
    2015-11-26 17:06:35, Info                  CSI    000058b1 [SR] Cannot repair member file [l:20{10}]"opencl.dll" of microsoft-windows-RemoteFX-clientVM-RemoteFXWDDMDriver-WOW64-C, Version = 10.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store, hash mismatch
    2015-11-26 17:06:35, Info                  CSI    000058b2 [SR] This component was referenced by [l:258{129}]"Microsoft-Windows-RemoteFX-VM-Setup-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.RemoteFX clientVM and UMTS files and regkeys"
    2015-11-26 17:06:35, Info                  CSI    000058b3 Hashes for file member \??\C:\Windows\SysWOW64\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
      Found: {l:32 b:49za8C5TRgSaDSUdC64s2a49uEKeT5hcOPrm/k5k1Lk=} Expected: {l:32 b:3nQy34XEqrcTm+le3PyhNMbyrGuxiT2D5+L7RJQKKgM=}
    2015-11-26 17:06:35, Info                  CSI    000058b4 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10240.16384_none_b928dea146e73395\opencl.dll do not match actual file [l:20{10}]"opencl.dll" :
      Found: {l:32 b:49za8C5TRgSaDSUdC64s2a49uEKeT5hcOPrm/k5k1Lk=} Expected: {l:32 b:3nQy34XEqrcTm+le3PyhNMbyrGuxiT2D5+L7RJQKKgM=}
    2015-11-26 17:06:35, Info                  CSI    000058b5 [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:20{10}]"opencl.dll"; source file in store is also corrupted
    Please try following command in admin command prompt
    Code:
    DISM /Online /Cleanup-Image /RestoreHealth
    If there are problems with RestoreHealth, please follow step 6 or 7 (depending on the file you have from the download) from the tutorial DISM - Repair Windows 10 Image - Tutorial
    Tried 'DISM' and it failed for the first time; however, fixed it and the restoration was successful. I wonder, is there any way to make sure that the "OpenCL.dll" is fixed/or the other errors, if any?
      My ComputerSystem Spec
  4.    27 Nov 2015 #14
    Join Date : Jun 2015
    Posts : 12,673
    Windows 10 Pro

    DISM is used to restore SFC.

    Please run sfc/scannow in admin command prompt, reboot and run sfc/scannow again.
      My ComputersSystem Spec
  5.    27 Nov 2015 #15
    Join Date : Nov 2015
    Posts : 11
    windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    DISM is used to restore SFC.

    Please run sfc/scannow in admin command prompt, reboot and run sfc/scannow again.
    Gotcha! On it
      My ComputerSystem Spec
  6.    30 Nov 2015 #16
    Join Date : Nov 2015
    Posts : 11
    windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    DISM is used to restore SFC.

    Please run sfc/scannow in admin command prompt, reboot and run sfc/scannow again.
    Ran the scan multiple times over a period of 2 days and always it said "Windows Resource Protection did not find any integrity violations."

    So I hope that means everything is perfect? However, I've done nothing related to opencl.dll personally, is there anything I need to worry about? And BTW, the restart time is still around 4-5 minutes.
      My ComputerSystem Spec
  7.    30 Nov 2015 #17
    Join Date : Jun 2015
    Posts : 12,673
    Windows 10 Pro

    DISM restored SFC, SFC restored the opencl.dll corruption.
    You don't have to do anything more

    To find out what is taking so long, we need a log of what is happening

    • Search "msconfig" (without quotes) and press enter,
    • go to the boot tab
    • enable 'boot log'
    • click ok > apply
    • reboot when asked

    The boot log file should be located at {windows partition}\Windows\, but I'm not sure exactly what it is called.
      My ComputersSystem Spec
  8.    03 Dec 2015 #18
    Join Date : Nov 2015
    Posts : 11
    windows 10
    Thread Starter

    Quote Originally Posted by axe0 View Post
    DISM restored SFC, SFC restored the opencl.dll corruption.
    You don't have to do anything more

    To find out what is taking so long, we need a log of what is happening

    • Search "msconfig" (without quotes) and press enter,
    • go to the boot tab
    • enable 'boot log'
    • click ok > apply
    • reboot when asked

    The boot log file should be located at {windows partition}\Windows\, but I'm not sure exactly what it is called.
    I apologize for a late reply. Anyway, I enabled Boot log and I'm attaching the same here. Let me know.
      My ComputerSystem Spec
  9.    03 Dec 2015 #19
    Join Date : Jun 2015
    Posts : 12,673
    Windows 10 Pro

    Unfortunately, it does only state what has and hasn't been loaded.
    I can remember that there were times of how long the drivers take to load, but that could be from something else.

    Following drivers couldn't load, all are Windows drivers.
    This does has influence on the boot time, because it takes more time to find the drivers.
    Code:
    BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\DRIVERS\NDProxy.sys
    BOOTLOG_NOT_LOADED \SystemRoot\system32\drivers\WdFilter.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys
    BOOTLOG_NOT_LOADED \SystemRoot\System32\drivers\dxgkrnl.sys



    BSOD code 0x133 caused by hal.dll & ntsokrnl.exe Diagnostics Test BSOD code 0x133 caused by hal.dll & ntsokrnl.exe
     Clean boot

    Please try the following:
    • Open taskmanager
      • Go to the tab startup
      • disable everything

    • Search msconfig and open it
      • Go to the tab services
      • Check 'hide microsoft services'
      • Uncheck all other services
      • Click apply and click ok

    • Reboot if asked

    See if the problem persist, if the problem does not persist enable in the startup tab in taskmanager 1 item and in the services tab in msconfig also 1 service, reboot and see if the problem persist. Keep doing this until you find the culprit or there is nothing left.
    If the problem still persist, try booting in safe mode and see if the problem still persist
      My ComputersSystem Spec

 
Page 2 of 2 FirstFirst 12


Similar Threads
Thread Forum
BSOD caused by driver ntoskrnl.exe
Hi, Got today brand new laptop-Alienware 17 R3. Randomly getting BSOD, some time irql_not_less_or_equal, or MEMORY_MANAGEMENT error. Happens during playing game or browsing or something else. Got 5-6 times. Could you help me please? Appreciate in...
BSOD Crashes and Debugging
Solved BSOD caused by ntoskrnl.exe please help
Hey all, I've attached 4 minidumps. Can you please help troubleshoot this intermittent BSOD?
BSOD Crashes and Debugging
BSOD caused by ntsoskrnl.exe
So uh, yeah, this is causing me issues. 42120
BSOD Crashes and Debugging
BSOD caused by ntoskrnl.exe
Hello! I have recurring blue screens on my laptop and can't seem to figure out what's causing them. Sometimes, the computer also freezes completely without any forewarning and the only way to shut it down is to remoce the battery. I should...
BSOD Crashes and Debugging
BSOD caused by ntoskrnl.exe
BSODs have been happening for a while but I'm not really sure what's the actual cause.
BSOD Crashes and Debugging
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:57.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums