BSOD 36 (NTFS_FILE_SYSTEM): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: NTFS_FILE_SYSTEM identifies a Windows bug check whose dump parameters and stack determine the failing component.

Could be also:
Constant	Type	OS
ERROR_SHARING_BUFFER_EXCEEDED	Win32 error	Windows
KERN_NOT_DEPRESSED	Kern return	Mac
ippStsNotSupportedCpu	Intel Ipp Status	Any
ENAMETOOLONG	errno	Linux
EINPROGRESS	errno	Mac
EIDRM	errno	Solaris
EDEADLK	errno	Windows

Previous	Next
FAT_FILE_SYSTEM	NPFS_FILE_SYSTEM

NTFS_FILE_SYSTEM

The NTFS_FILE_SYSTEM bug check has a value of 0x00000024. This indicates a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives.

Important

NTFS_FILE_SYSTEM Parameters

Parameter	Description
1	Specifies source file and line number information. For NTFS_FILE_SYSTEM, the high 16 bits (the first four hexadecimal digits after the "0x") identify the source file by its identifier number. For NTFS_FILE_SYSTEM, the low 16 bits identify the source line in the file where the bug check occurred.
2	If NtfsExceptionFilter is on the stack, this parameter specifies the address of the exception record.
3	If NtfsExceptionFilter is on the stack, this parameter specifies the address of the context record.
4	Reserved

Cause for NTFS_FILE_SYSTEM

One possible cause of this bug check is disk corruption. Corruption in the NTFS file system or bad blocks (sectors) on the hard disk can induce this error. Corrupted hard drive (SATA/IDE) drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

Resolution for NTFS_FILE_SYSTEM

To debug this problem: Use the .cxr (Display Context Record) command with Parameter 3, and then use kb (Display Stack Backtrace).

To resolve a disk corruption problem:

Check Event Viewer for error messages related to the hard drive appearing in the System Log that might help pinpoint the device or driver that is causing the error.
For NTFS_FILE_SYSTEM, try disabling any virus scanners, backup programs, or disk defragmenter tools that continually monitor the system.
You should also run hardware diagnostics supplied by the system manufacturer related to the storage sub system.
For NTFS_FILE_SYSTEM, use the scan disk utility to confirm that there are no file system errors. Select and hold (or right-click) on the drive you want to scan while investigating NTFS_FILE_SYSTEM and select Properties. Select Tools. Select the Check now button.
For NTFS_FILE_SYSTEM, confirm that there is sufficient free space on the hard drive. For NTFS_FILE_SYSTEM, the operating system and some applications require sufficient free space to create swap files and for other functions. For NTFS_FILE_SYSTEM, based on the system configuration, the exact requirement varies, but it is normally a good idea to have 10% to 15% free space available.
For NTFS_FILE_SYSTEM, use the System File Checker tool while investigating NTFS_FILE_SYSTEM to repair missing or corrupted system files. For NTFS_FILE_SYSTEM, the System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. For NTFS_FILE_SYSTEM, use the following command to run the System File Checker tool (SFC.exe).
```
REM NTFS_FILE_SYSTEM diagnostic command.
SFC /scannow
```
For more information, see Use the System File Checker tool to repair missing or corrupted system files.
Driver Verifier For NTFS_FILE_SYSTEM, Driver Verifier is a tool that runs in real time to examine the behavior of drivers. For NTFS_FILE_SYSTEM, if it see errors in the execution of driver code, it proactively creates an exception to allow that part of the driver code to be further scrutinized. For NTFS_FILE_SYSTEM, the driver verifier manager is built into Windows and is available on all Windows PCs. For NTFS_FILE_SYSTEM, to start the driver verifier manager, type Verifier at a command prompt. For NTFS_FILE_SYSTEM, you can configure which drivers you would like to verify. For NTFS_FILE_SYSTEM, the code that verifies drivers adds overhead as it runs, so try and verify the smallest number of drivers as possible. For more information, see Driver Verifier.

In the past, another possible cause of this stop code is depletion of nonpaged pool memory. For NTFS_FILE_SYSTEM, if the nonpaged pool memory is completely depleted, this error can stop the system. For NTFS_FILE_SYSTEM, however, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error.

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