BAD_POOL_HEADER: Stop error
TL;DRThis is a Windows blue screen error indicating that the system detected corruption in a memory pool used by the kernel, which usually points to a driver or hardware problem causing the crash.
Most likely cause: Faulty or incompatible device driver
Try first: Restart your PC
Likely causes
- Faulty or incompatible device drivermost likely
- RAM hardware issue or corruptionpossible
- Corrupted system files or recent Windows update conflictless likely
How to fix it
Safest first: SafeChanges settingsDangerous
Restart your PCSafe
Power off completely and turn it back on to see if the error was a one-time glitch.
Run Windows Memory DiagnosticSafe
Search for Windows Memory Diagnostic in the Start menu, choose to restart and check for memory problems.
mdsched.exeBoot into Safe Mode and update driversChanges settings
Restart while holding Shift, go to Troubleshoot > Advanced > Startup Settings > Restart, then select Safe Mode. Use Device Manager to update or roll back recent drivers.
If that didn't fix it
Boot from a Windows installation USB and run the command 'sfc /scannow' from the recovery command prompt.
When to see a technician
If the error continues after memory checks and driver updates, have a technician test the RAM and other hardware components.
Quick answers
- What does BAD_POOL_HEADER: Stop error mean?
- This is a Windows blue screen error indicating that the system detected corruption in a memory pool used by the kernel, which usually points to a driver or hardware problem causing the crash.
- What causes BAD_POOL_HEADER: Stop error?
- Faulty or incompatible device driver. (most likely) RAM hardware issue or corruption. (possible) Corrupted system files or recent Windows update conflict. (less likely)
- How do I fix BAD_POOL_HEADER: Stop error?
- Try these in order, safest first: 1. Restart your PC. 2. Run Windows Memory Diagnostic. 3. Boot into Safe Mode and update drivers.
- What if that didn't fix it?
- Boot from a Windows installation USB and run the command 'sfc /scannow' from the recovery command prompt.
- When should I see a technician?
- If the error continues after memory checks and driver updates, have a technician test the RAM and other hardware components.