- Software and digital services
- Operating system
BAD_POOL_HEADER
Windows BAD_POOL_HEADER: corrupt kernel memory pool header
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
High
Quick answer
Windows stopped because it found a damaged header on a block of the pool, the memory the kernel hands out to drivers. First note whether the crash is random and run Windows Memory Diagnostic; then look at the last driver or device you added.
Safety first
Stop and check this first
- Before anyone updates the BIOS or swaps parts, have your BitLocker recovery key at hand, usually stored in your Microsoft account; Microsoft cannot recover it for you.
- Driver Verifier can cause extra blue screens and slow the PC down: leave it to a technician who knows how to turn it off from Safe Mode.
Safe checks you can perform
- Record when it happens and its parameters
- RAM check with the Windows diagnostic
- Devices and drivers added recently
- Get the memory dump ready
Leave these tasks to a qualified professional
- Do not attempt this professional task: Dump analysis and special pool testing
- Do not attempt this professional task: Hardware test with a report
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Dump analysis and special pool testing
What they doA technician opens the dump in WinDbg, walks the pool lists and, if needed, enables Driver Verifier with the Special Pool option on the suspect driver.
They must show youthe !analyze -v output and the driver or pool tag they consider responsible.
In writingwhich driver was identified, what was updated or removed and how Driver Verifier was switched off afterwards.
Hardware test with a report
What they doIf the Windows memory test fails or stops continue with no clear driver, the PC maker or a technician runs their memory and system diagnostics.
They must show youthe memory test report with the modules checked and the result.
In writingwhich part failed the test, whether it was replaced and whether BIOS or firmware was updated.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Record when it happens and its parameters
- Who:
- you, no special tools needed.
- How:
- photograph the blue screen with your phone before it restarts and, back in Windows, open Event Viewer and look under Windows Logs, System, for critical errors at the time of the crash; note each day it happens.
- Result that matters:
- knowing whether the stop repeats with the same activity or strikes with no clear pattern.
- If it always appears while using the same program or device, suspect the related driver and review it first.
- If it strikes at random with different parameters, run the memory test before touching drivers.
- Evidence to keep:
- dated photos of the blue screen and a simple list of when each stop occurred.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Bug Check 0x19 BAD_POOL_HEADER
RAM check with the Windows diagnostic
- Who:
- you, with open files saved.
- How:
- type Memory in the Control Panel search box, choose Diagnose your computer's memory problems and let it restart; afterwards, in Event Viewer, System log, look for the MemoryDiagnostics-Results entry.
- Result that matters:
- a written RAM test result you can show later.
- If the test reports errors, keep the screenshot and take the PC for a memory check by the maker or a technician.
- If it finishes clean, memory becomes less suspect and recent drivers deserve a look.
- Evidence to keep:
- screenshot of the MemoryDiagnostics-Results event with its date.
Evidence: Bug Check 0x19 BAD_POOL_HEADER
Devices and drivers added recently
- Who:
- you, with the PC shut down to unplug things.
- How:
- remove the last external peripheral you connected before the stops began and boot; then right-click Start, open Device Manager and look for exclamation icons to choose Update driver, disable or uninstall.
- Result that matters:
- checking whether the crash goes away without that device or after fixing the flagged one.
- If it stops crashing, that peripheral or its driver is the lead suspect and its maker should supply a compatible version.
- If nothing changes, reconnect it and leave the case for dump analysis.
- Evidence to keep:
- name of the device removed or flagged and the number of days without stops.
Evidence: Troubleshooting Windows unexpected restarts and stop code errors
Get the memory dump ready
- Who:
- you, from Advanced system settings.
- How:
- search for Advanced system settings on the taskbar, open Startup and Recovery with its Settings button, under Write debugging information pick Automatic memory dump, click OK and restart.
- Result that matters:
- the next stop leaving a MEMORY.DMP file in the Windows folder for whoever analyses it.
- If it was already on and MEMORY.DMP or a Minidump folder with files exists, copy them to a USB stick for the technician.
- If it was off, turn it on now and wait for the next stop before asking for analysis.
- Evidence to keep:
- screenshot of the Startup and Recovery window and the date of the latest dump file.
Evidence: Stop code error or bug check troubleshooting (IT professionals)
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x00000019
- 0x19
- BAD POOL HEADER
- STOP 0x00000019
- stop code BAD_POOL_HEADER
What it means
Microsoft documents bug check 0x00000019 as a corrupt pool header. The pool was already damaged when the request that triggered the stop arrived, so the component caught at that moment may not be at fault: another driver often damaged it earlier. Parameter 1 tells which inconsistency was found, such as a broken free list or a freed block that someone modified afterwards. When the code shows up irregularly, Microsoft points to physical memory as a possible origin. Seeing this code is not enough to declare any component faulty.
Warnings and stop conditions
- Highsource verified
Before anyone updates the BIOS or swaps parts, have your BitLocker recovery key at hand, usually stored in your Microsoft account; Microsoft cannot recover it for you.
Evidence: Find your BitLocker recovery key
- Mediumsource verified
Driver Verifier can cause extra blue screens and slow the PC down: leave it to a technician who knows how to turn it off from Safe Mode.
Evidence: Stop code error or bug check troubleshooting (IT professionals)
Symptoms and causes
Probable causes · in order
- A driver writing past its memory blockCommon
Microsoft explains that the pool is already corrupt when the current request arrives and that an overrun neighbouring block is often to blame, not the code that detects it.
Evidence: Bug Check 0x19 BAD_POOL_HEADER
- RAM with intermittent faultsPossible
When the stop appears inconsistently, Microsoft's page links this code to faulty physical memory and asks you to run Windows Memory Diagnostic.
Evidence: Bug Check 0x19 BAD_POOL_HEADER
- Recently installed driver or hardwarePossible
The support guide says to remove hardware added just before the error and to check Device Manager for devices flagged with an exclamation mark.
Evidence: Stop code error or bug check troubleshooting (IT professionals) · Troubleshooting Windows unexpected restarts and stop code errors
Virtual technician
Does BAD_POOL_HEADER still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 2
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
- 3
Solución de problemas de reinicios inesperados y errores de código de detención de Windows
Microsoft · 2026 · official_doc
- 4
Find your BitLocker recovery key
Microsoft · 2026 · official_doc
- 5
Bug Check 0x19 BAD_POOL_HEADER
Microsoft · 2026 · official_doc
Was this entry useful?