The “Bad Pool Header” Blue Screen of Death (BSOD) in Windows 10 is a stop error (0x00000019) that indicates a serious memory management problem, often caused by faulty drivers, corrupted system files, or failing hardware. You can usually fix it by booting into Safe Mode, running the built-in memory diagnostic, and updating or rolling back problematic drivers, with a system restore or Windows reset as a fallback.
What Does “Bad Pool Header” Mean?
Windows uses a memory structure called a “pool” to allocate space for kernel-mode components like drivers and system services. Each allocated block has a header that stores metadata about the block—its size, owner, and state. When the system detects that a pool header is corrupted—either because it was overwritten, freed twice, or points to an invalid address—it halts the system with the Bad Pool Header error. This is a protective measure: continuing to run with corrupted memory could lead to data loss or system instability.
Common Causes of the Error
The error is almost never caused by a single, obvious factor. Instead, it typically stems from one of these sources:
- Faulty or incompatible drivers—especially graphics, network, or storage drivers that interact heavily with kernel memory.
- Corrupted system files—for example, after an interrupted Windows update or a disk error.
- Failing RAM—physical memory defects can corrupt pool headers at random.
- Overclocking or unstable BIOS settings—memory timings or voltages that are too aggressive.
- Third-party security software—antivirus or firewall tools that hook into the kernel can cause pool corruption.
Step-by-Step Fixes to Try
Start with the least disruptive fix and work your way up. If the error appears during startup, you may need to boot into Safe Mode first (hold Shift while clicking Restart, then choose Troubleshoot > Advanced Options > Startup Settings > Restart, then press 4 or F4).
1. Run the Windows Memory Diagnostic
Since bad RAM is a leading cause, test your memory first. Type “Windows Memory Diagnostic” in the Start menu, select it, and choose “Restart now and check for problems.” The system will reboot and run a memory test. If errors appear, replace the faulty RAM stick (you can identify which one by testing one stick at a time).
2. Update or Roll Back Drivers
Outdated or newly installed drivers are the most common software cause. Open Device Manager (right-click Start > Device Manager), expand categories, and look for devices with a yellow exclamation mark. Right-click the device, choose “Update driver,” then “Search automatically.” If the error started after a recent driver update, go to the driver’s Properties > Driver tab and click “Roll Back Driver.” Pay special attention to display adapters, network adapters, and storage controllers.
3. Run System File Checker (SFC) and DISM
Corrupted system files can be repaired with built-in tools. Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin)) and run:
sfc /scannow—this scans and repairs protected system files.- If SFC finds errors it cannot fix, run
DISM /Online /Cleanup-Image /RestoreHealthto repair the Windows image, then run SFC again.
4. Check for Windows Updates
Microsoft regularly patches bugs that cause stop errors. Go to Settings > Update & Security > Windows Update and click “Check for updates.” Install all pending updates, including optional driver updates (you can find these under “View optional updates”).
5. Uninstall Recently Installed Software
If the BSOD started after you installed a new program—especially a driver updater, antivirus, or system utility—uninstall it. Go to Settings > Apps > Apps & features, find the program, and uninstall. For security software, use the vendor’s official removal tool if available.
6. Disable Overclocking
If you have overclocked your CPU or RAM, revert to default BIOS/UEFI settings. Enter BIOS (usually by pressing Del or F2 during boot), load “Optimized Defaults,” and save. This eliminates unstable memory timings as a cause.
7. Perform a System Restore
If you have a restore point from before the error started, use it. Boot into Safe Mode, type “System Restore” in the Start menu, and choose a restore point. This reverts system files and drivers to an earlier state without affecting your personal files.
8. Reset or Reinstall Windows
If nothing else works, a full reset is the last software option. Go to Settings > Update & Security > Recovery > “Reset this PC.” Choose “Keep my files” to preserve personal data, but be aware that all installed applications will be removed. If the error persists even after a clean install, the problem is almost certainly hardware—most likely RAM or the motherboard.
What to Do If the Error Keeps Returning
If you have tried all the above and the Bad Pool Header still appears, you are likely dealing with a hardware issue. Beyond RAM, the SSD or HDD can cause this if it has bad sectors. Run chkdsk C: /f /r in an elevated Command Prompt to check the disk. Also, update your motherboard’s BIOS/UEFI to the latest version—manufacturers often fix memory compatibility issues in updates. If the problem is intermittent, try removing unnecessary peripherals (USB devices, external drives) to isolate the cause.
Frequently Asked Questions
Can a Bad Pool Header error be caused by a virus?
Yes, but it is uncommon. Rootkits or low-level malware can corrupt kernel memory structures. Run a full scan with Windows Defender Offline (Settings > Update & Security > Windows Security > Virus & threat protection > Scan options > Microsoft Defender Offline scan) to rule this out.
Will I lose my files if I reset Windows?
If you choose “Keep my files,” your personal documents, photos, and videos are preserved, but installed apps and settings are removed. If you choose “Remove everything,” all data is erased—back up to an external drive first.
How do I boot into Safe Mode if Windows won’t start?
Turn the PC on and off three times (press and hold the power button to force shutdown when the Windows logo appears). On the third restart, Windows should enter the Automatic Repair environment. From there, go to Advanced options > Startup Settings > Restart, then press 4 or F4 for Safe Mode.
Is Bad Pool Header the same as a memory management error?
No, but they are related. The “Memory Management” BSOD (0x0000001A) is a different stop code, though both point to kernel memory corruption. The fixes overlap, but Bad Pool Header specifically implicates pool allocation issues, which are most often driver-related.
Can outdated BIOS cause this error?
Yes. An outdated BIOS may have bugs in how it exposes memory to the operating system, especially with newer RAM modules. Check your motherboard manufacturer’s website for a BIOS update, but only apply it if you are comfortable—a failed BIOS flash can permanently damage the motherboard.
Should I replace my RAM immediately if I see this error?
Not immediately. Run the Windows Memory Diagnostic first. If it reports errors, then replace the RAM. If it reports no errors, the cause is more likely software, so continue with the driver and system file fixes before spending money on new hardware.
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 Apps Not Downloading From Play Store
- Secure a Samsung Galaxy After a Zero-Day Disclosure
- What to Check Before Installing Linux Alongside Windows
- Fix OEM Activation Error 0xc004c060 in Windows 10
- Why Does My App Run One Query for the List and One per Item?
- Fix Google Chrome Has Stopped Working