Skip to content

This article will help you to fix BAD POOL HEADER BSOD in Windows 10/8.1/8/7. BAD_POOL_CALLER/HEADER BSOD error may occur due to memory corruption.

We’ve often discussed Blue Screen of Death (BSOD) errors on Windows 10. In this post, we’re going to discuss yet another BSOD error around which we came recently. This BSOD error is related to memory corruption on your system. Here is the error message and screenshot for your reference:

Your PC ran into a problem and needs to restart. We’ll restart for you.

Stop Code: BAD POOL HEADER

FIX BAD POOL HEADER BSOD In Windows 10

From the developer point of view, BAD_POOL_HEADER bug check has a value of 0x00000019. There is another similar error called BAD_POOL_CALLER, you may spot with value 0x000000C2. Both of these errors generally occurs due to faulty RAM and/or due to bad pool request. The meaning of this stop code can be interpreted as follow. Suppose ‘X’ is a process that entered into memory pool. Now once the process is done, it tries to came out of that memory pool and if it fails to do so, Windows restarts your machine automatically to prevent any extra damage to your system. So when Windows audits this error and ran it such situation, you see the BSOD as shown above. Once Windows restarts of its own, the process is no longer available and your system acts normally.

So this message may appear once or twice to your system and when system recovers itself and everything becomes normal, you can ignore it. But if this stop code message appearing repeatedly, you need to fix it, to secure your machine from further damage.

FIX : BAD POOL HEADER BSOD In Windows 10

Instead of faulty RAM on your system, this issue might occur due to third-party antivirus tool you’re using. So try uninstalling the antivirus program and make sure you’ve updated all devices drivers and see if it helps you to prevent this stop code. In case if issue persists, go ahead with these fixes:

FIX 1 – Using Blue Screen Troubleshooter

Microsoft has employed in-built troubleshooters to take care of issues in Windows 10. These troubleshooters can automatically detect issues and fix them, without requiring additional inputs from user side.

How To Use Built-in Troubleshooters In Windows 10

To deal this BSOD message, you can run Blue Screen Troubleshooter using steps mentioned here:

Steps to run Blue Screen troubleshooter in Windows 10

FIX 2 – Using Windows Memory Diagnostics Tool

Windows Memory Diagnostics is an excellent in-built tool in Windows for checking the memory corruption. Since this BSOD error is generally caused by faulty RAM, you must to run Windows Memory Diagnostics tool here to deal this issue.

How To Use Windows Memory Diagnostics In Windows 10

Following guide will show how to run Windows Memory Diagnostics:

Steps to run Windows Memory Diagnostics tool in Windows 10

FIX 3 – Using Driver Verifier

We all know Driver Verifier is in-built Windows feature to track real-time behavior of system drivers. So if any hardware driver is causing this stop error on your system, Driver Verifier will help you to catch this.

How To Use Driver Verifier In Windows 10

Here is the guide on how to use Driver Verifier:

Steps to run Driver Verifier in Windows 10

We hope after trying above mentioned fixes, you should be able resolve the issue, finally. But in case if problem still persists, simply look for the crash dump file at C:\Windows\Minidump (assuming C: as system root drive). Post this dump file (.DMP) to Microsoft Community or Technet IT Pro forums to have assistance from dump analysts.

Hope something helps!


Facebook Google+ Twitter

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Comments

  • Kapil Arya : ^^ Do you still have the issue after trying above mentioned ...

    11 hours ago

  • jimc : Been there. Done that. The more I use windows 10 the more I ...

    11 hours ago

  • Lieve Fivez : I can't use MY Connect for my new tomt Tom Tom because I get...

    19 hours ago

  • Kapil Arya : ^^ It won't create any problem provided you delete the corre...

    20 hours ago

  • richard : by deleting the registory editor does it create any problem?...

    20 hours ago

  • Kapil Arya : ^^ It seems you're on Home edition and Group Policy Editor w...

    1 day ago