BAD_POOL_HEADER

Code: 0x19 (25)

As HRESULT:As NTSTATUS:

Parameters

ParameterDescription
0x2The pool entry being checked
0x3The pool entry being checked
0x5One of the pool entries
0x6One incorrectly-calculated entry
0x70
0x80
0x9One incorrectly-calculated entry
0xAThe pool entry that should have been found
0xD, 0xE, 0xF, 0x23, 0x24, 0x25Reserved
0x20The pool entry that should have been found
0X21The pool pointer being freed
0X22The address being freed

Description

The BAD_POOL_HEADER bug check has a value of 0x00000019. This indicates that a pool header is corrupt.

Important

This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Cause

The pool is already corrupted at the time of the current request.

This may or may not be due to the caller.

Resolution

The internal pool links must be walked using the kernel debugger to figure out a possible cause of the problem.

Then you can use special pool for the suspect pool tags, or use Driver Verifier "Special Pool" option on the suspect driver. The !analyze extension may be of help in pinpointing the suspect driver, but this is frequently not the case with pool corrupters.

Use the steps described in Analyze Bug Check Blue Screen Data to gather the Stop Code Parameters. Use the stop code parameters to determine the specific type of code behavior you are working to track down.

Driver Verifier

Driver Verifier is a tool that runs in real time to examine the behavior of drivers. If it see errors in the execution of driver code, it proactively creates an exception to allow that part of the driver code to be further scrutinized. The driver verifier manager is built into Windows and is available on all Windows PCs. To start the driver verifier manager, type Verifier at a command prompt. You can configure which drivers you would like to verify. The code that verifies drivers adds overhead as it runs, so try and verify the smallest number of drivers as possible. For more information, see Driver Verifier.

Windows Memory Diagnostics

If this Bug Check appears inconsistently, it could be related to faulty physical memory.

Run the Windows Memory Diagnostics tool, to test the memory. In the control panel search box, type Memory, and then select Diagnose your computer's memory problems.‌ After the test is run, use Event viewer to view the results under the System log. Look for the MemoryDiagnostics-Results entry to view the results.

Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.

Associated Modules

ModuleCodeFound inDescription
EventCreate.exe0x1978.11011%1
KernelBase.dll0x1978.1The drive cannot locate a specific area or track on the disk.
NetTCPIP.dll0x191011Properties %1 and %2 should not have values at the same time
VSSVC.exe0x191011Volume Shadow Copy Service Warning: The Microsoft Shadow Copy Provider is shutting down and is experiencing delay while waiting for in-progress calls to complete. %1
WinMgmtR.dll0x191011Event provider %1 attempted to register query "%2" whose target class "%3" is not an event class. The query will be ignored. Contact the application vendor.
WinSAT.exe0x191011Running the formal assessment is not supported on this version of the operating system.
cipher.exe0x1978.11011%1: The file system does not support encryption.
compact.exe0x1978.11011Invalid drive specification: %1
cscui.dll0x191011The registry value '%1' in key '%2\%3' is not, or does not expand to, a valid UNC path.
dsreg.dll0x191011Automatic registration failed. Failed to lookup the registration service information from Active Directory. Exit code: %1. See http://go.microsoft.com/fwlink/?LinkId=623042
dssec.dll0x1978.11011Replicating Directory Changes
ehepgres.dll0x197%1
findstr.exe0x1911%1: Error - invalid quiet mode flag.
finger.exe0x1978.1Received bad initial opcode. Opcode = %1!d!
fontview.exe0x1978.11011%1, Single Master
ftp.exe0x1978.1Received bad initial opcode. Opcode = %1!d!
hostname.exe0x1978.1Received bad initial opcode. Opcode = %1!d!
kernel32.dll0x1978.11011The drive cannot locate a specific area or track on the disk.
msprivs.dll0x1978.11011Remove computer from docking station
netcfg.exe0x191011Access denied: Please re-run command from an elevated command prompt.
netdacim.dll0x198.11011The specified entry point ranges are not the best match for the entry point IP address.
netnccim.dll0x198.11011The specified entry point ranges are not the best match for the entry point IP address.
netttcim.dll0x198.11011The specified entry point ranges are not the best match for the entry point IP address.
nslookup.exe0x1978.11011User Information
powershell.exe0x198.11011Cannot start Windows PowerShell version %1!ls! because it is not installed.
powershell.exe0x197Cannot start Windows PowerShell version %1!ls! because it is not correctly installed.
reagentc.exe0x198.11011%1: Unable to update configuration file: Access denied.
sstpsvc.dll0x191011The certificate used for Secure Socket Tunnelling Protocol (SSTP) is missing. You should configure a new certificate for SSTP or use default configuration
tpm.sys0x191011Creation of the Windows AIK directory failed.
w32time.dll0x191011The time provider NtpClient cannot determine whether the response received from %1 has a valid signature. The response will be ignored. The error was: %2
webservices.dll0x1978.11011The operation could not be completed because the policy object is in a faulted state.
wecutil.exe0x1978.11011Invalid option %1!s!. Option is not integer.
wevtsvc.dll0x191011The event logging service encountered a corrupt log file for channel %1. The log was renamed with a .corrupt extension.
wevtutil.exe0x1978.11011Failed to open event metadata for publisher %1!s!.
wfascim.dll0x191011ICMP Type:Code pairs are only supported in Firewall rules.
whealogr.dll0x1971011A corrected hardware error has occurred. Component: PCI/PCI-X Bus Error Source: %1 Error Type: %5 Segment:Bus: %7:%6 The details view of this entry contains further information.
win32kbase.sys0x191011PenVisualization
wininit.exe0x1911Boot App Anti-Rollback: Previous timer resumed with status: HRESULT: %1 Previous timer present: %2 Start time: %3 Grace period: %4 Attempted recovery enforcement succeeded: %5
winsrv.dll0x1978.11011CriticalAppShutdownTimeout
winsrvext.dll0x1911CriticalAppShutdownTimeout
40 entries