BAD_POOL_CALLER — Causes & Fix
Windows Stop code 0x000000C2 (BAD_POOL_CALLER) means a driver made an illegal memory-pool request — asking for or freeing kernel memory incorrectly.
- Applies to
- Any Windows PC
- Time to fix
- 30 minutes – 2 hours
What it means
Causes include a faulty driver, corrupt RAM, or damaged system files. This is a Windows Stop error (a "bugcheck" / blue screen) documented by Microsoft. The blue screen shows this code; more detail sits in the crash dump (%SystemRoot%\Minidump), which usually names the specific driver or component at fault — a free tool like BlueScreenView or WinDbg can read it.
Symptoms
- Blue screen citing BAD_POOL_CALLER
- Crashes tied to a specific device/driver
How to fix it
- 1
Update the offending driver
1. Identify the driver in the dump and update or roll it back.
- 2
Test RAM / repair files
1. Run Windows Memory Diagnostic. 2. Run "sfc /scannow" and DISM.
Frequently asked questions
0xC2 vs 0x19?
Both are memory-pool corruption. 0xC2 (BAD_POOL_CALLER) blames a driver that misused the pool; 0x19 is a corrupt pool header. Fixes overlap: update drivers and test RAM.
Last updated July 20, 2026
Guidance only — always consult a qualified professional or the official service manual before carrying out repairs.