How to Fix ‘BAD_POOL_CALLER’ (0x000000C2) in Windows 11

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.

  1. Press Win + X and open Event Viewer.
  2. Navigate to Windows Logs > System and locate the latest BugCheck (Event ID 1001) event.
  3. 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.
  4. 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.

  1. Press Win + X and select Device Manager.
  2. Expand key hardware categories: Network adapters, Sound, video and game controllers, and Display adapters.
  3. Right-click devices and select Properties > Driver.
  4. If the blue screen began after a recent update, click Roll Back Driver.
  5. 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.

  1. Press Win + R, type mdsched.exe, and press Enter.
  2. Select Restart now and check for problems (recommended).
  3. 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.

  1. Press Win + R, type sysdm.cpl, and press Enter to open System Properties.
  2. Go to the Advanced tab and click Settings under Performance.
  3. Switch to the Advanced tab and click Change under Virtual memory.
  4. Uncheck Automatically manage paging file size for all drives.
  5. Select No paging file, click Set, and restart your computer.
  6. 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.

  1. Open Command Prompt (Admin).
  2. Execute:
    DISM /Online /Cleanup-Image /RestoreHealth
    sfc /scannow
  3. 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.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.