BAD_POOL_CALLER (0xC2) in Windows 11: 8 Ways to Fix It

The BAD_POOL_CALLER (0xC2) error is a Blue Screen of Death (BSOD) in Windows 11 that can suddenly restart your PC and display a stop code. You may encounter it while using Windows normally, installing software, playing games, connecting a device, or shortly after starting the computer. The error indicates that Windows detected an invalid request involving the kernel memory pool, which is an area of memory used by Windows and device drivers. A faulty or incompatible driver is a common cause, but damaged system files, memory problems, recently installed hardware, or problematic software can also trigger the crash. In this guide, we’ll explain why BAD_POOL_CALLER (0xC2) occurs in Windows 11 and show you practical ways to troubleshoot and fix the BSOD.

Why Does BAD_POOL_CALLER (0xC2) Occur in Windows 11?

Windows uses a kernel memory pool to provide memory to system components and device drivers. The BAD_POOL_CALLER stop code appears when Windows detects that a component has made an invalid memory request or otherwise corrupted information associated with the memory pool.

Common causes include:

• Faulty or incompatible drivers: A problematic graphics, network, storage, USB, or other device driver can cause invalid memory operations.
• Recently updated drivers: A new driver version may introduce compatibility issues.
• Defective RAM: Faulty or unstable memory can corrupt data used by Windows and lead to BSODs.
• Recently installed hardware: New hardware or its driver may not work correctly with the system.
• Corrupted Windows system files: Damaged system components can cause unexpected kernel-level errors.
• Problematic software: Some antivirus, system utilities, virtualization tools, and other low-level applications can interact with Windows components and trigger crashes.
• Overclocking or unstable hardware settings: Changes to CPU or RAM settings can make the system unstable.
• Windows update or system changes: A recent update can expose a compatibility problem with an existing driver or application.

Because the error can have several causes, it is better to start with recent changes and driver-related troubleshooting before moving to hardware diagnostics.

1. Disconnect Recently Added Hardware

If BAD_POOL_CALLER (0xC2) started after you connected a new device or installed hardware, that device or its driver may be involved in the crash.

1. Shut down your Windows 11 PC.
2. Disconnect recently added external devices, such as:
   • USB drives
   • Printers
   • Webcams
   • External storage
   • USB hubs
   • Game controllers
   • Other recently connected peripherals
3. Start the PC again.
4. Use Windows normally for a while and check whether the blue screen returns.

If the system becomes stable after removing a particular device, reconnect devices one at a time to identify which one is causing the problem.

2. Update or Roll Back Device Drivers

A faulty, incompatible, or recently updated driver is a common cause of BAD_POOL_CALLER (0xC2). Graphics, network, storage, USB, and other hardware drivers can all cause kernel-level crashes when they do not work correctly with Windows 11.

Update a driver

1. Press Windows + X and select Device Manager.
2. Expand the category related to the hardware you recently changed or suspect.
3. Right-click the device and select Update driver.
4. Choose Search automatically for drivers.
5. Install an available update and restart Windows.

For important hardware such as graphics or chipset devices, you can also check the PC or hardware manufacturer’s website for the latest Windows 11-compatible driver.

Roll back a recently updated driver

If the blue screen started immediately after a driver update:

1. Open Device Manager.
2. Right-click the affected device and select Properties.
3. Open the Driver tab.
4. Select Roll Back Driver if the option is available.
5. Restart the PC.

If you cannot identify the problematic device, start with drivers that were updated shortly before the first 0xC2 crash.

3. Run System File Checker

Corrupted or missing Windows system files can contribute to BSODs, including BAD_POOL_CALLER (0xC2). Windows includes the System File Checker (SFC) tool to scan protected system files and replace damaged copies when possible.

1. Press Windows + S and search for Command Prompt.
2. Right-click Command Prompt and select Run as administrator.
3. Enter:

sfc /scannow

4. Press Enter.
5. Wait for the scan to reach 100%.
6. Restart your PC after the scan finishes.

If SFC reports that it could not repair some files, run the DISM repair command before running SFC again:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run:

sfc /scannow

Then restart Windows 11 and check whether the BAD_POOL_CALLER blue screen continues.

4. Check Your RAM for Errors

Defective or unstable RAM can cause unpredictable Windows crashes, including BAD_POOL_CALLER (0xC2). Windows 11 includes Windows Memory Diagnostic, which can check your system memory for errors.

Steps

