BAD_POOL_HEADER

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 00000020, a pool block header size is corrupt.
Arg2: 80594643, The pool entry we were looking for within the page.
Arg3: 80594c63, The next pool entry.
Arg4: e8c475ff, (reserved)

Debugging Details:
------------------

GetUlongFromAddress: unable to read from 80566d50

BUGCHECK_STR:  0x19_20

POOL_ADDRESS:  80594643

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

PROCESS_NAME:  System

LOCK_ADDRESS:  8055c4e0 -- (!locks 8055c4e0)

Resource @ nt!PiEngineLock (0x8055c4e0)    Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or
 already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or
 already deleted.

1 total locks

PNP_TRIAGE:
        Lock address  : 0x8055c4e0
        Thread Count  : 0
        Thread address: 0x00000000
        Thread wait   : 0x0

LAST_CONTROL_TRANSFER:  from 8054c583 to 804faf43

STACK_TEXT:
f7b008e8 8054c583 00000019 00000020 80594643 nt!KeBugCheckEx+0x1b
f7b00938 80594787 8059464b 00000000 81c94ee8 nt!ExFreePoolWithTag+0x2a3
f7b009b0 80598e29 fef6e248 00000001 e13ffbb4 nt!IopQueryDeviceResources+0x2ad
f7b009dc 8059968d e13ffba0 00000001 f7b00a2c nt!IopGetResourceRequirementsForAss
ignTable+0xd7
f7b00a38 8059c3ce f7b00a98 f7b00a74 00000000 nt!IopAllocateResources+0x4f
f7b00a90 8059c536 00000001 e13ffba0 00000001 nt!IopAssignResourcesToDevices+0x10
0
f7b00ac8 80593166 81c94ee8 00000000 f7b00b15 nt!IopProcessAssignResources+0xd6
f7b00d24 805937fa 81c94ee8 00000001 00000000 nt!PipProcessDevNodeTree+0xa6
f7b00d54 804f799e 00000003 8055c5c0 8056585c nt!PiRestartDevice+0x80
f7b00d7c 8053977d 00000000 00000000 82da0da8 nt!PipDeviceActionWorker+0x168
f7b00dac 805d0f70 00000000 00000000 00000000 nt!ExpWorkerThread+0xef
f7b00ddc 805470ee 8053968e 00000001 00000000 nt!PspSystemThreadStartup+0x34
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!ExFreePoolWithTag+2a3
8054c583 8b45f8          mov     eax,dword ptr [ebp-8]

SYMBOL_STACK_INDEX:  1

SYMBOL_NAME:  nt!ExFreePoolWithTag+2a3

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  48a3fbd9

FAILURE_BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+2a3

BUCKET_ID:  0x19_20_nt!ExFreePoolWithTag+2a3

Followup: MachineOwner
---------

0: kd>

这是什么原因啊