| Previous | Next |
| UNEXPECTED_INITIALIZATION_CALL | NO_MORE_IRP_STACK_LOCATIONS |
CACHE_MANAGER
CACHE_MANAGER is specific to the file-system cache manager, not a generic disk error. Microsoft documents parameter 1 as packed source-file and source-line information: the high 16 bits identify an internal source file and the low 16 bits identify the line. That makes the first parameter useful for correlating repeated crashes from the same kernel build even when the symbolic stack looks similar.
What the documented cause narrows down
Microsoft lists depletion of nonpaged pool as one possible cause. The important distinction is resource pressure in kernel memory: a cache-manager stop can be the component that detects the failure even when another kernel-mode driver consumed the pool. A storage device failure therefore should not be inferred from the stop name alone.
What to inspect
- Record parameter 1 and the exact Windows build before comparing dumps.
- Use
!analyze -vand inspect nonpaged-pool pressure and the stack around the cache-manager path. - Compare repeated dumps for the same packed source location; a changing location may point to broader corruption or resource exhaustion rather than one fixed assertion.
References
Looking for a different code? Search another status or error code.