SFC finish message

  • Thread starter Thread starter nkjg
  • Start date Start date
N

nkjg

Hi everyone,

I've got a bit of a dilemma here...

My comp has run inself into the ground to the point where
I am getting at least one Windows Explorer crash per day
and I've had two BSOD in the past week.

I have run Ad-Aware, Spybot S&D, and Norton AV 2004 scans,
and all have come up empty for the past 3 weeks or so
(save for a couple of tracking cookies found by Ad-Aware).

I have run SFC (from the command prompt) wtih my WinXP CD,
and I am wondering if there is supposed to be any message
after it's done telling me if it's replaced any files or
the like.

If I don't see any improvement in the next little while,
I'm just going to back everything up on the network drive
here at work and just reinstall everything.

Thanks in advance.

Nick
nkjg/at\interchange/dot\ubc/dot\ca
 
Ok, I've looked in the Event viewer under System, and at
the approximate time that I ran SFC, there are a number
of entries listed that came from :

Source: "Windows File Protection"
Category: "None"
Event (in chronological order): 64016, 64020 (there are
several of these), 64017, and 64016 again

Any help as to what these mean?

Thanks in advance,

Nick
nkjg/at\interchange/dot\ubc/dot\ca
 
Oh yeah... one more thing...

After I ran SFC, I checked the Windows Update site, and
it said that there were two critical updates that I
needed to download. When I went to "read more...", and
the two updates were dated at least two months back...

Isn't this somewhat counter-intuitive? This has the
potential of becoming an infinite loop where if you were
to run SFC at every boot (there is the option of doing
that), then you would also have to be constantly updating
those two updates.

Nick
nkjg/at\interchange/dot\ubc/dot\ca
 
Ah, I'm just an amateur, only 1 step ahead of you.
Did you look at the Description in the panel under the Event ID?

64016 = SFC started
64020 = Found something wrong
64017 = SFC ended
 
Anybody who knows better please chime in.

AFAIK ... SFC and Windows Update are unrelated.

My understanding of the situation is that Windows keeps a "baseline copy" of
all the system files it needs to run, in case any gets corrupted. SFC is a
mechansim to replace any corrupt files from the "baseline copy". The
implication is that Windows Update would have to store updated modules in
both the "daily use" and "baseline copy" folders. Otherwise, it would get
into the loop you describe.
 
-----Original Message-----
Hi everyone,

I've got a bit of a dilemma here...

My comp has run inself into the ground to the point where
I am getting at least one Windows Explorer crash per day
and I've had two BSOD in the past week.

I have run Ad-Aware, Spybot S&D, and Norton AV 2004 scans,
and all have come up empty for the past 3 weeks or so
(save for a couple of tracking cookies found by Ad- Aware).

I have run SFC (from the command prompt) wtih my WinXP CD,
and I am wondering if there is supposed to be any message
after it's done telling me if it's replaced any files or
the like.

If I don't see any improvement in the next little while,
I'm just going to back everything up on the network drive
here at work and just reinstall everything.

Thanks in advance.

Nick
nkjg/at\interchange/dot\ubc/dot\ca
.
Your PC problems may be caused by either faulty RAM,
Click to expand...
(one bad memory module), or device drivers that need to
be updated to current XP versions, mostly the video
display, and the sound drivers.
 
The combination of Event ID No: and Source produces no returns but the place to check this type information is :

http://www.microsoft.com/technet/su...ows Operating System&MajorMinor=5.1&LCID=1033

OR:

http://www.eventid.net/search.asp

I have not previously researched any Event ID no: of the order of 64000 so I was not sure where to check. If you use the first link and enter the source you get two results but not the particular numbers you mention.

Whilst the information above does not answer your particular enquiry it may help you (and others) research other error messages.

--

~~~~~~


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA
(e-mail address removed)
Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.

~~~~~~~~~~~~~~~~~~~~~~~~
 
I don't think that it's a problem with my hardware, since
I've had the computer running for about 4 months now
without any problems.

Also, if it were a faulty RAM chip, I was under the
impression that WinXP would not even start. As for my
video drivers, I have downloaded the latest drivers from
Compaq and they have been running on here since mid-March.
Sound drivers are original (i.e. installed when I got the
computer).

Thanks for the suggestion, though.

Nick
nkjg/at\interchange/dot\ubc/dot\ca
 
As pointed 64016 and 64017 are only giving information and are not error message. It would be interesting to see exact copies of the 64020 report and any other Error Report.

A tip for posting copies of Error Reports (Step 1). Run Event Viewer and double click on the error you want to copy. In the window which appears is a button resembling two pages. Double click the button and close Event Viewer. Now start your message ( email )and do a paste into the body of the message. This will paste the info from the Event Viewer Error Report complete with links into the message. Make sure this is the first paste after exiting from Event Viewer. It can be helpful to place a shortcut to Event Viewer on your Desktop.


--

~~~~~~


Hope this helps.

Gerry
~~~~~~~~~~~~~~~~~~~~~~~~
FCA
(e-mail address removed)
Stourport, Worcs, England
Enquire, plan and execute.
~~~~~~~~~~~~~~~~~~~~~~~~
Please tell the newsgroup how any
suggested solution worked for you.

~~~~~~~~~~~~~~~~~~~~~~~~
 
Back
Top