You were just using your PC normally, maybe gaming, browsing, or finishing up some work, and then out of nowhere your screen goes blue. "BAD_POOL_CALLER." Your computer restarts, you log back in, and you're left wondering what on earth just happened. If this sounds familiar, you're in the right place. I've helped hundreds of people work through this exact error, and the good news is that it's almost always fixable, often without any professional help.

In this guide, I'll walk you through exactly what BAD_POOL_CALLER means, why it tends to hit suddenly, and how to track it down and squash it step by step. We'll start with the quick, easy fixes and work our way up to the more advanced tools if we need them. By the time you're done reading, you'll either have solved the problem or have a very clear picture of what's causing it.

What Is BAD_POOL_CALLER, Exactly?

Before we dive into fixes, let's spend a minute understanding what this error actually means, because knowing the "why" makes the fix make a lot more sense.

Windows uses a memory management system called the "pool." Think of it like a shared memory warehouse where drivers and system processes can check out blocks of memory when they need them and check them back in when they're done. The kernel pool has two main sections: the paged pool (memory that can be swapped to disk) and the non-paged pool (memory that must always stay in RAM).

A BAD_POOL_CALLER error, officially Stop Code 0x000000C2, happens when a process or driver makes an illegal request to that memory pool. This could mean it's trying to allocate a block of memory with invalid parameters, free a block it doesn't own, or corrupt pool header information. The moment Windows detects this kind of invalid operation, it panics and crashes rather than let the corruption spread to critical system data. That's actually the crash doing its job, protecting you from something worse.

The reason it feels so "sudden" is that it often isn't triggered by the crash itself, it's triggered by a driver or hardware component that's been quietly misbehaving and just finally crossed a line Windows couldn't ignore. Something changed recently: a driver update, a new piece of hardware, a Windows update, or even just a gradual hardware degradation that finally hit a tipping point.

Common Causes of BAD_POOL_CALLER

This error has a fairly predictable set of culprits. Understanding which category you're dealing with helps you prioritize your troubleshooting:

Faulty or Incompatible Drivers

This is the single most common cause, and it accounts for probably 60–70% of BAD_POOL_CALLER cases I've seen. Drivers run in kernel mode, which means a buggy driver has direct access to the memory pool. A recently updated driver, especially for your GPU, network adapter, or audio device, is a prime suspect if the crashes started shortly after the update.

Defective RAM

Bad memory is a classic cause of pool corruption errors. If a RAM stick has a bad cell, it can flip bits in pool header data, causing Windows to see what looks like an illegal operation. Crashes from bad RAM tend to be somewhat random, they might happen during memory-intensive tasks or just randomly throughout the day.

Corrupted System Files

Windows system files or the Windows Registry can become corrupted after a failed update, an unexpected shutdown, or even a minor disk error. Corrupted system drivers fall into this bucket too.

Malware

Certain types of malware, particularly rootkits, operate at the kernel level and can absolutely cause pool corruption. If your crashes started without any hardware or software changes, malware is worth checking early.

Storage Device Issues

A failing hard drive or SSD can cause data to be read incorrectly from disk, including driver and system files that get loaded into pool memory. This can manifest as BAD_POOL_CALLER even though the root cause is storage.

Overclocking

If you've been running an overclocked CPU, GPU, or RAM, instability from that overclock can cause all kinds of pool corruption errors. This is an easy one to test by resetting to stock settings.

Quick Tip: Before you start troubleshooting, write down or photograph the full crash screen if you can catch it. The stop code parameters (the four hex values in parentheses after BAD_POOL_CALLER) can give you more specific clues. We'll talk about how to read those later.

Step-by-Step Fix Guide

We'll go from easiest to most involved. Start at Step 1 and work your way down until the crashes stop.

Check What Changed Recently

The fastest path to solving a "sudden" BSOD is figuring out what changed right before it started. Ask yourself: Did I install or update any drivers recently? Did Windows Update run? Did I plug in new hardware? Did I install new software?

