The Problem

BAD_POOL_HEADER (stop code 0x00000019) means Windows went to use a block of kernel memory and found its header damaged. The "pool" is the shared pot of kernel memory that drivers borrow from; each block carries a small header describing its size and owner. If a driver writes past the end of its block, or frees the same block twice, that header is destroyed — and the next component to touch it brings the system down.

The crucial point: the driver that crashes is rarely the driver that caused it. The damage happens earlier, and the blue screen fires whenever something else stumbles over the wreckage. That is why the named file changes between crashes, and why Driver Verifier (Step 7) is unusually valuable for this specific stop code.

Same code every boot, immediately? Suspect a security suite or a storage driver. Random and occasional? Test memory first — Step 6.

Symptoms

Blue screen reading BAD_POOL_HEADER, often naming a different file each time.
Crashes appear at no consistent moment — idle, browsing, gaming, copying files.
Frequently starts after installing a security suite, a VPN client, or a backup or disk tool.
May be interspersed with BAD_POOL_CALLER or PFN_LIST_CORRUPT, which share the same underlying cause.

Step 1: Get Into Safe Mode and Capture the Dumps

If the PC crashes before you can work, interrupt the boot three times to reach recovery, then Troubleshoot → Advanced options → Startup Settings → Restart → press 4. Routes in full: how to enter Safe Mode.
Make sure dumps are being saved: Windows + R → sysdm.cpl → Advanced → Startup and Recovery → Settings → Write debugging information = Small memory dump (256 KB).
Check C:\Windows\Minidump and note whether the named file differs between crashes — differing names strongly support pool corruption rather than one bad driver.
Read the crash records properly: how to use Event Viewer to find why your PC crashed.

Step 2: Uninstall What You Installed Most Recently

Open Settings → Apps → Installed apps and sort by Install date.
Remove anything installed shortly before the crashes started, particularly: security suites, VPN clients, disk cleaners, RGB and fan-control utilities, virtual drive tools, and backup agents. All of these install kernel drivers.
Reboot after each removal rather than uninstalling six things at once — otherwise you learn nothing.
In Device Manager, use View → Show hidden devices to spot leftover virtual adapters from removed software and uninstall those too.

Step 3: Remove Third-Party Antivirus Properly

Uninstall through Settings → Apps → Installed apps.
Then run the vendor's dedicated removal tool — nearly every suite leaves filter drivers behind after a normal uninstall, and those drivers are what corrupt the pool.
Reboot. Microsoft Defender re-enables itself automatically: fix Windows Defender not working.
Test for a full day before reinstalling anything.

Step 4: Check the Drive and File System

Pool corruption and disk corruption often travel together, because storage drivers sit in the same path.

Right-click Start → Terminal (Admin) and run:
```
chkdsk C: /f /r
```
Answer Y to schedule it, then reboot. On a large mechanical drive this takes hours — let it finish.
Check the drive's own health readings: check SSD and hard drive health.
Update the SSD firmware from the manufacturer's toolbox — outdated NVMe firmware is a documented cause of pool corruption.
Related: fix NTFS_FILE_SYSTEM BSOD.

Step 5: Repair Windows System Files

In Terminal (Admin):
```
sfc /scannow
```

Then:

DISM /Online /Cleanup-Image /RestoreHealth

Reboot, then run sfc /scannow a second time.
Full walkthrough: how to run SFC and DISM.

Step 6: Test the Memory Thoroughly

Windows + R → mdsched.exe → Restart now and check for problems.
Press F1 during the test and set Test Mix to Extended.
Follow up with MemTest86 from a USB stick for four passes or more — the built-in tool misses intermittent faults that MemTest86 catches.
Turn XMP / EXPO off in firmware and retest at stock speed: how to enter BIOS or UEFI.
Test sticks individually if you get errors: check and upgrade your RAM and fix MEMORY_MANAGEMENT BSOD.

Step 7: Run Driver Verifier With Pool Checks

This is the tool built for exactly this failure — it puts a guard page after every pool allocation so the offending driver crashes at the moment it oversteps, naming itself instead of an innocent bystander.

Windows + R → verifier → Create custom settings (for code developers).
Tick Special pool and Pool tracking in addition to Standard settings.
Choose Select driver names from a list and select only non-Microsoft drivers.
Reboot and use the PC normally. The next blue screen should name the real culprit.
Turn it off as soon as you have a name — from Terminal (Admin), or from Safe Mode if the PC will not boot:
```
verifier /reset
```

Step 8: Turn Off Fast Startup and Roll Back

Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable → untick Turn on fast startup. This forces a clean kernel initialisation on every boot instead of restoring a saved — possibly already corrupted — state.
If crashes started after an update, roll it back: Settings → Windows Update → Update history → Uninstall updates, or see fix Windows 11 after a bad update.
Use Windows + R → rstrui to return to a restore point predating the crashes.

What Not to Do

Don't trust the filename on the blue screen for this stop code. It names the victim, not the offender — that is what Step 7 is for.
Don't run a registry cleaner. It cannot touch kernel pool memory and can break working software.
Don't stack security tools. Two suites with two sets of filter drivers is a reliable way to produce this crash.
Don't skip the memory test because the PC "seems fine otherwise". Marginal RAM shows up as pool corruption long before anything else.

Still Not Working?

If Driver Verifier names nothing, memory tests clean, the drive is healthy, and no third-party kernel drivers remain, a repair install of Windows keeps your files while replacing every system component: reinstall Windows without losing data. Back up first — set up automatic backups.

How to Fix BAD_POOL_HEADER in Windows 11