Error Message:



This message typically indicates that a parity error in system memory has been detected. This error is almost always caused by a hardware problem: a configuration issue, defective hardware, or incompatible hardware. It is usually related to defective RAM, Level 2 (L2) RAM cache, or video RAM. However, it is sometimes caused when a device driver has accessed an address in the 0x8xxxxxxx range that does not exist (does not have a physical address mapping).

User Action:

This Stop message usually occurs after the installation of faulty hardware or when existing hardware fails. If hardware has recently been added to the system, remove it to see if the error recurs. If existing hardware has failed, remove or replace the faulty component. Run the hardware diagnostics supplied by the system manufacturer to determine which hardware component has failed. For details on these procedures, see the owners manual for your computer. Check that all network adapters in the computer are properly seated. Use an ink eraser or an electrical contact treatment, available at electronics supply stores, to ensure that network adapter contacts are clean. If the problem occurs on a newly installed system, check the availability of updates for the following items: firmware on reduced instruction set computing (RISC) systems, BIOS revisions on the motherboard, the SCSI controller or network adapters. Updates of this kind are typically available on the Web site or BBS of the hardware manufacturer. If the error occurs after installing a new or updated device driver, remove or replace the driver. If, under this circumstance, the error occurs during startup and the system partition is formatted with NTFS, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, start the computer using the Recovery Console in order to access the file. For additional error messages that might help pinpoint the device or driver that is causing the error, check System Log in Event Viewer. Disabling memory caching of the BIOS might also resolve this error. In addition, check the system for viruses, using any up-to-date, commercial virus scanning software that examines the Master Boot Record of the hard disk. This error can also be a result of hard disk corruption. Run Chkdsk /f /r on the system partition. Restart the system before the disk scan begins. If you cannot start the system due to the error, use the Recovery Console and run Chkdsk /r. Warning: If your system partition is formatted with the file allocation table (FAT) file system, the long file names used by Windows 2000 can be damaged if Scandisk or another MS-DOSbased hard disk tool is used to verify the integrity of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically derived from an MS-DOS startup disk or from starting MS-DOS on a multiboot system.) Always use the Windows 2000 version of Chkdsk on Windows 2000 disks. Finally, if all the above suggestions fail to resolve the error, take the system motherboard to a repair facility for diagnostic testing. A crack, a scratched trace, or a defective component on the motherboard can also cause this error. For more troubleshooting information about this stop error message, refer to the Microsoft Knowledge Base at