BAD_POOL_CALLER (0x000000C2) BSOD Explained: What It Is, Why It Happens, and How to Fix It for Good

The BAD_POOL_CALLER error occurs when a thread in the Windows kernel attempts to make an invalid memory pool request.

When your screen suddenly turns blue and displays the error code 0x000000C2, you're experiencing the BAD_POOL_CALLER Blue Screen of Death (BSOD). This message signals that a critical error has occurred in Windows’ memory management system, and it needs immediate attention.

This guide explains the meaning of the BAD_POOL_CALLER error, its causes, and how to resolve it step by step.

What Is the 0x000000C2 BAD_POOL_CALLER Error?

The BAD_POOL_CALLER error occurs when a thread in the Windows kernel attempts to make an invalid memory pool request. This might mean the process tried to allocate or free memory improperly—such as referencing memory that has already been freed, is unavailable, or accessed at the wrong time.

What’s a “Memory Pool”?

Windows uses memory pools to efficiently manage memory used by the kernel and system drivers. These pools allow short-term memory allocation for system-level processes. If a process mishandles this system memory, Windows forces a stop to prevent further damage.

Common Causes of BAD_POOL_CALLER (0x000000C2)

Here are the most frequent reasons why this BSOD might occur:

1. Faulty or Outdated Drivers

Drivers are the most common source of this error, especially if:

  • They try to access memory that doesn’t belong to them.
  • They’re incompatible with the current Windows version.
  • They’re buggy or not properly signed.

2. Corrupted System Files

Important Windows system files may become corrupted due to:

  • Incomplete software installations
  • Malware infections
  • Power failures or forced shutdowns

3. Faulty RAM or Hardware

Issues with your physical memory (RAM) can cause the system to reference bad memory locations, leading to this stop code.

4. Software Conflicts

Programs that directly interact with system memory—like third-party antivirus, virtualization software, or hardware monitoring tools—can cause BAD_POOL_CALLER errors.

5. Overclocking or Unstable Hardware Configurations

Pushing your CPU, GPU, or memory beyond their intended limits can cause memory access violations.

6. Hard Disk Issues

Disk errors or a failing hard drive can cause the system to load corrupted driver files or system components.

How to Fix BAD_POOL_CALLER (0x000000C2)

Follow these steps in order, from simple to more advanced, to resolve the issue.

1. Restart in Safe Mode

Safe Mode loads Windows with a minimal set of drivers and services.

  • Press Shift + Restart from the login screen → Choose Advanced OptionsStartup Settings → Select Safe Mode with Networking

2. Update or Roll Back Drivers

  • Press Windows + X, select Device Manager
  • Right-click on each major driver (Display, Network, Audio, etc.) → Select Update driver
  • If the problem began after a recent update, choose PropertiesDriver tab → Roll Back Driver

3. Run Windows Memory Diagnostic

To check for faulty RAM:

  • Press Windows + R, type mdsched.exe, hit Enter
  • Choose Restart now and check for problems
    If memory issues are detected, consider replacing the affected RAM module.

4. Check for Disk Errors

Use CHKDSK to scan for disk corruption:

  • Open Command Prompt as Administrator

Type:
bash
CopyEdit
chkdsk /f /r

  • Restart when prompted

5. Scan and Repair System Files

Corrupted Windows system files can be fixed using the SFC and DISM tools:

Open Command Prompt as Administrator and run:
bash
CopyEdit
sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

6. Uninstall Recently Installed Software

  • Go to Settings > Apps > Installed Apps
  • Sort by Install Date and uninstall any programs recently added before the BSOD started—especially system utilities or antivirus tools

7. Disable Overclocking

If your system is overclocked, go into BIOS/UEFI settings and reset CPU, GPU, and RAM to their default speeds.

8. Perform a Clean Boot

This will help isolate third-party conflicts:

  • Press Windows + R, type msconfig
  • On the Services tab, check Hide all Microsoft services → Click Disable All
  • Go to the Startup tab → Open Task Manager → Disable all
  • Restart your PC

9. Install Windows Updates

  • Go to Settings > Windows Update
  • Install all pending security and driver updates

10. Use System Restore

To revert Windows to a known working state:

  • Press Windows + R, type rstrui, press Enter
  • Choose a restore point from before the error began and follow the prompts

Tips to Prevent BAD_POOL_CALLER in the Future

  • Regularly update all drivers, especially network, graphics, and chipset drivers.
  • Avoid aggressive system optimizers or memory management tools from untrusted sources.
  • Use reputable antivirus software and schedule routine scans.
  • Don't overclock unless you understand the risks.
  • Keep your system updated and always shut down properly.

Recommended Tools for Further Diagnostics

  • BlueScreenView – Analyzes minidump files to show what caused the crash.
  • WhoCrashed – Provides readable crash reports for non-technical users.
  • Windows Event Viewer – Useful for spotting driver or system-related events before the crash.

Summary

Key Item

Description

Error Name:

BAD_POOL_CALLER

Stop Code:

0x000000C2

Cause:

Invalid memory pool request by a driver or process

Common Fixes:

Update drivers, scan RAM, check disk, uninstall bad software

Tools to Use:

SFC, DISM, CHKDSK, Memory Diagnostic, System Restore

If you continue experiencing this error after trying all the above, it may point to a deeper hardware problem or failing motherboard. At that point, contacting a PC repair technician or your system manufacturer may be necessary.

Support.Com Can Help!

If you’re still having trouble, consider reaching out to Support.Com for a personalized solution to all technical support issues.