Article ID: 824281 - View products that this article applies to.
When you try to print a document in Windows 2000 or open a document in Windows Explorer, you may receive the following Stop error message:
BAD_POOL_CALLER Stop 0xC2
This problem may occur when the document contains a bad or a corrupted embedded font.
Hotfix InformationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesNo prerequisites are required.
Restart RequirementYou must restart your computer after you apply this hotfix.
Hotfix Replacement InformationThis hotfix does not replace any other hotfixes.
File InformationThe English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date Time Version Size File name ---------------------------------------------------------- 16-Jul-2003 22:13 5.0.2195.6738 42,256 Basesrv.dll 16-Jul-2003 22:13 5.0.2195.6762 222,992 Gdi32.dll 16-Jul-2003 22:13 5.0.2195.6741 711,440 Kernel32.dll 16-Jul-2003 22:13 5.0.2195.6751 333,072 Msgina.dll 15-Jul-2003 20:08 5.0.2195.6776 4,858,368 Sp3res.dll 16-Jul-2003 22:13 5.0.2195.6766 380,176 User32.dll 16-Jul-2003 22:13 5.0.2195.6745 385,808 Userenv.dll 16-Jul-2003 22:13 5.0.2195.6775 243,984 Winsrv.dll 17-Jan-2003 14:06 5.0.2195.6656 236,304 Cmd.exe 08-Jul-2003 21:26 5.0.2195.6770 182,032 Winlogon.exe 08-Apr-2003 03:54 5.0.2195.6701 90,232 Rdpwd.sys 16-Jul-2003 21:32 5.0.2195.6784 1,628,784 Win32k.sys 16-Jul-2003 22:13 5.0.2195.6741 711,440 Kernel32.dll 16-Jul-2003 22:13 5.0.2195.6775 243,984 Winsrv.dll 16-Jul-2003 22:13 5.0.2195.6784 1,628,784 Win32k.sys
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/816915/ )New Naming Schema for Microsoft Windows Hotfix Packages
Article ID: 824281 - Last Review: January 26, 2012 - Revision: 4.0