Memory · critical

How to fix BAD_POOL_HEADER (0x19)

Memory troubleshooting guide

What this error means

Windows stopped because it found damaged bookkeeping data (a pool header) in the kernel's memory pool, the shared memory drivers use. Microsoft notes that the pool was already corrupted when the crash happened, so the program running at that moment is not necessarily the one that caused it. Usually a driver wrote past the end of its memory or used memory it had already freed. When the crash appears at random times with no pattern, Microsoft recommends testing the RAM.

Updated

Applies to
Windows 11 and Windows 10
Difficulty
Intermediate
Before changes
Low for steps 1–6; Driver Verifier in step 7 can cause extra crashes until it is turned off

Reviewed by Matyáš Rada · Documentation checked: 2026-10-31 · Checked against Microsoft's bug check documentation; not tested on every configuration.

Before you begin

Photograph the blue screen and note whether the crash happens in one situation or at random. Random crashes point more to RAM; crashes tied to one device or program point to its driver. If Windows cannot start, see the startup guide.

Work through these checks

0 of 7 complete
01Undo recent driver and software changes

Pool corruption is usually caused by a driver, and new drivers are the most likely suspects.

  1. Roll back recently updated drivers in Device Manager > device Properties > Driver > Roll Back Driver.
  2. Uninstall recently installed antivirus, VPN, virtual network, RGB, monitoring or disk tools in Settings > Apps > Installed apps.
  3. If Windows crashes at startup, do this in Safe Mode (recovery menu > Troubleshoot > Advanced options > Startup Settings > Restart > 4).

Microsoft Defender protects the PC while another antivirus is removed; keep it on.

What to expect

The crashes stop.

If it does not help

Reinstall needed programs one at a time, using their latest versions.

Browse related errors
02Update drivers from the device makers

A newer driver often fixes the memory bug that corrupts the pool.

  1. Install the latest chipset, network, Wi-Fi, audio and storage drivers from your PC, laptop or motherboard maker.
  2. Install the current graphics driver from NVIDIA, AMD or Intel.
  3. If the blue screen named a .sys file, update that driver first.
What to expect

Drivers are current and the PC runs without crashing.

If it does not help

Avoid driver updater programs; they often install wrong drivers.

Browse related errors
03Test the memory

Microsoft recommends Windows Memory Diagnostic when this bug check appears inconsistently.

  1. Press Win + R, type mdsched.exe and choose Restart now and check for problems.
  2. After the restart, open Event Viewer > Windows Logs > System and find the MemoryDiagnostics-Results entry.
What to expect

No memory errors are found.

If it does not help

If errors are found, follow the memory test errors guide on this site to find the faulty module.

Browse related errors
04Remove memory overclocks

An unstable memory profile corrupts data in ways that look exactly like a driver bug.

  1. In the BIOS, turn off XMP, EXPO or DOCP, or choose Load optimized defaults.
  2. Use the PC normally for a few days.
What to expect

The crashes stop at default memory settings.

If it does not help

If they stop, update the BIOS (step 6) before trying the memory profile again.

Browse related errors
05Repair system files and check the drive

Damaged system files can also lead to pool errors.

  1. In Terminal (Admin), run DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow.
  2. Run chkdsk C: /scan to check the system drive.
What to expect

No remaining problems are reported.

If it does not help

If chkdsk reports errors, run chkdsk C: /f and allow it at the next restart.

Browse related errors
06Update the BIOS

BIOS updates improve memory stability and compatibility.

  1. Find your exact PC or motherboard model on the maker's support page.
  2. Install the latest BIOS/UEFI version using the maker's instructions.

Do not switch off the PC during a BIOS update.

What to expect

The PC runs stably on the new firmware.

If it does not help

Check BIOS settings afterwards; they may be reset to defaults.

Browse related errors
07Find the driver with Driver Verifier

Microsoft recommends Driver Verifier's Special Pool option to catch the driver that corrupts the pool at the moment it does it.

  1. Create a restore point (search "Create a restore point").
  2. Open Command Prompt (Admin), type verifier, choose Create standard settings (it includes Special Pool) > Select driver names from a list, and tick only non-Microsoft drivers.
  3. Restart and use the PC until it crashes; the new blue screen names the driver.
  4. Turn Driver Verifier off with verifier /reset and restart.

Driver Verifier deliberately crashes the PC when it finds a problem and slows it down. Turn it off when you are done.

What to expect

A specific driver is named for you to update or remove.

If it does not help

If Windows does not start with Driver Verifier on, start in Safe Mode and run verifier /reset.

Browse related errors

Possible causes

  • A driver that writes outside its memory or uses memory after freeing it
  • Recently installed or updated drivers, antivirus or VPN software
  • Faulty or unstable RAM, including XMP/EXPO profiles
  • Damaged system files
  • Outdated BIOS

Useful Windows tools

These commands open Windows tools. Review changes before applying them.

mdsched.exe

Sources & further reading