BAD_POOL_HEADER (0x19): Causes and Fixes

BAD_POOL_HEADER (0x00000019)

Stop code 0x00000019, also written 0x19. Here is what it means, what usually causes it, and the safest order to work through fixes on Windows 11 and Windows 10.

In short

Windows found a damaged header in a block of memory it manages, the memory pool.

What BAD_POOL_HEADER means

Windows keeps track of kernel memory blocks with small headers. This stop appears when one of those headers is damaged, usually because a driver wrote outside its own memory, or because of faulty RAM or disk problems.

Common causes

A driver that writes outside its allocated memory
Faulty RAM
Disk errors or file system damage
Security or system-utility software that hooks deep into Windows

How to fix BAD_POOL_HEADER

Work through these in order and test after each one. Stopping as soon as the crashes stop tells you which change mattered.

Note the file name on the blue screen. If the screen shows a line such as "What failed" followed by a .sys file, write it down. Searching that file name shows which driver it belongs to, which tells you what to update or remove. The named file is the code that crashed, which is not always the root cause.
Undo the most recent change. If the blue screens began after a Windows update, a new driver or new software, remove that change first. Uninstall the update from Settings, Windows Update, Update history, or roll a driver back in Device Manager (right-click the device, Properties, Driver, Roll Back Driver).
Test the memory. Run Windows Memory Diagnostic (search for it in Start) for a quick check, then MemTest86 for several passes if the crashes continue. Any error points to a faulty stick or slot, or to memory settings the hardware cannot run reliably.
Repair Windows system files. Open Terminal (Admin) and run sfc /scannow. If it reports damage it could not repair, run DISM /Online /Cleanup-Image /RestoreHealth, restart, and run sfc /scannow once more.
Check the health of the drive. Read the SMART data with the drive maker's tool or CrystalDiskInfo and look for reallocated or pending sectors, media errors and a low remaining-life figure. Back up important files first if the drive reports any warning.

When to stop and protect your data

If the code appears after installing a specific program, uninstall it and look for an updated release before reinstalling.

Not sure this is your code?

The stop code appears as text on the blue screen. If the PC restarted before you could read it, open Event Viewer, then Windows Logs, then System, and look for a BugCheck event with ID 1001. You can also search all stop codes.

Related guides

Other memory errors

PAGE_FAULT_IN_NONPAGED_AREA (0x50)
MEMORY_MANAGEMENT (0x1A)

Frequently asked questions

What does BAD_POOL_HEADER mean?

Windows found a damaged header in a block of memory it manages, the memory pool. Windows keeps track of kernel memory blocks with small headers. This stop appears when one of those headers is damaged, usually because a driver wrote outside its own memory, or because of faulty RAM or disk problems.

What usually causes BAD_POOL_HEADER?

Typical causes: A driver that writes outside its allocated memory; Faulty RAM; Disk errors or file system damage; Security or system-utility software that hooks deep into Windows.

How do I fix BAD_POOL_HEADER (0x00000019)?

A sensible order is: 1) Note the file name on the blue screen; 2) Undo the most recent change; 3) Test the memory; 4) Repair Windows system files. If the code appears after installing a specific program, uninstall it and look for an updated release before reinstalling.

Use this guidance carefully

A stop code can have several causes, and these steps are general guidance rather than a diagnosis of your PC. If your data matters, back it up before repairs. If the problem continues, a hardware technician can test the parts.

See our testing methodology·Read our editorial policy