◇ Solution:

Step 1: First open the command prompt and run the "Chkdsk /r" (note: not CHKDISK, it feels like this, but …) command to check and repair hard disk errors. If Bad Track is reported, please use the check tool provided by the hard disk manufacturer to check and repair.

Step 2: Then disable all software that scans files, such as antivirus software, firewall or backup tools.

Step 3: right click on the c: \ winnt \ system32 \ drivers \ fastfat.sys file and select "properties" to see if its version matches the version of Windows used by the current system. (note: if it is XP, it should be c: \ windows \ system32 \ drivers \ fastfat.sys)

Step 4: Install the latest motherboard drivers, especially IDE drivers. If your optical drive and mobile storage also provide drivers, it is better to upgrade them to the latest version.

0x00000027:RDR_FILE_SYSTEM

◆ Error Analysis: It is difficult to determine the cause of this error, but a problem with Windows memory management will probably lead to the occurrence of this shutdown code.

◇ Solution: If it is due to memory management, increasing memory will usually solve the problem.

0x0000002EATA_BUS_ERROR

◆ Error analysis: The parity check of system memory memory generates errors, which are usually caused by the device driver accessing the non-existent memory address when defective memory (including physical memory, secondary cache or video card memory) exists. In addition, the hard disk is damaged by viruses or other problems to generate this shutdown code.

◇ Solution:

(1) check the virus

(2) use the "chkdsk /r" command to check all disk partitions.

(3) use Memtest86 and other memory testing software to check the memory.

(4) Check whether the hardware is installed correctly, for example, whether it is firm and whether there are stains on gold fingers.

0x00000035:NO_MORE_IRP_STACK_LOCATIONS

◆ Error Analysis: Literally, there should be a stack problem with the driver or some software. In fact, the real cause of the failure should be the driver's native problem or the memory quality problem.

◇ Solution: Please use the driver and memory related solutions of the conventional solutions described earlier to eliminate them.

0x0000003F:NO_MORE_SYSTEM_PTES

◆ Error analysis: an error related to system memory management, such as: memory management problems caused by a large number of input/output operations: defective drivers using memory resources incorrectly; An application (e.g. backup software) is allocated a large amount of kernel memory.

◇ Solution: Uninstall all newly installed software (especially those applications that enhance disk performance and antivirus software) and drivers.

0x00000044:MULTIPLE_IRP_COMPLIETE_REQUESTS

◆ Error analysis: usually caused by hardware driver.

◇ Solution: Uninstall the recently installed driver. This failure rarely occurs. As far as we know, the Falstaff.sys file is the main culprit when using some software of this company in http://..........com/. (Does the author not fear lawsuits and publish the company's website)

0x00000050: PAGE_FAULT_IN_NONPAGED+AREA

◆ Error analysis: This error will be caused by faulty memory (including indoor memory, secondary cache and video memory), incompatible software (mainly remote control and antivirus software), damaged NTFS volume and faulty hardware (for example, PCI card itself is damaged).

◇ Solution: Please use the solutions related to memory, software, hardware, hard disk, etc. in the conventional solutions described earlier to eliminate them.

0x00000051:REGISTRY_ERROR

◆ Error Analysis: This shutdown code indicates that there is an error in the registry or system configuration manager. Due to physical damage to the hard disk itself or problems in the file system, an input/output error occurs when reading the registration file.

◇ Solution: Use "chkdsk /r" to check and repair disk errors.

0x00000058:FTDISK_INTERNAL_ERROR

◆ Error Analysis: Indicates that an error occurred in the main driver of the fault tolerance set.

◇ Solution: First try to restart the computer to see if the problem can be solved. If not, try "the last correct configuration" to solve the problem.

0x0000005E:CRITICAL_SERVICE_FAILED

◆ Error analysis: caused by startup identification of a very important system service.

◇ Solution: If a new piece of hardware comes out after installing it, you can first remove the hardware and check whether it is compatible with Windows 2K/XP through the online list. Then start the computer. If the blue screen still appears, please use "Last Correct Configuration" to start Windows. If this still fails, it is recommended to repair and install or reinstall.

0x0000006F:SESSION3_INITIALIZATION-FAILED

◆ Error Analysis: This error usually occurs when Windows starts, and is usually caused by a faulty driver or a corrupted system file.

◇ Solution: It is recommended to repair and install the system using the Windows installation CD.

0x00000076: PROCESS_HAS_LOCKED_PAGES

◆ Error analysis: It is usually because a driver did not release the occupied memory correctly after completing an input/output operation

◇ Solution:

