Bad_Pool_Header 0x019 BSOD

We are having an issue on a laptop were the computer is frequently recieving a BSOD. It is a Windows XP machine on an SBS2008 domain.

The BSODs have all been Bad_Pool_Header 0x019. They have happened randomly while working in Excel, powerpoint, and printing from IE. It can be caused by clicking on the Font portion of Word or Excel.

I have analyzed the minidump files using WinDbg but am not an expert at it.
What I have seen using the !analyze -v is that the pool header is already corrupt at the time of the current request. The pool_address is different in each dump file but it always points to Pooltag Gpff : GDI physical font file.

We have tried repairing office, and recreating the page file by setting it to not use one and then setting it to the recommended size.

I am attaching the dump files and the notes i have on this case.

Thanks for your help,
Who is Participating?

Improve company productivity with a Business Account.Sign Up

klilerConnect With a Mentor Author Commented:
The issue has been resolved. It was a printer that had been installed a little while before the issue started happening. Deleted it and the issue went away. We were just getting ready to do a format and reload so happy to find that.

Thanks for the help and suggestions.

I'm not an expert on analyzing a minidump file either. Mostly because when ever I have a BSOD problem, 90% of the time it's a problem with a memory module. If you can duplicate it, I would try the good old "simple" memory test by removing one memory module at a time and try to duplicate it.
PrecifijoConnect With a Mentor Commented:
You can also try running sfc /scannow  if the previous suggestion does not work.
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

dbruntonConnect With a Mentor Commented:
Try rebuilding your font cache.


Windows Font Cache (Windows 2000/XP/Vista)
The Windows operating system has a font cache file that is located here:
Delete this file, and restart your system. A new FNTCACHE.DAT file will be created on startup.
klilerAuthor Commented:
We've run the SFC /scannow and reset the Font cache with no change (selecting the font dropown in Excel BSODs the machine).

A hardware memory test is currently running.
Good. I'm almost certain that it's being caused by bad memory. However, if that's not the case, you need to read the following article:

Your minidump seems to point to the win32k.sys driver.  
klilerAuthor Commented:
The memory test has completed two passes without errors.

Any additional steps we can try?

did you read the article I posted on my previous comment?

Try installing a font viewer.  Here is one you can use as shareware  (just don't exceed the time limit of the font)

Use whichever font viewer you get and see if it can handle all of the fonts.  I'm still tempted to think that this is a font problem due to where the debug is pointing and the Excel font problems.

You don't have a huge amount of fonts in your font directory by any chance do you?
klilerAuthor Commented:
klilerAuthor Commented:
Issue causing bluescreens was a Kyocera driver.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.