Repetitive reboot during repair installation

P

Party Phil

Hi,
I am running a desktop machine Windows XP with SP2 and have the
installation disk with SP2. I installed Mozilla Firefox onto the PC
yesterday, got it working fine and then shut down the computer. Having
installed Firefox onto my laptop (which I am using now) which uses the
same version of Windows successfully I did not expect any problems.

When I came to boot up the desktop today, the computer kept crashing
and restarting just as it reached the welcome screen of Windows XP
(before the log-in / desktop). I disabled the auto-restart option and
found that there was a "BAD_POOL_CALLER" error with - STOP: 0x000000C2
(0x00000043, 0xDF1C7000, 0x00000000, 0x00000000)

Having read a bit on these forums and other sites it seemed that my
installation of a new program had caused the error and I saw
recommendations to run a repair installation of Windows XP SP2. I
decided that I would have a go at running the repair install and
started out by booting off the CD-ROM and selected the option to enter
Windows Setup (because I had seen warnings against using the recovery
console at http://www.michaelstevenstech.com/XPrepairinstall.htm#RI).
The setup process recognised the earlier installation of Windows and I
selected the 'R' option to repair the current Windows installation.

This resulted in a load of files being copied in preparation for the
setup and after agreeing to the license agreement, the setup was
initiated. Once the time remaining reached 33 minutes I was then
prompted to select the language and enter the Product Key. I did both
of these steps and the setup continued. However once the time remaining
reached 25 minutes and the setup process was "Completing Installation",
the computer rebooted with the same 'Bad Pool Caller' error and resumed
setup at 39 minutes remaining.

This continual rebooting during the setup process is where I am stuck
now. I have no idea how to stop the cycle repeating or what to do to
eradicate the 'Bad Pool Caller' error. I am on the verge of taking the
computer to get fixed at my local PC Shop, and I don't really want to
do that!!

Can anyone help me with this problem please!? Any advice is much
appreciated - I see a lot of people have had similar problems but there
doesn't appear to be a clear solution to this exact scenario.

Regards,
Phil Clark
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top