Step 1: click start-> run: regedt32 to find [hklm \ system \ currentcontrolset \ control \ sessionmanager \ memory management], and create a new double-byte value of "TrackLockedPages" on the right with a value of 1. this way Windows will track which driver is the problem when the error occurs again.

Step 2: If the blue screen appears again, the error message will become:

STOP:0x0000000CB(0xY,0xY,0xY,0xY)DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS

The fourth "0xY" will be displayed as the name of the problem driver, and then it will be updated or deleted.

Step 3: Enter the registry and delete the added "TrackLockedPages".

0x00000077:KERNEL_STACK_INPAGE_ERROR

◆ Error Analysis: Indicates that the kernel data to be used is not found in virtual memory or physical memory. This error often results in disk problems, and the corresponding data is damaged or corroded by viruses.

◇ Solution: Use antivirus software to scan the system; Use the "chkdsk /r" command to check and repair disk errors, or if not, use the tools provided by the disk manufacturer to check and repair.

0x0000007A:KERNEL_DATA_INPAGE_ERROR

◆ Error analysis: This error is often caused by kernel data in virtual memory not being read into memory. The reason may be bad clusters, viruses, disk controller errors and memory problems in the virtual memory page file.

◇ Solution: First, use the antivirus software upgraded to the latest virus database to kill the virus. If there is still 0xC000009C or 0xC000016A code in the promotion information, it indicates that it is caused by a bad cluster and the disk detection tool of the system cannot be automatically repaired. At this time, enter the "Failure Recovery Console" and manually repair it with the "chkdsk /r" command.

0x0000007B:INACESSIBLE_BOOT_DEVICE

◆ Error analysis: Windows cannot access the system partition or boot volume during the boot process. It usually occurs during the first boot after replacing the motherboard, mainly because the IDE controller of the new motherboard and the old motherboard use different chipsets. Sometimes it may also be caused by virus or hard disk damage.

◇ Solution: Generally, the problem can be solved by starting the computer with the installation CD and then performing repair and installation. For viruses, the DOS version of antivirus software can be used for killing (the main battle is kv2005DOS version download). If there is a problem with the hard disk itself, please install it into other computers, and then use "chkdsk /r" to check and repair the disk errors.

0x0000007E:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

◆ Error Analysis: The system process generated an error, but the Windows error handler was unable to capture it. The causes include: hardware compatibility, faulty drivers or system services, or some software.

◇ Solution: Please use the "Event Viewer" to get more information and find out the root of the error. (Discovery seems not to be a solution. It seems that everyone here has to be self-reliant! )

0x0000007F:UNEXPECTED_KERNEL_MOED_TRAP

◆ Error analysis: It is usually caused by faulty hardware (e.g. memory) or some software. Sometimes overclocking will also cause this error.

◇ Solution: Check the memory with detection software (e.g. Memtest86). If overclocking is performed, please cancel overclocking. Pull the PCI hardware card out of the motherboard slot or replace the slot. In addition, if some motherboards (e.g. nForce2 motherboards) overclock, overheating of the South Bridge chip will also cause a blue screen. At this time, adding heat sink to the chip alone can often effectively solve the problem.

0x00000080:NMI_HARDWARE_FAILURE

◆ Error Analysis: It is usually caused by hardware. (It seems that blue screen is closely related to hardware error)

◇ Solution: If the new hardware is installed recently, please remove it, then try to replace the slot and install the latest driver. If the driver is upgraded, please restore the original version. Check whether there is any pollution and damage to the memory gold finger; Scan for viruses; Run "chkdsk /r" to check and repair disk errors; Check that all hardware plug-in cards have been firmly inserted. If the above attempts are ineffective, you will have to seek help from a professional computer maintenance company.

0x0000008E:KERNEL_MODE_EXCEPTION_NOT_HANDLED

◆ Error Analysis: The kernel-level application generated an error, but the Windows error handler did not capture it. It is usually a hardware compatibility error.

◇ Solution: Upgrade drivers or BIOS.

0x0000009C:MACHINE_CHECK_EXCEPTION

◆ Error analysis: usually caused by hardware. Usually caused by overclocking or hardware problems (memory, CPU, bus, power supply).

◇ Solution: If overclocking occurs, please lower the original CPU frequency and check the hardware.

0x0000009FRIVER_POWER_STATE_FAILURE

◆ Error analysis: It is often related to power supply and often occurs in power supply-related operations, such as shutdown, standby or sleep-off.

◇ Solution: Reinstall the system. If it cannot be solved, please replace the power supply.

0x000000A5:ACPI_BIOS_ERROR

◆ Error analysis: It is usually because the motherboard BIOS cannot fully support the ACPI specification.

