Help - Search - Members - Calendar
Full Version: bad_pool_header
Scot's Newsletter Forums > Main > All Things Windows
cityKID55
During the last week I occasionally get a 'bad_pool_header' msg during boot - just as the Windows welcome msg displays. Boot stops and physical memory is dumped. Usually, a reboot solves this, but on 2 occasions it required repeat attempts. No new hardware installed in over a year (new external USB2 HD, but I haven't powered it for 3 weeks)
LilBambi
Here's one possibility:

Netgear wireless card may be at fault:
http://www.tweaksforgeeks.com/BAD_POOL_HEADER.html
QUOTE
Windows XP SP2 BAD_POOL_HEADER Error

**2/27/05 - New drivers have been released for the Netgear adapters that hopefully fixes this issue

Windows XP Service Pack 2 is usually a good thing. However, it's not without it's problems. Most notably is it's crashing of more 'sloppily' written drivers. If you're now experiencing the BAD_POOL_HEADER Blue Screen Of Death on bootup and have a NetGear wireless network card in your machine, then remove it. More than likely this will allow you to boot. I've also heard of some LinkSys wireless network cards causing this same error as well. As of the writing of this article, there are no new drivers from either LinkSys or NetGear. I've also been unable to find any support on their site about the issue. If your NetGear card uses the Atheros chipset, then you may be able to use those drivers to get back up and running.

Note: If you still can't boot even with the card removed, or into safe mode, you'll need to use the recovery console to disable the driver.

The Indexing Service will, on occasion, also cause SP2 to crash. I suspect that machines that start to exhibit this symptom after having SP2 installed have greater underlying issues. Anyway, to stop the indexing service from running, then click Start->Run type services.msc, and click OK.

--picture here--

Double click the  Indexing Service and set the startup type to either manual, or disabled. By default, I believe it's manual. (You'll notice on this machine it's not running, and is set to manual. I haven't changed the setting at all. Also, this machine is running SP2) If your machine BSOD's upon bootup, then you'll likely have to boot to safe mode to change this. You can also disable the Indexing Service using msconfig, however, it's generally better practice to do it the services.msc way.


However, there are apparently many reasons for such a thing...

Indexing Service on SP2:
http://forums.tweaktown.com/showthread.php?t=18119

USB 2.0 issues:
http://www.techspot.com/vb/topic17282.html

More....:
http://www.google.com/search?q=bad_pool_he...:en-US:official

Hope one of these helps your situation.
zlim
I found one person running XP with SP2, had the same problem and solved it by turning off the Indexing Service.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.