Error Message:



This Stop message indicates that a driver or a system DLL has been corrupted or is missing. Typically, the name of the damaged file is displayed as part of the message.

User Action:

To remedy this error, run the Emergency Recovery Disk (ERD) and allow the system to repair or replace the missing or damaged driver file on the system partition. You can also run an in-place upgrade over the top of the existing copy of Windows 2000. This preserves all registry settings and configuration information, but replaces all system files. If any Service Packs and/or hotfixes had previously been applied, reinstall them in the appropriate order (latest Service Pack, then any post-Service Pack hotfixes in the order in which they were originally installed, if applicable). If a specific file was identified in the Stop message as being corrupted, replace that individual file manually. If the system partition is formatted with FAT, restart the computer from an MS-DOS startup disk and copy the file from the original source onto the hard disk. If the partition is NTFS, restart the system, press F8 at the Operating System Loader menu, and choose Safe Mode with Command Prompt. From there, copy a fresh version of the file from the original source onto the hard disk. If the file 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. If these methods fail, reinstall Windows 2000 and then restore the system from a backup. Note If the original file from the product CD has a file name extension ending in an underscore, the file needs to be uncompressed before it can be used. The Recovery Consoles Copy command automatically detects compressed files and expands them as they are copied to the target location. If you are using Safe Mode to access a drive, use the Expand command to uncompress and copy the file to the target folder. You can use the Expand command in the command line environment of Safe Mode. Disk errors can be a source of file corruption. Run Chkdsk /f /r to detect and resolve any file system structural corruption. Restart the system before the disk scan begins on a system partition. If the error occurred immediately after RAM was added to the system, the paging file might be corrupted or the new RAM itself might be either faulty or incompatible. To determine if newly added RAM is causing a Stop message 1. Return the system to the original RAM configuration. 2. Use the Recovery Console to access the partition containing the paging file and delete the file Pagefile.sys. 3. While still in the Recovery Console, run Chkdsk /r on the partition that contained the paging file. 4. Restart the system. 5. Set the paging file to an optimal level for the amount of RAM added. 6. Shutdown the system and add your RAM. The new RAM must meet the system manufacturers specifications for speed, parity, and type (that is, fast page-mode (FPM) vs. extended data out (EDO) vs. synchronous dynamic random access memory (SDRAM)). Match the new RAM to the existing installed RAM as closely as possible. RAM comes in many different capacities, and more importantly, in different formats (single inline memory modules SIMMs or dual inline memory modules DIMMs). The electrical contacts can be either gold or tin and it is not wise to mix these contact types. If you experience the same error message after reinstalling the new RAM, run hardware diagnostics supplied by the system manufacturer, especially the memory scanner. For details on these procedures, see the owners manual for your computer. When you can log on to the system again, check the System Log in Event Viewer for additional error messages that might help pinpoint the device or is causing the error. Disabling memory caching of the BIOS might also resolve this error. For more troubleshooting information about this Stop message, refer to the Microsoft Knowledge Base at