BSOD 34 (FILE_SYSTEM): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: FILE_SYSTEM

Could be also:
Constant	Type	OS
ERROR_WRONG_DISK	Win32 error	Windows
KERN_INVALID_MEMORY_CONTROL	Kern return	Mac
ippStsStreamEnd	Intel Ipp Status	Any
ERANGE	errno	Any

Previous	Next
QUOTA_UNDERFLOW	FAT_FILE_SYSTEM

FILE_SYSTEM

FILE_SYSTEM is bug check 0x22. Microsoft lists the code but describes it only as very infrequent and does not publish a parameter table or a specific file-system driver for it. That absence matters: the symbolic name is not evidence that FAT, NTFS, CDFS, or NPFS is responsible.

Do not manufacture parameter meanings

For this code, interpret the four bug-check arguments from the dump and debugger output rather than assigning them semantics borrowed from another file-system stop code. Microsoft explicitly recommends !analyze for codes whose individual reference contains no richer public contract.

What can still be verified

Capture the exact stop arguments, Windows build, and loaded-module list.
Use !analyze -v and inspect the stack for a concrete file-system or filter-driver path.
Compare storage and file-system events at the crash time only after the dump identifies an I/O-related path; the name alone is too broad for a disk-corruption conclusion.

References

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