System File Checker Freezes When Update to SP3

I updated my XP Pro SP2 with SP3 on a CD.Since then when I run sfc
/scannow,sfc freezes about 30 percent through.Am I missing something?How
does one update sfc to run on SP3?

When I re-boot, chkdsk finds many files in trouble but fixes.Not sure where
the log is so that I can review which files.I suspect the DLL cache is
messed up.

Didn't find anything on a Google search that helped.

I read that SP3 update would make arrangements in the DLL cache for sfc to
work.

The system runs OK afterward but sfc will not run.

Any help is certainly appreciated.

Bob

You might find it best to disregard you have a CD. To use a CD you need
to have a slipstreamed CD containing your the contents of your original
CD plus all subsequent SP updates.

Read this link as it contains a way forward if you have no CD
http://ask-leo.com/i_dont_have_an_in..._need_one.html

If you need to point to a folder choose I386.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Bob Jones wrote:CD
I updated my XP Pro SP2 with SP3 on a CD.Since then when I run sfc
/scannow,sfc freezes about 30 percent through.Am I missing
something?How does one update sfc to run on SP3?

When I re-boot, chkdsk finds many files in trouble but fixes.Not sure
where the log is so that I can review which files.I suspect the DLL
cache is messed up.

Didn't find anything on a Google search that helped.

I read that SP3 update would make arrangements in the DLL cache for
sfc to work.

The system runs OK afterward but sfc will not run.

Any help is certainly appreciated.

In cmd type:Sfc /Scannow REVERT or SFC /REVERT
This uses the default run scan.

"Bob Jones" wrote:

I updated my XP Pro SP2 with SP3 on a CD.Since then when I run sfc
/scannow,sfc freezes about 30 percent through.Am I missing something?How
does one update sfc to run on SP3?

When I re-boot, chkdsk finds many files in trouble but fixes.Not sure where
the log is so that I can review which files.I suspect the DLL cache is
messed up.

Didn't find anything on a Google search that helped.

I read that SP3 update would make arrangements in the DLL cache for sfc to
work.

The system runs OK afterward but sfc will not run.

Any help is certainly appreciated.

I slipstreamed my XP CD and SP3 and SFC chose the correct source path but
again froze at 40-50 percent complete.The frezing is independent of the call
for a CD.

When the system freezes I cold re-boot it and chkdsk runs.The results are
errors that say the DLL cache has corrupted files and chkdsk fixes the
files.The system runs OK after re-boot and until the next time I run SFC.

I will try and expand sfc.exe and replace it.

I can find no one who has had this problem and MS is SLOW getting back to me
with the fix.
All ideas/help are certainly appreciated.


"Andrew E." wrote in message
...
In cmd type:Sfc /Scannow REVERT or SFC /REVERT
This uses the default run scan.

"Bob Jones" wrote:

I updated my XP Pro SP2 with SP3 on a CD.Since then when I run sfc
/scannow,sfc freezes about 30 percent through.Am I missing something?How
does one update sfc to run on SP3?

When I re-boot, chkdsk finds many files in trouble but fixes.Not sure
where
the log is so that I can review which files.I suspect the DLL cache is
messed up.

Didn't find anything on a Google search that helped.

I read that SP3 update would make arrangements in the DLL cache for sfc
to
work.

The system runs OK afterward but sfc will not run.

Any help is certainly appreciated.

Bob

Does your Windpws XP CD include SP2?

Please post copies of all Error and Warning Reports appearing in
the System and Application logs in Event Viewer for the last boot. No
Information Reports or Duplicates please. Indicate which also appear in
a previous boot.

You can access Event Viewer by selecting Start, Control Panel,
Administrative Tools, and Event Viewer.

A tip for posting copies of Error Reports! Run Event Viewer and double
click on the error you want to copy. In the window, which appears is a
button resembling two pages. Click the button and close Event
Viewer.Now start your message (email) and do a paste into the body of
the message. Make sure this is the first paste after exiting from
Event Viewer.

Are there any yellow question marks in Device Manager? Right click on
the My Computer icon on your Desktop and select Properties,
Hardware,Device Manager. If yes what is the Device Error code?

Try Start, Run, type "sigverif.exe" without quotes and hit OK. What
drivers are listed as unsigned? Disregard those which are not checked.

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

Bob Jones wrote:
I slipstreamed my XP CD and SP3 and SFC chose the correct source path
but again froze at 40-50 percent complete.The frezing is independent
of the call for a CD.

