In general it is an indication that some hardware device has failed, but not always. it could be anything
But this is one of those categories where it could be just about anything... a bad hard drive, bad memory module, bad driver for any of 67 different devices... just about any hardware problem or driver problem or certain software problems... difficult to tell. So that means you have to go to a lot of work to finger it out. But first, we will guess at the obvious... something in the driver pool. http://support.microsoft.com/default...NoWebContent=1<http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q310/5/27.asp&NoWebContent=1> http://www.osr.com/ddk/ddtools/bccodes_8k9z.htm http://www.microsoft.com/technet/tre...d_stp_czgw.asp<http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/reskit/prmd_stp_czgw.asp> This covers a broad range of problems... including failure of hard drives, memory, USB device, Networks, and so on. Could also be related to old drivers or defective drivers as the error message suggests. To deal with these, you can go to Control Panel -> System -> Hardware -> Device Manager and look for yellow, red, or black flags next to any of the devices.. If there are any flags, that is the device with the problem Do a gurgle search for a program called Verifier, or perhaps “using driver Verifier to identify issues with Windows drivers. Do a gurgle search for a program called Verifier. This will enable you to use Driver Verifier to identify issues with Windows drivers. Driver Verifier is included in Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot. Also see Support.microsoft.com Scan with this program. Select "display existing settings" or "display info about currently verified drivers" and verifier will take a few seconds to build the list and it will show the results of the drivers you selected before the reboot. Now the question is...what to do with the info?? You have no clue, perhaps?. You'll see info about pool allocations failed, pool allocations not tracked, this pool, that pool etc. They will all be over your head. But look for any driver that has "pool allocations failed" or perhaps "faults injected" You may find some use in these articles If you can pull them up. http://support.microsoft.com/default...&Product=winxp<http://support.microsoft.com/default.aspx?scid=kb;en-us;315252&Product=winxp> Debugging http://support.microsoft.com/default...&Product=winxp<http://support.microsoft.com/default.aspx?scid=kb;en-us;818501&Product=winxp> On Tue, Oct 13, 2009 at 9:16 AM, Jeffrey Race <[email protected]> wrote: > Last few days I receive BSOD with diagnostic > BAD_POOL_CALLER > 0x000000C2 0x00000099 0x[varies] 0x00000000 0x00000000 > > googling doesn't readily reveal anything precisely my case and > I don't know enough to differentiate hardware vs software errors. > I'd appreciate any guidance how to interpret the screen error > message, useful references to read, or -- gasp -- even the > answer to my prayers as to what is starting to go wrong > > tks for all help > jeffrey race > > _______________________________________________ > Thinkpad mailing list > [email protected] > http://stderr.org/cgi-bin/mailman/listinfo/thinkpad > _______________________________________________ Thinkpad mailing list [email protected] http://stderr.org/cgi-bin/mailman/listinfo/thinkpad
