Windows BSOD BAD_POOL_HEADER (0x00000019) — Memory Pool Corruption
Criticalbsod
Overview
BAD_POOL_HEADER BSOD occurs when a kernel memory pool header is corrupted, typically caused by faulty drivers, antivirus software, or bad RAM.
Key Details
- 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
Common Causes
- 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
Steps
- 1Uninstall third-party antivirus temporarily and test with Windows Defender only
- 2Boot into Safe Mode and check if the BSOD recurs — if not, a third-party driver is the cause
- 3Run Windows Memory Diagnostic (Win+R > mdsched.exe) to check RAM
- 4Open Device Manager and roll back recently updated drivers
- 5Use Driver Verifier (verifier.exe) to identify the faulty driver — enable for non-Microsoft drivers only
Tags
windowsbsodbad-pool-headermemorydriver
More in Bsod
windows-0000000A-irql-not-less-or-equalWindows Error 0x0000000A — IRQL NOT LESS OR EQUAL
Criticalwindows-00000050-page-fault-in-nonpaged-areaWindows Error 0x00000050 — PAGE FAULT IN NONPAGED AREA
Criticalwindows-0000007E-system-thread-exception-not-handledWindows Error 0x0000007E — SYSTEM THREAD EXCEPTION NOT HANDLED
Criticalwindows-0000007A-kernel-data-inpage-errorWindows Error 0x0000007A — KERNEL DATA INPAGE ERROR
Criticalwindows-000000EF-critical-process-diedWindows Error 0x000000EF — CRITICAL PROCESS DIED
Criticalwindows-00000133-dpc-watchdog-violationWindows Error 0x00000133 — DPC WATCHDOG VIOLATION
CriticalFrequently Asked Questions
Antivirus software uses kernel filter drivers to scan files. A bug in these drivers can corrupt adjacent memory pool headers.