When the system freezes I cold re-boot it and chkdsk runs.The results
are errors that say the DLL cache has corrupted files and chkdsk
fixes the files.The system runs OK after re-boot and until the next
time I run SFC.
I will try and expand sfc.exe and replace it.

I can find no one who has had this problem and MS is SLOW getting
back to me with the fix.
All ideas/help are certainly appreciated.


"Andrew E." wrote in message
...
In cmd type:Sfc /Scannow REVERT or SFC /REVERT
This uses the default run scan.

"Bob Jones" wrote:

I updated my XP Pro SP2 with SP3 on a CD.Since then when I run sfc
/scannow,sfc freezes about 30 percent through.Am I missing
something?How does one update sfc to run on SP3?

When I re-boot, chkdsk finds many files in trouble but fixes.Not
sure where
the log is so that I can review which files.I suspect the DLL cache
is messed up.

Didn't find anything on a Google search that helped.

I read that SP3 update would make arrangements in the DLL cache for
sfc to
work.

The system runs OK afterward but sfc will not run.

Any help is certainly appreciated.

No problems in device manager.
My CD is XP SP1.I updated SP2 from web and have a CD for SP3.

Following are unsigned files:

ftprnl45.dat 4/29/1998 None Not Signed
N/A
ftprnt45.dll 6/12/2000 0.2.0.0 Not Signed
N/A
ftprui45.dll 6/12/2000 0.2.0.0 Not Signed
N/A
[c:\windows\system32\spool\drivers\w32x86\3]
e_dupa20.exe 2/2/2007 None Signed
N/A SEIKO EPSON Corporation
e_dupa2e.dll 1/22/2007 2.0.0.0 Not Signed
N/A
e_fabrcca.dll 3/12/2007 6.0.0.0 Not Signed
N/A
e_faifcca.dat 3/12/2007 None Not Signed
N/A
e_faircca.dll 1/22/2007 1.0.2.0 Not Signed
N/A
e_famtcca.exe 3/9/2007 5.0.1.0 Not Signed
N/A
e_faprcca.dll 3/12/2007 6.0.0.0 Not Signed
N/A
e_farncca.exe 1/25/2007 5.0.0.0 Not Signed
N/A
e_faskcca.dll 11/13/2006 5.0.0.0 Not Signed
N/A
e_fasocca.dll 3/6/2007 1.0.1.0 Not Signed
N/A
e_fasrcca.dll 3/26/2007 6.0.0.0 Not Signed
N/A
e_faticca.exe 3/12/2007 6.0.0.0 Not Signed
N/A
e_faudcca.dll 11/13/2006 0.1.2.2 Not Signed
N/A
e_fba6cca.dll 2/21/2007 6.1.0.0 Not Signed
N/A
e_fbapcca.dll 11/30/2006 5.12.0.0 Not Signed
N/A
e_fbcscca.exe 11/16/2006 1.0.1.0 Not Signed
N/A
e_fbidcca.lmd 1/17/2007 None Not Signed
N/A
e_fbl6cca.dll 12/20/2006 6.2.0.0 Not Signed
N/A
e_fcf0cca.cfg 3/9/2007 None Not Signed
N/A
e_fconcca.dll 11/13/2006 4.0.10.0 Not Signed
N/A
e_fdspcca.dll 4/10/2007 0.3.1.10 Not Signed
N/A
e_fgepcca.dll 2/26/2007 1.0.1.0 Not Signed
N/A
e_fgrccca.dll 9/21/2006 3.0.4.0 Not Signed
N/A
e_fhbrcca.dll 3/30/2007 1.0.0.0 Not Signed
N/A
e_fhm0cca.dll 1/18/2007 4.3.1.1 Not Signed
N/A
e_fhsrcca.dll 3/30/2007 1.0.0.0 Not Signed
N/A
e_fht0cca.dll 2/13/2007 3.2.1.1 Not Signed
N/A
e_fhutcca.dll 3/30/2007 10.0.6.0 Not Signed
N/A
e_fhutcca.exe 3/30/2007 10.0.6.0 Not Signed
N/A
e_fjbccca.dll 4/5/2007 0.1.1.6 Not Signed
N/A
e_fmaicca.dll 1/22/2007 0.3.1.10 Not Signed
N/A
e_fmw0cca.dll 3/29/2007 1.1.0.0 Not Signed
N/A
e_fokacca.dll 12/13/2006 None Not Signed
N/A
e_fpi1cca.dat 2/9/2007 None Not Signed
N/A
e_fprecca.exe 10/31/2006 0.1.0.4 Not Signed
N/A
e_fprmcca.prm 12/14/2006 None Not Signed
N/A
e_fprucca.dll 1/23/2007 0.2.0.14 Not Signed
N/A
e_fsr0cca.dll 2/23/2007 3.0.1.1 Not Signed
N/A
e_fui1cca.dll 1/22/2007 0.7.0.1 Not Signed
N/A
e_fuiccca.dll 3/12/2007 0.3.50.48 Not Signed
N/A
e_fuipcca.dll 1/22/2007 0.6.0.2 Not Signed
N/A
e_fuircca.dll 3/12/2007 0.7.0.4 Not Signed
N/A
e_fvifcca.vif 4/12/2007 None Not Signed
N/A
e_qi121e.chm 2/21/2007 None Not Signed
N/A
e_s40rp7.exe 1/11/2007 4.0.2.0 Not Signed
N/A
ebapi4.dll 11/30/2006 5.12.0.0 Not Signed
N/A
ebpbidi.dll 1/30/2007 6.3.0.0 Not Signed
N/A
epset32.dll 2/26/2007 3.0.0.8 Not Signed
N/A
epupdate.dat 4/21/2004 None Not Signed
N/A
mxdwdrv.dll 3/22/2007 0.3.6000.0 Not Signed
N/A
mxdwdui.dll 3/22/2007 0.3.6000.16438 Not Signed
N/A
mxdwdui.gpd 8/31/2006 None Not Signed
N/A
mxdwdui.ini 4/21/2006 None Not Signed
N/A


