BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
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.
Arguments:
Arg1: 0000000000000003, the pool freelist is corrupt.
Arg2: ffffc000b0695010, the pool entry being checked.
Arg3: ffffc000b0695010, the read back flink freelist value (should be the same as 2).
Arg4: dead000000000000, the read back blink freelist value (should be the same as 2).
//Linked list corruption, an address has been corrupt
2: kd> dc dead000000000000
dead0000`00000000 ???????? ???????? ???????? ???????? ????????????????
dead0000`00000010 ???????? ???????? ???????? ???????? ????????????????
dead0000`00000020 ???????? ???????? ???????? ???????? ????????????????
dead0000`00000030 ???????? ???????? ???????? ???????? ????????????????
dead0000`00000040 ???????? ???????? ???????? ???????? ????????????????
dead0000`00000050 ???????? ???????? ???????? ???????? ????????????????
dead0000`00000060 ???????? ???????? ???????? ???????? ????????????????
dead0000`00000070 ???????? ???????? ???????? ???????? ????????????????
//The address has been written over with 'dead', not the typical behaviour of bad RAM
2: kd> dt nt!_LIST_ENTRY ffffc000b0695010
[ 0xffffe000`a6202790 - 0xffffe000`a6602790 ]
+0x000 Flink : 0xffffe000`a6202790 _LIST_ENTRY [ 0xffffc000`b0695010 - 0xffffc000`b0695010 ]
+0x008 Blink : 0xffffe000`a6602790 _LIST_ENTRY [ 0xdead0000`00000000 - 0x00800001`40001000 ]
//The linked list has indeed been corrupted, the address has been overwritten