Sign in with
Sign up | Sign in
Your question

The bugcheck was: 0x00000024

Last response: in Windows 7
Share
Anonymous
a b $ Windows 7
December 22, 2009 12:50:04 AM

Our home desktop PC had been running WinXP-64 for 2years without any issues. Since the Installation of Win7-64 I keep getting BSOD every few days. Event viewer shows "The bugcheck was: 0x00000024" as the cause of all these crashes. What is this bugcheck and how can I fix it?

More about : bugcheck 0x00000024

a c 215 $ Windows 7
December 22, 2009 12:55:25 AM

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.

--------------------------------

To boil it down... you need to do 3 things here:

1. Run Hard drive diagnostics
2. Run RAM diagnostics
3. Add RAM if you don't have enough (though I'm doubtful on this one...)

For number 1 and 2, Download and burn a copy of the Ultimate Boot CD (www.ultimatebootcd.com) It contains Memtest86+, an excellent RAM diagnostic utility, as well as a number of good hard drive diagnostic tools. Run 2 or 3 of them just to be sure.
m
0
l
!