Jump to content
Posted 28 July 2014 - 07:10 AM
Posted 28 July 2014 - 07:30 AM
Posted 28 July 2014 - 08:09 AM
sounds like you have some corrupt files, try click start type cmd, hold shift and ctrl then hit enter that will bring up command box and that will be in admin mode then run sfc /scannow if there are any corrupt files that should fix them,,,,,,,,,,,,,,,,,,,,,,maybe
Posted 28 July 2014 - 01:33 PM
Posted 28 July 2014 - 03:06 PM
The fact that the computer recommended running checkdisk means there may be corrupt sectors on the hard drive now. This is caused either by data being garbled while written to the disk, or the fact that the disk itself is malfunctioning.
Try going into the Windows Recovery Environment (http://windows.microsoft.com/en-us/windows/what-are-system-recovery-options#what-are-system-recovery-options=windows-7) and running chkdsk /f /r from the command prompt. Then try running sfc /scannow, also from the recovery environment.
Posted 28 July 2014 - 07:30 PM
Posted 28 July 2014 - 07:31 PM
Posted 28 July 2014 - 08:39 PM
Indeed. Either works.
In the recovery environment, X is a temporary disk created in RAM. As you noted, just switch to the drive letter where your system is located, or enter chkdks c: /f /r.
The disk/volume has to be unmounted because checkdisk needs to be the only program running on your hard drive in order for it to do what it needs to do. So you can either unmount it, or set it to run the next time the system restarts.
Posted 29 July 2014 - 06:33 AM
OK - thanks for explanation
Ran chkdsk /f /r in recovery environment and it found no errors.
Was unable to run sfc /scannow from recovery environment as kept getting following message:
- There is a system repair pending which requires reboot to complete. Restart windows and run sfc again
I rebooted several times (both to normal windows & to recover environment) but was unable to get sfc to run.
I was able to get sfc to run in normal windows and it reported same as earlier (i.e. finding corrupt files it was unable to fix).
Note that normal windows mode does seem more stable now - while waiting for next step will test out and see what issues still are
It did appear that normal windows was more stable than it had been previously.
Posted 29 July 2014 - 06:55 AM
The fact that checkdisk didn't find any errors is a good sign.
Go back to the recovery console command prompt and enter dism.exe /image:C:\ /cleanup-image /revertpendingactions
This should clear the pending sfc command.
Then reboot, try booting into Safe Mode (http://windows.microsoft.com/en-us/windows/start-computer-safe-mode#start-computer-safe-mode=windows-7) and running sfc /scannow again. More on System File Checker: http://support.microsoft.com/kb/929833
Posted 29 July 2014 - 02:06 PM
dism.exe command appeared to execute correctly.
the sfc /scannow command in safe mode gave similar results to previous - ran successfully but indicated had corrupt files that it couldn't repair - it appears to me to be about 8-9 files that it cannot repair.
On the bright side - the computer appears stable again... has been running for several hours now without a problem (have been using it as I normally would) and no error messages, etc. I assume one of the SFC runs must have repaired the program causing the primary symptoms.
Should we worry about the sfc results?
Posted 29 July 2014 - 02:22 PM
If you were able to run sfc, then the dism.exe command did work.
It is a bit worrisome that it was unable to fix some files. They could be critical files; they may be something that might cause minor problems down the road; they might be minor glitches you can probably ignore.
Go through these steps http://support.microsoft.com/kb/928228/da (it says Windows Vista but it will work with Windows 7). This will create a text file on your hard drive -- once it's created, you can search for "sfcdetails.txt" in the Search box on the Start menu to find it. Paste all the entries, in full, where the SR reads "Cannot repair member file" and we'll have a look and determine what the next steps need to be.
Posted 29 July 2014 - 07:42 PM
Following were entries located by findstr command (from new sfc /scannow run in safe mode)
Posted 29 July 2014 - 08:44 PM
Do you have Visual Studio installed on your computer? What version or versions of the .NET Framework to you have installed? I'll explain in a bit.
Here's a rundown of the files SFC couldn't fix:
IEExec.exe is part of Visual Studio .NET Framework. It is used to debug applications launched using a URL, and it works with Internet Explorer.
However, for some reason, bleepingcomputer.com has it listed as possible malware:
Cvtres.exe is part of Visual Studio and .NET Framework
diasymreader.dll is part of Visual Studio and .NET Framework
dfdll.dll is part of .NET Framework
dfsvc.exe is part of .NET Framework
EventLogMessages.dll is part of .NET Framework, it assists in writing event logs.
mscorwks.dll is part of .NET Framework
EventLogMessages.dll used in writing event log messages. It is often used by .NET Framework.
The .NET Framework is used by programmers, including Microsoft itself, to assist their program code to run in Windows. The above indicates you may have issues launching and running some programs if this isn't resolved -- but it's hard to say which programs.
If you have Visual Studio installed, uninstall it and reinstall it. As for the .NET Framework, please post back with the version(s) you have installed.
dw20.exe is an error-reporting application for Microsoft products that collects info on crashes and errors and sends them to Microsoft. It can be safely ignored.
0 members, 0 guests, 0 anonymous users