◇ Solution: If there is no corresponding BIOS upgrade, when installing Windows 2K/XP, press F7 when prompted by "PressF6 if you need to install a third-party SCSI or RAID Driver", so Windows will automatically prohibit the installation of ACPI HAL and install Standard

PC HAL.

0x000000B4:VIDEO_DRIVER_INIT_FAILURE

◆ Error Analysis: This stop message indicates that Windows cannot enter the graphical interface because it cannot start the graphics card driver. It is usually a problem with the graphics card or there is a hardware conflict with the graphics card (for example, a conflict with a parallel or serial port).

◇ Solution: Enter the safe mode to see if the problem is solved. If yes, please upgrade the latest graphics driver. If not, it is likely that there is a conflict between the graphics card and the parallel port. You need to press WIN+break in the safe mode to open "System Properties", find and double-click the item connected to the printed LPT1 port in the hardware-> Device Manager, cancel the selection of "Use Automatic Configuration" in the "Resources" tab, and then change "03BC" of "Input/Output Range" to "0378".

0x000000BE:ATTEMPTED_WRITE_TO_READONLY_MEMORY

◆ Error analysis: caused by a driver attempting to write data to read-only memory. It is usually after installing a new driver, system service or upgrading the firmware program of the device.

◇ Solution: If the driver or service file name is included in the error message, please uninstall or disable the newly installed driver or software according to this information.

0x000000C2:BAD_POOL_CALLER

◆ Error Analysis: A kernel-level process or driver mistakenly attempts to enter memory operation. It is usually caused by the driver or software with BUG.

◇ Solution: Please refer to the items related to conventional solutions described earlier for exclusion.

0x000000CERIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

◆ Error analysis: usually caused by faulty driver or system service.

◇ Solution: Please refer to the items related to conventional solutions described earlier for exclusion.

0x000000D1RIVER_IRQL_NOT_LESS_OR_EQUAL

◆ Error analysis: It is usually caused by the faulty driver (such as Logitech MouseWare of Logitech mouse

Drivers in versions 9.10 and 9.24 will cause this failure). At the same time, defective memory, damaged virtual memory files, and some software (such as multimedia software, antivirus software, backup software, DVD player software) will also cause this error.

◇ Solution: Check the newly installed or upgraded driver (if there is a similar file name such as "acpi.sys" on the blue screen, you can be very sure of the driver problem) and software; Test the memory for problems; Enter the "Recovery Console", go to the partition where the virtual memory Pagefile.sys is located, execute the "del pagefile.sys" command, and delete the pagefile; Then execute the "chkdsk /r" command in the partition where the page file is located; After entering Windows, reset the virtual memory. If you encounter this blue screen while surfing the Internet, and you are just downloading and uploading a large amount of data (e.g. online games, BT downloads), then it should be a problem with the network card driver, which needs to be upgraded.

0x000000EA:THREAD_STUCK_IN_DEVICE_DRIVER

◆ Error analysis: usually caused by graphics card or graphics card driver.

◇ Solution: Upgrade the latest video card driver first. If not, replace the video card to test whether the fault still occurs.

0x000000ED:UNMOUNTABLE_BOOT_VOLUME

◆ Error analysis: Generally, it is caused by an error in the hard disk. Sometimes, it is also recommended to check whether the hard disk connection is not in good contact or not using a connection that meets the transmission specifications of the hard disk. For example, ATA-100 still uses the connection of ATA-33, which does not matter to the low-speed hard disk. However, the requirement for telling the hard disk (supporting ATA-66 or above) is relatively strict, and the connection with wrong specifications may sometimes cause this kind of failure that cannot be started. If this error occurs frequently after repair, it is probably the precursor of hard disk damage.

◇ Solution: Normally, restart will solve the problem. It is recommended to execute the "chkdsk /r" command to check and repair the hard disk anyway

0x000000F2:HARDWARE)INTERRUPT_STORM

◆ Error Analysis: The kernel layer detected an interrupt storm in the system. For example, a device did not release the interrupt it occupied after completing the operation. This is usually caused by a defective driver.

◇ Solution: Upgrade or uninstall the newly installed hardware drivers.

0x00000135:UNABLE_TO_LOCATE_DLL

◆ Error analysis: It usually indicates that a file is missing or damaged, or there is an error in the registry.

◇ Solution: If the file is missing or damaged, the corresponding file name will normally be displayed in the blue screen information. You can find the corresponding file through the network or other computers and copy it to the SYSTEM32 subfolder under the system folder. If the file name is not displayed, it is very likely that the registry is damaged. Please use system restore or previous registry backup to restore.

0x0000021A:STATUS_SYSTEM_PROCESS_TERMINATED

