The BAD_POOL_HEADER Stop Error in Windows 11/10/8/7 signified with the error code 0x00000019 indicates that the pool header is corrupted. A Bad Pool Header issue is caused due to problems with Windows memory allocation. This error usually occurs after you’ve installed new hardware or software – usually the antivirus software – that doesn’t work with your Windows computer. However, faulty drivers and routers, bad sectors or other disk write issues could also cause this Blue Screen.
Fix BAD_POOL_HEADER Blue Screen on Windows
If you are unable to start Windows in Normal mode, try booting in Safe Mode. That will help as you work through a resolution. You can try the procedures listed below to resolve this issue. Go through the entire list of suggestions first and then decide which one or more of these you would like to try out.
1] Uninstall recently installed software
If you recently installed any software, uninstall it and see if that makes the error go away. Most of the time, third-party antivirus applications are responsible for the error. In case you have installed antivirus software products on your system, you can try uninstalling them temporarily. If this resolves the problem, you can replace them with other applications. In the Control Panel window, click on “Programs and Features” to open the list of programs installed on the system and uninstall the antivirus program – or the recently installed software.
2] Uninstall recently installed hardware
If you recently installed any hardware, open Devices Manager, find the hardware driver, right-click on it and select Uninstall. Restart your computer and see.
3] Disconnect external devices
Another cause of the error might be external devices that are interfering with the system. To isolate this cause, disconnect all peripherals and external devices except for the keyboard and mouse and restart your machine. Check if it resolves the issue. If it works, one or more of the previously connected external hardware devices might be faulty and need to be replaced. If this does not resolve the issue, you can try the next steps.
4] Disable Fast Startup feature
Disable Fast Startup feature and see. It is enabled by default in Windows. At times, it can interfere with the system and cause pool header corruption.
5] Update Device Drivers
Faulty drivers may cause issues. Though Windows Update updates all drivers, they can be manually updated as well if the former step doesn’t work. 
To update device drivers, press Win + R and open the Run window. Type devmgmt.msc to open the device manager. In the list of drivers, right-click on individual drivers and select “Update Driver Software” for each driver. Update all of them one by one.
You could also use Driver Verifier Manager to examine the behavior of bad drivers.
6] Perform a Clean Boot
Perform a Clean Boot and check if it resolves the problem. If you face no issues, it means that some non-Microsoft process is causing this stop error. You will have to manually try and identify the offender.
7] Perform Hardware Clean Boot
A Hardware Clean Boot is different from the usual Clean Boot State. The hardware components that are not necessary for a system to run are disabled in the Device Manager. 
Press Win+R to open the Run window. Type devmgmt.msc and press Enter to open the Device Manager. You may disable the drivers for the following devices by right-clicking them and selecting the option to disable them.
- Display Adapters.
- DVD/CD-ROM drives.
- Sound, video and game controllers.
- Network Adapters.
- Modems
- Ports
- USB Devices and controller – provided you are NOT using USB/Wireless Mouse or Keyboard.
Restart the system and verify if this fixes the error. If it does, then it means that one of these devices is the cause. Again you will have to try and identify the device manually by trial and error method.
8] Run Windows Memory Diagnostics Tool
You could also run the built-in Windows Memory Diagnostics Tool. Open the tool and click Diagnose your computer’s memory problems.? Once the run is completed, you may open the Event Viewer and look for the results in the MemoryDiagnostics-Results entry.
9] Check your RAM
This is usually done by a hardware expert, but it has been reported that the issue could be with the RAM. Therefore, it should be verified.
Hope something helps!
If you are an advanced user, you may visit Microsoft for more on this stop error.
See this post if you receive a BAD_POOL_CALLER error.
