| Previous | Next |
| MEMORY1_INITIALIZATION_FAILED | CONFIG_INITIALIZATION_FAILED |
CACHE_INITIALIZATION_FAILED
Cache manager initialization failure for CACHE_INITIALIZATION_FAILED
CACHE_INITIALIZATION_FAILED is bug check code 0x00000066. The cache manager coordinates cached file I/O with the memory manager and file systems. This boot-phase bug check means the system could not initialize required cache-manager state.
How to read it in a dump
- Look for interactions with memory manager, file systems, storage, and boot-start file-system filters.
- The failure is early in startup, before normal cached I/O workloads.
- Memory pressure, corrupted system files, or filter drivers may be involved.
What to check
- Check boot-start file-system filters, storage drivers, and system file integrity.
- Inspect memory manager and cache manager stack frames.
- Compare with FILE_INITIALIZATION_FAILED and DIRTY_* memory bug checks if multiple dumps exist.
References
Dump evidence
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 “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each 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 cache / initialization.
- 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 this result before collecting the dump and event logs. 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.