BAD_POOL_CALLER

BAD_POOL_CALLER. A kernel-mode process or driver incorrectly attempted to perform memory
operations. Typically, a faulty driver or buggy software causes this.

The BAD_POOL_CALLER bug check has a value of 0x000000C2. This indicates that the current thread is making a bad pool request.

A Windows 2000-based print server may randomly stop responding (hang) with a "Stop" error message on a blue screen. The stop code is 0x000000C2, and the first parameter is always 0x00000007. When this error occurs, you may not be able to log on until after several "Stop" errors and restarts. The System event log on the server will contain many printing-related error messages.

What may cause BAD_POOL_CALLER error?

When it is processing some kinds of print jobs, Win32k.sys might doubly free a pool. This causes the "Stop" error message.

BAD_POOL_CALLER Windows Error: Solutions and Fixes

To resolve this problem, obtain the latest service pack for Windows 2000.