| Previous | Next |
| DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS | PAGE_FAULT_BEYOND_END_OF_ALLOCATION |
PAGE_FAULT_IN_FREED_SPECIAL_POOL
PAGE_FAULT_IN_FREED_SPECIAL_POOL is a Special Pool use-after-free detection. Microsoft says the system referenced memory that had already been freed and notes that this usually indicates a system-driver synchronization problem. The emphasis is lifetime and synchronization, not allocation length.
Why Special Pool changes the evidence
Driver Verifier can place selected allocations in Special Pool so freed memory becomes protected. A stale reference that might otherwise corrupt unrelated data then faults at the invalid access. The crash therefore provides a better point for examining the thread and stack that still held the reference.
Investigate ownership transitions
- Find the code path that releases the object or buffer and the path that later touches it.
- Check cancellation, completion, timer, DPC, worker-item, and device-removal synchronization.
- Use the dump stack and verifier settings to identify the participating driver; do not treat the fault as recoverable with a kernel
try/except.
References
Looking for a different code? Search another status or error code.