Open the Windows Event Viewer (press Win + X, then select "Event Viewer"). Navigate to Windows Logs > System and look at entries from around the time the crashes started. You're looking for Critical or Error entries that might point to a specific driver or service.

You can also open Settings > Windows Update > Update History to see exactly what updates installed and when. If a driver update or Windows Update installed right before the crashes started, that's very likely your culprit.

Run a Malware Scan

Before we start touching drivers and system settings, let's rule out malware quickly. Open Windows Security (search for it in the Start menu), go to Virus & threat protection, and run a full scan. If you want a second opinion, the free version of Malwarebytes is excellent and can be installed alongside Windows Defender without conflict.

Let the scan complete fully, this can take 30–60 minutes for a full scan but it's worth doing once to check the box. If malware is found and removed, restart and monitor your system before doing anything else.

Analyze the Minidump File

Every time Windows crashes with a BSOD, it creates a minidump file that records what was happening at the moment of the crash. These files are incredibly useful because they often directly identify the driver that caused the problem.

Minidump files are stored in C:\Windows\Minidump. To read them, download the free tool WhoCrashed from Resplendence Software. Install and run it, and it will automatically analyze your minidump files and display a plain-English report, often naming the exact driver file that triggered the crash.

Alternatively, you can use WinDbg from the Microsoft Store if you want more detailed analysis, but WhoCrashed is much more beginner-friendly and is usually sufficient to identify the problem driver.

Pro Tip: If C:\Windows\Minidump is empty, your system might not be configured to save minidumps. Go to Settings > System > About > Advanced system settings > Startup and Recovery > Settings, and under "Write debugging information," select "Small memory dump (256 KB)." After the next crash, the minidump will be there.

Roll Back or Reinstall Suspect Drivers

If your minidump analysis or your own memory points to a specific driver, here's how to address it:

To roll back a driver: Press Win + X and open Device Manager. Find the device whose driver you want to roll back (e.g., your GPU under Display adapters), right-click it, choose Properties, go to the Driver tab, and click "Roll Back Driver" if it's available. This reverts to the previously installed driver version.

To reinstall a driver cleanly: For GPU drivers especially, use the Display Driver Uninstaller (DDU) tool. Boot into Safe Mode first (hold Shift while clicking Restart, then go to Troubleshoot > Advanced options > Startup Settings > Restart > press 4). Run DDU to completely remove your GPU driver, then restart normally and install the driver fresh from the manufacturer's website (NVIDIA, AMD, or Intel).

Common drivers to check and update or roll back:

GPU drivers (NVIDIA GeForce Experience or AMD Adrenalin)
Network adapter drivers (especially if you recently updated)
Audio drivers (Realtek HD Audio is a frequent offender)
Chipset drivers
USB controller drivers

Run Windows Memory Diagnostic

Let's test your RAM. Press Win + R, type mdsched.exe, and press Enter. Choose "Restart now and check for problems." Your PC will restart and run a memory test before Windows loads. The basic test takes 10–20 minutes.

If errors are found, you have faulty RAM. Try removing one stick at a time and testing with each individually to identify which stick is bad. If you have multiple sticks, also try different slots, sometimes it's a slot issue rather than the RAM itself.

For a more thorough memory test, download MemTest86 (free, from memtest86.com), create a bootable USB drive, and run it for at least 2 full passes. MemTest86 is more comprehensive than the Windows tool and can catch errors the built-in tool misses.

Important: If you're getting BAD_POOL_CALLER crashes frequently, don't skip the RAM test. Faulty RAM can cause intermittent crashes that look exactly like driver problems, and you could spend hours chasing the wrong thing.

Run SFC and DISM to Repair System Files

Windows includes built-in tools to scan for and repair corrupted system files. Open Command Prompt as Administrator (right-click the Start button, select "Terminal (Admin)" or "Command Prompt (Admin)").

First, run DISM to repair the Windows image itself:

