I have an issue where my computer will have an unexpected shutdown while I am away from my Surface for a bit. I have my power settings configured so that while it's plugged in it never goes to sleep but from the event viewer it does appear to be going into a Connected Standy mode at some point. It seems to be random but it has been really bad today and happened 4 times already. The only real messages I get in the event viewer are that the system wasn't shut down properly and one that says the last shutdown was unexpected. I have also noticed that it appears to only happen when I am connected to my Surface Dock (The new one). I've had it plugged in at home to just the regular power supply and it hasn't crashed once.
If anyone has an idea on what I should be looking for I would really appreciate it.
What I have tried so far...
- I ran "sfc /scannow" and got the following...
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.
- The CBS.log shows the following files can't be repaired...
2016-01-21 15:01:52, Info CSI 00003ce4 [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-01-21 15:01:53, Info CSI 00003ced [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-01-21 15:03:38, Info CSI 00004d3e [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-01-21 15:03:38, Info CSI 00004d41 [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
- I have also run "DISM.exe /Online /Cleanup-image /Scanhealth", it looks to complete successfully...
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================100.0%==========================]
The component store is repairable.
The operation completed successfully.
- I then ran "DISM.exe /online /cleanup-image /restorehealth", this fails and I haven't been able to figure out how to fix it...
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================100.0%==========================]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specify
ing a source location, see Configure a Windows Repair Source.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
--------------------------------------------------------------------------------------------------
Surface Pro 3 i7 / 256GB connected to a Microsoft Surface Dock
If anyone has an idea on what I should be looking for I would really appreciate it.
What I have tried so far...
- I ran "sfc /scannow" and got the following...
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.
- The CBS.log shows the following files can't be repaired...
2016-01-21 15:01:52, Info CSI 00003ce4 [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-01-21 15:01:53, Info CSI 00003ced [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-01-21 15:03:38, Info CSI 00004d3e [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-01-21 15:03:38, Info CSI 00004d41 [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
- I have also run "DISM.exe /Online /Cleanup-image /Scanhealth", it looks to complete successfully...
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================100.0%==========================]
The component store is repairable.
The operation completed successfully.
- I then ran "DISM.exe /online /cleanup-image /restorehealth", this fails and I haven't been able to figure out how to fix it...
Deployment Image Servicing and Management tool
Version: 10.0.10586.0
Image Version: 10.0.10586.0
[==========================100.0%==========================]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specify
ing a source location, see Configure a Windows Repair Source.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
--------------------------------------------------------------------------------------------------
Surface Pro 3 i7 / 256GB connected to a Microsoft Surface Dock