Microsoft KB Archive/824281

= BAD_POOL_CALLER Stop 0xC2 Error Occurs When You Print in Windows 2000 =

Article ID: 824281

Article Last Modified on 10/26/2006

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Advanced Server

-





SYMPTOMS
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



CAUSE
This problem may occur when the document contains a bad or a corrupted embedded font.



Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
No prerequisites are required.

Restart Requirement
You must restart your computer after you apply this hotfix.

Hotfix Replacement Information
This hotfix does not replace any other hotfixes.

File Information
The 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



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.



MORE INFORMATION
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:

816915 New Naming Schema for Microsoft Windows Hotfix Packages

Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB824281

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.