An unexpected blue screen crash displaying the stop code: ‘BAD_POOL_CALLER’ or bug check code 0x000000C2 halts Windows 11 during normal operation. In Windows operating system architecture, the kernel manages two dynamic memory pools: the paged pool (virtual memory that can be swapped to disk) and the non-paged pool (physical RAM reserved for high-priority kernel threads and drivers). When a kernel-mode program or device driver issues an invalid memory request—such as attempting to free memory that has already been deallocated, accessing non-existent pool addresses, or freeing memory at an illegal IRQL—the memory manager halts immediately to prevent corruption.
What Causes BAD_POOL_CALLER in Windows 11?
Bug check 0x000000C2 indicates that a kernel component has violated memory pool allocation rules. Common triggers include:
- Buggy Third-Party Device Drivers: Audio, Wi-Fi, or graphics drivers containing double-free memory bugs or deallocating unallocated pool blocks.
- Defective Hardware RAM: Corrupted physical memory cells failing to maintain pool allocation headers.
- Aggressive Antivirus Kernel Filters: Low-level security software corrupting pool headers during deep packet inspection.
- Corrupted Windows Virtual Memory Paging File: Bad sectors or corruption within
pagefile.sys. - Outdated Motherboard BIOS / Chipset Drivers: Incompatible memory controller microcode causing memory timing desynchronisation.
Step 1: Check Parameter 1 in Event Viewer
The first parameter of bug check 0x000000C2 pinpoints the exact nature of the memory pool violation.
- Press Win + X and open Event Viewer.
- Navigate to Windows Logs > System and locate the latest BugCheck (Event ID 1001) event.
- Inspect Parameter 1:
0x00000007: Attempted to free a pool allocation that was already freed (double-free).0x00000009: Attempted to free pool memory that was not allocated.0x00000041: Corrupted pool header detected.0x0000000A: Attempted to free a pool allocation at an invalid IRQL.
- Parameter 2 often contains the starting address of the pool block, helping identify the offending driver via minidump analysis.
Step 2: Update or Roll Back Problematic Device Drivers
Faulty drivers are the primary culprit behind pool allocation faults.
- Press Win + X and select Device Manager.
- Expand key hardware categories: Network adapters, Sound, video and game controllers, and Display adapters.
- Right-click devices and select Properties > Driver.
- If the blue screen began after a recent update, click Roll Back Driver.
- Otherwise, install the latest certified WHQL drivers directly from the hardware vendor.
Step 3: Test Hardware Memory Using Windows Memory Diagnostic
Physical memory degradation can corrupt pool headers in RAM.
- Press Win + R, type
mdsched.exe, and press Enter. - Select Restart now and check for problems (recommended).
- Wait for the multi-pass memory test to finish. If errors are identified, replace defective RAM sticks.
Step 4: Recreate the Windows Paging File (pagefile.sys)
Purging a corrupted virtual memory paging file eliminates paged pool corruption.
- Press Win + R, type
sysdm.cpl, and press Enter to open System Properties. - Go to the Advanced tab and click Settings under Performance.
- Switch to the Advanced tab and click Change under Virtual memory.
- Uncheck Automatically manage paging file size for all drives.
- Select No paging file, click Set, and restart your computer.
- After rebooting, return to the same menu and re-enable Automatically manage paging file size.
Step 5: Run System File Checker and DISM Repairs
Verifying kernel binaries ensures core operating system libraries are uncorrupted.
- Open Command Prompt (Admin).
- Execute:
DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow - Allow the scan to complete and restart Windows 11.
Updating faulting drivers, testing physical RAM, recreating the paging file, and repairing system files eliminates BAD_POOL_CALLER crashes in Windows 11.