Troubleshoot blue screen failures in Windows use

the content in this article collect on the network

Stop message: 0x0000000A failure (device already installed)
Description text: irql_not_less_or_equal
Common Cause: The driver uses an unhealthy memory address.

Workaround: If Windows 2000 can also start, check the shutdown information displayed in Event Viewer, identify the device or driver that is causing the problem, turn off or disable some newly installed drivers, and remove the newly installed add-ons; remove some newly installed hardware ; Ensure that the drivers for the hardware device have been updated, and that the system has the latest BIOS, disable the memory caching feature in the BIOS, such as cache or shadow, run the system diagnostic tools provided by the computer manufacturer, especially the memory check; Check the Microsoft compatible hardware list (HCL) , ensure that all hardware and drivers are compatible with Windows 2000, restart the computer, and select Last Known Good Configuration to start the computer.

Stop message: 0x0000000a failure (when new device is newly added)
Description text: irql_not_less_or_equal
Common Cause: The driver uses an unhealthy memory address.

Workaround: During the block process, the screen prompts "when Setup is checking the computer hardware configuration, press the F5 key and follow the prompts to select the appropriate computer type." For example, when the juice machine is a single processor, select "Standard PC", disable the memory caching feature in the BIOS, remove all adapter cards, disconnect all hardware devices that are not necessary to start the computer, and then reinstall Windows 2000, if the system has a SCSI adapter card, Please indicates to an card sellers for the latest Windows 2000 drivers, disable the Sync negotiation feature, check the SCSI ID number of the endpoint and device, and if the system is equipped with an IDE device, the IDE port is primary. Check the master/slave/only settings for the IDE device. Remove all other IDE devices except hard drives, run system diagnostic tools provided by the computer manufacturer, especially memory checks, check the Microsoft compatible hardware list (HCL), ensure all hardware and drivers are compatible with Windows 2000, select Last Known Good Configuration Start the computer.

Stop message: 0x0000001e failure
Description text: kmode_exption_not_handled
Common Cause: Disk failure.

Workaround: Check for sufficient disk space, especially for new installations, disable the drivers shown in the Stop message and all newly installed drivers, and if you are using a video driver that is not provided by Microsoft, try switching to the standard VCA driver or by Windows 2000 supported appropriate drivers; Make sure the system has the latest BIOS; Select Last Known Good Configuration to start the computer.

Stop message: 0x00000023 and 0x00000024 failures
Description text: Fat_file_system or Ntfs_file_system
Common causes: Serious drive fragmentation, overloaded file I/O, third-party drive mirroring software, or some anti-virus software error.

Workaround: Disable some anti-virus software or backup programs, disable all defragmentation applications, run chkdsk/f to overhaul the hard drive, and then restart the computer; Select Last Known Good Configuration to start the computer.

Stop message: 0x0000002e failure
Description text: Data_bus_error
Common Cause: Parity errors in system memory.

Workaround: Run the System diagnostic tool provided by the computer manufacturer, especially the memory check, disable the memory caching feature in the BIOS, and try to start with "Safe Mode". If Safe mode starts your computer, try changing to a standard VGA driver. If this does not resolve the issue, you may need to use a different video adapter (compatible video adapter is listed in the "Compatible hardware List"), ensure that the drivers for the hardware device have been updated, and that the system has the latest bi0s, remove some newly installed hardware, and select "Last Known Good Configuration" to start the computer.

Stop message: 0x0000003f failure
Description Wenyu: No_mor_system_ptes
Common Cause: The driver was not completely purged.

Workaround: Remove some of the installed software, including backup tools or disk utilities, such as defragmentation and anti-virus software.

Stop message: 0x00000058 failure
Description text: Ftdisk_intern_error
Common Cause: An error occurred in the master drive of the fault-tolerant set.

Workaround: Start the computer from the mirrored (second) system drive with the Windows 2000 bootable floppy disk, and select Last Known Good Configuration to start the computer.

Stop message: 0x0000007b failure
Description text: Inaccessi_ble_boot_device
Common Cause: A problem occurred during initialization of the A/O system (usually a boot drive or file system)

Workaround: Check the computer for any viruses. This stop message usually appears when there is a virus in the boot sector, repair the drive with the repair console, remove the newly installed hard drive or control card, and if the system is equipped with a SCSI adapter card, indicates to an the card vendor for the latest Windows 2000 drivers, disable the Sync negotiation feature, Check the SCSI ID number of the end header and device, and if the system is equipped with an IDE device, set the IDE port to primary. Check the master/slave/0nly of the ided device. Apart from the hard disk, remove all other IDE devices and run Chkdsk. If Windows 2000 does not start Chkdsk, you must remove and connect the hard disk to another Windows 2000f system, then check the hard disk with the Chkdsk command, and select Last Known Good Configuration to start the computer.

Stop message: 0x0000007f failure
Description text: Unexpected_kernel_mode_trap
Common causes: hardware or software problems, hardware failure.

Workaround: Run the system diagnostic tools provided by the computer manufacturer, especially the memory check. This stop message often occurs in the case of errors or mis-mating memory, disables the memory caching feature in the BIOS, removes or replaces hardware and other peripherals, examines the Microsoft compatible hardware list (HCL), and ensures that all hardware and drivers are compatible with Windows 2000. This problem may be caused by an incompatible motherboard; Select Last Known Good Configuration to start the computer.

