New
#61
Having trouble getting the reliability history. I typed "reliability history" (without the quotes) in the Search bar and received a Bing search results page. How do I get the Reliability Tool?
Having trouble getting the reliability history. I typed "reliability history" (without the quotes) in the Search bar and received a Bing search results page. How do I get the Reliability Tool?
Eval of RKILL Log:
O2Micro Flash Memory Card Windows Driver by O2Micro International LTD.Code:Checking for processes to terminate: * C:\Windows\System32\SDIOAssist.exe (PID: 3344) [WD-HEUR] 1 proccess terminated!
This is the software driver package for the installed O2Micro Flash Memory Card Reader. The driver package is required in order for the O2Micro Flash Memory Card Reader to function properly and is the software that allows your computer to communicate with this hardware device.
Home - O2Micro.com
You might want to check if there is an updated driver for this?
These can probably be fixed using DISM tool, would you agree @essenbe? [Although the SFC (below) doesn't mention these.]Code:* MMCSS => \SystemRoot\system32\drivers\mmcss.sys [Incorrect ImagePath] * SystemEventsBroker => %SystemRoot%\system32\svchost.exe -k DcomLaunch [Incorrect ImagePath] * WSService => %SystemRoot%\System32\svchost.exe -k wsappx [Incorrect ImagePath] * CompositeBus => \SystemRoot\System32\DriverStore\FileRepository\compositebus.inf_amd64_912dfdedc3d2f520\CompositeBus.sys [Incorrect ImagePath]
The "missing services" tends to be a bug that shows up in RKILL every once and a while.
Understood about the caregiver stuff.
Can you please provide the list of installed programs, using Ccleaner?
Open Task Manager and go to the Details tab. Click at the top of the column CPU to sort by descending usage. Watch it and see if you can identify the process which peaks at that moment - it may give us a clue.
Please upload the log. I can be found at C:\AdwCleaner\
Not a problem at all.
SFC eval:
The opencl.dll is a Windows bug - nothing is wrong with your SFC scan. What version Windows do you have on this thing? I thought this bug was fixed by MS.Code:2016-08-08 18:38:52, Info CSI 00004492 [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-08-08 18:38:52, Info CSI 00004499 [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-08-08 18:38:52, Info CSI 0000449a [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-08-08 18:38:52, Info CSI 0000449d [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-08-08 18:38:54, Info CSI 00004509 [SR] Verify complete
Attachment 95023
I think there's only one day showing because I just re-installed Windows 10. If you need more data, I'll wait a few days and resend. However, it looks like explorer.exe is a problem.
Just going back to this post:
Did you have Avast installed on the W7 system when you upgraded? If so, your user profile(s) and possibly the system has been corrupted. I've just spent the better part of the last 3 days working on a W7 system upgraded to W10 while Avast was still installed. It had terrible problems, and although I've got it in working condition, it still has remnants of problems which will ONLY be corrected by a clean install.
Were you able to get Reliability History to come up? What errors are we seeing there?Never mind - I am just seeing your post above.
In Task Manager, in the Details Tab, click on the Name column to sort alphabetically. Highlight Explorer.EXE (not explorer.exe), right-click and select Open file location. Where does that process reside? The normal explorer.exe resides in C:\Windows.
@simrick if he will run Dism /Online /Cleanup-Image /CheckHealth , it should tell whether any corruption is found and whether it can be fixed by DISM. It won't fix anything, just scan the files for corruption.
If it can be repaired, I would try:
Dism.exe /online /cleanup-image /StartComponentCleanup
Then Dism /Online /Cleanup-Image /RestoreHealth
Then sfc /scannow. Run it three times with a reboot in between each time, or until it says 'no integrity violations found.