◆ Error analysis: The user mode subsystem, such as Winlogon or CSRSS, has been damaged, so the security cannot be guaranteed any more, resulting in the system being unable to start up. Sometimes, when the system administrator mistakenly modifies the user account permissions, the system cannot access the system files and folders.

◇ Solution: Use "Last Correct Configuration". If it is not valid, you can use the installation CD for repair and installation.

STOP 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH

◆ Error analysis: It is usually caused by damage to the driver or system DLL file. Generally, the file name will appear on the blue screen.

◇ Solution:

(1) Repair and install using Windows installation CD;

(2) if you can still enter the safe mode, you can "start-> run": sfc /scannow

(3) You can also use the method of extracting files to solve this problem. Enter the "Recovery Console" and use the copy or expand command to copy or decompress the damaged files from the CD. However, the blue screen is usually the problem of driver files, so the expand command will be used. For example, the blue screen prompts tdi.sys files, because the driver files are usually in i386\driver compression package. So use: expand% cdrom: \ i386 \ driver.cab \ f: TDI.sysc: \ winnt \ system \ drivers. (xp is expand% cdrom: \ i386 \ driver.cab \ f: TDI.sysc: \ windowns \ system \ Drivers) If these blue screen shutdown codes appear at startup, if blue screen appears at Windows startup and error messages appear in the table, then most of the time there is a problem with the hardware. Please use the diagnostic tools provided by the hardware manufacturer to determine whether there is a problem with the hardware, and go to its website to see if there is the latest driver.

Solution to Blue Screen Problem Windows 2K/XP Blue Screen Fault Inspection Information

　　1：***STOP 0x0000001E(0xC0000005,0xFDE38AF9,0x0000001,0x7E8B0EB4)

KMODE_EXCEPTION_NOT_HANDLED ***

The first part of the error is a Stop Code (STOP 0x0000001E) which is used to identify the type of error that has occurred. The second part of the error is a set of four numbers enclosed in brackets, representing a random developer-defined parameter (this parameter is completely incomprehensible to ordinary users and only understood by the driver writer or Microsoft operating system developer). The third part is the name of the error. The first line of information is usually used to identify the driver or device that produced the error. Most of this information is concise, but downtime can be used as a search term in Microsoft Knowledge Base and other technical materials. Windows 2K/XP has a lot of blue screen information, but the causes are often focused on incompatible hardware and drivers, problematic software, viruses, etc. Therefore, it provides some conventional solutions for everyone. When encountering blue screen errors, they should be eliminated by referring to these solutions.

(1): restart;

(2): Check whether the new hardware is plugged in firmly and install the latest driver. At the same time, check whether the hardware is compatible with the operating system against the hardware compatibility category of Microsoft website. If your hardware is not listed in the table, you will get the hardware manufacturer website to query.

(3): New drivers and new services: If you have just installed a new driver for a certain hardware or installed a certain software, and it has added corresponding items (such as antivirus software, CPU cooling software, firewall software, etc.) to the system service, and there is a blue screen failure during restart or use, please go to safe mode to uninstall or disable them;

(4): Virus checking: Viruses such as shock wave and oscillation wave sometimes cause Windows blue screen of death, so virus checking is essential. At the same time, some trojan spyware will also cause a blue screen, so it is better to use relevant tools for scanning and checking.

(5): Check BIOS and hardware compatibility: For newly installed computers, blue screen problems often occur, BIOS should be checked and upgraded to the latest version, and memory related items should be closed at the same time. For example, caching and mapping, in addition, one should check one's own hardware against Microsoft's hardware compatibility list, and if the motherboard BIOS cannot support large-capacity hard disks, it will also lead to blue screens, which need to be upgraded.

(6): check the system log: enter: EventVwr.msc in the start-> menu. press enter to display "event viewer", and pay attention to check the "system log" and "application log" items indicating "error";

(7): Query the stop code: Write down the dense E-text on the blue screen, then go to other computers to surf the Internet, enter the Microsoft Help and Support Network http://support.microsoft.com/, and enter the stop code in the "Search (Knowledge Base)" in the upper left corner. If there is no suitable information in the search result, you can select "English Knowledge Base" to search again. Under normal circumstances, you will find useful solutions here. In addition, in search engines such as baidu and Google, using the stop code of the blue screen or the following explanatory text as the key words for search will often bring additional gains.

(8): Last correct configuration: Under normal circumstances, the blue screen appears after updating the hardware driver or adding new hardware and installing its driver. At this time, the last correct configuration provided by Windows 2K/XP is the shortcut to solve the blue screen. Restart the system, press F8 when the startup menu appears, the advanced startup options menu will appear, and then select "Last Correct Configuration";