DISM /Online /Cleanup-Image /RestoreHealth

Wait for this to complete, it can take 15–30 minutes and will download replacement files from Windows Update. Once it finishes, run the System File Checker:

sfc /scannow

SFC will scan all protected Windows files and replace any corrupted ones with clean cached versions. If it reports finding and fixing corrupted files, restart your PC and monitor for crashes.

Check Your Storage Drive for Errors

Run a check on your primary drive to look for bad sectors or file system errors. Open Command Prompt as Administrator and run:

chkdsk C: /f /r /x

You'll likely be told the volume is in use and asked if you want to schedule the check for the next restart. Type Y and restart. The check will run before Windows loads and can take anywhere from a few minutes to over an hour depending on your drive size.

If you have an SSD, also check the manufacturer's health tool (Samsung Magician, Crucial Storage Executive, WD Dashboard, etc.) for any drive health warnings. An SSD showing reallocated sectors or media errors should be treated as a potential failure candidate.

Disable Fast Startup

Windows Fast Startup is a feature that saves a hibernation snapshot of the kernel to speed up boot times. This can sometimes cause driver state issues that lead to pool errors. It's worth disabling as a troubleshooting step.

Go to Control Panel > Power Options > Choose what the power buttons do. Click "Change settings that are currently unavailable," then uncheck "Turn on fast startup (recommended)." Save changes and do a full restart (not a shutdown and power-on, but Start > Restart).

Reset Overclocks to Default

If you've overclocked your CPU, GPU, or RAM (including XMP/EXPO RAM profiles), try reverting everything to stock settings temporarily. Enter your BIOS/UEFI at boot (usually by pressing Delete, F2, or F10 during the boot screen), find the option to "Load Optimized Defaults" or "Reset to Default," and save and exit.

Run your system at stock settings for a day or two. If the crashes stop, your overclock was the instability source. You can gradually re-tune from there, or just leave it at stock if stability matters more than performance.

Advanced Troubleshooting

If you've worked through all the steps above and still getting crashes, it's time to pull out the heavier tools.

Use Driver Verifier to Catch the Guilty Driver

Windows has a built-in tool called Driver Verifier that puts extra stress on drivers to force misbehaving ones to crash immediately, rather than waiting for random conditions. This is a more aggressive approach but can definitively identify a problematic driver.

Warning: Driver Verifier will cause intentional crashes if it finds a problematic driver. Do not use this on a production machine where you can't afford downtime. Save your work before enabling it.

Press Win + R, type verifier, and press Enter. Choose "Create standard settings," then "Automatically select all drivers installed on this computer," and click Finish. Restart your PC. Driver Verifier will now stress-test your drivers, and if a bad driver causes a crash, the minidump will directly name it.

After you've identified (or not identified) the culprit, disable Driver Verifier by running verifier /reset from an elevated Command Prompt and restarting.

Analyze the Minidump with WinDbg

If WhoCrashed doesn't give you clear results, WinDbg from the Microsoft Store provides deeper analysis. After installing it:

Open WinDbg and go to File > Open Crash Dump
Navigate to C:\Windows\Minidump and open the most recent .dmp file
Wait for the symbols to load, then type !analyze -v in the command box and press Enter
Look for the "MODULE_NAME" and "IMAGE_NAME" fields in the output, these name the driver or module responsible

Perform a Clean Boot

A clean boot starts Windows with only Microsoft services and drivers running, disabling all third-party startup programs. If the crashes stop in clean boot, a third-party program or service is causing the problem.

Press Win + R, type msconfig, go to the Services tab, check "Hide all Microsoft services," then click "Disable all." Go to the Startup tab, click "Open Task Manager," and disable all startup items. Restart and test. If stable, re-enable services and startup items in groups to narrow down which one is causing the issue.

Check for BIOS/Firmware Updates

