| Previous | Next |
| NTFS_FILE_SYSTEM | CDFS_FILE_SYSTEM |
NPFS_FILE_SYSTEM
NPFS_FILE_SYSTEM points at the Named Pipe File System path. NPFS implements Windows named-pipe semantics, so this stop code is materially different from FAT, CDFS, or a storage-volume bug check even though older reference text reused similar pool-exhaustion wording.
Read parameter 1 as a location key
Microsoft defines the high 16 bits of parameter 1 as an internal source-file identifier and the low 16 bits as a source-line number. Preserve that value with the OS build. It is a better discriminator for repeated NPFS failures than guessing from an application that happened to use a named pipe.
Diagnostic focus
- Run
!analyze -vand inspect the kernel stack for NPFS and filter-driver frames. - Because Microsoft lists nonpaged-pool depletion as a possible cause, check kernel memory pressure instead of treating the pipe name as the root cause.
- Correlate the crash with drivers that intercept file-system I/O or IPC traffic; a user-mode named-pipe client cannot by itself explain a kernel stop.
References
- Microsoft: Bug Check 0x25 NPFS_FILE_SYSTEM
- Microsoft: Named Pipes
- Microsoft: WinDbg kernel dump analysis
Looking for a different code? Search another status or error code.