Stop message:0x00000050malfunction
Description text: Page_fault_in_nonpaged_area
Common Cause: Memory error (data cannot use paging file).

Workaround: Remove all newly installed hardware and run all system diagnostic software provided by the computer manufacturer. In particular, memory checks; Check that all new hardware or software is installed correctly, if this is a fresh installation, contact your hardware or software manufacturer for any Windows updates or drivers you may need, disable or uninstall all anti-virus programs, and disable BIOS memory options.

Stop message: 0x00000077 failure
Description text: Kernel_stel_stack_inpage_error
Typical reason: You cannot read the required page of kernel data into memory from a paging file.

Workaround: Use the latest version of the anti-virus software to check for viruses on your computer. If the virus is found, perform the necessary steps to clear it off the computer. Refer to all system diagnostic software provided by the manufacturer, especially memory check, disable BIOS memory option.

Stop message: 0x00000079 failure
Description text: Mismatched_hal
The usual reason: the hardware abstraction layer does not match the kernel or machine type (typically occurs when a single-processor and multiprocessor configuration files are mixed in the same system).

Workaround : To resolve this error, use the command console to replace the wrong system files on your computer. The kernel files of a single-processor system are Ntoskml.exe, while the kernel files of a multiprocessor system are Ntkrnlmp.exe, but these files correspond to the files on the installation media, and after Windows 2000 is installed, regardless of which source file is used, will be renamed to the Ntoskml.exe file. The HAL file also uses the name Hal.dll after the install, but there are several possible HAL files on the installation media.

Stop message: 0x0000007a failure
Description text: Kernel_data_inpage_error
Common Cause: The pages required for kernel data cannot be read into memory from the paging file (typically due to a failure on a paging file, a virus, a disk controller error, or a faulty memory).

Workaround: Use the latest version of the anti-virus software to check for viruses on your computer. If a virus is found. Then perform the necessary steps to remove him from the computer, see the anti-virus software documentation to learn how to perform these steps, or if the computer is formatted with the NTFS file system. You can restart the computer, and then run the CHKDSK/F/R command on the system partition. If the command cannot be started because of an error, use the command console and run the CHKDSK/R command, running all system detection software provided by the computer manufacturer, especially the memory check.

Stop message: 0xc0000021a failure
Description text: status_system_process_terminated
The usual reason: the user-mode subsystem, such as Winlogon or the client Server Runtime Subsystem (CSRSS), is corrupted, so security is no longer guaranteed.

Workaround: Remove any newly installed hardware, or restart the computer if you cannot log on. When the list of available operating systems appears, press the F8 key, select the Last Known Good Configuration option to start the computer, run the Recovery Console, and allow the system to fix any detected errors.

Stop message: 0xc0000221 failure
Description text: Status_image_checkisu7m_mismatch
Common Cause: The driver or system DLL has been corrupted.

Workaround: Run the console and allow the system to fix any detected errors, or if an error occurs immediately after the memory is added to the computer, the paging file may be corrupted, or the new memory will be faulty or incompatible. Remove the Pagefile.sys and return the system to its original memory configuration.

hope this will give you some help, do not see the full screen of English and letters and headache.

Add "General Stop Troubleshooting"

In theory, the pure 32-bit Windows 2000/XP will not crash, but this is only theoretically. A virus or hardware and hardware driver mismatch causes WINDOWS2000/XP to crash, and when Windows 2000/XP freezes, the monitor screen turns blue, and then a stop fault message appears. Here we describe the general stop fault handling method and special stop troubleshooting, respectively.

General Stop fault handling

1. First use the new antivirus software to check if there is a virus on your computer.

2. If Windows 2000/XP can start, check the information in Event Viewer to determine which device or driver is causing the failure. The Event Viewer is started by: start, Settings \ \ Control Panel, administrative tools \ \ Event Viewer, System log.

3. If you cannot start the computer, try to start the computer with Safe mode or Last Known Good configuration, and then remove or disable the newly installed add-in program or driver. If you cannot start your computer with Safe mode, use the repair console. Repair Console can disable some services, rename device drivers, overhaul boot sectors, or master boot records.

4. Remove the newly installed hardware device (RAM, adapter card, hard drive, modem, etc.).

5. Ensure that the drivers for the hardware device have been updated and that the system has the latest BIOS.

6. Run the system diagnostic tools provided by the computer manufacturer, especially the memory check.

7. Check the Microsoft compatible hardware list (HCL) to ensure that all hardware and drivers are compatible with WINDOWS2000/XP. Hcl.txt is in the Support folder of the Windows 2000/XP CD-ROM.

8. Disable the memory caching feature in the BIOS.

9. Restart the computer, at the Start screen, press F8 to enter advanced boot options, and then select Last Known Good Configuration. (Note: When you start the computer by using Last Known Good configuration, all of the computer's settings are reset to the configuration at the last successful startup.) ) 

10. If you have access to the Web, go to http://www.micr-osoft.com/ntserver/and click "Support"/"Search
knowledge Base ", at" Type your keywords here ", enter" Stop "and the corresponding number (if a Stop message" stop:0x0000000a "appears, you can enter" stop0x0000000a "here), Press ENTER to find out the workaround for the stop problem that appears.

This article is from the "run-of-the-punk blogs" blog, so be sure to keep this source http://xiexf.blog.51cto.com/11235927/1916876

Troubleshoot blue screen failures in Windows use