Blue Screen Bad Pool Header: Causes and Fixes
The BAD_POOL_HEADER blue screen in Windows means the operating system detected corruption or an inconsistency in a pool of memory used by Windows or a driver. It is often associated with faulty or incompatible drivers, memory problems, or damaged system data; the stop message alone does not identify which cause is responsible.
What the Bad Pool Header error means
Windows uses pools of system memory to provide space for the operating system and drivers to store data temporarily. The “header” is bookkeeping information that describes a block in a pool, such as its size and state. If Windows finds that this information is invalid, it stops to avoid continuing with potentially corrupted data.
The blue screen may display BAD_POOL_HEADER or the stop code 0x00000019. It can appear during startup, while using a particular device, or apparently at random. A crash can result from a driver writing to memory incorrectly, incompatible low-level software, failing RAM, or disk and system-file problems. The stop code is a clue, not a diagnosis.
Start with safe, simple checks
If Windows starts again after the crash, save your work and note what happened just before it: for example, installing a driver, connecting a device, or waking the computer from sleep. If the computer is in a loop, disconnect nonessential USB devices and restart. Keep the keyboard, mouse, and display connected, then see whether Windows can start.
- Undo a recent change. If the crashes began after installing a driver, app, update, or device, temporarily remove or roll back that change where possible.
- Check for repeatability. A crash only when a particular device or activity is involved can help narrow down the cause, but does not prove that device is defective.
- Back up important files. If Windows remains usable, copy important data to a separate location before deeper troubleshooting. Repeated crashes can interrupt work and complicate recovery.
- Avoid repeated forced shutdowns. Use the power button only when Windows is unresponsive. Interrupting writes can cause additional data problems.
Update or roll back drivers and software
Drivers let Windows communicate with hardware, and a buggy or mismatched driver is a common type of cause for memory-pool errors. Open Settings > Windows Update and install appropriate available updates, then restart. For a particular device, use Device Manager: right-click the device, choose Properties, and check the Driver tab for options such as Roll Back Driver or Update Driver. The available choices vary by device and installed driver.
If the problem began immediately after a driver update, rolling it back may be more useful than installing another version. For a newly added peripheral, disconnect it and test whether the crashes stop. Avoid driver-download sites that promise automatic fixes; use Windows Update or the computer or device maker’s support source, and confirm the driver matches the exact hardware and Windows edition.
Recently installed antivirus, backup, disk, or hardware-monitoring utilities can also interact with system components. If there is a strong timing link, uninstall the recent software using Windows Settings and restart. Do not leave the computer without essential protection longer than needed, and do not remove system components merely because their names are unfamiliar.
Check Windows files and the drive
Windows includes tools that can inspect and repair some system-file damage. Open Terminal or Command Prompt as an administrator, then run:
DISM /Online /Cleanup-Image /RestoreHealth- After it completes, run
sfc /scannow
These commands may take time. Let each finish and read its result; a repair is not guaranteed to fix a crash caused by hardware or a driver. Restart afterward and check whether the blue screen returns.
Storage trouble can contribute to instability, though BAD_POOL_HEADER does not by itself mean the drive is failing. Check the drive maker’s diagnostic guidance or Windows’ drive-health information if available, and back up files if there are read errors, unusual drive behavior, or repeated file corruption. Do not assume a disk-check result proves every component is healthy.
Test memory and consider hardware
Faulty or unstable RAM can corrupt data used by Windows. Search Start for Windows Memory Diagnostic, open it, and choose to restart and check. Save your work first because the test requires a restart. If the diagnostic reports memory problems, or crashes continue despite software troubleshooting, the computer may need a more thorough hardware test or repair.
Overheating, unstable memory settings, and a recently changed component can also cause intermittent crashes. If the problem began after changing firmware settings, restore the previous stable settings rather than experimenting with unfamiliar options. Do not open a laptop or desktop unless you know how to handle its components safely; consult the device documentation or a qualified repair service when needed.
If Windows will not start
When Windows repeatedly crashes during startup, it may enter the Windows Recovery Environment automatically after failed starts. You can also reach recovery options using Windows installation or recovery media. From the recovery screen, choose Troubleshoot > Advanced options. Depending on what is available, try Startup Repair, System Restore, or Startup Settings to start in Safe Mode.
In Safe Mode, remove a recently added driver or app, or use Device Manager to roll back a driver. System Restore can return system settings and installed programs to an earlier restore point; it is not a substitute for a file backup. Before resetting or reinstalling Windows, understand which option preserves personal files and which can remove apps or data. If files are not backed up, consider recovery options before choosing a destructive reset.
Frequently Asked Questions
Is BAD_POOL_HEADER caused by RAM?
It can be, but RAM is only one possibility. Drivers, recently installed software, system-file damage, and other hardware issues can produce the same stop code.
What does stop code 0x00000019 mean?
It identifies the BAD_POOL_HEADER stop error. It indicates Windows found an inconsistency in memory-pool bookkeeping, but it does not specify the faulty driver or component.
Can I fix the error without reinstalling Windows?
Often, yes. Start with recent driver or software changes, Windows updates, system-file checks, and a memory test. Reinstalling is a later option, not the first diagnostic step.
Why does the blue screen appear only sometimes?
Intermittent faults may depend on a particular driver, device, workload, or memory condition. Note what is connected and what Windows is doing when each crash occurs; a pattern can guide troubleshooting.
Should I keep using the computer after this error?
If Windows is stable after one crash, back up important files and troubleshoot. Repeated crashes, memory-test errors, or signs of storage failure warrant prompt attention rather than continued normal use.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.