An outdated BIOS can sometimes cause memory management issues, especially with newer CPUs or RAM configurations. Check your motherboard manufacturer's website for BIOS updates. Read the changelog carefully, if any update mentions memory stability, pool issues, or BSOD fixes, it's worth installing.

Be cautious with BIOS updates, follow the manufacturer's instructions precisely and don't interrupt the process. A failed BIOS update can brick your motherboard.

Test with a Live Linux USB

This sounds unusual, but it's a quick way to test whether your issue is hardware or software. Download Ubuntu or any Linux distro, create a bootable USB with Rufus, and boot from it (no installation needed, just "Try Ubuntu"). If your system runs stably for several hours in Linux, your hardware is likely fine and the problem is in your Windows installation or drivers. If Linux also crashes or freezes, you likely have a hardware issue (RAM, storage, or overheating).

When to Consider a Windows Repair or Reinstall

If you've tried everything above and the crashes persist, a deeper Windows corruption may be at play. At this point, you have two options:

In-place Upgrade Repair: Download the Windows 11 (or 10) ISO from Microsoft's website, mount it, and run setup.exe from within Windows. Choose "Upgrade this PC now" and make sure it says "Keep personal files and apps." This reinstalls Windows system files without wiping your data or programs. It's essentially a repair install and resolves deep system corruption in most cases.

Clean Reinstall: If the in-place repair doesn't work, a clean reinstall is the nuclear option. This wipes your Windows installation and starts fresh. You'll need to back up your data first and reinstall your applications. It's time-consuming but it resolves virtually any software-side cause of BAD_POOL_CALLER.

Before you reinstall: If the crash continues on a fresh Windows install, your problem is definitely hardware, most likely RAM, storage, or (less commonly) a failing motherboard. A clean install is also a useful hardware/software diagnostic tool in that sense.

How to Prevent BAD_POOL_CALLER in the Future

Once you've fixed the immediate problem, here are habits and practices that will significantly reduce your chances of seeing this error again:

Keep Drivers Updated, But Thoughtfully

Don't blindly update every driver the moment a new version drops. For GPU drivers especially, wait a week or two after a major release to let others report any issues. Check forums like Reddit's r/nvidia or r/AMD before updating. When you do update, note the date so you know exactly when to roll back if problems start.

Use Windows Update Wisely

Keep Windows up to date for security, but after major feature updates, check community feedback first. You can pause updates in Settings > Windows Update > Pause updates for up to 5 weeks. This gives time for Microsoft to push hotfixes for any update-introduced issues.

Run Periodic Memory Tests

Memory can degrade over time. Running MemTest86 once a year, or any time you start getting unexplained crashes, catches RAM problems early. It's much easier to replace a RAM stick before it causes data corruption than after.

Monitor Temperatures

Overheating can cause all kinds of instability including pool errors. Use HWiNFO64 (free) to monitor your CPU and GPU temperatures. For a desktop, clean dust from your PC every 6–12 months. For a laptop, make sure vents aren't blocked. Idle CPU temps should generally be under 50°C, and under load under 90–95°C (under 80°C is ideal).

Be Careful With Third-Party System Tools

Tools that hook deep into the kernel, like certain antivirus programs, RAM optimizers, driver updaters, or system cleaners, can cause pool issues. Stick to reputable, well-known software. Avoid "speed booster" or "RAM cleaner" type utilities, which rarely help and can cause exactly this kind of instability.

Create System Restore Points

Before installing new drivers or major software, create a System Restore Point: search for "Create a restore point" in the Start menu, click "Create," and give it a name. If something breaks, you can roll back your entire system state to that point in minutes.

Frequently Asked Questions

Why did BAD_POOL_CALLER start happening suddenly when I didn't change anything?

This is actually very common, and it's usually because something did change even if you don't remember it. Windows Update frequently installs driver updates silently in the background. RAM can also degrade gradually until it crosses a threshold. A storage device can develop bad sectors without warning. Check your Windows Update history first, there's often a driver update that installed right before the crashes began.

