Blue screen… Begining dump of physical memory

40 pts.
Windows 2000 Server
Help I am getting this error on my windows 2000 server stop 0x00000024 (0x0019025E,0xBD7154E, 0XBD71513C, 0xF1C31F7D) NTFS_File_System Xmode_Exception_Not_Handled Address 8045647C base at 50400000 Date stamp ntoskrnl.exe AddressBFB9B2BE base at BFB81000 Date stamp tcpip.sys Begining dump of Physical Memory Dumping physical memory to disk Please help me out

Answer Wiki

Thanks. We'll let you know when a new response is added.

I am no Windows Expert, but by default I have been working on it for over 20 years.

I found this on Microsoft’s Support Page: Error message in Windows 2000 – “Stop 0x24” or “NTFS _FILE_SYSTEM”

This issue can occur if a problem occurred within the Ntfs.sys file. The Ntfs.sys file is the driver file that enables your computer to read and write to NTFS partitions. Damage in the NTFS file system, damaged portions of your hard disk, or damaged SCSI or IDE drivers can also cause this issue.

To resolve this issue:
1. Interpret the error message. The stop error is followed by four parameters defined in order of appearance:

• Source file and line number.
• Optionally contains the address of the exception record.
• Optionally contains the address of the context record.
• Optionally contains 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.
2. Check Event Viewer for error messages from SCSI, FASTFAT (the System Log), or Autochk (the Application Log) that might help determine the device or driver that is causing the error.
3. Try disabling any virus scanning programs, backup programs, or disk defragmenter tools that constantly monitor your computer, and if possible, run hardware diagnostics tools supplied by your computer manufacturer.
4. Run chkdsk /r to detect and resolve any file system structural damage.
5. Depletion of non-paged pool memory can cause this issue. If you create a Services for Macintosh (SFM) volume on a large partition (7 gigabytes or larger) with a large number of files (at least 100,000) while the AppleTalk driver Apf.sys is running, the indexing routine consumes a large amount of non-paged pool memory. If the non-paged pool memory is completely depleted, this error can cause your computer to stop responding (hang). However, if the amount of available non-paged pool memory is very low during the indexing process, another kernel-mode driver requiring non-paged pool memory can also cause this issue. To resolve this issue, increase the amount of installed RAM to increase the quantity of non-paged pool memory available to the kernel, or reduce the number of files on the SFM volume.
Any corrupted system or data volume that is using NTFS can cause this error message. If you receive a “stop 0x24” error message when you restart the computer or when you try to run Setup or Recovery Console, you may not be able to determine the cause of the problem by using the steps outlined above. Instead, use one of the following methods to resolve the corrupted NTFS volume.


To make it easy just save off all your data and reload Windows from scratch. You might also want to put in a put in a disk drive.

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Pressler2904
    While the information provided above is correct as far as it goes, there are a number of other issues to consider as well: - The error discussed can be generated by a corrupt boot volume or by actual physical damage to the drive or array. Windows (especially Win2K) does NOT differentiate between physical disks and logical volumes presented by a RAID controller. Do you have a single physical drive as your boot volume, or is it part of a RAID array? If it is a RAID array, you will need to either boot from the array setup CD or from the controller ROM in order to attempt recovery. If you are booting from a single physical disk, then the Windows CD would be your best bet. - Have you validated your physical drive(s)? For single drive installations, use the tools available from the drive or computer manufacturer's website (Hitachi, WD, Seagate all have specific tools for their drives); for multiple disk arrays, use the controller BIOS to validate the component disks. - If you cannot repair the boot volume (and to my experience, you have about a 50/50 chance here), you might do well to perform a parallel install: On the system in question, add a disk of the appropriate type (SCSI, IDE, SATA or SAS) - different types can be used, for example an IDE drive can be used for a setup where the original drive is SCSI, but it's probably better to use the same type(s) of drive(s) - and install the proper version of Windows 2000. You will also need to install any needed programs on this new drive. Once installed and configured, you can then attempt to access the original drive or array and migrate your data. There are lots of variables to consider here, so additional information specific to your installation will be required - keep us posted on your progress...
    2,190 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: