Windows BSOD BAD_POOL_HEADER (0x00000019) — Memory Pool Corruption

BAD_POOL_HEADER BSOD occurs when a kernel memory pool header is corrupted, typically caused by faulty drivers, antivirus software, or bad RAM. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: Stop code 0x00000019 — the pool memory allocator detected corruption in a pool header. Pool headers track memory allocations in kernel space. Corruption usually means a driver wrote beyond its allocated memory. Antivirus filter drivers are frequent culprits due to kernel-level file system hooks. Can occur gradually as pool corruption accumulates before causing a crash. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: Driver bug overwriting adjacent memory pool headers (buffer overflow). Antivirus software with faulty kernel filter drivers. Bad RAM causing random bit flips in kernel memory. Incompatible or outdated third-party drivers. Windows Update installing an incompatible driver. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Uninstall third-party antivirus temporarily and test with Windows Defender only. Boot into Safe Mode and check if the BSOD recurs — if not, a third-party driver is the cause. Run Windows Memory Diagnostic (Win+R > mdsched.exe) to check RAM. Open Device Manager and roll back recently updated drivers. Use Driver Verifier (verifier.exe) to identify the faulty driver — enable for non-Microsoft drivers only. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our Windows Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.