ResolutionĪctivate Driver Verifier with memory pool options enabled, to obtain more information about these errors and to locate the faulting driver.ĭriver Verifier is a tool that runs in real time to examine the behavior of drivers. Typically this is at a bad IRQL level or double freeing the same memory allocation, etc.

CauseĪn invalid pool request has been made by the current thread. In particular, 0 indicates nonpaged pool and 1 indicates paged pool. The _POOL_TYPE codes are enumerated in Ntddk.h. The current thread attempted to free a paged pool address in the middle of an allocation. Start offset from the beginning of the paged pool, in pages Using such tags makes tracking pool issues difficult. The current thread attempted to allocate a pool with a tag that does not contain any letters or digits. (This would be untrackable and could possibly corrupt the existing tag tables.) The current thread attempted to allocate a pool with a tag of 'BIG'. (This would be untrackable, and possibly corrupt the existing tag tables.) The current thread attempted to allocate a pool with a tag of 0 The current thread marked an allocation request MUST_SUCCEED. (This code can also indicate corruption in the pool header.)

The current thread attempted to free pool with an invalid address. (The caller of MmFreeContiguousMemory is passing a bad pointer.) The current thread attempted to free an invalid contiguous memory address. Start offset, in pages, from beginning of paged pool The current thread attempted to free a non-allocated paged pool address. The current thread attempted to free an invalid pool address. The current thread attempted to free a virtual address that was never in any pool. The current thread attempted to free a non-allocated nonpaged pool address. The current thread attempted to free the kernel pool at a user-mode address. The current thread attempted to release a quota on a corrupted pool allocation. (The memory might belong to another component.) The current thread attempted to free pool memory by using the wrong tag. The current thread attempted to free the pool at an invalid IRQL. The current thread attempted to allocate the pool at an invalid IRQL. The current thread attempted to free the pool, which was already freed. The current thread requested a zero-byte pool allocation. Parameter 1 indicates the type of violation. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Asus usb bt400 bad pool header