(9): Install the latest system patch and Service Pack: Some blue screens are caused by defects in Windows itself, which can be solved by installing the latest system patch and Service Pack.

Hardware Compatibility List for 　　Windows XP: http://support.microsoft.com/defaul...kb; zh-cn; 314062

Hardware Compatibility Category of 　　Windows 2K: http://winqual.microsoft.com/download/display.asp?

　　FileName=hcl/Win2000HCL.txt

　　2：0x0000000A:IRQL_NOT_LESS_OR_EQUAL

Error analysis: It is mainly caused by the driver of the problem, defective or incompatible hardware and software. From a technical point of view, it indicates that there is a memory address in kernel mode that it does not have permission to access at too high an in-process request level (IRQL).

Solution: Please try to exclude the 2, 3, 5, 8 and 9 solutions described earlier.

　　3：0x00000012:TRAP_CAUSE_UNKNOWN

Error Analysis: If this error message is encountered, unfortunately, the result of KeBudCheck analysis is that the cause of the error is unknown.

Solution: Please carefully recall when this mistake occurred. What did you do to the system when it first happened? What was being done at the time of occurrence, find out the possible reasons from this information, and then select the corresponding solution to try to exclude.

4：0x0000001A:MEMORY_MANAGEMENT

Error Analysis: This memory management error is often caused by hardware, for example, newly installed hardware, memory itself has problems, etc.

Solution: If it appears when installing Windows, it may be because your computer cannot meet the minimum memory and disk requirements for installing Windows.

　　5：0x0000001E:KMODE_EXCEPTION_NOT_HANDLED

Error Analysis: The Windows kernel has detected an illegal or unknown process instruction. This shutdown code is usually caused by the problem memory or a reason similar to the previous 0x0000000A.

Solution:

(1) Hardware Compatibility Problem: Please check whether all hardware is included in the latest hardware compatibility list mentioned earlier.

(2) device drivers, system services or memory conflicts and interrupt conflicts with problems; If the name of the driver appears in the blue screen information, please try to disable or delete the driver in the installation mode or the fault recovery console, and disable all newly installed drivers and software. If the error occurs during the system startup, please enter the safe mode and rename or delete the files indicated in the blue screen information.

(3) If the error message clearly indicates that Win32K.sys: It is most likely caused by the third-party remote control software and needs to be recovered from the failure, the console will shut down the service for the software.

(4) Appears during the first restart after installing Windows: the most probable cause is insufficient disk space in the system partition or BIOS compatibility problems.

(5) If it occurs when a software is shut down: it is very likely that there is a design defect in the software province, please upgrade or uninstall it.

　　6：0x00000023:FAT_FILE_SYSTEM

　　　 0x00000024:NTFS_FILE_SYSTEM

Error analysis: 0x00000023 usually occurs when reading and writing the system partition of FAT16 or FAT32 file system, while 0x00000024 is due to an error in NTFS.sys file (this driver file is used to allow the system to read and write disks using NTFS file system). The two blue screen errors are most likely caused by physical damage to the disk itself or damage to interrupt request packet (IRP). Other reasons include: too many hard disk fragments; File read and write operations are too frequent, and the amount of data is very large or caused by some disk image software or antivirus software.

Solution: First open the command prompt and run the "Chkdsk /r" (note: not CHKDISK, it feels like this, but …) command to check and repair hard disk errors. If Bad Track is reported, please use the check tool provided by the hard disk manufacturer to check and repair.

The second step is to disable all software that scans files, such as antivirus software, firewall or backup tools.

Step 3: Right click on C; \ winnt \ syst \ drivers \ fastfat.sys file and select "properties" to see if its version matches the version of Windows used by the current system. (note: if it is XP, it should be c: \ windows \ syst \ drivers \ fastfat.sys).

Step 4: Install the latest motherboard drivers, especially IDE drivers. If your optical drive and mobile storage also provide drivers, it is better to upgrade them to the latest version.

　　7：0x00000027:RDR_FILE_SYSTEM

Error Analysis: It is difficult to determine the cause of this error, but a problem with Windows memory management is likely to lead to the occurrence of this shutdown code.

Solution: If it is due to memory management, increasing memory will usually solve the problem.

8：0x0000002EATA_BUS_ERROR

Error analysis: parity check of system memory memory generates errors, which are usually caused by defective memory (including physical memory, secondary cache or video card display memory) when the device driver accesses the memory address that does not exist. In addition, the hard disk has been damaged by viruses or other problems to generate this shutdown code.

Solution:

(1) check the virus;

(2) Use the "chkdsk /r" command to check all disk partitions;

