Re: SFC caused BSOD

Tech-Archive recommends: Fix windows errors by optimizing your registry

"C J." <no.reply@xxxxxxxxxxxxxxx> wrote in message news:uEISE6HpHHA.1852@xxxxxxxxxxxxxxxxxxxxxxx

"Rock" <Rock@xxxxxxxxxx> wrote in message news:uyfcXYCpHHA.3252@xxxxxxxxxxxxxxxxxxxxxxx
"JayJay" wrote
On the spur of the moment decided to run SFC. Started SFC and it
asked a number of times for me to enter the Windows XP CD, I pressed
the retry button and eventually the check completed.
Starting the computer up this morning I received a BSOD with Stop:
0x0000007e error message. Luckily I had made an image file using
Acronis TrueImage just prior to running SFC so was able to restore
back. Just to make sure it was SFC that caused the problem I again
rerun SFC then turned off the computer. After rebooting the BSOD
screen came up with the same Stop message.
With SFC using Windows 98 it gave the option to change the file or
not, I never received any message when running SFC with Windows XP.

I am aware that many forums and newsgroup's recommend running SFC to
check that all system files are okay but if my experience is anything
to go by it's a potential mine field. Has anyone else experienced a
similar problem after running SFC? And how does one go about checking
the system files if SFC causes a problem?

Here is a link to a general reference about that stop error message, but nothing specific to SFC.
http://aumha.org/a/stop.htm
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Wonderful that you are using ATI to protect yourself from glitches like this. Good choice and well worth it, eh?

As you have discovered Sfc /scannow in XP does not give you any messages about what it's doing. You can look in the logs in event viewer to see what it has done. I don't remember which of the two logs it places it's messages, windows of applications.

Here is a link with info on Sfc in XP.
http://www.updatexp.com/scannow-sfc.html

Personally I don't see Sfc being of great value in fixing problems. I have seen an occasional post where running it helped, but usually not. Maybe there is a problem with some software or hardware driver installed in your system that is causing this problem to occur.

If you really wanted to check this out in more detail you could do a clean boot and try SFC again to see if the results are any different. Also I don't know if SFC will run in safe mode but that's another option to try. Safe mode loads a limited set of drivers. If it completes ok in Safe mode, assuming it will run in Safe mode at all, then that would point to a driver loading in normal mode as the cause.

Clean Boot Troubleshooting

How to Troubleshoot By Using the Msconfig Utility in Windows XP
http://support.microsoft.com/?id=310560

How to perform advanced clean-boot troubleshooting in Windows XP
http://support.microsoft.com/?id=316434

How to perform a clean boot in Windows XP
http://support.microsoft.com/?id=310353

A description of the Safe Mode Boot options in Windows XP
http://support.microsoft.com/kb/315222/en-us

--
Rock [MS-MVP User/Shell]
As a side topic discussion...

Its funny you mention "Clean boot - Safe Mode" I have SFC set up to run from my harddrive instead of off the CD on a "Full Retail" Version of Pro SP2. I usually run "SFC/ Scannow" from the built in Administrator account instead of my user account thats experiencing a problem(s). I've seen messages in safe mode ( administrator account ) that SFC couldn't run because a Windows service wasn't loaded. Exactly which one it was escapes me at the moment.

Ok, I haven't tried it in Safe Mode in ages so I didn't remember if it would run from there. The OP should still try running from a clean boot.

Also, the last time I ran SFC to correct problems with some kooky desktop behavior about a month ago or so - SFC corrected the problems, (whater they were) and all updates were current and intact, according to Windows Update. However, when I went to use Windows Media Player 10 an incorrect version of wmp.dll was reported, and so I had to reinstall the program and its security updates. Strange eh?

All SFC does is make sure the dllcache file is populated with the correct files. Windows file protection takes care of replacing the working files from dllcache if they get deleted. So that's why SFC usually doesn't have much impact. It's only when the working file is borked and the file in dllcache is no good that it helps. This isn't too often.

--
Rock [MS-MVP User/Shell]

.

Quantcast