Stop: 0x00000019 = BAD_POOL_HEADER

I am running XP Home on a Toshiba Satellite 5005 S504.
I have recently performed a full restore (format) on the HDD, and was left
with basic Windows Xp Home ed. I installed various updates, then skipped up
to SP1. which resulted in error msg and bad driver for a sound device, which
I removed.

Sp1 was looping for a while, ending with a dreaded blue screen error msg.,
but appeared to have cleared. My laptop ran trouble free for a few days, and
seemd to be stable.

So I installed SP2 from a cd, and got the dreaded blue screen when I
attempted to reboot. Cold boot did not help. I keep getting a blue screen
when the boot cycle reaches "welcome".
The error msg is BAD_POOL_HEADER
Stop: 0x00000019 (0x00000020, 0x82E1B1D0, 0x 82 F1B200, 0x1A060004)
The latter numbers in parentheses change on each boot attemp.

I have been trying to solve this one for days.

I finally was able to remove SP2, and my machine stabilized. When I
attempted to install SP2 again, I ended up with the same problem: dreaded
blue screen.

I hope I have provided enough background info.

Please help.

--
Still learning

"JL" wrote:

> I am running XP Home on a Toshiba Satellite 5005 S504.
> I have recently performed a full restore (format) on the HDD, and was left
> with basic Windows Xp Home ed. I installed various updates, then skipped up
> to SP1. which resulted in error msg and bad driver for a sound device, which
> I removed.
>
> Sp1 was looping for a while, ending with a dreaded blue screen error msg.,
> but appeared to have cleared. My laptop ran trouble free for a few days, and
> seemd to be stable.
>
> So I installed SP2 from a cd, and got the dreaded blue screen when I
> attempted to reboot. Cold boot did not help. I keep getting a blue screen
> when the boot cycle reaches "welcome".
> The error msg is BAD_POOL_HEADER
> Stop: 0x00000019 (0x00000020, 0x82E1B1D0, 0x 82 F1B200, 0x1A060004)
> The latter numbers in parentheses change on each boot attemp.
>
> I have been trying to solve this one for days.
>
> I finally was able to remove SP2, and my machine stabilized. When I
> attempted to install SP2 again, I ended up with the same problem: dreaded
> blue screen.

I've had the exact same problem; I installed a new motherboard (MicroStar
K8N Neo), processor(AMD64 3200) and video card (ATI Radeon 9800 Pro). System
stabilized under a "repair" install of XP2. All hotfixes up to SP2 worked.
Tried "updating" device drivers per Windows Update; turned out the ones on
the ATI site were unstable, so I backed the drivers down to those on the
install disk. Everything remained stable. Installed XP2, and now I get the
bluescreen of death at least twice a day now. The error is BAD_POOL_HEADER
0x00000019; params are 0x00000020, 0xE18668E8, and then varying 3rd & 4th
(e.g. 0xE1866998 and 0x0c160401). Contrary to what the Help tells me, no
error message is sent upon startup, whether or not I have checked "Automatic
restart after error".

Is there anyone who has a clue?

-- Clueless

Forgot to add that system is regularly cleared of malware by AdAware, Spybot
S&D, and Spyware Doctor. Current on Norton AntiVirus 2002. Router is
LinkSysWRT54GS secured w/128 bit WEP.

Thanks.

"Dave Simpson" <Dave Simpson@discussions.microsoft.com> wrote in message
news:0E635075-D5A1-4781-B046-3731C340A814@microsoft.com...
> "JL" wrote:
>
>> I am running XP Home on a Toshiba Satellite 5005 S504.
>> I have recently performed a full restore (format) on the HDD, and was left
>> with basic Windows Xp Home ed. I installed various updates, then skipped up
>> to SP1. which resulted in error msg and bad driver for a sound device, which
>> I removed.
>>
>> Sp1 was looping for a while, ending with a dreaded blue screen error msg.,
>> but appeared to have cleared. My laptop ran trouble free for a few days, and
>> seemd to be stable.
>>
>> So I installed SP2 from a cd, and got the dreaded blue screen when I
>> attempted to reboot. Cold boot did not help. I keep getting a blue screen
>> when the boot cycle reaches "welcome".
>> The error msg is BAD_POOL_HEADER
>> Stop: 0x00000019 (0x00000020, 0x82E1B1D0, 0x 82 F1B200, 0x1A060004)
>> The latter numbers in parentheses change on each boot attemp.
>>
>> I have been trying to solve this one for days.
>>
>> I finally was able to remove SP2, and my machine stabilized. When I
>> attempted to install SP2 again, I ended up with the same problem: dreaded
>> blue screen.
>
> I've had the exact same problem; I installed a new motherboard (MicroStar
> K8N Neo), processor(AMD64 3200) and video card (ATI Radeon 9800 Pro). System
> stabilized under a "repair" install of XP2. All hotfixes up to SP2 worked.
> Tried "updating" device drivers per Windows Update; turned out the ones on
> the ATI site were unstable, so I backed the drivers down to those on the
> install disk. Everything remained stable. Installed XP2, and now I get the
> bluescreen of death at least twice a day now. The error is BAD_POOL_HEADER
> 0x00000019; params are 0x00000020, 0xE18668E8, and then varying 3rd & 4th
> (e.g. 0xE1866998 and 0x0c160401). Contrary to what the Help tells me, no
> error message is sent upon startup, whether or not I have checked "Automatic
> restart after error".
>
> Is there anyone who has a clue?


The third parameter on Stop messages often seems to be an address
somewhere within a related module. You can use the Support Tools
pstat utility (or dumpchk if you have a dump) to try to see if the address
is within the bounds of a driver.

E.g. open a command window and see if this pipeline finds anything:

pstat -s | find /i ".sys E186"

Etc.


