Stop 0x24 or NTFS_FILE_SYSTEM

The Stop 0x24 message indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to NTFS File System (NTFS) drives. A similar Stop message, 0x23, exists for the file allocation table (FAT16 or FAT32) file system.

Interpreting the Message

This Stop message has four parameters:

1. Source file and line number
2. A non-zero value that contains the address of the exception record (optional)
3. A non-zero value that contains the address of the context record (optional)
4. A non-zero value that contains the address where the original exception occurred (optional)

Parameters for this Stop message are useful only to Microsoft technical support with access to Windows source code. Stop messages resulting from file system issues have the source file and the line number within the source file that generated the error encoded in their first parameter. The first four hexadecimal digits (also known as the high 16 bits) after the 0x identify the source file number, and the last four hexadecimal digits (the low 16 bits) identify the source line in the file where the stop occurred.

Resolving the Problem

The following suggestions are specific to Stop 0x24 errors. For additional troubleshooting suggestions that apply to all Stop errors, see the section titled "Stop Message Checklist" later in this tutorial.

• Malfunctioning SCSI and Advanced Technology Attachment (ATA) hardware or drivers can also adversely affect the system's ability to read and write to disk, causing errors. If using SCSI hard disks, check for cabling and termination problems between the SCSI controller and the disks. Periodically check Event Viewer for error messages related to SCSI or FASTFAT in the System Log or any messages in the Applications And Services Logs\Microsoft\Windows\DiskDiagnostic\Operational log.
• Verify that the tools you use to continually monitor your system-such as virus scanners, backup programs, or disk defragmenters-are compatible with Windows. Some disks and adapters come packaged with diagnostic software that you can use to run hardware tests. For more information, see the documentation for your computer, hard disk, or controller.
• Check your hard disk for problems.
• onpaged pool memory might be depleted, which can cause the system to stop. You can resolve this situation by adding more RAM, which increases the quantity of nonpaged pool memory available to the kernel.