kliler
asked on
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,
Grant
Minidump.zip
Tammy-s-BSOD-notes.docx
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
Precifijo
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
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:
http://support.microsoft.com/kb/834450
Your minidump seems to point to the win32k.sys driver.
http://support.microsoft.com/kb/834450
Your minidump seems to point to the win32k.sys driver.
ASKER
The memory test has completed two passes without errors.
Any additional steps we can try?
Thanks!
Any additional steps we can try?
Thanks!
did you read the article I posted on my previous comment?
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
'
ASKER
Issue causing bluescreens was a Kyocera driver.