0x000000C2_
Bad Pool Caller
If your Windows 10/11 machine is throwing 0x000000C2, the system has flagged a fault identified as "Bad Pool Caller". Understanding the root cause helps you avoid an unnecessary reinstall.
What Actually Happened
Windows kernel halted due to: a kernel-mode process or driver incorrectly performed a memory pool operation.
Symptoms
Blue screen appears with stop code BAD_POOL_CALLER
Common Causes
- Kernel condition: a kernel-mode process or driver incorrectly performed a memory pool operation
- Outdated or conflicting third-party driver
- Overheating or failing hardware (RAM/SSD)
How to Fix It
-
01
Boot into Safe Mode and roll back recently installed drivers
-
02
Run memory diagnostic:
mdsched.exe -
03
Run system scan:
sfc /scannow && DISM /Online /Cleanup-Image /RestoreHealth
System Administrator Emergency Kit
Stop searching for syntax under pressure. Get 100+ verified, battle-tested emergency recovery commands for Windows & Linux in one printable PDF guide.
Root Cause Breakdown
Stop code BAD_POOL_CALLER (0x000000C2) triggered a bugcheck to protect memory integrity.
Should You Worry?
Urgent. Save work frequently to avoid data loss.
Power-User Tip
Check minidump logs in C:\Windows\Minidump to identify the failing .sys file.
Software fix: $0; Hardware replacement: $50�$250