fs_rec.sys message showing up on Blue Screen Issue is repeatable! Need Help

  • Thread starter Thread starter Mark Ronning
  • Start date Start date
M

Mark Ronning

Here is the situation. If I do a chkdsk /f or any check desk even using the
recovery console off my XP startup disk I get this message (listed below).
I even tried doing a clean install on XP and tried a repair.

I scheduled a thorough scan disk on my C Drive. It completes and during the
reboot phase it crashes to a blue screen of death with the following
message.
***STOP: 0X0000007E(OXC0000005,OXF7DB, OXF7CA2C40, OXF7CA2940

***FS_REC.SYS ADDRESS F7DBF51D BASE AT F7DBF000, DATE STAMP 3B7D8361

Microsoft has a level 3 engineer contacting me later today. Has anyone else
experienced this issue. Please let me know, it really is annoying.

Thanks Mark
 
I've got the same problem. It seems to have originated
sometime within the last week, after using Windows XP Home
(and Scandisk) for almost 2 months. I last ran Scandisk
without problem about a week ago, but today get the
fs_rec.sys BSOD every time I run Scandisk on my system
partition and it tries to reboot afterward.

I haven't added any hardware or changed hardware drivers
during that period. I'm wondering if this problem was
introduced by some system software change via Windows
Update, which I ran a couple of times in the last week.

Please post any corrective actions Microsoft provides you.
Thanks!
 
Greetings, all,

Regarding the STOP 0x0000007e and fs_rec.sys after using
chkdsk on a reboot of XP:

I too have got lumbered with this problem, (although
firing up the recovery console and doing a chkdsk /p from
there works OK) and have searched high and low in the
Knowledge Base for a solution and have so far found
nothing specific. I too would be very interested to know
what Microsoft has to say about the problem.

Kind regards,
Roger.
 
Mark, did the MS engineer fix this problem? I have same
problem on new laptop with WinXP Home just updated via
internet, so I wonder if the updates are the problem &
whether to update again might correct. I see from Google
groups search there was problem with this file fixed by
SP2 for NT 4.
I also see Mark Connell has the same problem unanswered in
the performance & maintanence part of this XP newsgroup -
see Aug 21 @ 8:07.

Any ideas appreciated, Ron
 
Back
Top