XP Pro Blue Screen Error

Paul Cockerel · External Since: Oct 26, 2009 Posts: 1

I have Raid 1 Set up on a version of XP Pro and get this error message, I've
searched the knowledge base and forums and didn't find anything. Any help
would be appreciated.
0x00000024 (0X001902FE, 0XAAA25858, 0XAAA2554, 0XB9D50027)

NTFS.SYS-ADDRESS B9D50027 BASE AT B9D2B000 DATE STAMP 48025BE5

Leonard Grey · External Since: Jan 12, 2009 Posts: 98

STOP 0x24: NTFS_FILE_SYSTEM
http://www.aumha.org/a/stop.php#0x24
---
Leonard Grey
Errare humanum est

Paul Cockerel wrote:
> I have Raid 1 Set up on a version of XP Pro and get this error message, I've
> searched the knowledge base and forums and didn't find anything. Any help
> would be appreciated.
> 0x00000024 (0X001902FE, 0XAAA25858, 0XAAA2554, 0XB9D50027)
>
> NTFS.SYS-ADDRESS B9D50027 BASE AT B9D2B000 DATE STAMP 48025BE5
>

Richard · External Since: May 13, 2009 Posts: 36

> "Paul Cockerel" <PaulCockerel.RemoveThis@discussions.microsoft.com> wrote in message
> news:3DF20AF1-9D9E-48C4-A40C-774D38D4169D@microsoft.com...
> I have Raid 1 Set up on a version of XP Pro and get this error message,
> I've searched the knowledge base and forums and didn't find anything.
> Any help would be appreciated.
> 0x00000024 (0X001902FE, 0XAAA25858, 0XAAA2554, 0XB9D50027)
>
> NTFS.SYS-ADDRESS B9D50027 BASE AT B9D2B000 DATE STAMP 48025BE5

Hi Paul,

What is your complete Windows version, edition, and service pack level?
(For instance, I'm using Windows XP, Professional, Service Pack 3. Smile

Is the computer fully patched at Windows Update? Did you have problems
installing any of the October updates? Any other observations?

STOP 0x24: NTFS_FILE_SYSTEM
http://www.aumha.org/a/stop.php#0x24

Where are your getting the BSOD (Blue Screen of Death)?

The 4 additional parameters with your 0x00000024 STOP message are:
1. Source file and line number.
>> File: 0x0019 (Decimal:25), Line: 0x02FE (Decimal:766)
2. The address of the exception record.
3. The address of the context record.
4. The address where the original exception occurred.

"All stop errors due to problems with NTFS or FAT have encoded in their
first parameter the source file and the line number within the source file
that generated the stop error. The high 16 bits (the first four hexadecimal
digits after 0x) identify the source file number, and the lower 16 bits
(the last four hexadecimal digits of the parameter) identify the source
line in the file where the stop occurred."

Your message is the 2nd message this month with the 0x00000024 STOP error,
and the same (0x001902FE) first parameter.

If unable to start your computer normally, or in Safe Mode, boot to your
Windows setup CD, and use Recovery Console to fix the file system:
CHKDSK C: /P
(Assuming Windows is installed on your C: drive, change letter if not.)

It is not necessary to use the /R parameter unless you have dropped or
severely bumped the drive and suspect physical damage to sectors.

If you can get into Safe Mode with Command Prompt, use this command:
CHKDSK C: /F

(Note: /F at Windows command prompt is the same as /P in Recovery Console.)

Microsoft NOTE: "The Chkdsk tool has built-in support for NTFS and does
not require the Ntfs.sys driver to make repairs."

Therefore, if you have problems with Chkdsk, the drive itself is the more
likely problem, (not ntfs.sys,) either corrupt SCSI or IDE drivers, or
physical malfunction, such as power supply or over heating.

HTH. (Hope This Helps. Smile

--Richard

John John - MVP · External Since: Mar 06, 2009 Posts: 24

Richard wrote:
>> "Paul Cockerel" <PaulCockerel DeleteThis @discussions.microsoft.com> wrote in message
>> news:3DF20AF1-9D9E-48C4-A40C-774D38D4169D@microsoft.com...
>> I have Raid 1 Set up on a version of XP Pro and get this error message,
>> I've searched the knowledge base and forums and didn't find anything.
>> Any help would be appreciated.
>> 0x00000024 (0X001902FE, 0XAAA25858, 0XAAA2554, 0XB9D50027)
>>
>> NTFS.SYS-ADDRESS B9D50027 BASE AT B9D2B000 DATE STAMP 48025BE5
>
>
> Hi Paul,
>
> What is your complete Windows version, edition, and service pack level?
> (For instance, I'm using Windows XP, Professional, Service Pack 3. Smile

>
> Is the computer fully patched at Windows Update? Did you have problems
> installing any of the October updates? Any other observations?
>
> STOP 0x24: NTFS_FILE_SYSTEM
> http://www.aumha.org/a/stop.php#0x24
>
> Where are your getting the BSOD (Blue Screen of Death)?
>
> The 4 additional parameters with your 0x00000024 STOP message are:
> 1. Source file and line number.
> >> File: 0x0019 (Decimal:25), Line: 0x02FE (Decimal:766)
> 2. The address of the exception record.
> 3. The address of the context record.
> 4. The address where the original exception occurred.
>
> "All stop errors due to problems with NTFS or FAT have encoded in their
> first parameter the source file and the line number within the source file
> that generated the stop error. The high 16 bits (the first four hexadecimal
> digits after 0x) identify the source file number, and the lower 16 bits
> (the last four hexadecimal digits of the parameter) identify the source
> line in the file where the stop occurred."
>
> Your message is the 2nd message this month with the 0x00000024 STOP error,
> and the same (0x001902FE) first parameter.
>
> If unable to start your computer normally, or in Safe Mode, boot to your
> Windows setup CD, and use Recovery Console to fix the file system:
> CHKDSK C: /P
> (Assuming Windows is installed on your C: drive, change letter if not.)
>
> It is not necessary to use the /R parameter unless you have dropped or
> severely bumped the drive and suspect physical damage to sectors.
>
> If you can get into Safe Mode with Command Prompt, use this command:
> CHKDSK C: /F
>
> (Note: /F at Windows command prompt is the same as /P in Recovery Console.)
>
> Microsoft NOTE: "The Chkdsk tool has built-in support for NTFS and does
> not require the Ntfs.sys driver to make repairs."

If you do not disable the ntfs.sys driver the Recovery Console will load
it (from the CD or the floppy diskette set) and chkdsk *will* use it.
This may prevent chkdsk from successfully running on the corrupt volume.
See: http://support.microsoft.com/kb/228888

For all its worth, (I have not experienced that many 0x24 errors,
probably 5 or 6 in 13+ years of running NT systems), but I have never
been able to successfully resolve the problem. In all my cases the file
system was always damaged or corrupted beyond repair by chkdsk and the
driver was never the problem. I always view 0x24 errors as very bad
news, of course YMMV.

Regards;

John

PS. Keep up the good work, your posts are always very informative and
helpful!