Bad pool header blue screen windows 7 driver#

Arg4: 0032003a00360030, The corrupted value found following the pool block. Arg3: 0000000000001f40, The number of bytes allocated for the pool block. Arg2: fffffa8011ead000, The pool pointer being freed. Typically this means the consumer (call stack ) has overrun the block. Arguments: Arg1: 0000000000000021, the data following the pool block being freed is corrupt.

Bad pool header blue screen windows 7 driver#

The internal pool links must be walked to figure out a possible cause of the problem, and then special pool applied to the suspect tags or the driver verifier to a suspect driver. This may or may not be due to the caller. Hello, For the sake of completion, another exact same situation, BSOD's twice every month on average BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. Would a crash dump allow me to better determine what's going on here? I've resisted that because these nodes have 32GB of RAM. Would anyone here concur with this assessment? As often as HP has been releasing driver updates for blades of late, it's nearly impossible to tell which driver might have been recently updated and started this problem.

GetUlongFromAddress: unable to read from fffff80001fa4250ДEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP Arg4: 003900390031002e, The corrupted value found following the pool block. Arg3: 0000000000008fc0, The number of bytes allocated for the pool block. Arg2: fffffa8020109000, The pool pointer being freed. Here's a Windbg !analyze -v for the latest crash, which happened just after noon today: BAD_POOL_HEADER (19) The pool is already corrupt at the time of the current request. There is no active user logged on to the host OS when this occurs. Recently we began seeing random blue screens from each of the four nodes. These are HP BL460c's all in one chassis, configured identically. I have a four node Hyper-V cluster running 2008 SP2.