STOP: c000007b error SFCFILES.dll Solution

flychromeboy

New Member
Reaction score
0
I got the following BSOD message on a client's computer after a anti-spyware scan and wanted to share the solution with you all as there isn't much info on it on the interwebs. A bit of background, Advent 7078 laptop running XP Home. The message was:

STOP: c000007b {Bad Image}
The application or DLL \??\C:\WINDOWS\System32\sfcfiles.dll is not a valid windows image. Please check this against your installation diskette.


Before finding the solution this was what I did:
  1. Rebooted and chose Last Good Configuration- Fail
  2. Booted into Safe Mode - Fail
  3. Googled the STOP message. Not much information on how to fix it. I was guessing it had to do with some spyware infection. The dll in question was a monitoring tool which checks system files for corruption ect

Ok here's the solution:
  1. Put in my XP Home disc and entered into Recovery Console
  2. copied and expanded the sfcfiles.dll from the XP disc to the Windows\System32 directory (initially I just copied over the dll file, thinking that would solve it, but on further investigation, you need to expand dll files. The super techs among you will already know this, but as I didn't, this step is crucial, and can help others out there.

    The command is expand d:\I386\sfcfiles.dl_ c:\Windows\System 32

    (where d: and c: are the dvd drive and hard drive respectively). Another thing I learnt is that dll files on the disc are labelled with an _ at the end and not labelled dll. Only when they become expanded do they take the full dll extention
  3. Rebooted and voila, no more BSOD and booted into Windows fine.
 
It's very nice of you to share your fix with us but please be aware that this type of fix is basic repair tech knowledge. A BSOD that directly points to a bad file and almost tells you what to do, you unpack a copy of the file from a windows disk, problem goes away. Its not something many here would get stuck on, its certainly not SUPER TECH stuff. That's all I am going to say. ;)
 
...you unpack a copy of the file from a windows disk, problem goes away.

One of the benefits of having multiple computers of the same model and "coreload" at the office. Just grab the file from a running machine, place it in the appropriate location and issue resolved.

Tom
 
It's very nice of you to share your fix with us but please be aware that this type of fix is basic repair tech knowledge. A BSOD that directly points to a bad file and almost tells you what to do, you unpack a copy of the file from a windows disk, problem goes away. Its not something many here would get stuck on, its certainly not SUPER TECH stuff. That's all I am going to say. ;)

True, but maybe one day a real tech will use google and find that fix to solve a problem, getting it done faster than trying to remembering the command that he hasn't used in a while, and avoid asking a basic question in the forum.

Couldn't resist :p
 
True, but maybe one day a real tech will use google and find that fix to solve a problem, getting it done faster than trying to remembering the command that he hasn't used in a while, and avoid asking a basic question in the forum.

Couldn't resist :p

Hmm... sarcasm?. No, not from this bunch... they love me, yeah, they love me....hmmmm.... whatever.... where's my beer......

But anway..... when a BSOD is nice enough to tell you where to go looking for a fix its just hilarious to see it posted here....

"Please check this against your installation diskette"

Why can't I get those. How about something like this:

STOP: 0x00432499a: Dude, I knows it's a Friday... and I mean.... like nobody needs this kind of stress right before the weekend.... but there is this file... wait, wait, it's not like a big important file, it's some little DLL for a file opening thing or a freaking cache purge or whatever. Anyway, it's not bad..... I mean not bad like "INACCESSIBLE_BOOT_DEVICE" bad, but still, it's not like good or cool or fun or something. What I am trying to say is that I can't do anything else until you copy a good version into that 'C:\windows\system32' whatever folder and then reboot your machine. But then like, after you copy the file and reboot, its gonna act kinda weird for like five minutes with no icons on the desktop and you're gonna probably start to freak, BUT DONT !. Just go make yourself a cup of hot cocoa or something and chill, because without you doing anything its just gonna resolve itself..... Seriously, I'm not kidding. After that it will be smooth sailing and you can tell everyone you solved the problem and it will make you like a total hero or something. Now that's cool, I mean its worth this blue screen now, right?. Chicks dig dudes that can fix computers, right ?. Please tell me that's true, because that's all the hope we have in here....... Well, fix it or don't fix it, whatever...... I mean you can just reformat the drive and start over. Like that hasnt been done before.....ha ha, but anyway..... Do what you gotta do and just try to enjoy the rest of your day.
 
Last edited:
Back
Top