BSOD 35 (FAT_FILE_SYSTEM): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Disable or uninstall any anti-virus, disk defragmentation or backup utilities. Check your hard drive configuration, and check for any updated drivers. Run CHKDSK /F to check for hard drive corruption, and then restart your computer.

Could be also:
Constant	Type	OS
KERN_INVALID_SECURITY	Kern return	Mac
ippStsDoubleSize	Intel Ipp Status	Any
EDEADLK	errno	Linux
EAGAIN	errno	Mac
ENOMSG	errno	Solaris

Previous	Next
FILE_SYSTEM	NTFS_FILE_SYSTEM

FAT_FILE_SYSTEM

FAT_FILE_SYSTEM is about the FAT file-system path. Its parameters are not merely placeholders: if FatExceptionFilter appears on the stack, parameter 2 is the exception-record address and parameter 3 is the context-record address. Those records are the first place to look before blaming the disk generically.

Distinguish structural corruption from a faulting I/O path

Microsoft documents file-system corruption, bad sectors, and damaged SCSI or IDE driver behavior as possible causes. It also lists nonpaged-pool depletion. A dump with a usable exception context should be analyzed at the recorded instruction; Event Viewer storage errors and file-system checks are more relevant when the evidence instead points to read/write failures or damaged FAT structures.

Useful checks

Use .cxr with parameter 3 when the documented exception-filter condition is met, then inspect the stack.
Correlate system storage events with the crash time.
Use chkdsk /f /r only for the corruption path; it does not diagnose a faulty filter or kernel driver.

References

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