| Previous | Next |
| DRIVER_VERIFIER_DETECTED_VIOLATION | DRIVER_CAUGHT_MODIFYING_FREED_POOL |
DRIVER_CORRUPTED_EXPOOL
The DRIVER_CORRUPTED_EXPOOL bug check has a value of 0x000000C5. For DRIVER_CORRUPTED_EXPOOL, this indicates that the system attempted to access invalid memory at a process IRQL that was too high.
Important
This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.
DRIVER_CORRUPTED_EXPOOL Parameters
| Parameter | Description |
|---|---|
1 |
Memory referenced |
2 |
IRQL at time of reference |
3 |
0: Read 1: Write |
4 |
Address that referenced memory |
Cause for DRIVER_CORRUPTED_EXPOOL
The kernel attempted to access pageable memory (or perhaps completely invalid memory) when the IRQL was too high. For DRIVER_CORRUPTED_EXPOOL, the ultimate cause of this problem is almost certainly a driver that has corrupted the system pool.
In most cases, this bug check results if a driver corrupts a small allocation (less than PAGE_SIZE). Larger allocations result in bug check 0xD0 (DRIVER_CORRUPTED_MMPOOL).
Resolution for DRIVER_CORRUPTED_EXPOOL
The !analyze debug extension displays information about the bug check and can be helpful in determining the root cause. If you have recently installed any new software, check to see if it is properly installed. For DRIVER_CORRUPTED_EXPOOL, check for updated drivers on the manufacturer's website.
For DRIVER_CORRUPTED_EXPOOL, to debug this error, use the special pool option of Driver Verifier. For DRIVER_CORRUPTED_EXPOOL, if this fails to reveal the driver that caused the error, use the Global Flags utility to enable the special pool by pool tag.
For DRIVER_CORRUPTED_EXPOOL, for information about the special pool, consult the Driver Verifier section of the Windows Driver Kit.
Distinctive failure boundary for DRIVER_CORRUPTED_EXPOOL
DRIVER_CORRUPTED_EXPOOL identifies driver corruption of executive pool. Focus on executive pool allocations, tags, headers, guards, allocation/free stacks, and verifier findings. Identify writes beyond an allocation, double frees, use-after-free access, and incorrect pool type or IRQL.
Separating DRIVER_CORRUPTED_EXPOOL from neighboring bug checks
This value concerns executive pool integrity; keep it distinct from corruption of memory-manager private pool structures. For DRIVER_CORRUPTED_EXPOOL, preserve the original dump and use the documented parameters and stack to verify this distinction before changing drivers or platform configuration.
Looking for a different code? Search another status or error code.