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 result 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. The high 16 bits (the first four hexadecimal digits after the "0x") identify the source file by its identifier number. 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

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

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:

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 it, Driver Verifier is a tool that runs in real time to examine the behavior of drivers. 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. The driver verifier manager is built into Windows and is available on all Windows PCs. To start the driver verifier manager, type Verifier at a command prompt. You can configure which drivers you would like to verify. 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. If the nonpaged pool memory is completely depleted, this error can stop the 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.