Microsoft KB Archive/282504

From BetaArchive Wiki
Knowledge Base


How to Troubleshoot a STOP 0x0000001A MEMORY_MANAGEMENT Error Message

Article ID: 282504

Article Last Modified on 3/2/2007



APPLIES TO

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Datacenter Server



This article was previously published under Q282504

SYMPTOMS

If you are running Windows 2000, you may receive the following error message:

STOP 0x0000001A (parameter, parameter, parameter, parameter)
MEMORY_MANAGEMENT

For example:

Stop 1A (0x00000001, 0x00000043, 0x00024893, 0xffffffff)

The first parameter is 1, therefore the subtype is "The fork clone block reference count is corrupt. Only occurs on checked builds."

Everything else, must be examined individually.

CAUSE

This issue can indicate the existence of a general memory-management problem. The error message that is mentioned in the "Symptoms" section of this article is a Windows 2000 Executive character-mode STOP error message.

RESOLUTION

To resolve this issue, use the appropriate method:

  • If this is the first time you have started the computer after you install new hardware, remove the hardware and restart your computer.
  • View the following Microsoft Hardware Compatibility List Web site to verify that the hardware and its drivers are compatible with Windows 2000: For more information about your hardware, contact the manufacturer of your hardware.
  • If you are installing Windows 2000 for the first time, verify that your computer meets the Windows 2000 system requirements, including the amount of RAM and disk space that are required to install the operating system.
  • If Windows 2000 is loaded and no new hardware has been installed, restart your computer with the recovery options set to create a dump file. If the error message that is mentioned in the "Symptoms" section of this article continues to appear, select the Last Known Good option when you restart your computer. If there is no Last Known Good configuration, try to use the Emergency Repair Disk (ERD).

For additional information about Emergency Repair Disks, click the article number below to view the article in the Microsoft Knowledge Base:

231777 How to Create an Emergency Repair Disk in Windows 2000


For additional information about the Last Known Good configuration and other Windows 2000 boot options, click the article number below to view the article in the Microsoft Knowledge Base:

202485 Description of Safe Boot Mode in Windows 2000


Keywords: kberrmsg kbhardware kbprb KB282504