Stop: 0x24

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I have already posted this issue before but I'm still having problems
with my computer restarting. So I've been reading a lot of articles under
this search to find out what's going on with my computer. I tried System
Restore, running the chdsk /f for disk errors, and just about all that I
could find in resolution to this problem as prompted by Microsoft's online
articles but nothing seems to work.

Whenever I first turn on my computer, it restarts within 4 minutes and
then a blue screen appears with the following message:

Microsoft has detected an error..
STOP: 0x00000024 (0x001902FE, 0xF48F63C8, 0xF48F60C4, 0x8056AE04)

And then it asks me to run a disk check for chdsk /f, which I have done
so more than enough times but nothing happens. I also clicked on properties
for my C:/ drive and tried to run error-checking to check for volume errors.
I chose Scan for and attempt recovery of bad sectors but during the 2nd
phase, it says that the disk check cannot be completed.
I'm very lost so if --anyone-- can help, please do. Thank you in advance.

**I might also add that I am a novice at this so really, reading Microsoft
articles to configure a computer problem is difficult to understand at times,
especially when they throw in abbreviations of words or computer codes.

Thanks again~
 
Crysta said:
Hello,

I have already posted this issue before but I'm still having
problems
with my computer restarting. So I've been reading a lot of articles
under this search to find out what's going on with my computer. I
tried System Restore, running the chdsk /f for disk errors, and just
about all that I could find in resolution to this problem as prompted
by Microsoft's online articles but nothing seems to work.

Whenever I first turn on my computer, it restarts within 4 minutes
and then a blue screen appears with the following message:

Microsoft has detected an error..
STOP: 0x00000024 (0x001902FE, 0xF48F63C8, 0xF48F60C4, 0x8056AE04)

And then it asks me to run a disk check for chdsk /f, which I have
done
so more than enough times but nothing happens. I also clicked on
properties for my C:/ drive and tried to run error-checking to check
for volume errors. I chose Scan for and attempt recovery of bad
sectors but during the 2nd phase, it says that the disk check cannot
be completed. I'm very lost so if --anyone-- can help, please do.
Thank you in advance.

**I might also add that I am a novice at this so really, reading
Microsoft articles to configure a computer problem is difficult to
understand at times, especially when they throw in abbreviations of
words or computer codes.

Thanks again~
Click to expand...

See http://aumha.org/kbestop.htm

--
Frank Saunders, MS-MVP OE
Please respond in Newsgroup only. Do not send email
http://www.fjsmjs.com
Protect your PC
http://www.microsoft.com./athome/security/protect/default.aspx
http://defendingyourmachine.blogspot.com/
 
Crysta said:
Hello,

I have already posted this issue before but I'm still having
problems
with my computer restarting. So I've been reading a lot of articles
under
this search to find out what's going on with my computer. I tried
System Restore, running the chdsk /f for disk errors, and just about
all that I could find in resolution to this problem as prompted by
Microsoft's online articles but nothing seems to work.

Whenever I first turn on my computer, it restarts within 4 minutes
and
then a blue screen appears with the following message:

Microsoft has detected an error..
STOP: 0x00000024 (0x001902FE, 0xF48F63C8, 0xF48F60C4, 0x8056AE04)

And then it asks me to run a disk check for chdsk /f, which I have
done
so more than enough times but nothing happens. I also clicked on
properties for my C:/ drive and tried to run error-checking to check
for volume errors. I chose Scan for and attempt recovery of bad
sectors but during the 2nd phase, it says that the disk check cannot
be completed.
I'm very lost so if --anyone-- can help, please do. Thank you in
advance.

**I might also add that I am a novice at this so really, reading
Microsoft articles to configure a computer problem is difficult to
understand at times, especially when they throw in abbreviations of
words or computer codes.

Thanks again~
Click to expand...

Test the hard drive and the RAM. Here's how:

1) Test the RAM - I like Memtest86+ from www.memtest.org. Obviously, you
have to get the program from a working machine. You will either
download the precompiled Windows binary to make a bootable floppy or
the .iso to make a bootable cd. If you want to use the latter, you'll
need to have third-party burning software on the machine where you
download the file - XP's built-in burning capability won't do the job.
In either case, boot with the media you made. The test will run
immediately. Let the test run for an hour or two - unless errors are
seen immediately. If you get any errors, replace the RAM.

