won't boot, BAD_POOL_CALLER stop error 0x000000c2

G

Guest

I have a Gateway 610 running Windows XP Media Center Edition. I have been
getting a blue screen with the error message BAD_POOL_CALLER immediately
after the Windows Startup screen comes on, with parameters 0x000000c2
(0x00000043, 0xCF4A1000, 0x00000000, 0x00000000).

I have tried using Last Known Good Configuration, Safe Mode, and every other
disaster recovery tool I can imagine and all give the same error when
attempting to start Windows. I attempted to do an in-place installation of
Windows XP, but it stops at the same point in the installation each time. I
know that this error is a memory violation caused by a driver or software
attempting to free a virtual address that was never in any pool. I have
followed the instructions on every site I could find on the Internet that
referred to this specific error or stop errors in general, but none have
worked, including everything on Microsoft's support website I could find. In
addition, no new software or drivers had been added to the compiuter for
months before this happened except for Windows updates and antivirus updates.
By looking up the Windows Update log, I saw that Windows updated itself just
a few hours before the error occured so this is the only thing I can imagine
caused it. Also, since one site I found said this error could be caused by
faulty memory, I bought some new memory and tried starting the computer using
that but the same error occured at the same time so it must be caused by some
kind of driver or something that was installed by Windows update. Does
anyone have any additional ideas of how to fix this problem and / or how to
prevent it from happening again in the future if I end up just having to
reformat the drive?
 

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