Following are errors in applications and system since last boot,all appeared
in previous boot:


Event Type: Error
Event Source: PctSpk
Event Category: None
Event ID: 0
Date: 7/8/2008
Time: 3:26:54 PM
User: N/A
Computer: BOBSCOMPUTER
Description:
The description for Event ID ( 0 ) in Source ( PctSpk ) cannot be found. The
local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: PctSpk error: 1063,
StartServiceCtrlDispatcher failed..

Event Type: Error
Event Source: PctSpk
Event Category: None
Event ID: 0
Date: 7/8/2008
Time: 3:16:15 PM
User: N/A
Computer: BOBSCOMPUTER
Description:
The description for Event ID ( 0 ) in Source ( PctSpk ) cannot be found. The
local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: PctSpk error: 1063,
StartServiceCtrlDispatcher failed..

Event Type: Warning
Event Source: Userenv
Event Category: None
Event ID: 1517
Date: 7/8/2008
Time: 3:20:24 PM
User: NT AUTHORITY\SYSTEM
Computer: BOBSCOMPUTER
Description:
Windows saved user BOBSCOMPUTER\Bob registry while an application or service
was still using the registry during log off. The memory used by the user's
registry has not been freed. The registry will be unloaded when it is no
longer in use.

This is often caused by services running as a user account, try configuring
the services to run in either the LocalService or NetworkService account.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/8/2008
Time: 3:25:09 PM
User: N/A
Computer: BOBSCOMPUTER
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/8/2008
Time: 3:20:25 PM
User: N/A
Computer: BOBSCOMPUTER
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/8/2008
Time: 3:16:41 PM
User: N/A
Computer: BOBSCOMPUTER
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/8/2008
Time: 3:14:20 PM
User: N/A
Computer: BOBSCOMPUTER
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/8/2008
Time: 10:13:09 AM
User: N/A
Computer: BOBSCOMPUTER
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/8/2008
Time: 10:10:50 AM
User: N/A
Computer: BOBSCOMPUTER
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/8/2008
Time: 7:37:32 AM
User: N/A
Computer: BOBSCOMPUTER
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/8/2008
Time: 5:50:10 AM
User: N/A
Computer: BOBSCOMPUTER
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/8/2008
Time: 5:47:50 AM
User: N/A
Computer: BOBSCOMPUTER
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Warning
Event Source: Print
Event Category: None
Event ID: 8
Date: 7/8/2008
Time: 4:45:22 AM
User: BOBSCOMPUTER\Bob
Computer: BOBSCOMPUTER
Description:
Printer EPSON Stylus C120 Series was purged.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/8/2008
Time: 4:23:35 AM
User: N/A
Computer: BOBSCOMPUTER
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 7/8/2008
Time: 2:43:21 AM
User: N/A
Computer: BOBSCOMPUTER
Description:
The Fast User Switching Compatibility service depends on the Terminal
Services service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it
has no enabled devices associated with it.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.