ntfs.sys 0x24 error after clean install reboot - Overclock.net

Kerrdawg · 07-26-07

I am experiencing technical problems with my MOBO and windows.

I recently updated my old HDD from XP PRO to VISTA ULTIMATE, and after I installed some updates and a few drivers I rebooted my pc to a BSOD and a ntfs.sys 0x24 error. So I re-installed XP PRO and the same thing after a few updates and driver installs.
SO I switched HDDs to one of my rappy X's non raid mode and installed XP Pro again same thing.
Stripped out all but one stick of ram, CPU, 1 Vid card, 1 brand new WD500GB hdd and 1 BRD burner. Same thing!!! Also tried to install a fresh copy of windows on diffrent drives, plugged into different ports of the SATA controller.

I am thinking that the board has taken a crap, and the IDE/SATA controller has gone bad. I am going to boot to recovery console and rename NTFS.sys and reinstall it, to see what happens. I am at witts end here.

Anyone had this issue before?

jaslew · 07-26-07

Quote:

Bug Check 0x24: 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.

Parameters
The following parameters are displayed on the blue screen.

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 SCSI and IDE drivers can also adversely affect the system's ability to read and write to disk, thus causing the error.

Another possible cause 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.

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

To resolve a disk corruption problem: Check Event Viewer for error messages from SCSI and FASTFAT (System Log) or Autochk (Application Log) that might help pinpoint the device or driver that is causing the error. 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. For details on these procedures, see the owner's manual for your computer. Run Chkdsk /f /r to detect and resolve any file system structural corruption. You must restart the system before the disk scan begins on a system partition.

To resolve a nonpaged pool memory depletion problem: Either add new physical memory to the computer (thus increasing the quantity of nonpaged pool memory available to the kernel), or reduce the number of files on the Services for Macintosh (SFM) volume.

SOURCE

		Overclock.net - Overclocking.net > Software, Programming and Coding > Operating Systems > Windows
ntfs.sys 0x24 error after clean install reboot

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)