?
Solved

Bad_Pool_Header 0x019 BSOD

Posted on 2011-02-10
11
Medium Priority
?
2,420 Views
Last Modified: 2012-05-11
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,
Grant
Minidump.zip
Tammy-s-BSOD-notes.docx
0
Comment
Question by:kliler
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
  • 2
11 Comments
 
LVL 5

Expert Comment

by:Precifijo
ID: 34865914
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.
0
 
LVL 5

Assisted Solution

by:Precifijo
Precifijo earned 400 total points
ID: 34865931
You can also try running sfc /scannow  if the previous suggestion does not work.
0
 
LVL 49

Assisted Solution

by:dbrunton
dbrunton earned 400 total points
ID: 34866017
Try rebuilding your font cache.

From http://forums.quark.com/t/15314.aspx

Windows Font Cache (Windows 2000/XP/Vista)
The Windows operating system has a font cache file that is located here:
C:\Windows\System32\FNTCACHE.DAT
Delete this file, and restart your system. A new FNTCACHE.DAT file will be created on startup.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:kliler
ID: 34868107
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.
0
 
LVL 5

Expert Comment

by:Precifijo
ID: 34868198
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:

http://support.microsoft.com/kb/834450

Your minidump seems to point to the win32k.sys driver.  
0
 

Author Comment

by:kliler
ID: 34868325
The memory test has completed two passes without errors.

Any additional steps we can try?

Thanks!
0
 
LVL 5

Expert Comment

by:Precifijo
ID: 34871872
did you read the article I posted on my previous comment?
0
 
LVL 49

Expert Comment

by:dbrunton
ID: 34875969
Hmm.

Try installing a font viewer.  Here is one you can use as shareware http://www.mindworkshop.com/fontrang.html  (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?
0
 

Accepted Solution

by:
kliler earned 0 total points
ID: 34899860
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.

Grant
0
 

Author Comment

by:kliler
ID: 34899947
'
0
 

Author Closing Comment

by:kliler
ID: 34936444
Issue causing bluescreens was a Kyocera driver.
0

Featured Post

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Ok I have been working on this for some time having learned and gained certification in XenDesktop 4 along came version 5 which was released last month. Since then I have been working to deploy XenDesktop 5 in a small environment with only 2 virt…
It is only natural that we all want our PCs to be in good working order, improved system performance, so that is exactly how programs are advertised to entice. They say things like:            •      PC crashes? Get registry cleaner to repair it!    …
Two types of users will appreciate AOMEI Backupper Pro: 1 - Those with PCIe drives (and haven't found cloning software that works on them). 2 - Those who want a fast clone of their boot drive (no re-boots needed) and it can clone your drive wh…
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Suggested Courses

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question