BTW such diagnosis is normally off-topic for this newsgroup.
You may find better assistance on a newsgroups which specializes
in your OS.


Good luck

Robert Aldwinckle
---

I have been trying to install windows xp pro with little success. The first attempt, I got everything installed and then when I installed service pack 3, I started getting a "your bios is not acpi compliant" bsod. I used the f7 method of silencing acpi on the bios, but now I can never boot to windows or complete the installation without getting a stop: 0x00000019 BAD_POOL_HEADER error. Let me know if you guys figure out how to fix this problem.

I am using an asus a8n-sli deluxe with an amd 64 fx 3800+, 1 gb of ram in dual channel (2x512mb), nvidia 7950 gt, western digital caviar 80gb hd.

Neophile,

I am having the exact same problem as you mention. I am also using an ASUS A8N-SLI mobo as well as an FX60. I'm using F7 to disable ACPI and getting the Bad_pool_header error at the reboot during the windows install.

I have actually managed to get past the reboot during install several times (out of perhaps 15 attempts) and complete the windows installation (not sure why it is so hit and miss). In all of those cases the system is fine until the next boot up, at which time I am prompted with a screen asking whether to start windows normally or in safe mode. None of the safe mode options, last good config, or normal mode will boot. From this point there seems to be no other option aside from a new install.

I did not have this problem 2 years or so ago when I was installing from an SP1 Disc, but this time around I have a new copy of XP with SP3. I suspect that SP3 is the culprit for the bad pool error but the reboot issue may turn out to be bad hardware.

What is reallly baffling me is why after a sucessful install, that all is well until the next boot and then my install is toast. Very strange.

I'm out of ideas at this point

<QP>
0x00000019: BAD_POOL_HEADER
A pool header issue is a problem with Windows memory allocation. Device
driver issues are probably the most common, but this can have diverse causes
including bad sectors or other disk write issues, and problems with some
routers. (By theory, RAM problems would be suspect for memory pool issues,
but I haven’t been able to confirm this as a cause.)
</QP>
Source & more: http://aumha.org/a/stop.htm
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

SkyBum wrote:
> Neophile,
>
> I am having the exact same problem as you mention. I am also using an
> ASUS A8N-SLI mobo as well as an FX60. I'm using F7 to disable ACPI and
> getting the Bad_pool_header error at the reboot during the windows
> install.
>
> I have actually managed to get past the reboot during install several
> times (out of perhaps 15 attempts) and complete the windows installation
> (not sure why it is so hit and miss). In all of those cases the system
> is fine until the next boot up, at which time I am prompted with a
> screen asking whether to start windows normally or in safe mode. None
> of the safe mode options, last good config, or normal mode will boot.
> From this point there seems to be no other option aside from a new
> install.
>
> I did not have this problem 2 years or so ago when I was installing
> from an SP1 Disc, but this time around I have a new copy of XP with SP3.
> I suspect that SP3 is the culprit for the bad pool error but the reboot
> issue may turn out to be bad hardware.
>
> What is reallly baffling me is why after a sucessful install, that all
> is well until the next boot and then my install is toast. Very strange.
>
>
> I'm out of ideas at this point

Quote:

---

Originally Posted by SkyBum

Neophile,

I am having the exact same problem as you mention. I am also using an ASUS A8N-SLI mobo as well as an FX60. I'm using F7 to disable ACPI and getting the Bad_pool_header error at the reboot during the windows install.

I have actually managed to get past the reboot during install several times (out of perhaps 15 attempts) and complete the windows installation (not sure why it is so hit and miss). In all of those cases the system is fine until the next boot up, at which time I am prompted with a screen asking whether to start windows normally or in safe mode. None of the safe mode options, last good config, or normal mode will boot. From this point there seems to be no other option aside from a new install.

I did not have this problem 2 years or so ago when I was installing from an SP1 Disc, but this time around I have a new copy of XP with SP3. I suspect that SP3 is the culprit for the bad pool error but the reboot issue may turn out to be bad hardware.

What is reallly baffling me is why after a sucessful install, that all is well until the next boot and then my install is toast. Very strange.

I'm out of ideas at this point

---

ok, I have since fixed this issue. What you need to do:

if you can get through an entire install without problem, fine. DO NOT INSTALL SP3!!! This service pack is not compatible with this motherboard. It will bsod after installing this sp, no matter what. Install all windows updates, EXCEPT sp3. There is no need to disable acpi support with f7 during install, either. All you need to do is disable usb support, disable 1394 (firewire) support, disable cool 'n' quiet, reinstall windows, update windows except sp3, then turn those functions back on, except cool 'n' quiet or 1394 unless you use firewire for anything. I hope this helps.

I was also able to resolve my issues. I did install from an SP3 disk as that was the only option I had, but in my case, disabling Cool and Quiet and also APM (advanced power management) in the BIOS allowed windows to install sucessfully and it has been rock solid ever since. I also didnt press F7 during the install.

I have no idea whether it was the Cool and Quiet setting or the APM setting which allowed the install to proceed without the usual headaches but it was definitely one of the two.

Next time I am feeling brave I am going to enable APM in the BIOS and cross my fingers...

SkyBum wrote:

> I was also able to resolve my issues. I did install from an SP3 disk as
> that was the only option I had, but in my case, disabling Cool and Quiet
> and also APM (advanced power management) in the BIOS allowed windows to
> install sucessfully and it has been rock solid ever since. I also didnt
> press F7 during the install.

Did you check the manufacturer's web site for firmware updates?

It sounds as if there may be a fault in either the firmware or the hardware
design, I suggest you take this up with the motherboard manufacturer.

This applies to neophile too. (Note that not installing SP3 is only a temporary
solution as security updates will not be provided for SP2 indefinitely.)

Harry.