Bad_pool_header Blue screen Win Xp stop

Bad pool headerHi, do anyone know how to solve a BAD_POLL_HEADER... this is not a permanent error, it comes and goes..The only unsual thing that are new on this pc are:*SP2 upgrade (i think this is the problem)and e-mule recently installed...Win XP starts normally, and when we try to login into an user account POW.. The Killer blue screen appears... the messegae is long and in spanich.. so the relevant infoBAD_POOL HEADER_ and 0x00000019

people post mesages about pretty interesting topics...but, why can't people get more involved in real life problems... this forums are suppoused to be tech priority, no???so please, if you happend to pass by this topic, help me solve this problem!!!

hmmm.... i've seen the blue screen of death once in sp1 but not on sp2.and i think your unaware of the of incompatibility of sp2 in some software, i also experiece some weird prob from it which lead to re-install. but i think you do it. just check new updates from ms, they new have new pacth for this. if problem persist try thier cunsolting sections. i believe they something for you ^_^and kindly don't double post-thnx

Google search on: 0x00000019 BAD POOL HEADER

 

Search on M$ site for the same error

 

And looking at the info on Microsoft it looks to be an error in a router;

STOP 0x00000019 BAD_POOL_HEADER

 

Nils

Me too having problems with XP. Now all worms are specially made for it I think that's why 98 works smoothly but XP currepted easily.Sohail Ahmed

Here you go! Taken from Microsoft "English Knowledge Base".SYMPTOMSA computer running Windows NT may display one of the following blue screen STOP error messages while it processes a datagram packet:STOP 0x0000000A IRQL_NOT_LESS_OR_EQUAL-or-STOP 0x00000019 BAD_POOL_HEADERCAUSEA router incorrectly set the packet fragmentation bit on a browser broadcast datagram packet. The Tcpip.sys driver attempts to reassemble this packet and causes pool memory corruption.RESOLUTIONTo resolve this problem, obtain the fix mentioned below. The new Tcpip.sys driver will now check the length field on the packet to prevent it from processing fragments that do not exist.STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):S E R V P A C KMicrosoft has confirmed this to be a problem in Windows NT version 3.51. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

rapco,

 

I'm closing this post. Looks like it's resolved. If you still have problem PM me and I'll open it up.

 

sohahm, you should specify your problem a little more. A general statement like that is not going to get you any help (if you are looking for it). A broad statement like that will make most people jump to the next topic, why waste time asking you to specify so we know what you have a problem with. Put in any error messages and what you were doing prior to error etc.

 

Nils

 

Opened it back up, not resolved. give rapco your best.....

Edited January 6, 2005 by NilsC (see edit history)

Try setting the indexing service to manual. To do that enter services.msc in the run command box. It seems so far to have fixed my Issue on my computer. It would just bluescreen on boot and say that or would just bluescreen on regular use. I have Windows XP with SP2 Running on a gigabyte G-7VT600-L with a Sempron 2500+ and 512MB of samsung PC3200 Ram, And a ATI 9600 Pro Video card.

You have bad RAM, random access memory

Bad_pool_header

 

You have bad RAM, random access memory

pool header

Bad_pool_header

 

BSOD Bad_Pool_Header

Stop 0x00000019 (0x00000020,0xE13CB000,0xE13CBBF8,0xDB7FDB7F) happens everytime I burn using Nero BSOD Not always the same BSOD sometimes IRQL_NOT_LESS_THAN. But always burning is this ause by the DVD Burner worn out because on a start up most of time won't read?

Ahhh yes the IRQL_NOT_LESS_OR_EQUAL. I have seen this several time in my computer experience. The realistic answer is that IRQL_NOT_LESS_OR_EQUAL or BAD_POOL_HEADER could mean absolutely anything and unlike POST codes, Microsoft is not very descriptive with their BSOD or kernel panic codes. Basically about 1,000 different and distinctively separate conditions can cause either code. You may be able to Google and find some specific information but I have found this to be mostly a black hole.My personal experience has taught me that this is usually a hardware or low level device driver problem. The first place I would start is with the RAM and Microsoft offers a free tool called Windows Memory Diagnostic (http://forums.xisto.com/no_longer_exists/). If this turns up nothing you may want to see if the system is overheating by removing the cover from the case. The third thing I would do is reinstall Windows. Unfortunately this is a very hard problem to diagnose and you may have to try several things before you get any relief at all.

Usually IRQL_NOT_LESS_OR_EQUAL, based on my past experiences only happens to either a bad hard drive or faulty memory.Other than that, it's usually fine. Rarely would it be caused by a graphics card VRAM.xboxrulz

BAD_POOL_HEADERBad_pool_headerI am an Eve-Online gamer. And this same error has crept on me NUMEROUS times... But ONLY while playing Eve... Nothing else I have tried will cause a blue screen... And this bytes when you are deep in PvP. LolOk... I run Windows XP SP2, just updated ALL my drivers, if it is a router configuration (I'm looking into it as you read this), I have yet to find the issue. RAM tests excellent (a pair of corsairs), Graphics card I think is the only thing that it could be... Eve uses MASSIVE graphics.. And that game does EVIL things to computers sometimes because of it.Maybe I should upgrade to the new GTX (NVidia Loyal).-reply by SnowMon

go to safe mode and uninstall the display driver an then restart the computer

check if indexing services is on or off., if off great.

restart the computer and then reinstall the video driver if not clean installation required.

Hi, I have a toshiba satellite L350d, it use to have a 2gb memory 2x1GB (PC2 5300s)Now I bought 2x2GB (PC2 5300s) to get a 4GB and installed both but when I switch on my laptop I get the BSoD with Driver_IRQL_Not_LEss_OR_EQUAL error with ataport.SysAddress 814A2AE1Base at 81499000Datestamp 49ee8a3aCurrently running Windows 7Any help would be most welcome. Thank YoU

-reply by Evans