Windows BSOD Error 0x000000C2 — BAD_POOL_CALLER Fix

What Does This Error Mean?

The 0x000000C2 blue screen error is called BAD_POOL_CALLER. It means a driver or program made an invalid request to the Windows memory pool. Think of it like someone trying to check out a library book that does not exist. This is almost always caused by a buggy driver or recently installed software.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows Server

Common Causes

A driver is making invalid memory allocation or deallocation requests
Recently installed software is poorly coded and mismanages system resources
A Windows update introduced a driver compatibility issue
Antivirus or security software is interfering with system memory operations
Corrupted Windows system files are causing memory management errors

How to Fix It

Think about what changed recently. Did you install new software, a new driver, or a Windows update? Uninstall or roll back the most recent change.

Go to Settings > Apps > Installed Apps to uninstall software. For drivers, open Device Manager, right-click the device, and choose 'Roll Back Driver.'
Update all your drivers, especially display, network, and USB drivers. Open Device Manager and check each category for devices with yellow warning icons.

You can also visit your computer manufacturer's support page and download their latest driver package.
Temporarily disable your antivirus software and see if the blue screens stop. If they do, your antivirus is the problem.

Some antivirus programs use deep system hooks that conflict with Windows memory management. Consider switching to a different antivirus.
Run the System File Checker. Open Command Prompt as administrator and type 'sfc /scannow' then press Enter.

This scans for and repairs corrupted Windows system files. Restart your computer after it finishes.
Run the DISM repair tool. Open Command Prompt as administrator and type 'DISM /Online /Cleanup-Image /RestoreHealth' then press Enter.

This repairs the Windows system image. It can take 15 to 30 minutes and requires an internet connection.

When to Call a Professional

If BAD_POOL_CALLER keeps happening after trying all the steps below, there may be a deeper system corruption issue. A technician can analyze crash dump files to identify the exact driver or component causing the problem. Diagnostics and repair typically cost $50 to $100.

Frequently Asked Questions

What is the difference between BAD_POOL_HEADER and BAD_POOL_CALLER?

BAD_POOL_HEADER (0x00000019) means the memory pool's tracking data got corrupted. BAD_POOL_CALLER (0x000000C2) means a driver or program made an illegal request to the memory pool. Both are related to memory management, but BAD_POOL_CALLER more directly points to a specific buggy driver or program.

Can I find out which driver is causing this?

Yes, but it requires some technical steps. Open Event Viewer from the Start menu. Look under Windows Logs > System for critical errors around the time of the crash. The error details often mention a specific driver file name like 'xyz.sys.'

Will reinstalling Windows fix this?

It can, but it is a last resort. Try updating drivers and running system file repair tools first. If nothing else works, a clean Windows install will remove any corrupted drivers or software. Make sure to back up your personal files before reinstalling.