SFC scannow cannot repair problem..

i am having problems with my system not wanting to boot up occasionally, when I finally achieved boot up I did a sfc scannow and got the following results: Windows Resource Protection had found corrupt files but was unable to fix some of them and the reference given was "C:\Windows\Logs\CBS\CBS.log".

I opened the cbs.log and went to the part that says cannot repair which is attached.
I have no idea what these means, I know that there is a way to extract files from the installation disc but I wouldn't know which ones.
Also I don't know if this is the problem that is making my pc not to boot up normally.

Anyone know what could I do in this case??

Thanks in advance you all..

yes, Already did a startup repair and a repair install,

after i did the repair install I used sfc scannow and gave me the same report.

thanks

ryo said:

did you already try to Repair Install

ok, i;ll try that tomorrow ,
thnks for quick response

Night Hawk said:

Try scheduling a run of the checkdisk utility with the "chkdsk /r /p" command. You may want to download and run the drive manufacturer's own hard drive diahnostics tool as well to see if you have any bad sectors now being seen.

You can also burn a repair tool cd with the automatic startup repair tool to see that will help correct any minor startup problems if not seen in the F8 boot options menu.

This started when my pc did not sarted properly, giving me 1 long and 2 short beep codes and not being able to enter Bios or anything, (no signal to the black screen), after reseating video card and memory it will boot up normally.
Then the problem happpens again when I restart my computer, the same beep codes and showing "32" on the back of my MOBO (debug led).

I leave the computer alone for like an hour and i am able to boot up again normally, but when i restart the computer the problem reappears. Reseating video and memory no longer works, the only thing that works is letting the computer alone for 1 hour or more so i could turn it on properly.

On one of those normal bootings i took the oportunity to do a sfc scannow in command prompt so i could see if there is any corrupted system files that is causing my system to behave such way.

after doing this i wrote what i wrote at the beginning on this thread.

I am just wondering if this scannow results have anything to do with what is going on, If it does i would like to know how the hell I could read that cbs.log so I could know which files to replace with the installation disk.

If that's having anything to do with the start up problem then i am totally lost here.


that's it thanks....

ryo said:

what is the error or warning??

give me a detail of your problem, because you just mention that's not work properly like before.

4 memory sticks of 2gb each= 8gb

ryo said:

try like hawk suggest.
if that's still can't, i wonder that's cause into your memory, how much GB you put your memory.