Windows 7: SFC/SCANNOW found problems

HI all. I run the sfc/scannow and it founds some corrupted files. May someone, kindly, tell me what's the issues? May it be related to IE9 RC? How can I attach my CBS.log, which is 7.56 MB?
Thanks

That command should replace the files it finds corrupted. It would be very difficult to tell how or why they became corrupted, but if it found the files, did it solve your issue that led you to run the command?

First thanks for the answer. When I run the command it solve the issue but, the strange is that each time I run SFC/SCANNOW found it and resolve it. It seems to me that this didn't happen since I install IE9 RC

I would run a check disc, and check the SMART status of the drive. consistently corrupting core files is an indication of a larger problem.

sometimes it is needed to run sfc/scannow several times not just once i have found. more information here How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

Ah, I see. You've had it find issues multiple times. Yes, as others have said, I'd start testing out the hard drive and the memory.

Yes, I'll follow your suggestions and I'll let you know. Thanks for now

If you feel this is related to IE9 then uninstall it and see if the problem goes away.

When SFC cannot repair files after several tries, then the next step is a Repair Install

I uninstalled IE9 that, btw, I don't use prefering Chrome and... sfc/scannow didn't find any integrity violation. I think I'll update IE when the RTM will be release.
Thanks a lot to all of you for supporting my issue
Have a nice day

It could be different to your problem, but I now have sfc finding 'corrupt files' no matter how many time it's run on both my real machine and a reference virtual machine which is a fresh install plus updates.

On both machines sfc /scannow now dumps 900+ files in \windows\winsxs\temp\pendingrenames. They don't get cleaned up on reboot and they accumulate - 900+ new ones each time. Nothing gets fixed and I have no reason to believe that there are any corrupt files at all. Both machines function flawlessly apart from the identical sfc issue.

The initial payload of 900 temp files were dated 10th Feb - I'd run sfc after a power cut knocked the machine out. I only discovered the issue watching the filenames go by during a defrag last night.

I suspect an update is to blame - possibly KB976902 or one of the February batch.