Bad_Pool_Header since SP2 install

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Well, I've long since become used to XP having the occasional blue screen of
death. But ever since I installed SP2, I've been seeing the "bad pool header"
BSOD error pop up somewhat frequently (2-3 times a week, now). I understand
that it can be a driver issue, but how can I possibly track down what driver
is causing it?

The stop codes I got for the error are as follows:
0x00000019
0x00000020
0xE1B15300
0xE1B15460
0x0C2C0221

Can anyone help? This is becoming seriously irritating. I apologize in
advance if this is the wrong section to post, but this is the only place I
found any mention of the "bad pool header" error.
 
I also have a very similar problem "bad pool caller". If you manage to find
the fault I'd appreciate the help to get rid of it. If I find it first I'll
post the results here for you all.

cheers Scott~
 
try this link from microsoft support page... don't ask me how to fix it... I
just thought you might be interested... looks like a possible fix / help
page for us all...!!!

regards Scott
 
I have had the self-same problems too. In addition, it turned out
that the rogue program was also causing my optical drives (CD, CDRW &
DVDRW) to "not" see disk which I inserted.

I tracked the problem dow to an application called "U-storage tools
2.5" supplied as part of a USB Key product. The application allowed a
USB key to be partitioned into public and private areas. Removing
this product remove BOTH the BAD_POOL_HEADER problem AND my PCs
inability to "see" optical disks!

Regards
Guy
 
Sorry, folks, but none of the fixes that were recommended worked. I'm in
serious need of a fix for this- the crashes are happening more frequently,
and are starting to cause errors in my programs. I don't have any USB key
software installed on my computer- but I'll see if I can find an update for
my computer for the USB ports and see if that helps.
 
Really thanx for this tip Guy. I had also the problem of a bad_pool_header
after I installed SP2. When I inserted my usb-stick my pc hangs up with a
blue screen. The problem with the optical disk-drives apeared already before
the install of sp2. It was also not possible to read from my 4in1 cardreader.

The problem by me was also my USB-stick partioning and formatting tool. The
programm is called Tinydisk.exe and is running in the background. After I
stopped the service everything worked fine again.
I checked also on the net for a new version and found it on
http://www.veritech.com.tw/download.htm. First I had version 1.0 now i have
version 2.9 and everything works fine.

Greets

Bert
 
I'm not seeing this link that you are refering too. I am also encountering
this issue, and this error is happening quite frequently. No hardware has
been installed within the last week (when problem started). The only
difference in the configuration is the addition of a network printer (which
was added yesterday)
 
Monk1 said:
I'm not seeing this link that you are refering too. I am also
encountering
this issue, and this error is happening quite frequently. No
hardware has
been installed within the last week (when problem started).
The only
difference in the configuration is the addition of a network
printer (which
was added yesterday)


 > > I'm having same problem,
 > > My stops are different but I assume the same basic
problem.
 > >
 > > "The Rogue Wolf" wrote:
 > >
  > >> Well, I've long since become used to XP
having the occasional blue screen
  > >> of
  > >> death. But ever since I installed SP2, I've
been seeing the "bad pool
  > >> header"
  > >> BSOD error pop up somewhat frequently (2-3
times a week, now). I
  > >> understand
  > >> that it can be a driver issue, but how can I
possibly track down what
  > >> driver
  > >> is causing it?
  > >>
  > >> The stop codes I got for the error are as
follows:
  > >> 0x00000019
  > >> 0x00000020
  > >> 0xE1B15300
  > >> 0xE1B15460
  > >> 0x0C2C0221
  > >>
  > >> Can anyone help? This is becoming seriously
irritating. I apologize in
  > >> advance if this is the wrong section to post,
but this is the only place
  > >> I
  > >> found any mention of the "bad pool header"
error.

Don’t know if this will help here, but my fixed stopped the BSOD on
two XP SP2 systems. If you have nortons "go back" program loaded
uninstall it.
 
mrJR said:
Don't know if this will help here, but my fixed stopped the
BSOD on two XP SP2 systems. If you have nortons "go back"
program loaded uninstall it. It stopped mine.
Good luck

I’ve been getting the same error, but only when I try to send a fax.
Anyone listening to this thread find a solution to this problem?

- David
 
David,
Did you manage to solve your fax problem? If you did, please share your
solution with me. I've an identical problem.

Ran
 
user1636 said:
David,
Did you manage to solve your fax problem? If you did, please
share your
solution with me. I've an identical problem.

Ran

 > > Don't know if this will help here, but my fixed
stopped the
 > > BSOD on two XP SP2 systems. If you have nortons "go
back"
 > > program loaded uninstall it. It stopped mine.
 > > Good luck

Nope, have not solved this problem. Nice to know I’m not the only one,
though.


- David
 
Don't know if this will help, but a combination of Allsync, and ProcommPlus
caused this to happen on my machine once I uninstalled both pieces of
software the PC came back. Unfortunate, because I use both of these programs
quite a bit.

Christopher Hower
 
christopherhow said:
Don't know if this will help, but a combination of Allsync,
and ProcommPlus
caused this to happen on my machine once I uninstalled both
pieces of
software the PC came back. Unfortunate, because I use both of
these programs
quite a bit.

Christopher Hower

Sadly, I don’t have either of the programs you’ve mentioned on my
machine, so they are not the cause of the fax/BSOD issue, at least
here. I wonder if there is a DLL or driver that these programs have in
common that’s causing the crash....

- David
 
I now cannot boot into safe mode. post stops at
"multi(0)disk(0)rdisk(0)partition(1)\windows\system32\drivers\mup.sys" Any
ideas?
 
Back
Top