fs_rec.sys and BSODs

I'm having some probs with BSODs related to fs_rec.sys. I know this is something to do with the file system so I haven't tampered too much. Occasionally I get BSODs at start up before the logon screen and I always get them after running chkdsk /f. Needless to say, chkdsk doesn't fix anything either. I have tried running Norton Disk Doctor but I can't get it to fix anything in XP's GUI as it says the drive is being hogged by something...presumably XP. Scheduling that doesn't work either. I have tried replacing the file but that didn't help so it wasn't corrupt.

Here's the tech info from the error report:

STOP: 0x0000007E (0xC0000005, 0xF8AA851D, 0xF8A35C34, 0xF8A35934)

Fs_Rec.sys - Address F8AA851D base at F8AA8000, Datestamp 3b7d8361

.Here is the site referring to the STOP code

My specs:

Athlon XP2000, Gigabyte 7VRXP M/B, 512Mb PC333, Western Digital 80Gb + 120Gb(SE) HDDs, Leadtek A250 Graphics, SB Audigy, Diamond V92 modem, Lite-On DVD-ROM & CD-RW, MSI Bluetooth Dongle, PS/2 mouse + keyboard.

The drivers haven't been updated in about 2 months. The only updates have been to XP. I am looking for solutions that preferably involve not reinstalling everything as I don't have time for that. Any help would be most appreciated.

You can't use chkdsk in xp like you could in 9x ...

What you need to do is right click whichever drive, properties tools, error checking & then tick both boxes (this'll schedule chkdsk to run at startup - the only time it can correct file system errors & remap bad sectors - it needs to be not using it, chkdsk will run & windows will restart again)

As far as not updating any drivers I'd ssuggest you at least get the VIA chipset patchess (hyperions) as these will have an effect on your file system for sure ... on which subject is this a FAT or NTFS drive ?

So my advice, update at least your chipset drivers (they'll have 'newer' ide so harddisk drivers) & use the windows option to schedule chkdsk, don't try & run it from command prompt (any write behind behaviour windows might have defined for your disk will prevent it running 'correctly' otherwise) .... Give that a try.

They are both NTFS formatted. Will give what you suggested a whirl and I'll report back later.

I have tried what you suggested and it kicked up the same error report. Any other ideas?

Anyone know how to run Norton Disk Doctor in XP so it'll fix stuff? Says it needs scheduled but it never runs on restart.

Running Nero and/or Incd? I suggest you download the latest version from www.nero.com.

Quote:

---

Originally posted by NooNoo
Running Nero and/or Incd? I suggest you download the latest version from www.nero.com.

---

Now there's a possibility ... fs_rec.sys has something to do with cdfs not either FAT or NTFS when I engage brain ....

So either as Noo suggests or try running SFC (System file checker -if you know how in xp) & see if that file is either corrupted or overwritten by another application (I think that's Noo's thinking ...).

Ran sfc, it completed and nothing popped up on the screen so I presume that's a good thing (either that or it's just another example of programs not telling you what's happening). As far as nero goes, that will take a while to get over dialup so unless I get a good connection today, I'll task my brother with getting it through his uni network. Cheers so far.

After 6hrs downloading, I got Nero, updated it and there's no probs any more...or at least CHKDSK doesnt throw out an error report. Does anyone know how to run Norton Disk Doctor outwith XP as there are still errors appearing with that? Thanks NooNoo & Confus-ed.

Quote:

---

Originally posted by ringo2143z
... Does anyone know how to run Norton Disk Doctor outwith XP as there are still errors appearing with that?...

---

Go on then ... what are the "errors" first ?

DO you mean you want to run it from command prompt, its a windoze program so there isn't a way to run it 'outwith XP' as it depends on windows components to produce its results ... I'm not a fan though, the very latest version seems 'better' (but its still a big fat resource hog & doesn't always want to 'get on' with many applications I like to install, its tricky to configure 'correctly' too if you've 'tampered' in any way shape or form with XPs default serverices) ... Is this Home or Pro btw ?

Do I detect an air of sarcasm there!?!?!

It's XP Home. The latest version of Systemworks has worked ok for me. I generally only use it for fixing registry errors though. The bit from the scan report is below.

[CENTER]SECURITY DESCRIPTORS STATUS
---------------------------

The 'Fix errors' checkbox was not checked.
Corrective actions indicated below were
not written to the disk.

Correcting errors in the master file table's (MFT) BITMAP attribute.

Norton Disk Doctor found problems with the file system.
Run Norton Disk Doctor and check the Fix Errors option.

Haven't a clue what this means and if it's worth fixing. There is a way of running systemworks on boot by using the CD but I can't for the life of me find it [the CD]. Symantec's website suggests there's a util on their ftp site for doing it but I can't find that either.

If you don't use Norton, what do you use for sorting registry errors and disk errors? I'm not someone who agrees with regular reinstalls of everything...waste of my time.

No, you just detect Confus-ed :D

As for registry errors - I fix them by hand and disk errors chkdsk and the diagnostics from the manufacturer are my friend.

Quote:

---

Originally Posted by NooNoo

No, you just detect Confus-ed :D

As for registry errors - I fix them by hand and disk errors chkdsk and the diagnostics from the manufacturer are my friend.

---

Come on now NooNoo.
I can walk into a new customer location and have Norton WinDoctor find over 200 registry "errors".
"Norton WinDoctor is the safe and easy way to diagnose and repair the most common types of Windows problems. It checks all the information necessary for Windows to run properly. Plus it checks for components needed by programs that run under Windows."

Of course these are minor errors which should really be called a cleaning of the registry. But geez, to do this by hand, looking through thousands of lines of text would take forever.
So what do you mean by you fix them by hand?

Also, with XP and 2K, stick with chkdsk but check both options:
Automatically fix file system errors.
scan for and attempt recovery of bad sectors.
Norton Disk Doctor was good with Win9x/me but chkdsk now does the job.

What do you call errors?

If you mean blind keys because uninstallers don't work properly, that's something entirely different, that is housekeeping. When uninstalling a program you can do one of two things, leave them, or search the registry for the name of the application.

If I have an unknown machine I use Regcleaner (which is not regclean btw) This shows you the blind alleys. It does not blindly clean up your registry and then you find some apps don't work quite right.


Norton is fine for the consumer, for the troubleshooter it is a nightmare.

Quote:

---

Originally Posted by NooNoo

What do you call errors?

If you mean blind keys because uninstallers don't work properly, that's something entirely different, that is housekeeping. When uninstalling a program you can do one of two things, leave them, or search the registry for the name of the application.

If I have an unknown machine I use Regcleaner (which is not regclean btw) This shows you the blind alleys. It does not blindly clean up your registry and then you find some apps don't work quite right.


Norton is fine for the consumer, for the troubleshooter it is a nightmare.

---

That is exactly what I said:
"Of course these are minor errors which should really be called a cleaning of the registry"
So is Regclean your "manual" fix?
"So what do you mean by you fix them by hand" :confused:

Quote:

---

Originally Posted by TripleRLtd

That is exactly what I said:
"Of course these are minor errors which should really be called a cleaning of the registry"
So is Regclean your "manual" fix?
"So what do you mean by you fix them by hand" :confused:

---

I mean exactly that, if there is sympton of a bad key, I go find it. If I get hardware problems I go into the enum section and remove the key and reinstall the device. Things like creative drivers are a pain, because they quite often screw up and you end up pulling them out of the reg.

Unregister or re registers dlls as appropriate. What I don't do with a computer that I don't know the history of is put an app on it that has a mind of its own.