Safe Mode Boot Loop; Normal Boot OK

[System Administrator]

Windows XP Pro SP3 with latest updates as of 22 August.

After seeing signs of malware infection on a user workstation
yesterday, I attempted to boot to Safe Mode to run a virus/malware
scan. Machine would not boot into Safe Mode. After displaying
loading mup.sys for a few seconds it would reboot itself. After
pressing F8 to get to the boot choices, selecting Last Known Good
Configuration allowed normal boot. Finding that the malware did not
load if logged in as Administrator (normal machine login is as a Power
User), I was able to clean the machine of the malware. However,
attempts to login to Safe Mode still loop. Stopping the automatic
restart brings up the BSD with:

IRQL_NOT_LESS_OR_EQUAL

Stop 0x0000000A (0xF79A8354, 0X000000FF, 0X00000001, 0X804E5619)

Any ideas on how to fix?

Thanks in advance.

 

[db]

sometimes boot looping can
be stopped/fixed by booting
with a win cd, logging into
the recovery console and running
the commands>:

fixboot

but in your case, I would run
the following commands instead:

chkdsk /p
fixboot
fixmbr

then "exit" and try booting
without cd.

--
db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
- @Hotmail.com

"share the nirvana mann" - dbZen

~~~~~~~~~~~~~~~

 

[System Administrator]

Thank you for your response. Sorry for my late response - I'm only at
this client one day per week. I just tried your suggestions. I
performed all three: chkdsk /p (I then did a /r as a problem was
found), fixboot, and fixmbr. The computer still loops on attempts to
boot to safe mode. Boot to normal mode still works OK. Any
additional ideas? Thanks.

 

[db]

unfortunately, I don't have much to
offer,

except maybe running an sfc /scannow
in normal mode "or"

a repair installation with a winxp
cd.

perhaps, there is something installed
in normal mode, like an antivirus or
firewall that is not allowing access to
the safemodes as some sort of protection.

so maybe a clean boot is a viable step
to initiate during this analysis.

--
db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
- @Hotmail.com

"share the nirvana mann" - dbZen

~~~~~~~~~~~~~~~

 

[System Administrator]

OK, thanks. I will give those a try when the computer becomes
available for diagnostic testing.

 

[Jose]

OK, thanks.  I will give those a try when the computer becomes
available for diagnostic testing.

unfortunately, I don't have much to
offer,

except maybe running an sfc /scannow
in normal mode "or"

a repair installation with a winxp
cd.

perhaps, there is something installed
in normal mode, like an antivirus or
firewall that is not allowing access to
the safemodes as some sort of protection.

so maybe a clean boot is a viable step
to initiate during this analysis.

--
db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
-  @Hotmail.com

"share the nirvana mann" - dbZen

Good 'ol mup.sys. I have a new appreciation for mup.sys issues these
days.

When booting is Safe Mode and the last thing you see is mup.sys, the
common assumption is that the problem is with mup.sys, but that is not
the problem file.

The problem file is what comes after mup.sys, and you can't see it
since your system is stuck or reboots, but you can figure out what the
file is and then you can fix it.

There is no need for guesswork (unless you like that).

If you have only occasional access, provide detailed system
configuration info as follows:

Click Start, Run and in the box enter:

msinfo32

Click OK, and when the System Summary info appears, click Edit, Select
All, Copy and then paste back here.

There will be some personal information (like System Name and User
Name), and whatever appears to be private information to you, just
delete from the pasted information.

This will minimize back and forth Q&A and eliminate guesswork and
assumptions.

Describe the mouse, keyboard and any other external USB device
environment. Wired, wireless, USB, PS2, printer, etc.

My first suspect is a USB mouse and you don't need a mouse to boot and
choose Safe Mode since the keyboard is available. Will your system
boot in Safe Mode with no mouse?

Things are different if you are in a docking station, etc. but I would
start with the mouse - no matter how it hooks up. You do not need it
to boot in Safe Mode (or any mode).

We can figure out exactly what it is later after getting more
information.

 

[Jose]

OK, thanks.  I will give those a try when the computer becomes
available for diagnostic testing.

unfortunately, I don't have much to
offer,

except maybe running an sfc /scannow
in normal mode "or"

a repair installation with a winxp
cd.

perhaps, there is something installed
in normal mode, like an antivirus or
firewall that is not allowing access to
the safemodes as some sort of protection.

so maybe a clean boot is a viable step
to initiate during this analysis.

--
db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
-  @Hotmail.com

"share the nirvana mann" - dbZen

....and if it is a laptop with an added external KB & M, unplug them
and boot using the built in devices.