can't stop xp pro reboot loop

[sandy j]

Hi,
I hope there is hope for me..I was reading an article on AOL's
home page. Before I could really get into it, AOL closed, and the
computer started a reboot.
I can get as far as the desktop, then the reboot starts. I've tried
'safe mode' and still the desktop closes before I can do anything.
I saw a similar problem here, and tried the suggested fix (using
'safe mode w/networking' and still couldn't get to 'my computer'
to complete the rest of the instructions, before the reboot started.
I have 2 files I would really like to retrieve from the hard drive.
Do I have a chance of getting them? (Anyone responding, please
don't get too technical)

Thanks

 

[db ´¯`·.. >]

try booting up with any
winxp setup cd then
select the repair option
to initiate the recovery
console.

then when you get to
the disk system prompt
run the following commands:

chkdsk
fixboot
fixmbr

then "exit', remove cd
and hopefully your booting
will be normal again.

--

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

"share the nirvana" - dbZen

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

 

[Gerry]

Sandy

Please post a copy of the Stop Error report.

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Keep pressing the F8
key during Start-Up and select option - Disable automatic restart on
system failure.

Do not re-enable automatic restart on system failure until you have
resolved the problem. Check for variants of the Stop Error message.

What is your computer make and model?

What do yiu have by way of a Windows XP CD

Have you tried Last Known Good Configuration?
A description of the Safe Mode Boot options in Windows XP
http://support.microsoft.com/kb/315222/en-us

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[Patrick Keenan]

Hi,
I hope there is hope for me..I was reading an article on AOL's
home page. Before I could really get into it, AOL closed, and the
computer started a reboot.
I can get as far as the desktop, then the reboot starts. I've tried
'safe mode' and still the desktop closes before I can do anything.
I saw a similar problem here, and tried the suggested fix (using
'safe mode w/networking'

Try, "last known good".

and still couldn't get to 'my computer'
to complete the rest of the instructions, before the reboot started.
I have 2 files I would really like to retrieve from the hard drive.
Do I have a chance of getting them?

In the very worst case, there shouldn't be any problem in recovering the
files. Just, before you start drastic repairs, attach the drive to another
system and copy the files off. It's that simple.

(Anyone responding, please
don't get too technical)

Something that I have found works in a number of cases is to attach the
drive to another XP system, locate "pagefile.sys" in the root, and delete
it. Empty the wastebasket, put the drive back in, and restart. Pagefile
corruption can apparently cause looping restarts, but if you're getting as
far as the desktop, the problem is likely with something else and you need
to turn off "restart on crash" to see the error report.

Try rstarting in Safe Mode, log into the Administrator account. If you can
get into that one, then it may just be that your profile is damaged, and you
need to create a new one and migrate your files. This is not really a big
deal.

HTH
-pk

 

[sandy j]

Hi Ben,

thank you very much for your quick response to my query?

as you suggested, i used a winxp bootable cd. pressing the f8 key
i was able to change the reboot setting. I didn't see a screen that
would allow me to select a repair option, to complete the rest of
your instructions. When I booted w/o pressing the f8 key i went
to the desktop, then the reboot loop. Is there a step I'm missing?
should i wind up in dos to complete your instructions?

 

[db ´¯`·.. >]

ok,

what is occurring is that
even though you have inserted
the winxp cd into your drive,

your system is still booting
from the hard disk.

you will need to enable
your system to boot from
the cd and not the hd.

to do this, you will have to
open your bios/cmos menu
and look for the option to
change the boot order.

check your computer user
manual for the instructions.

but as I recall, almost immediately
when you power up the computer
there should be a notation on the
screen to press the f2 key to
enter the setup.

the f2 key/setup will occur before
the next phase of your system,
whereas the option to press the
f8 key subsequently occurs.

once you modify your bios to
boot from cd and reboot, your
computer will then begin loading
the setup files from the cd.

a screen will then be produced
that will provide the option to
install windows "or" repair.

selecting repair will begin the
process of installing and loading
the recovery console mentioned
in my previous response.

----------------

I'll be online for the next couple
of hours and will be monitoring
your postings....


--

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

"share the nirvana" - dbZen

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

Hi Ben,

thank you very much for your quick response to my query?

as you suggested, i used a winxp bootable cd. pressing the f8 key
i was able to change the reboot setting. I didn't see a screen that
would allow me to select a repair option, to complete the rest of
your instructions. When I booted w/o pressing the f8 key i went
to the desktop, then the reboot loop. Is there a step I'm missing?
should i wind up in dos to complete your instructions?

 

[sandy j]

Hi Gerry,

thank you for your help. following your instructions i have the
following on the first boot.. irql_not_less_or_equal
stop code.. 0x0000000a (0xc02af220, 0x0000000, 0x8050e043)
i received the following on the second boot ... page_fault_in_
nonpaged_area
stop code.. 0x00000050 (0xc14b2fdc, 0x00000000, 0xba62ecf7,
0x00000000
ntfs.sys-address ba62ecf7 base@ba60a000, datestamp 45cc56a7
the computer was built by a friend, he upgraded and gave this to
me. the software was already installed, but he included a
bootable windows xp professional cd. i tried last known good
configuration, and restore before my post.
again thanks for any help you can provide..

 

[sandy j]

--
sandy j
Hi Patrick,

thanks for your reply.

i tried rebooting in safe mode as adminstrator. i really don't feel
comfortable doing the instructions that suggest i move the hard drive
to another computer and the reference to changing something in the
"root" is a little more my expertise allows. to make changes in the
root, i would need real specific instructions.

thanks again

 

[Gerry]

Sandy

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793589.aspx

0x0000000A: IRQL_NOT_LESS_OR_EQUAL
Typically due to a bad driver, or faulty or incompatible hardware or
software. Use the General Troubleshooting of STOP Messages checklist
above. Technically, this error condition means that a kernel-mode
process or driver tried to access a memory location to which it did not
have permission, or at a kernel Interrupt ReQuest Level (IRQL) that was
too high. (A kernel-mode process can access only other processes that
have an IRQL lower than, or equal to, its own.)
Source: http://aumha.org/a/stop.htm

You receive a "Stop 0x0000000A" error message in Windows XP
http://support.microsoft.com/kb/314063/

Background information on Stop Error message
http://msdn2.microsoft.com/en-us/library/ms793437.aspx

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
(Click to consult the online MSDN article.)
Requested data was not in memory. An invalid system memory address was
referenced. Defective memory (including main memory, L2 RAM cache, video
RAM) or incompatible software (including remote control and antivirus
software) might cause this Stop message, as may other hardware problems
(e.g., incorrect SCSI termination or a flawed PCI card).
Source: http://aumha.org/a/stop.htm

Background information on Stop Error message:
http://msdn2.microsoft.com/en-us/library/ms795746.aspx

What is the make and model of the hard drive

Run chkdsk /r from the Recovery Console.
http://www.bleepingcomputer.com/tutorials/tutorial117.html

Another possible cause of the problem is bad memory. Have you made any
recent changes? How many sticks of RAM memory does the computer have? If
more than one you can swap sticks in and out to test whether one is
defective. You might test your RAM memory
http://www.memtest.org/

http://www.elephantboycomputers.com/page2.html#Hardware_Tshoot

--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

 

[sandy j]

Hi Ben,

i hope you're still on line....i'm at the recovery console, but it doesn't
look like i thought it would.
how do i input the commands you gave me?

 

[sandy j]

i'm not sure if you received my new cry for help so here it is again,

Hi Ben,

i hope you're still on line....i'm at the recovery console, but it doesn't
look like i thought it would.
how do i input the commands you gave me?
--

--
sandy j

Hi Ben,

thank you very much for your quick response to my query?

as you suggested, i used a winxp bootable cd. pressing the f8 key
i was able to change the reboot setting. I didn't see a screen that
would allow me to select a repair option, to complete the rest of
your instructions. When I booted w/o pressing the f8 key i went
to the desktop, then the reboot loop. Is there a step I'm missing?
should i wind up in dos to complete your instructions?

 

[db ´¯`·.. >]

ok,
after it initializes it
will ask for your password.

if you had none, then just
hit the enter key to bypass
the question.

another question will ask
which o.s. you want to log
into.

so if you only had one o.s.
then you would press the
number 1 key and then
enter.

you will then see a drive
letter and a prompt like
this >:

at the prompt type then
enter the command

chkdsk

after the above completes,
type then enter the command

fixboot

after the above completes
type then enter the command

fixmbr

if you are curious about
the commands available
in this enviroment, type
and enter

help

in any case, after your
run chkdsk, fixboot and
fixmbr

type and enter the command

exit


remove cd and see if you
can boot normally again.

--

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

"share the nirvana" - dbZen

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

 

[db ´¯`·.. >]

ok,
after it initializes it
will ask for your password.

if you had none, then just
hit the enter key to bypass
the question.

another question will ask
which o.s. you want to log
into.

so if you only had one o.s.
then you would press the
number 1 key and then
enter.

you will then see a drive
letter and a prompt like
this >:

at the prompt type then
enter the command

chkdsk

after the above completes,
type then enter the command

fixboot

after the above completes
type then enter the command

fixmbr

if you are curious about
the commands available
in this enviroment, type
and enter

help

in any case, after your
run chkdsk, fixboot and
fixmbr

type and enter the command

exit


remove cd and see if you
can boot normally again.


--

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

"share the nirvana" - dbZen

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

 

[sandy j]

Hi Ben,

i figured out what i needed to do to get to the command prompt, and
started keying as you instructed. i messed up, i should've paid more
attention to the screen. after i keyed in 'chkdsk', enter. the message
on screen is "volume appears to be in good condition and was not
checked. use /p if you want to check the volume anyway". i didn't
do that but input the next command 'fixboot' enter. the message on
screen is "the target partition is d:.
are you sure you want to write a new bootsector to the partition d:?
this is a one space answer. i don't understand this, i didn't think i
was partitioning the hard drive, and i didn't get to key in the next
command "fixmbr".

can you help? i'll be eternally grateful if i can get through this with
my sanity.
thanks

 

[sandy j]

Gerry,

thanks so very much for your help. i haven't added anything to
the computer, but after reading what the possible reasons
could be, i remember a screen that flashed a error with mcafee.
when i saw the error, my first instinct was to remove it, but
then the reboot loop started.
i started acting on the instructions i receive for the recovery
console, and messed up. i should've paid more attention to
the prompts. the last message i received is "are you sure you want
to write a new bootsector to the partition d". i don't understand
the message so i wanted to close out without updating, but don't
know how. can you help?
i will be eternally greatful

 

[db ´¯`·.. >]

yeah, I know they sound
intimidating, but they serve
the purpose of fixing any
corruption involving the
data needed for proper
booting.

so you can enter y or
yes to proceed.

by saying yes to the
questions, you are allowing
the commands to run and
"fix" the boot and master
boot record.



--

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

"share the nirvana" - dbZen

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

 

[Anna]

Hi,
I hope there is hope for me..I was reading an article on AOL's
home page. Before I could really get into it, AOL closed, and the
computer started a reboot.
I can get as far as the desktop, then the reboot starts. I've tried
'safe mode' and still the desktop closes before I can do anything.
I saw a similar problem here, and tried the suggested fix (using
'safe mode w/networking' and still couldn't get to 'my computer'
to complete the rest of the instructions, before the reboot started.
I have 2 files I would really like to retrieve from the hard drive.
Do I have a chance of getting them? (Anyone responding, please
don't get too technical)

Thanks

--
sandy j

Hi Gerry,

thank you for your help... (SNIP)
the computer was built by a friend, he upgraded and gave this to
me. the software was already installed, but he included a
bootable windows xp professional cd. i tried last known good
configuration, and restore before my post.
again thanks for any help you can provide..

--
sandy j

Hi Patrick,

thanks for your reply.

i tried rebooting in safe mode as adminstrator. i really don't feel
comfortable doing the instructions that suggest i move the hard drive
to another computer and the reference to changing something in the
"root" is a little more my expertise allows. to make changes in the
root, i would need real specific instructions.

Hi Ben,

thank you very much for your quick response to my query?

as you suggested, i used a winxp bootable cd. pressing the f8 key
i was able to change the reboot setting. I didn't see a screen that
would allow me to select a repair option, to complete the rest of
your instructions. When I booted w/o pressing the f8 key i went
to the desktop, then the reboot loop. Is there a step I'm missing?
should i wind up in dos to complete your instructions?

Hi Ben,

i hope you're still on line....i'm at the recovery console, but it doesn't
look like i thought it would.
how do i input the commands you gave me?

sandyj:
Since as you've indicated in your initial post that there are only two files
that you *really* want to save from your problem system, it would be best at
the outset if, as Patrick has suggested, you (or someone) could install your
HDD in another working system, hopefully access the contents of your drive
and then copy the two files to some removable media, e.g., floppy disk,
flash drive, CD, etc. At least you would have the two files that are
important to you. Of course all this assumes the HDD is non-defective and
data from it could be accessed while it's connected as a secondary HDD in a
working system.

But you've indicated that you're not comfortable with undertaking the
preceding so we'll let that pass and go on from there.

We're going to assume that the problem you're experiencing is *not* due to
some hardware-related problem. Rather we'll assume that the problem arises
as a result of your XP operating system (OS) that for one reason or another
has become corrupted. Hopefully up to the time that the problem arose you've
been using some kind of an anti-malware (anti-virus) program to avoid
contamination from that end.

Since you've been able to access the Recovery Console as "db" suggested, I
trust you've been able to invoke the commands "db" has suggested. I would
hope that by doing so your problem would be resolved. If so, fine - but I
have the feeling that is not the answer to your problem.

If it's not...

Fortunately you've been able to boot to the XP OS installation CD and arrive
at the "Welcome to Setup" screen. I assume you accessed the Recovery Console
by pressing the "R" key, right?

Assuming that your problem remains after invoking the commands "db" has
suggested, it would probably be worthwhile for you to undertake a Repair
install of the OS. I realize you've never done this before but it's not a
complicated nor terribly difficult process to undertake. By & large it would
be quite similar to fresh-installing the XP OS on your system but all your
programs & data would be retained in the process. This Repair install that
I'll generally describe is *not* the "repair" process you followed by
pressing the "R" key at the "Welcome to Setup" screen. Unfortunately
Microsoft used the same term to describe two completely different
procedures.

So do this...

1. Boot again to your XP OS installation CD and at the "Welcome to Setup"
screen press the Enter key.

2. The following screen will reflect your currently installed OS. Note the
option indicating you can repair the installed OS by pressing the "R" key.
Do so.

3. The repair process will continue just about the same way you would be
making a fresh install of the OS. Along the way you will need to enter your
Product ID, so have that handy.

Hopefully this repair process will resolve your problem and you will have a
bootable, functional system again with all your programs & data intact.
Needless to say there's no guarantee here since it's conceivable there are
other issues (hardware and/or software) present other than a corrupted OS
that are causing the problem(s) you're experiencing.

Assuming the repair install is successful...

If you carried out that process with an XP OS installation CD containing
SP2, then work with the system for a few days to ensure all is well. Then
install SP3 on your system.

If you used a pre-XP-OS-SP2 version to carry out the repair process, install
SP2 on your system, then work with it as explained above.

And, of course, use your anti-malware, anti-virus program(s) to ensure your
system is malware-free.
Anna

 

[sandy j]

Hi Ben,

i guess i'm your worst nightmare. i did as you instructed, but no go.
i got the following "the problem seems to be caused by the following
file: ntfs.sys
page_fault_in_nonpaged_area"
stop: 0x00000050 (0xc1105fdc, 0x00000000, 0xba62ecf7, 0x00000000)
ntfs.sys - address ba62ecf7 base at ba60a000, datestamp 45cc56a7.
one of the responses i received stated the problem may be my
security software. i would like to stay on long enough to uninstall
mcafee, do you think that's possible?

 

[db ´¯`·.. >]

nah, your not a
nightmare.

the worse ones are
the trolls who undermine
and sabotage attempts
to help those in need.

-------------------

ok.

so it can be assumed that
the messages were produced
after rebooting and not
produced at the time you
executed the disk commands.

here are the instructions to
address that specific error
you received.

go to the resolution section:

http://support.microsoft.com/kb/822800

--

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

"share the nirvana" - dbZen

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

 

[sandy j]

Hi Anna,

thanks for the greatly appreciated, detailed response. i tried to follow
your instructions with the win xp bootable cd i have but received
messages stating some .dll's weren't copied correctly. this is the only
win xp 32 bit cd i have. i do have a win xp 64 bit that i was going to
install after i copied the files i'm trying to retrieve. also, i haven't had
a chance to download the new drivers i will need for the 64 bit.
if i use the 64 bit so i can follow the instructions you were nice enough
to provide, will that cause a problem?
thanks again for your help