Solved system file checker log does not show file not repaired

[outbound]

Ran system file checker and it said it found corrupted files but could not repair all of them. Looking at the log is not helping. I have posted the last several lines as they are representative of the entire log with the exception of the last few lines that mention an actual repair. Where is the file(s) system file checker couldn't repair? If there is a corrupted file(s), how do I find it?



2015-01-26 00:18:26, Info CSI 0000032a [SR] Beginning Verify and Repair transaction
2015-01-26 00:18:27, Info CSI 0000032c [SR] Verify complete
2015-01-26 00:18:27, Info CSI 0000032d [SR] Verifying 100 (0x0000000000000064) components
2015-01-26 00:18:27, Info CSI 0000032e [SR] Beginning Verify and Repair transaction
2015-01-26 00:18:29, Info CSI 00000330 [SR] Verify complete
2015-01-26 00:18:29, Info CSI 00000331 [SR] Verifying 100 (0x0000000000000064) components
2015-01-26 00:18:29, Info CSI 00000332 [SR] Beginning Verify and Repair transaction
2015-01-26 00:18:31, Info CSI 00000334 [SR] Verify complete
2015-01-26 00:18:31, Info CSI 00000335 [SR] Verifying 100 (0x0000000000000064) components
2015-01-26 00:18:31, Info CSI 00000336 [SR] Beginning Verify and Repair transaction
2015-01-26 00:18:32, Info CSI 00000338 [SR] Verify complete
2015-01-26 00:18:32, Info CSI 00000339 [SR] Verifying 18 (0x0000000000000012) components
2015-01-26 00:18:32, Info CSI 0000033a [SR] Beginning Verify and Repair transaction
2015-01-26 00:18:32, Info CSI 0000033c [SR] Verify complete
2015-01-26 00:18:32, Info CSI 0000033d [SR] Repairing 0 components
2015-01-26 00:18:32, Info CSI 0000033e [SR] Beginning Verify and Repair transaction
2015-01-26 00:18:32, Info CSI 00000340 [SR] Repair complete

 

[ICIT2LOL]

Hello and welcome outbound mate you should have a look in the Event Viewer - it is a bit tedious but you may be able to track it down.
What I would do too is run this
http://www.sevenforums.com/tutorials/433-disk-check.html I usually use Option 2 and the /f and /r switches if necessary

To check the event viewer http://www.sevenforums.com/tutorials/226084-event-viewer-open-use-windows-7-a.html

PS If you like you can see the details of the sfc using this
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[outbound]

Thanks for trying to help me. I did all that, but nothing found. Running the system file checker was an ordeal in itself as it kept saying it found corrupt files but could not fix them all, but when I would look at the log file, there were no bad files showing. When I would try to run it from the command prompt from within the Repair Your Computer option (F8 at boot to get to menu), it would tell me that it couldn't run because there is a pending repair, and instructed me to reboot. So I would reboot and try again, but get the same message. Finally found a command to use that forced it to work from the command prompt within the Repair Your Computer option. And after all that, no errors found. So I have something running in Windows that causes system file checker to return a false positive when I try to run it from within Windows, but my system files are fine. Here's the command that worked for me from the command prompt within the Repair Your Computer option: sfc /scannow /offbootdir=c:\ /offwindir=c:\windows

 

[ICIT2LOL]

Yes I think you are talking of safe mode outbound that is the usuallF8 action when powering up.

Now just in case something nasty has got in run this after making the bootable disk. http://support.kaspersky.com/4162 it scans the machine from power up and does not involve Windows at all.

If that does not do anything then try this Anti-rootkit utility TDSSKiller

 

[outbound]

Great, thanks for the info and links. Yeah, it's Safe Mode, but it doesn't say Safe Mode. It says Repair Your Computer, but once you select it, you're looking at VGA graphics, so yes, it's Safe Mode. lol Probably OEM Dell stuff. Everything seems to be working fine right now, and I've ran Malware Bytes, Hitman Pro, and AVG with nothing found. Only thing is that when I tried to use System Restore earlier in an attempt to solve the problem with system file checker, it failed every time. So then I tried a variety of solutions on the web to fix System Restore, but none of them got it to work. And yes, it's turned on with no extra drives showing. Usually gives the message that System Restore failed because restore point was deleted or corrupted. Obviously not true though, unless it is deleting and/or corrupting each new point because it keeps failing even with new restore points. I tried the anti-rootkit program that you provided, but it didn't find anything. Haven't tried the other one yet, but it says it's for when your system won't boot, which mine will boot just fine. I may try it later though. Thanks again for your help.