Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Opencl.dll can not be repaired


  • Please log in to reply
2 replies to this topic

#1 EagleAD

EagleAD

  • Members
  • 1 posts
  • OFFLINE
  •  

Posted 17 February 2016 - 12:12 PM

I've been getting a blue screen error and when I run sfc/scannow it can't repair the errors.

 

This is the CBS.log entry:

 

2016-02-17 12:02:39, Info                  CSI    00005160 [SR] Verify complete
2016-02-17 12:02:39, Info                  CSI    00005161 [SR] Repairing 1 components
2016-02-17 12:02:39, Info                  CSI    00005162 [SR] Beginning Verify and Repair transaction
2016-02-17 12:02:39, Info                  CSI    00005163 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 D3aY0v8h7TSFEaPW45GJUBIqgdDjayKDkZRy1fIhW2M=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-17 12:02:39, Info                  CSI    00005164 [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
2016-02-17 12:02:39, Info                  CSI    00005165@2016/2/17:17:02:39.445 Primitive installers committed for repair
2016-02-17 12:02:39, Info                  CSI    00005166 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 D3aY0v8h7TSFEaPW45GJUBIqgdDjayKDkZRy1fIhW2M=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-17 12:02:39, Info                  CSI    00005167 [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
2016-02-17 12:02:39, Info                  CSI    00005168 [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"
2016-02-17 12:02:39, Info                  CSI    00005169 Hashes for file member \??\C:\WINDOWS\SysWOW64\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 jCmkCA0mNZb0snMaNo0DIhNAS+gDvbwn885A6iOX8Tk=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-17 12:02:39, Info                  CSI    0000516a Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll do not match actual file [l:10]"opencl.dll" :
  Found: {l:32 D3aY0v8h7TSFEaPW45GJUBIqgdDjayKDkZRy1fIhW2M=} Expected: {l:32 9rnAnuwzPjMQA7sW63oNAVhckspIngsqJXKYSUeQ5Do=}
2016-02-17 12:02:39, Info                  CSI    0000516b [SR] Could not reproject corrupted file [l:23 ml:24]"\??\C:\WINDOWS\SysWOW64"\[l:10]"opencl.dll"; source file in store is also corrupted
2016-02-17 12:02:39, Info                  CSI    0000516c@2016/2/17:17:02:39.483 Primitive installers committed for repair
2016-02-17 12:02:39, Info                  CSI    0000516d [SR] Repair complete
2016-02-17 12:02:39, Info                  CSI    0000516e [SR] Committing transaction
2016-02-17 12:02:39, Info                  CSI    0000516f Creating NT transaction (seq 2), objectname [6]"(null)"
2016-02-17 12:02:39, Info                  CSI    00005170 Created NT transaction (seq 2) result 0x00000000, handle @0xb5c
2016-02-17 12:02:39, Info                  CSI    00005171@2016/2/17:17:02:39.499 Beginning NT transaction commit...
2016-02-17 12:02:39, Info                  CSI    00005172@2016/2/17:17:02:39.499 CSI perf trace:
CSIPERF:TXCOMMIT;4028
2016-02-17 12:02:39, Info                  CSI    00005173 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
 
 
Anyone have a clue what's up here?


BC AdBot (Login to Remove)

 


#2 SleepyDude

SleepyDude

  • Malware Response Team
  • 3,052 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Portugal
  • Local time:01:33 AM

Posted 17 February 2016 - 12:29 PM

Hi :welcome: to BleepingComputer,
 
The log show a know problem of the Windows 10 TH2, please follow the guide posted by Aura @Sysnative forum
http://www.sysnative.com/forums/windows-update/18121-guide-opencl-dll-corruption-sfc-dism-windows-10-update-1511-th2.html
 
The BSOD is not related with this error for sure.

• Please do not PM me asking for support. Post on the forums instead it will increases the chances of getting help for your problem by one of us.
• Posts in the Malware section that are not replied to within 4 days will be closed. PM me or a moderator to reactivate.
• Please post your final results, good or bad. We like to know! Thank you!

 
Proud graduate of GeekU and member of UNITE
___
Rui

 
 


#3 usasma

usasma

    Still visually handicapped (avatar is memory developed by my Dad


  • BSOD Kernel Dump Expert
  • 25,091 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southeastern CT, USA
  • Local time:08:33 PM

Posted 18 February 2016 - 03:39 PM

Once you've repaired the opencl.dll error, wait for the next BSOD and then do this:

Please run this report collecting tool so that we can provide a complete analysis:  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.

 


My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able.

- John  (my website: http://www.carrona.org/ )**If you need a more detailed explanation, please ask for it. I have the Knack. **  If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users