(3) use Memtest86 and other memory testing software to check the memory;

(4) Check whether the hardware is installed correctly, for example, whether it is firm and whether there are stains on gold fingers.

　　9：0x00000035:NO_MORE_IRP_STACK_LOCATIONS

Error Analysis: Literally speaking, there should be a stack problem with the driver or some software. In fact, the real cause of this failure should be a problem with the driver itself or a quality problem with the memory.

Solution: Please use the driver and memory related solutions in the general solution described earlier to exclude.

10：0x0000003F:NO_MORE_SYSTEM_PTES

Error analysis: an error related to system memory management, such as: memory management problems caused by a large number of input/output operations: defective drivers using memory resources incorrectly; A certain application (e.g. backup software) is allocated a large amount of kernel memory, etc.

Solution: Uninstall all newly installed software (especially those applications that enhance disk performance and antivirus software) and drivers.

　　11：0x00000044:MULTIPLE_IRP_COMPLIETE_REQUESTS

Error analysis: usually caused by hardware drivers.

Solution: Uninstall the recently installed driver. This failure rarely occurs. What we already know is that it is in use.

Some software of this company in http://..........com/ will appear from time to time, and the culprit is Falstaff.sys file.

　　12：0x00000050AGE_FAULT_IN_NONPAGED+AREA

Error analysis: The problem memory (including indoor memory, secondary cache, video memory), incompatible software (mainly remote control and anti-virus software), damaged NTFS volume and faulty hardware (such as the CI card itself is damaged) will cause this error.

Solution: Please use the solutions related to memory, software, hardware, hard disk, etc. in the conventional solution to eliminate them.

　　13：0x00000051:REGISTRY_ERROR

Error Analysis: This shutdown code indicates an error in the registry or system configuration manager. Due to physical damage to the hard disk itself or problems with the file system, an input/output error occurs when reading the registration file.

Solution: Use "chkdsk /r" to check and repair disk errors.

　　14：0x00000058:FTDISK_INTERNAL_ERROR

Error Analysis: Indicates an error occurred in the primary driver of the fault tolerance set.

Solution: First try to restart the computer to see if the problem can be solved, if not, then try "the last correct configuration" to solve the problem.

　　15：0x0000005E:CRITICAL_SERVICE_FAILED

Error analysis: caused by startup identification of a very important system service.

Solution: If a new piece of hardware comes out after installing it, you can first remove the hardware and check whether it is compatible with Windows 2K/XP through the online list, then start the computer. If the blue screen still appears, please use "Last Correct Configuration" to start Windows. If this still fails, it is recommended to repair, install or reinstall.

　　16：0x0000006F:SESSION3_INITIALIZATION-FAILED

Error Analysis: This error usually occurs when Windows starts, and is usually caused by a faulty driver or a corrupted system file.

Solution: It is recommended to use the Windows installation CD to repair and install the system.

　　17：0x00000076ROCESS_HAS_LOCKED_PAGES

Error Analysis: It is usually because a driver did not release the occupied memory correctly after completing an input/output operation.

Solution: 1. click start-> run: regedt32, find [hklm \ system \ currentcontrolset \ control \ sessionmanager \ memory management], and create a new double-byte value of "TrackLockedPages" on the right, with a value of 1, so that Windows can track which driver is the problem when the error occurs again. 2. If the blue screen appears again, the error message will become: STOP: 0x0000000CB (0xY, 0xY, 0xY, 0xY, 0xY) Driver _ LEFT _ LOCKED _ PAGES _ IN _ PROCESS, where the fourth "0xY" will be displayed as the name of the problem driver, and then it will be updated or deleted. Finally, enter the registry and delete the added "TrackLockedPages".

　　18：0x00000077:KERNEL_STACK_INPAGE_ERROR

Error Analysis: Indicates that the kernel data to be used is not found in virtual memory or physical memory. This error often results in disk problems, and the corresponding data is damaged or corroded by viruses.

Solution: Use anti-virus software to scan the system, use the "chkdsk /r" command to check and repair disk errors, and if not, use the tools provided by the disk manufacturer to check and repair.

　　19：0x0000007A:KERNEL_DATA_INPAGE_ERROR

Error Analysis: This error is often caused by kernel data in virtual memory not being read into memory, which may be due to bad clusters, viruses, disk controller errors and memory problems in the virtual memory page file.

Solution: First, use the antivirus software upgraded to the latest virus database to kill the virus. If there is still 0xC000009C or 0xC000016A code in the promotion information, it indicates that it is caused by a bad cluster and the disk detection tool of the system cannot be automatically repaired. At this time, enter the "Failure Recovery Console" and use the "chkdsk /r" command to manually repair.