1. Press Windows + R. Type: mdsched.exe Press Enter.
2. Select Restart now and check for problems (recommended).
3. Windows will restart and perform a memory test.
4. Wait for the test to finish and allow Windows to start again.

If Windows reports memory errors, the RAM may be defective, improperly seated, or unstable. If your PC has multiple RAM modules, testing them individually can help identify a problematic module, but only do this if you are comfortable working with PC hardware.

If you recently changed RAM or enabled memory overclocking such as XMP/EXPO, return the memory settings to their default values and check whether the BSOD stops.

5. Uninstall Recently Installed Software or Updates

If BAD_POOL_CALLER (0xC2) started shortly after installing a program, driver, or Windows update, that recent change may be responsible. Software that installs low-level components, such as security tools, hardware utilities, or system-management programs, can sometimes affect Windows kernel operations.

Uninstall a recently installed app

1. Press Windows + I to open Settings.
2. Go to Apps > Installed apps.
3. Sort the list by Date installed.
4. Find the application installed shortly before the BSOD started.
5. Click the three dots (⋯) next to it.
6. Select Uninstall.
7. Restart Windows and check whether the problem returns.

Remove a recent Windows update

If the crashes started immediately after a Windows update, you can remove the latest quality update:

1. Open Settings > Windows Update > Update history.
2. Select Uninstall updates.
3. Find the recent quality update.
4. Click Uninstall.
5. Restart the PC.

Avoid removing an update simply because it is recent. This step is most useful when the update timing closely matches the onset of the 0xC2 crashes.

6. Check Third-Party Security Software

Some antivirus programs, firewall tools, system optimizers, hardware monitoring utilities, and similar applications install components that operate closely with the Windows kernel. If one of these components is incompatible or corrupted, it can contribute to BAD_POOL_CALLER (0xC2) crashes.

1. Think about whether you recently installed or updated a third-party security or system utility.
2. Open Settings > Apps > Installed apps.
3. Find the recently installed or updated program.
4. Uninstall it if you suspect it coincides with the start of the BSOD.
5. Restart Windows 11.
6. Use the PC normally and check whether the blue screen returns.

If you use third-party antivirus software, Windows Security can provide basic built-in protection while you troubleshoot.

If the problem disappears after removing a particular application, check the software manufacturer’s website for a newer Windows 11-compatible version before reinstalling it.

7. Start Windows 11 in Safe Mode

Safe Mode starts Windows with a limited set of drivers and services. If the BAD_POOL_CALLER (0xC2) blue screen stops occurring in Safe Mode, a third-party driver, service, or startup application becomes more likely to be involved.

1. Press Windows + R.
2. Type msconfig and press Enter.
3. Open the Boot tab.
4. Select Safe boot and choose Minimal.
5. Click Apply and OK.
6. Select Restart.

Windows will start in Safe Mode.

Use the PC for a while and check whether the BSOD occurs again. If the problem does not appear in Safe Mode, review recently installed drivers and startup applications.

Return to normal Windows

After testing:

1. Press Windows + R, type msconfig and press Enter.
2. Open the Boot tab and Clear Safe Boot.
3. Click Apply > OK.
4. Restart the PC.

If Windows is already crashing before you can reach the desktop, you can enter the Windows Recovery Environment and use Troubleshoot > Advanced options > Startup Settings to enable Safe Mode.

8. Use System Restore

If BAD_POOL_CALLER (0xC2) started after a recent driver, software installation, or system change, System Restore can return Windows 11 to an earlier restore point.

System Restore changes system files, drivers, installed programs, and system settings, but it normally does not remove your personal files such as documents, photos, or other personal data.

Steps

1. Press Windows + R.Type: rstrui.exe Press Enter.
2. Select Choose a different restore point if available.
3. Select a restore point created before the BAD_POOL_CALLER crashes started.
4. Click Next. Review the changes and select Finish.
5. Allow Windows to restart and complete the restoration.

If Windows cannot start normally, open Windows Recovery Environment and go to Troubleshoot > Advanced options > System Restore.

After the restoration is complete, use Windows normally and check whether the 0xC2 blue screen returns.

Frequently Asked Questions

Restart Your Computer

Sometimes, a simple reboot can resolve temporary system glitches that cause BSOD errors. Restarting your computer clears temporary cache, resets system processes, and can fix minor memory allocation issues. If the error does not reappear after rebooting, it may have been caused by a temporary system hiccup. However, if the BSOD returns, further troubleshooting is needed.

