Re: BAD_POOL_HEADER blue screen of death
- From: "jjjjj" <j@xxxxx>
- Date: Mon, 4 Jul 2005 00:28:56 -0400
The "pool" referred to is a memory pool. It is possible that the memory is
causing the problem....
Take it out and see if the problem goes away. Can you reproduce it at will?
What steps cause the error to be thrown?
"Harvey" <Harvey@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:071168FA-E783-4296-B166-DDAA62CE1B2E@xxxxxxxxxxxxxxxx
>
> Thanks Ron:
>
> > When requesting assistance with STOP message please include the STOP
> > code and all 4 parameters as well as any file or module names that may
> > be mentioned in the message.
>
> Here's some stuff I copied down one time it happened.
>
> STOP 0x00000019 (0x00000020, 0x857D9000, 0x857D90E0, 0xA1C0000)
>
> Do you find that helpful? <G>
>
> It also dumped over 100 pages of physical memory to disc. I have no idea
> where the dump is, or what to do with it if I found it.
>
> Also, I installed no new hardware, except for some more memory. Is it
> possible that could cause the problem? I don't even know what a "pool
header"
> is!
>
> Harvey
> >
> > Here is a MSDN article with regard to this error in Windows 2000. It
> > would apply equally to Windows XP.
> >
> > "If this is the first time you have booted after installing new
> > hardware, remove the hardware and boot again. Check the Microsoft
> > Hardware Compatibility List to verify that the hardware and its
> > drivers are compatible with Windows 2000. For information about the
> > hardware, contact the supplier. If you are installing Windows 2000 for
> > the first time, check the Windows 2000 system requirements, including
> > the amount of RAM and disk space required to load the operating
> > system. Also, check the Hardware Compatibility List to verify that the
> > system can run Windows 2000. If Windows 2000 is loaded and no new
> > hardware has been installed, reboot with recovery options set to
> > create a dump file. If the message continues to appear, select the
> > Last Known Good option when you reboot."
> >
> > Also make certain that the Error Reporting option is enabled and that
> > you submit the error report for this item to Microsoft. There may be
> > a known solution that is not yet published in the Knowledge Base, and
> > the error reporting tool will get this for you. The error reporting
> > settings can be accessed via Control Panel - System - Advanced. Click
> > on the Error Reporting button in the bottom right corner of the
> > window. Enable it, at least until this problem is checked out, for
> > both Windows and Programs (all of them).
> >
> > Good luck
> >
> >
> > Ron Martell Duncan B.C. Canada
> > --
> > Microsoft MVP
> > On-Line Help Computer Service
> > http://onlinehelp.bc.ca
> >
> > In memory of a dear friend Alex Nichol MVP
> > http://aumha.org/alex.htm
> >
.
- References:
- BAD_POOL_HEADER blue screen of death
- From: Harvey
- Re: BAD_POOL_HEADER blue screen of death
- From: Ron Martell
- Re: BAD_POOL_HEADER blue screen of death
- From: Harvey
- BAD_POOL_HEADER blue screen of death
- Prev by Date: Re: "Open With" broken in context menu
- Next by Date: Re: svchost consumes 100% of CPU on startup
- Previous by thread: Re: BAD_POOL_HEADER blue screen of death
- Next by thread: Re: Mouse keeps freezing
- Index(es):