Skip to content
0x00000019BAD_POOL_HEADERStop codeWidely reported

BAD_POOL_HEADER (0x19): what it means and how to fix it

Updated Oct 6, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

This error occurs when Windows detects that a section of system memory, known as a pool, has become corrupted. It is most commonly caused by faulty hardware or a malfunctioning device driver. Running the built-in Windows Memory Diagnostics tool is the best first step to identify the cause.

What it means

Understanding the Pool Header

When Windows manages memory, it organizes data into blocks called pools. Each of these blocks has a header, which acts like a label containing important information about the size and location of the data. The BAD_POOL_HEADER error means that Windows has encountered a header that does not match its expected state. Essentially, the system is trying to read or write to a memory block, but the instructions it finds there are garbled or physically impossible.

Why This Happens

This error is a protective measure. When Windows realizes the memory structure is damaged, it stops the computer immediately to prevent further data loss or permanent system instability. This corruption usually happens because a piece of software, often a device driver, has written data into a memory area it does not own. This is known as an overrun. Alternatively, the physical memory sticks inside your computer may be failing, causing data to be stored or retrieved incorrectly. Because the system cannot trust the integrity of the data in memory, it cannot continue to operate safely.

Common causes

  • Faulty physical RAM modules.
  • Corrupted or outdated device drivers.
  • A device driver writing to memory it does not own.
  • Inconsistent system memory structures.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Run Windows Memory Diagnostics

    Use this to check if your physical RAM modules are failing.

    1. Click the Start button and type Memory.
    2. Select the option labeled Diagnose your computer's memory problems.
    3. Choose to restart your computer now to check for problems.
    4. Wait for the scan to complete and for the computer to restart.
    5. Open Event Viewer after restarting to view the results under the System log, looking for MemoryDiagnostics-Results.
    Did this fix it?
  2. Update your device drivers

    Use this if the error happens frequently after installing new hardware or software.

    1. Right-click the Start button and select Device Manager.
    2. Expand the categories to find your hardware devices.
    3. Right-click a device and select Update driver.
    4. Choose to search automatically for updated driver software.
    5. Repeat this process for your primary hardware components like graphics or network adapters.
    Did this fix it?
  3. Run the Driver Verifier

    Use this advanced tool to identify a specific driver causing the memory corruption.

    1. Click the Start button and type cmd.
    2. Right-click Command Prompt and select Run as administrator.
    3. Type verifier and press Enter to open the Driver Verifier Manager.
    4. Follow the on-screen prompts to select the drivers you wish to monitor.
    5. Restart your computer to begin the verification process.
    Did this fix it?

Is it just you?

25+ Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 2, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

Is my computer broken if I see BAD_POOL_HEADER?

Not necessarily. It often indicates a software driver conflict or a temporary memory glitch that can be resolved without replacing hardware.

Can I fix this error by reinstalling Windows?

Reinstalling Windows may resolve the issue if it is caused by corrupted system files or drivers, but it will not fix the problem if your physical RAM is faulty.

What should I do if the error keeps happening?

If the error persists after checking your memory and updating drivers, you may need to consult a professional to test your hardware components individually.