20：0x0000007B:INACESSIBLE_BOOT_DEVICE

Error analysis: Windows cannot access the system partition or boot volume during the boot process. It usually occurs during the first boot after replacing the motherboard. It is mainly caused by the IDE controller of the new motherboard and the old motherboard using different chipsets. Sometimes it may also be caused by virus or hard disk damage.

Solution: Generally, the problem can be solved by starting the computer with the installation CD and then performing repair and installation. For viruses, the DOS version of antivirus software can be used for killing (the main battle is kv2005DOS version download). If there is a problem with the hard disk itself, install it on another computer, and then use "chkdsk /r" to check and repair disk errors.

　　21：0x0000007E:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Error Analysis: The system process generates an error, but the Windows error handler cannot capture it. The causes include: hardware compatibility, faulty drivers or system services, or some software.

Solution: Please use "Event Viewer" to get more information and find the root cause of the error.

　　22：0x0000007F:UNEXPECTED_KERNEL_MOED_TRAP

Error analysis: usually caused by faulty hardware (e.g. memory) or some software, sometimes overclocking will also cause this error.

Solution: check the memory with detection software (e.g. Memtest86). if overclocking occurs, please cancel the overclocking, unplug the PCI hardware card from the motherboard slot, or replace the slot. in addition, if some motherboards (e.g. nForce2 motherboards) overclock, the overheating of the south bridge chip will also cause a blue screen. at this time, adding heat sink to the chip alone can often effectively solve the problem.

　　23：0x00000080:NMI_HARDWARE_FAILURE

Error analysis: usually caused by hardware.

Solution: If new hardware is installed recently, remove it, and then try to replace the slot and install the latest driver. If the driver is upgraded, please restore the original version. Check whether there is any pollution and damage to the memory gold finger and scan for viruses; Run "chkdsk/r" to check and repair disk errors; Check that all the hardware cards have been plugged in firmly. If the above attempts are ineffective, you will have to find a professional computer maintenance company to ask for help.

　　24：0x0000008E:KERNEL_MODE_EXCEPTION_NOT_HANDLED

Error Analysis: A kernel-level application generated an error, but the Windows error handler did not capture it, usually due to a hardware compatibility error.

Solution: Upgrade drivers or upgrade BIOS.

　　25：0x0000009C:MACHINE_CHECK_EXCEPTION

Error analysis: usually caused by hardware, usually due to overclocking or hardware problems (memory, CPU, bus, power supply).

Solution: If overclocking occurs, please lower the original CPU frequency and check the hardware.

　　26：0x0000009FRIVER_POWER_STATE_FAILURE

Error analysis: it is often related to power supply and often occurs in power-related operations, such as shutdown, standby or sleep-off.

Solution: reinstall the system, if not, please replace the power supply.

　　27：0x000000A5:ACPI_BIOS_ERROR

Error Analysis: It is usually because the motherboard BIOS cannot fully support the ACPI specification.

Solution: if there is no corresponding BIOS upgrade, press F7 when prompted by "pressf6 if you need to install a third-party SCSI or raid driver" when installing Windows 2K/XP, so Windows will automatically prohibit the installation of ACPI HAL and install Standard PC HAL.

　　28：0x000000B4:VIDEO_DRIVER_INIT_FAILURE

Error Analysis: This stop message indicates that Windows cannot enter the graphics interface because it cannot start the graphics card driver. It is usually a problem with the graphics card or there is a hardware conflict with the graphics card (for example, a conflict with a parallel or serial port).

Solution: enter safe mode to see if the problem is solved. if yes, please upgrade the latest graphics driver. if not, it is likely that the graphics card conflicts with the parallel port. in safe mode, you need to press WIN+break to open "system properties", find and double-click the item connected to the printed LPT1 port in hardware-> device manager, cancel the selection of "use automatic configuration" in the "resources" tab, and then change "03BC" of "input/output range" to "0378".

　　29：0x000000BE:ATTEMPTED_WRITE_TO_READONLY_MEMORY

Error Analysis: A driver attempts to write data to read-only memory, usually after installing a new driver, system service, or upgrading the firmware program of the device.

Solution: If the driver or service file name is included in the error message, please uninstall or disable the newly installed driver or software according to this information.

30：0x000000C2:BAD_POOL_CALLER

Error Analysis: A kernel-level process or driver mistakenly attempts to enter memory operations, usually caused by the driver or software with bugs.

Solution: Please refer to the general solution related items described earlier for exclusion.

31 0x000000CERIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

Error analysis: usually caused by faulty drivers or system services.