Is BAD_POOL_CALLER dangerous? Can it cause data loss?

The BSOD itself is actually a protective mechanism, Windows crashes deliberately to prevent data corruption from spreading. However, if you're getting frequent crashes while working on unsaved files, you can lose that unsaved work. Repeated crashes also put stress on your storage drive from unexpected shutdowns. If you have a failing hard drive causing the crashes, that's an independent data loss risk. Back up your important files to an external drive or cloud storage while you're troubleshooting.

My minidump points to ntoskrnl.exe, what does that mean?

ntoskrnl.exe is the Windows kernel itself. When a crash report blames ntoskrnl.exe, it usually doesn't mean the kernel is corrupted, it's more often a sign that a driver caused a pool corruption and Windows didn't catch it until slightly later, when the kernel was the one acting on the corrupted data. In this case, run Driver Verifier to find the actual misbehaving driver, or look earlier in the crash stack for other referenced modules.

Can antivirus software cause BAD_POOL_CALLER?

Yes, absolutely. Antivirus and security software runs at the kernel level and is one of the most common non-GPU driver causes of pool errors. This is especially true if you recently installed a new antivirus product or updated an existing one. If you've ruled out hardware and GPU drivers, try temporarily uninstalling your third-party antivirus (use the vendor's dedicated removal tool, not just Add/Remove Programs) and see if the crashes stop. Windows Defender is sufficient for most users and doesn't cause these issues.

I'm getting these crashes only when gaming. Does that narrow it down?

Yes, it significantly narrows it down. If crashes only happen during gaming, your GPU driver is the most likely suspect by far, gaming puts the GPU under sustained full load and stresses the driver heavily. Try a clean driver reinstall using DDU. Also check if your GPU is overheating (HWiNFO64 can log temps during gaming). If crashes happen in one specific game but not others, a corrupted game file or an anti-cheat driver in that game might be the culprit. Verify the game's file integrity through Steam/Epic/etc.

Will upgrading to Windows 11 fix BAD_POOL_CALLER if I'm on Windows 10?

No, not typically. BAD_POOL_CALLER is a fundamental Windows kernel mechanism that exists in both Windows 10 and 11. The same driver or hardware problem will follow you to Windows 11. In fact, if you upgrade while the underlying issue exists, it can complicate diagnosis. Fix the root cause first, then upgrade if you want to, don't use the upgrade as a fix attempt.

How many crashes is "too many", at what point should I consider a hardware replacement?

If MemTest86 finds errors in your RAM after multiple passes, replace the RAM, it's not going to get better. If SMART data or the manufacturer's tool shows your SSD or hard drive has reallocated sectors or other health warnings, plan to replace it soon. For GPUs, if you're getting artifacts (visual glitches) alongside the crashes, the GPU hardware itself may be failing. Multiple crashes per day that persist after clean Windows install and clean drivers strongly suggest a hardware issue. At that point, systematic hardware testing and replacement is the right path forward.

Quick Reference: Troubleshooting Checklist

Here's a condensed version of everything we covered, in priority order:

Check what changed recently (updates, new hardware, new software)
Run a full malware scan with Windows Defender + Malwarebytes
Analyze minidump files with WhoCrashed to identify the driver
Roll back or clean-reinstall the suspect driver (use DDU for GPU)
Run Windows Memory Diagnostic, follow up with MemTest86 if needed
Run DISM /RestoreHealth then SFC /scannow
Run CHKDSK on your primary drive
Disable Fast Startup
Reset any overclocks to stock settings
Use Driver Verifier if a specific driver still hasn't been identified
Perform a clean boot to isolate third-party software
Check for BIOS updates
Run in-place Windows repair or clean reinstall as a last resort

Work through these methodically and you'll find the culprit. The vast majority of BAD_POOL_CALLER cases resolve within the first four or five steps. You've got this, and if you get stuck at any point, the details in each step above should give you enough information to know exactly what you're looking at and what to try next.