2) Test the hard drive with a diagnostic utility from the mftr. Download
the file and make a bootable floppy or cd with it. Boot with the media
and do a thorough test. If the drive has physical errors, replace it.

If this seems too difficult - and there is *no* shame in admitting that
it isn't your cup of tea - take the machine to a professional computer
repair shop (not your local equivalent of BigStoreUSA).

Malke
 
I have a similar problem but cannot get windows to start at all, I tested the
RAM by putting it into another comp, its ok, I took the HD to a shop and they
told me that it was ok but they error was a windows one and that all i could
do was reformat the HD, It has all of my old software and photos and files
etc that I dont want to lose.

STOP: 0x00000024(0x001902KA,OXF7CE2700,OXF7CE2400,OXF74DFBEF)
NTFS.SYS-ADDRESS F74DFBEF BASE AT F747B000 DATESTAMP 3D6DE5C1

is the error and the comp just keeps rebooting, the message is only visible
if I try to boot on the windows disk.

can this be rescued, or can i rescue the files in another way?
 
Tony said:
I have a similar problem but cannot get windows to start at all, I
tested the RAM by putting it into another comp, its ok, I took the HD
to a shop and they told me that it was ok but they error was a windows
one and that all i could do was reformat the HD, It has all of my old
software and photos and files etc that I dont want to lose.

STOP: 0x00000024(0x001902KA,OXF7CE2700,OXF7CE2400,OXF74DFBEF)
NTFS.SYS-ADDRESS F74DFBEF BASE AT F747B000 DATESTAMP 3D6DE5C1

is the error and the comp just keeps rebooting, the message is only
visible if I try to boot on the windows disk.

can this be rescued, or can i rescue the files in another way?
Click to expand...

Next time make a new post instead of tacking onto a very old closed
thread. Research your stop error here:

http://www.aumha.org/win5/kbestop.htm

If you decide to format the drive and clean-install Windows, you can get
your data off first with either Knoppix, a Bart's PE, or ERD Commander
(expensive but I believe an emergency version is available for d/l).

Knoppix is a Linux distro on a live cd. You will need a computer with
two cd drives, one of which is a cd/dvd-rw OR a usb thumb drive with
enough capacity to hold your data. To get Knoppix, you need a computer
with a fast Internet connection and third-party burning software.
Download the Knoppix .iso from www.knoppix.net and create your bootable
cd. Then boot with it and it will be able to see the Windows files. If
you are using the usb thumb drive, right-click on its icon (on the
Desktop) to get its properties and uncheck the box that says "Read
Only". Then click on it to open it. Note that the default mouse action
in the window manager used by Knoppix (KDE) is a single click to open
instead of the traditional MS Windows' double-click. Otherwise, use the
K3b burning program to burn the files to cd/dvd-r's.

http://www.nu2.nu/pebuilder/ (Bart's PE)
http://www.winternals.com/Products/AdministratorsPak/EmergencyDownload/Default.aspx

Malke
 
Driver Development Tools: Windows DDK

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 increase the amount of installed memory (which increases the quantity of nonpaged pool memory available to the kernel), or reduce the number of files on the SFM volume.
 
I have the same problem only this is with two different hard drives in
the same system. I went to go use my computer one day and it was stuck
in a cycle of booting, bluescreening and rebooting. I couldn't get it
to boot so I got out the Win2K CD and tried to re-install. The
installation got all the way to where it was going to format the hard
drive and it too blue screened. I attempted this a number of time to
the same result.

I proceeded by installing a new drive and installing Win2K on it. The
system was fine now. I tried to install the old drive as a slave to the
new one for additional space and received the same blue screen on
bootup. My assumption: Bad Drive. I pulled it out and lived on the new
drive.

All was fine for about a week. Now I wake up and the system is doing
the cyclical blue screen reboot sequence. As did the other one this one
will now not allow me to install Win2K either.

I am now leaning toward a virus or a physical problem with the IDE
bus.

Any suggestions?

Jeremy Severson
MCP
 
Back
Top