Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2390
  • Last Modified:

FLTMGR.SYS Causes Computer to Reboot over and over

Have an XP system which reboots itself over and over. If you choose safe mode, it reboots, if you choose normal mode, it reboots.

I was able to view the load process in safe boot and right before the reboot, the last file, which it seems to choke on is FLTMGR.SYS.  

Other than doing a reload of XP on top of itself, has anyone run across this problem before?

Thanks,
Dale
0
dgore1
Asked:
dgore1
  • 2
  • 2
1 Solution
 
LeeTutorretiredCommented:
This page explains a bit about the file:

http://www.file.net/process/fltmgr.sys.html

You probably have a corrupt version in the folder

c:\Windows\System32\Drivers

and you need to replace it.

If you cannot get into Safe mode, then you will need to use the Recovery Console, which is described in this MSKB article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;314058
Description of the Windows XP Recovery Console

On my computer, there is another copy of the fltmgr.sys file in this folder:

c:\Windows\ServicePackFiles\i386

You need to make sure your primary boot device is the CD-ROM drive -- go into the BIOS to ensure this, if necessary, boot from the Windows XP installation CD-ROM, then use the COPY command, like this:

copy c:\Windows\ServicePackFiles\i386\fltmgr.sys  c:\Windows\System32\Drivers\fltmgr.sys


Then type EXIT and when the pc reboots, you should be able to boot into XP.
0
 
dgore1Author Commented:
The strange news is this hard drive, an 80 GB SATA drive is formatted with 2 FAT32 partitions.  So I can boot using a win98 boot disk...the recovery console is a no go since this is ACER OEM, and was a syspreped image.  I tried the microsoft hotfix to remove the password from the recovery console and a no go there.

No option for the repair, so I did a parallel install and the machine boots fine right now.  However, I would like to try your idea of now copying the fltmgr.sys but I'm going to try to copy from c:\windows2\system32\drivers\fltmgr.sys to the bad boot area in c:\windows\system32\drivers\fltmgr.sys.

I'll let you know how that goes.

thanks,
Dale
0
 
LeeTutorretiredCommented:
dgore1, any feedback?
0
 
dgore1Author Commented:
I made a dup of the system and did both a parallel install, which worked of course but also I could copy good boot files into the bad file area as necessary...seems as if norton could have been the culprit...the user fessed up and did some kind of update to norton right before the crash!!!

Thanks,
Dale
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now