Windows 7 / Getting Started

---

Stop 0xC2 or BAD_POOL_CALLER

The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:

• By allocating a memory pool size of zero bytes
• By allocating a memory pool that does not exist
• By attempting to free a memory pool that is already free
• By allocating or freeing a memory pool at an IRQL that was too high

This Stop message is typically the result of a faulty driver or software.

Interpreting the Message

Table below describes the information provided by Stop 0xC2 messages. The value of the first parameter indicates the type of violation (see the Description column) and determines the meaning of the next three parameters.

Table below Parameter Listings for Stop Message 0xC2

Parameter 1	Parameter 2	Parameter 3	Parameter 4	Description
0x00	This value is always 0	The pool type being allocated	The pool tag being used	The caller is requesting a zero-byte pool allocation
0x01, 0x02, or 0x04	Pointer to pool header	First part of pool header contents	This value is always zero	Pool header has been corrupted
0x06	Reserved	Pointer to pool header	Pool header contents	Attempt to free a memory pool that was already freed
0x07	Reserved	Pointer to pool header	This value is always zero	Attempt to free a memory pool that was already freed
0x08	Current IRQL	Pool type	Size of allocation	Attempt to allocate pool at invalid IRQL
0x09	Current IRQL	Pool type	Address of pool	Attempt to free pool at invalid IRQL
0x40	Starting address	Start of system address space	This value is always zero	Attempt to free usermode address to kernel pool
0x41	Starting address	Physical page frame	Highest physical page frame	Attempt to free a nonallocated nonpaged pool address
0x42 or 0x43	Address being freed	This value is always zero	This value is always zero	Attempt to free a virtual address that was never in any pool
0x50	Starting address	Start offset in pages from beginning of paged pool	Size in bytes of paged pool	Attempt to free a nonallocated paged pool address
0x99	Address being freed	This value is always zero	This value is always zero	Attempt to free pool with invalid address or corruption in pool header
0x9A	Pool type	Size of allocation in bytes	Allocation's pool tag	Attempt to allocate must succeed

Resolving the Problem

The following suggestions are specific to Stop 0xC2 errors. For additional troubleshooting suggestions that apply to all Stop errors, see the section titled "Stop Message Checklist" later in this tutorial.

• A Stop 0xC2 message might occur after you install a faulty device driver, system service, or firmware. If a Stop message lists a driver by name, disable, remove, or roll back that driver to correct the problem. If disabling or removing drivers resolves the issues, contact the manufacturer about a possible update. Using updated software is especially important for multimedia applications, antivirus scanners, DVD playback, and CD mastering tools.
• A Stop 0xC2 message might also be due to failing or defective hardware. If a Stop message points to a category of devices (such as disk controllers, for example), try removing or replacing the hardware to determine whether it is causing the problem.
• If you encounter a Stop 0xC2 message while upgrading to Windows, the problem might be due to an incompatible driver, system service, virus scanner, or backup. To avoid problems while upgrading, simplify your hardware configuration and remove all third-party device drivers and system services (including virus scanners) prior to running setup. After you have successfully installed Windows, contact the hardware manufacturer to obtain compatible updates.

More Info For more information about Stop 0xC2 messages, see the Knowledge Base at http://support.microsoft.com/. Search the Knowledge Base using the keywords 0x000000C2 and 0xC2.