Bad Pool Caller

[DenzilVoorhees]

Hi,

I'm on an old computer it's spec:

2.5ghz AMD XP
512MB RAM
40GB HDD
32MB Graphics Card
Windows XP

All of a sudden every time i boot up i get the following message:

Bad_Pool_Caller

STOP 0x000000C2 (0x00000043, 0xC9A37000, 0x00000000, 0x00000000)

I can't even get into Safe Mode.

Any ideas?

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

Plot thickened recently, tried a Windows Repair installation incase it was a
driver conflict and got the following:

Got a bit more information:

I finally found my Windows XP CD and started a repair install, the first
time i ran it: i got the following error:

Bad_Pool_Caller
STOP 0x000000C2 (0x00000043, 0xD25B7000, 0x00000000, 0x00000000)

So i tried the repair again and kept a close eye on it:

When it said: "25 minutes to go and above the progress bar (which was 2/3
through) it said 'Completing Installation"

Bad_Pool_Caller
STOP 0x000000C2 (0x00000043, 0xD5D37000, 0x00000000, 0x00000000)

 

[Gerry]

Denzil

Do you need to recover data from the drive. You can put the drive in a
second computer as a slave drive to recover important data. This should
be done first.

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

BAD_POOL_CALLER2: BAD_POOL_CALLER
(A kernel-mode process or driver incorrectly attempted to perform memory
operations. Typically, a faulty driver or buggy software causes this.
Source: http://aumha.org/a/stop.htm

This problem commonly go nowhere -see link
http://snurl.com/egj8v [www_google_co_uk]

Your best bet probably is a reinstall but you may have failing hardware.
What is the computer make and model?

--


Hope this helps.

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

 

[DenzilVoorhees]

Hi Gerry,

My computer was bought from a company who set up their own using different
brands so would have to open it up to check (got this computer many years
ago).

So i can slave the HDD to recover data, that is good. Thought i'd lost it
all. If i can get windows to almost start up, that means that my HDD isn't
broken, right?

I've actually got a spare USB HDD Enclosure lying about somewhere, that
would be just as good as putting it another PC as a slave?

Thanks for your help

Denzil

Denzil

Do you need to recover data from the drive. You can put the drive in a
second computer as a slave drive to recover important data. This should
be done first.

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

BAD_POOL_CALLER2: BAD_POOL_CALLER
(A kernel-mode process or driver incorrectly attempted to perform memory
operations. Typically, a faulty driver or buggy software causes this.
Source: http://aumha.org/a/stop.htm

This problem commonly go nowhere -see link
http://snurl.com/egj8v [www_google_co_uk]

Your best bet probably is a reinstall but you may have failing hardware.
What is the computer make and model?

--


Hope this helps.

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

Hi,

I'm on an old computer it's spec:

2.5ghz AMD XP
512MB RAM
40GB HDD
32MB Graphics Card
Windows XP

All of a sudden every time i boot up i get the following message:

Bad_Pool_Caller

STOP 0x000000C2 (0x00000043, 0xC9A37000, 0x00000000, 0x00000000)

I can't even get into Safe Mode.

Any ideas?

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

Plot thickened recently, tried a Windows Repair installation incase
it was a driver conflict and got the following:

Got a bit more information:

I finally found my Windows XP CD and started a repair install, the
first time i ran it: i got the following error:

Bad_Pool_Caller
STOP 0x000000C2 (0x00000043, 0xD25B7000, 0x00000000, 0x00000000)

So i tried the repair again and kept a close eye on it:

When it said: "25 minutes to go and above the progress bar (which was
2/3 through) it said 'Completing Installation"

Bad_Pool_Caller
STOP 0x000000C2 (0x00000043, 0xD5D37000, 0x00000000, 0x00000000)