Solution: Please refer to the general solution related items described earlier for exclusion. 　　

32：0x000000D1RIVER_IRQL_NOT_LESS_OR_EQUAL

Error analysis: It is usually caused by the faulty driver (for example, Logitech MouseWare 9.10 and 9.24 drivers of Logitech mouse will cause this failure). At the same time, defective memory, damaged virtual memory files, and some software (for example, multimedia software, antivirus software, backup software, DVD player software) will also cause this error.

Solution: Check the newly installed or upgraded driver (if there is a similar file name such as "acpi.sys" in the blue screen, you can be very sure of the driver problem) and software; Test the memory for problems; Enter the "Recovery Console", go to the partition where the virtual memory Pagefile.sys is located, execute the "del pagefile.sys" command, delete the pagefile, and then execute the chkdsk /r "command in the partition where the pagefile is located. Reset virtual memory after entering Windows. If you encounter this blue screen while surfing the internet, and you are just downloading and uploading a large amount of data (e.g. online games, BT downloads), then it should be the driver of the network card and you need to upgrade its driver.

　33：0x000000EA:THREAD_STUCK_IN_DEVICE_DRIVER

Error Analysis: Usually Caused by Graphics Card or Graphics Card Driver.

Solution: Upgrade the latest video card driver first. If not, replace the video card to test if the failure still occurs.

　34：0x000000ED:UNMOUNTABLE_BOOT_VOLUME

Error analysis: generally, it is caused by a disk error. sometimes it is suggested to check whether the hard disk connection is not in good contact or not using a connection line conforming to the transmission specifications of the hard disk. for example, ATA-100 still uses the connection line of ATA-33, which does not matter to low-speed hard disks. however, the requirement for telling hard disks (supporting ATA-66 or above) is relatively strict, and the connection line with wrong specifications may sometimes cause such failures that cannot be started. If this error occurs frequently after repair, it is likely to be the precursor of hard disk damage.

Solution: Normally, restart will solve the problem. However, it is recommended to execute the "chkdsk /r" command to check and repair the hard disk.

　35：0x000000F2:HARDWARE)INTERRUPT_STORM

Error Analysis: The kernel layer has detected an interrupt storm in the system. For example, a device did not release the interrupt it occupied after completing the operation. This is usually caused by a defective driver.

Solution: Upgrade or uninstall the newly installed hardware drivers.

　36：0x00000135:UNABLE_TO_LOCATE_DLL

Error Analysis: It usually indicates that a file is missing or damaged, or there is an error in the registry.

Solution: If the file is lost or damaged, the corresponding file name will normally be displayed in the blue screen information. You can find the corresponding file through the network or other computers and copy it to SYSTEM32 subfolder under the system folder. If the file name is not displayed, it is very likely that the registry is damaged. Please use system restore or previous registry backup to restore.

37：0x0000021A:STATUS_SYSTEM_PROCESS_TERMINATED

Error Analysis: The user mode subsystem, such as Winlogon or CSRSS, is damaged, so the security cannot be guaranteed any more, resulting in the system being unable to start. Sometimes, when the system administrator mistakenly modifies the user account permissions, they cannot access the system files and folders.

Solution: Use "Last Correct Configuration". If it is not valid, you can use the installation CD for repair and installation.

　38：STOP 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH

Error Analysis: It is usually caused by damage to the driver or system DLL file. Under normal circumstances, the file name will appear on the blue screen.

Solution:

(1) Repair and install using Windows installation CD;

(2) if you can still enter the safe mode, you can "start-> run": sfc /scannow

(3) The method of extracting files can also be used to solve the problem. Enter the "Recovery Console" and use the copy or expand command to copy or decompress the damaged files from the CD. However, the blue screen is usually the problem of driver files, so the expand command will be used. For example, the tdi.sys file is prompted in the blue screen, because the driver files are usually in i386\driver compression package. So use: expand% cdrom: \ i386 \ driver.cab \ f: tdi.sysc: \ winnt \ system \ drivers. (xp is expand% cdrom: \ i386 \ driver.cab \ f: tdi.sysc: \ windowns \ system \ drivers).

39: If the following blue screen shutdown code appears at startup:

If there is a blue screen and an error message in attachment 1 when Windows starts, then most of the time there is a problem with the hardware. please use the diagnostic tools provided by the hardware manufacturer to determine whether there is a problem with the hardware and check its website for the latest BIOS or firmware update program. If there is no problem with the hardware, reinstall Windows 2K/XP. If the same problem still occurs, you can only resort to professional technical support.

If you encounter the error message in Annex 2, you will only have to reinstall Windows. If you cannot solve the problem, it is recommended to ask for professional technical support.