If you see a blue screen with “BAD_POOL_HEADER” on Windows 10, it means a driver or system process corrupted the memory pool that Windows uses to track allocated memory. The fix usually involves updating or rolling back drivers, running memory diagnostics, and checking for disk errors — here’s how to do it step by step.
What Does “Bad Pool Header” Actually Mean?
Windows uses a “pool” of memory pages for kernel-mode drivers and system services. Each allocation gets a small header that records its size, owner, and state. When a driver writes past the end of its buffer, frees memory twice, or accesses memory it no longer owns, that header gets corrupted. The next time Windows checks the pool, it detects the mismatch and crashes with a BAD_POOL_HEADER stop code (0x00000019) to prevent further damage.
This is a kernel-mode bug, so it rarely comes from normal apps. The usual culprits are:
- Outdated or faulty device drivers (especially network, graphics, storage, or chipset drivers)
- Recently installed software that installs a kernel driver (antivirus, VPN, virtualization tools)
- Faulty RAM or a damaged page file
- Corrupted system files or a failing hard drive
Before You Start: Boot Into Safe Mode
If the error appears during startup and you can’t get to the desktop, you’ll need to enter Safe Mode. Safe Mode loads only the minimum set of drivers, so if the crash stops happening there, you’ve confirmed a third-party driver is responsible.
- Restart your PC and press the power button to interrupt startup three times in a row. Windows will boot into the Recovery Environment.
- Go to Troubleshoot > Advanced options > Startup Settings > Restart.
- Press 4 or F4 to choose Enable Safe Mode.
Once in Safe Mode, you can apply the fixes below. If the error doesn’t appear in Safe Mode, focus on drivers and recently installed software.
Fix 1: Update or Roll Back Problematic Drivers
Since a corrupt driver is the most common cause, start there. Open Device Manager (right-click the Start button and select it). Look for devices with a yellow warning icon, but even without one, check the following categories:
- Display adapters — graphics drivers are frequent offenders
- Network adapters — Wi-Fi and Ethernet drivers
- Storage controllers — especially if you use RAID or NVMe
- System devices — chipset and firmware drivers
For each, right-click and choose Update driver > Search automatically. If Windows doesn’t find anything new, go to the manufacturer’s website and download the latest driver manually. Avoid generic “driver updater” tools; they often install the wrong version.
If the error started after a recent driver update, use Roll Back Driver in the same Properties dialog. That reverts to the previous version that worked.
Fix 2: Run Windows Memory Diagnostics
Faulty RAM can corrupt pool headers randomly. Windows has a built-in tool to test memory. Type “Windows Memory Diagnostic” in the Start menu and run it. Choose Restart now and check for problems. The PC will reboot and run a memory test that takes about 20 minutes. After it finishes, Windows restarts and shows the results.
If the test reports errors, your RAM is likely bad. Try reseating the memory modules (remove and reinstall them) or test each stick individually if you have more than one. If errors persist, replace the faulty module.
Fix 3: Check for Disk Errors and Corrupted System Files
A failing hard drive or SSD can also cause memory corruption, because data read from disk may be wrong. Run chkdsk and the System File Checker to repair issues.
- Open Command Prompt as administrator (right-click Start > Windows Terminal (Admin)).
- Run
sfc /scannowand wait for it to complete. It will repair corrupted Windows files. - Then run
chkdsk C: /f /r. You’ll be prompted to schedule a scan on next reboot — type Y and restart.
Note that chkdsk can take a long time on large drives. If it finds bad sectors, back up your important data immediately and consider replacing the drive.
Fix 4: Uninstall Recently Added Software
If the crashes began after installing a new program, that software might have installed a kernel-mode driver. Common examples include:
- Antivirus or firewall suites
- Virtualization tools (VirtualBox, VMware, Hyper-V)
- VPN clients with TAP drivers
- Game anti-cheat software
Go to Settings > Apps > Installed apps, sort by install date, and uninstall anything that matches the crash timeline. If the problem disappears, you’ve found the culprit. You can try reinstalling the latest version from the vendor, but if it crashes again, avoid that software.
Fix 5: Disable Fast Startup and Update Windows
Fast Startup (a hybrid shutdown) can sometimes cause memory pool issues because it doesn’t fully clear kernel memory. Disable it:
- Open Control Panel > Power Options > Choose what the power buttons do.
- Click Change settings that are currently unavailable.
- Uncheck Turn on fast startup and save changes.
Also make sure Windows is fully updated. Go to Settings > Windows Update and install all pending updates, including optional driver updates. Microsoft frequently patches kernel bugs that cause stop errors.
When to Consider a System Restore or Reset
If none of the above works, you can try System Restore to roll back to a point before the errors started. Type “Create a restore point” in Start, open the System Properties, and click System Restore. Choose a restore point that predates the first crash.
If you don’t have a restore point, the last resort is Reset this PC (Settings > Update & Security > Recovery). Choose Keep my files to reinstall Windows without losing personal data, but you’ll need to reinstall apps. This often clears any deep driver corruption.
Frequently Asked Questions
Is BAD_POOL_HEADER always caused by RAM?
No. While faulty RAM is a possible cause, driver bugs are far more common. Always update drivers first before buying new memory. The memory diagnostic is a good second step, but don’t assume the worst until you’ve ruled out software.
Can overheating cause this error?
Indirectly, yes. Overheating can cause hardware instability, including memory errors. Check your CPU and GPU temperatures with a free tool like HWMonitor. If temperatures exceed 90°C under load, clean dust from fans and improve airflow.
Will reinstalling Windows fix it?
Usually, yes, because it replaces all system files and removes third-party drivers. But if the cause is faulty hardware (RAM or disk), the error will return even after a clean install. That’s why you should test hardware first.
How do I read the crash dump to find the exact driver?
Use the free tool BlueScreenView from NirSoft. It reads the minidump files in C:\Windows\Minidump and shows which driver was loaded when the crash occurred. The driver name in the “Caused By Driver” column points directly to the culprit.
Is it safe to keep using my PC after one occurrence?
If it happens once and doesn’t recur, you can continue, but be cautious. If it happens again, the underlying issue is still there. Run the diagnostics above before relying on the system for important work.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- Fix Text Cursor Turning White in Windows 11
- Force Quit Non-Responding Apps on Mac: 6 Ways
- Chromebook Not Charging? Fix It Fast
- iPhone Won’t Make Calls but Texts Work? Fixes
- Android to iPhone Hotspot: Connect & Fix Issues
- How to Auto-Enable Low Power Mode on iPhone