Disconnect External Devices

Faulty peripherals such as USB drives, external hard drives, or printers can cause BSODs. Try removing all external devices and restart your computer. If the issue does not occur again, reconnect each device one at a time to determine which one is causing the problem. If you identify a faulty device, try updating its drivers or replacing it.

Boot into Safe Mode

If Windows frequently restarts with a blue screen and you are unable to access it to perform troubleshooting steps, then you need to boot Windows into Safe Mode.

Safe mode is a diagnostic mode of a computer that enables users of Windows 10 to enter an altered version of windows and correct any problems that may be preventing them from entering booting up normally. safe mode different from the normal operating mode in that it uses default drivers and setting upon startup and only system required software programs are loaded upon startup.

Disable Fast Startup

Fast Startup helps your computer boot faster but can sometimes cause memory allocation conflicts, leading to BSOD errors. Disabling it can help stabilize the system.

• Press Win+X at the same time. Select Power Options on the pop-up menu.
• Select Choose what the power button does in the left panel
• Click Change settings that are currently unavailable.
• Uncheck the box next to Turn on fast startup (recommended) and click the Save Changes button.
• Restart your PC and check if the issue persists.

Update Drivers and Windows

Outdated or incompatible drivers can cause memory-related issues. When drivers are outdated, they may not function properly with the latest Windows updates, leading to system crashes. Updating your drivers ensures that your hardware communicates correctly with the operating system, reducing the risk of BSOD errors.

1. Press Win + X and select Device Manager.
2. Expand Display adapters, Network adapters, and Storage controllers.
3. Right-click each device and select Update driver.
4. Choose Search automatically for drivers.
5. If Windows does not find a newer driver, visit the manufacturer’s website to download and install the latest version manually.
6. Restart your PC and check if the issue is resolved.

Run Windows Memory Diagnostic Tool

The error would also occur due to faulty RAM. The RAM may be stuck with dust. Take it out and do some cleaning. If the error still can’t be resolved, you might need to replace it with a new one. Take your PC to the repair store near you if you are not comfortable fixing RAM issue.

Sometimes, this error may be caused by a memory problem. So you should run the built-in Windows Memory Diagnostic Tool to find out memory problems and fix the bad pool header. To run the Memory Diagnostic Tool, follow the steps below.

• At first, click on the start button search and type memory.
• You will see Windows Memory Diagnostic on the start menu search 
• Click on it. This will open the Memory Diagnostic tool. Here, you will see two options.

• select “Restart now and check for problems (Recommended)“. This will restart Windows and check for memory Errors
• Windows will automatically detect any memory related problems.
• Once completed, check the results in the Event Viewer under Windows Logs > System. If memory issues are detected, consider replacing your RAM modules.

Run SFC and DISM Commands

Corrupt system files can trigger BSOD errors. Running System File Checker (SFC) and Deployment Image Servicing and Management (DISM) commands can repair damaged files and restore system integrity.

• Open Command Prompt as Administrator.
• Run the command sfc /scannow to scan and fix corrupted files
• Next, run the DISM command DISM /Online /Cleanup-Image /RestoreHealth to repair Windows image health.
• Once the scanning is complete 100% Restart your computer and check if the issue is resolved.

Disable Indexing Service / Windows Search

Also, disabling the Indexing Service (if running) can fix a bad pool header BSOD Error. This will Fix Issues between drivers/software and Microsoft’s Indexing Service.

• First, press Windows + R, type services.msc, and press Enter.
• Once in the Services window opens, scroll down look for Indexing Service
• Right-click on the Indexing Service, select Properties,

Now stop the service if it’s running. From Service Status, click Apply, then OK to save changes, and follow the steps below.

Check disk Errors using CHKDSK

A failing hard drive can lead to data corruption and BSOD errors. Running the CHKDSK command can scan and repair disk-related issues.

• Open the Command Prompt as administrator,
• Now, type the command chkdsk c:  /f /r /x and press Enter.

command explained: Here command CHKDSK for check hard disk, C: is your system installed drive letter /F for force /R for Repair and /x for forcefully dismount the drive.

• Type Y and press Enter to schedule a scan on the next restart.
• Restart your PC and allow the scan to complete.
• If errors are found, Windows will attempt to repair them.
• If the disk is failing, consider replacing your hard drive or SSD.

If none of the above solutions work, consider resetting Windows to its default settings. This will remove problematic files and software while giving you the option to keep your personal data.