What does BSOD 222 (POOL_CORRUPTION_IN_FILE_AREA) mean?

 
Could be also:
ConstantTypeOS
ERROR_BAD_FILE_TYPEWin32 errorWindows
Previous Next
DRIVER_INVALID_STACK_ACCESS IMPERSONATING_WORKER_THREAD

POOL_CORRUPTION_IN_FILE_AREA

The POOL_CORRUPTION_IN_FILE_AREA bug check has a value of 0x000000DE. This indicates that a driver has corrupted pool memory that is used for holding pages destined for disk.

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.

POOL_CORRUPTION_IN_FILE_AREA Parameters

None

Cause for POOL_CORRUPTION_IN_FILE_AREA

When the Memory Manager dereferenced the file, it discovered this corruption in pool memory.

Dump evidence for POOL_CORRUPTION_IN_FILE_AREA

For POOL_CORRUPTION_IN_FILE_AREA, preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “POOL_CORRUPTION_IN_FILE_AREA”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for POOL_CORRUPTION_IN_FILE_AREA

  • Run WinDbg !analyze -v, then inspect the documented meaning of each POOL_CORRUPTION_IN_FILE_AREA parameter instead of relying only on the probably-caused-by line.
  • Find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with pool / corruption / in / file / area.
  • For POOL_CORRUPTION_IN_FILE_AREA, keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.

Do not repeatedly reboot a machine affected by POOL_CORRUPTION_IN_FILE_AREA before collecting the dump and event logs. For POOL_CORRUPTION_IN_FILE_AREA, recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.


Looking for a different code? Search another status or error code.