Solved System File Checker question

[Roman5]

Hi,

I ran a command prompt with sfc /scannow and again with sfc /verifyonly as per your tutorial. In both cases it got to 100% verified then the command prompt box just disappeared. Is that a good sign? Assuming all is ok, I was waiting for it say "Windows Resource Protection did not find any integrity violations".

 

[seavixen32]

Welcome to Windows Seven Forums.

Out of curiosity I ran a system file scan on my computer, and on completion the command prompt box informed me that no violations were found and it remained open until I typed the Exit command and executed it.

As for your query, I don't know the significance of it so I'm hoping someone else will throw some light on the matter.

 

[SledgeDG]

Simply check if a log ha been created in \windir\Logs\CBS\CBS.log.
For example C:\Windows\Logs\CBS\CBS.log (you have to read it as admin or at least copy it to the desktop first before you can open it

If there is none you might want to run sfc /scannow again (up to 3 times)

-DG

 

[theog]

May be worth running from boot:
http://www.sevenforums.com/tutorials/139810-sfc-scannow-run-command-prompt-boot.html

 

[Anak]

Hi! Roman5, welcome to 7F

That does seem odd. I was only able to find one reference (so far) of that happening to others. Does System File Checker write a log file to the hard drive?, help, FAQ, forums, question, answer, advice, opinion and howto for Windows, Linux and Mac OS X

To open Event viewer:

The Event Viewer Console

1. Open the Event Viewer Console through one of the following methods:

- From the RUN Command, type eventvwr.msc and press enter.
​

- Click the Start Globe, select All programs, Administrative Tools, and then select Event Viewer;

- NOTE: In some Windows 7 releases you can right click on 'Computer' and select 'Manage', you will then need to filter select the event viewer in from the Microsoft Management Console (MMC) window that appears.
​

2. Expand Windows Logs and click on System, to see your System Events.

From member TimStitt's tutorial here: http://www.sevenforums.com/tutorials/83841-event-viewer-create-custom-system-monitoring.html


To help in performing SDG's suggestion see option three here: http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[Roman5]

Hello and thanks for the replies guys. There is indeed a CBS.log file created today in which opens with notepad and is very long and detailed. Can't make head or tail of it though.

I notice it has log info from the 14th may right through to today. I've only done the scan today though. The first line of entry says

2011-05-14 15:09:23, Info CBS Starting TrustedInstaller initialization.

 

[Brink]

Hello Roman,

You can use the steps in OPTION THREE in the tutorial below to create a sfcdetails.txt file on your desktop with only the SFC scan details from the CBS.LOG in it. If you upload the sfcdetails.txt file, we'll be happy to take a look at it to see if SFC found anything that it could not fix.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[Roman5]

Thank you Brink. I had trouble getting the elevated command prompt to change path to C:\Windows\System32 but it seems to have worked in the end.

http://homepage.ntlworld.com/merlin.five/sfcdetails.txt


All looks ok doesn't it. I was only trying to see if there's anything corrupted causing my very occassional event ID 41 kernel power issue. It only seems to happen during games, where it freezes along with a loud buzzing. Happened in 2009 a few times during playing crysis along with a BSOD, and recently a couple of times in a driving game, no BSOD, but freeze, buzz, black screen, and reboots itself. I disabled my overclock and it seems to have cleared up, although this happened a few times before I ever overclocked, so I'm not convinced the overclock is the source of the problem.

 

[Brink]

Correct, your SFC verify report doesn't show anything wrong with your system files.

For your BSOD issue, I would recommend to post that in a new thread in the Crashes and Debugging forum area instead for more specific help with it though.

 

[Roman5]

Ok, will do. Thanks.

 

[Brink]

You're welcome. I hope the BSOD will get sorted soon for you.