Windows 2K/XP Blue Screen Troubleshooting Information
1:*** STOP 0x0000001E(0xC0000005,0xFDE38AF9,0x0000001,0x7E8B0EB4)
KMODE_EXCEPTION_NOT _HANDLED ***
The first part of the error is the Stop Code, or STOP 0x0000001E, which identifies the type of error that has occurred, and the second part of the error is a set of four numbers enclosed in parentheses that represent a random, developer-defined
Parameters (which are impossible for a normal user to comprehend. Only driver writers or Microsoft operating system developers understand it), the third part is the error name, and the first line of the message is usually used to identify the driver or device that produced the error. Most of this information is very concise, but the downtime can be used as a search term in the Microsoft Knowledge Base and other technical information. Windows 2K/XP blue screen information is very large, but the reasons for them tend to be centered on incompatible hardware and drivers, faulty software, viruses, and so on, and therefore provides some general solutions for you to troubleshoot against when encountering a blue screen error. These programs to rule out. 1: reboot; 2: check whether the new hardware is firmly inserted, and install the latest driver, but also should be compared to the Microsoft Web site's hardware compatibility category to check whether the hardware is compatible with the operating system, if your hardware is not in the table, then get to the hardware manufacturer's Web site for querying; 3: the new driver and the new service: if you just installed the new driver for a certain hardware or installed a certain software, and it is in the system service, and it is in the system service. software, and it adds the corresponding items in the system services (for example: antivirus software, CPU cooling software, firewall software, etc.), in the reboot or the use of the blue screen failure, please go to Safe Mode to uninstall or disable them; 4: check for viruses: for example, Shockwave and Oscillating Wave and other viruses sometimes lead to the Windows blue screen of death, so checking for viruses is indispensable. At the same time, some Trojan spyware can also trigger the blue screen, so it is best to use the relevant tools for scanning and checking; 5: check the BIOS and hardware compatibility: for the newly installed computer often blue screen problems, you should check and upgrade the BIOS to the latest version, and at the same time to close the memory-related items. For example: cache and mapping, in addition, you should also check their own hardware against Microsoft's hardware compatibility list, there is, if the motherboard BIOS can not support large-capacity hard disk will also lead to blue screen, the need to upgrade it; 6: check the system log: in the start - & gt; menu enter: EventVwr.msc, enter to appear in the "Event Viewer", pay attention to check the" system log" and "Event Viewer". The first thing you need to do is to check the "System Log" and "Application Log" for items that indicate an "error"; 7: Query the downtime code: write down the dense E in the blue screen, then go online to other computers and enter the Microsoft Help and Support Network; 314062
Hardware compatibility category for Windows 2K:/download/display.asp?
FileName=hcl/win/windows2k.htm/windows2k.htm/windows2k.htm/windows2k.htm/windows2k.htm/windows2k.htm/windows2k.htm FileName=hcl/Win2000HCL.txt
2:0x0000000A:IRQL_NOT_LESS_OR_EQUAL
Error analysis:Mainly caused by faulty drivers, defective or incompatible hardware and software. From a technical point of view. Indicates that there is too high an Internal Request Level (IRQL) in kernel mode to access a memory address that it is not authorized to access
Memory Address.
Solution: please try to troubleshoot with options 2, 3, 5, 8, and 9 of the previously described solutions.
3: 0x00000012:TRAP_CAUSE_UNKNOWN
ERROR ANALYSIS: If this error message is encountered, then unfortunately it should be analyzed for KeBudCheck as the cause of the error is unknown.
Solution: Think back carefully to when this error occurred; what you did to the system when it first occurred; what you were doing at the time of the error, and identify the possible causes from this information, so that you can choose the appropriate solution to try to eliminate.
4: 0x0000001A:MEMORY_MANAGEMENT
Error Analysis: This memory management error is often caused by hardware, such as newly installed hardware, problems with the memory itself, etc. The error is caused by the fact that the system is not working properly.
Solution: If it occurs during the installation of Windows, it may be due to the fact that your computer does not meet the minimum memory and disk requirements for installing Windows.
5:0x0000001E:KMODE_EXCEPTION_NOT_HANDLED
Error Analysis:The Windows kernel has checked for an illegal or unknown process instruction. This downtime code is usually caused by faulty memory or something similar to the previous 0x0000000A.
Solution:
(1) Hardware compatibility problem: Please check whether all the hardware is included in the latest hardware compatibility list mentioned earlier.
(2) Problematic device drivers, system services, or memory conflicts and interrupt conflicts; If the name of the driver appears in the blue screen message, try disabling or removing the driver in the Installation Mode or Failure Recovery Console, and disable all just-installed drivers and software. If the error occurs during the system startup process, enter the Safe Mode, and rename or delete the file indicated in the blue screen message. rename or delete the files indicated in the blue screen message.
(3) If the error message clearly indicates Win32K.sys: it is likely to be caused by a third-party remote control software, you need to recover from the failure, the console will be closed to the services of the software.
(4) Appears on the first reboot after installing Windows: The most likely cause is insufficient disk space on the system partition or a BIOS compatibility problem.
(5) If it occurs when you close a piece of software, it is likely that the software itself has a design flaw, so please upgrade or uninstall it.
6: 0x00000023:FAT_FILE_SYSTEM
0x00000024:NTFS_FILE_SYSTEM
Error analysis: 0x00000023 usually occurs when reading or writing to the system partition of a FAT16 or FAT32 filesystem, while 0x00000024 is due to a system failure of the FAT16 or FAT32 filesystem. 0x00000024 is due to an error in the NTFS.sys file (the purpose of this driver file is to allow the system to read and write disks that use the NTFS file system). These two blue screen errors are most likely caused by either physical damage to the disk itself or damage to the Interrupt Request Packet (IRP). Other causes include: excessive disk fragmentation of the hard disk; too frequent file read/write operations and a very large amount of data or due to some disk mirroring software or antivirus software.
Solution: First, open a command line prompt and run the "Chkdsk /r" (note: not CHKDISK, it feels like this, but ......) command to check and repair the hard disk errors, and if you report the existence of a Wyatt track (Bad Track), please use the hard disk manufacturer's checking tool for If a Bad Track is reported, use the checking tool provided by the hard disk manufacturer to check and repair it.
The second step is to disable all software that scans files, such as antivirus, firewalls, or backup tools.
Third: Right-click on the C;\winnt\syst\drivers\fastfat.sys file and select "Properties" to see if its version matches the current version of Windows. (Note: For XP, it should be C:\windows\syst\drivers\fastfat.sys).
Fourth: Install the latest motherboard drivers, especially the IDE driver. If your CD-ROM drive and removable memory are also provided with drivers, it is best 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 this downtime code.
Solution: If it's a problem with memory management, adding more memory usually solves the problem.
8: 0x0000002EATA_BUS_ERROR
Error Analysis: System memory memory parity generates an error, usually due to defective memory (including physical memory, L2 cache, or graphics card video memory) when the device driver accesses a non-existent memory address and other reasons. In addition, hard disks are damaged by viruses or other problems in order for this downtime code to appear.
Solutions: (1) Check for viruses;
(2) Check all disk partitions using the "chkdsk /r" command;
(3) Check memory using memory testing software such as Memtest86;
(4) Check that the hardware is correctly mounted, e.g., is it secure, and that there is no tarnish on the gold fingers.
9: 0x00000035:NO_MORE_IRP_STACK_LOCATIONS
Error analysis: Literally, there should be a stack problem with the driver or some software, but in fact, the real cause of this failure should be a problem with the driver or a quality problem with the memory.
Solution: Please use the regular solutions related to the driver and memory as described in the previous section to troubleshoot.
10: 0x0000003F:NO_MORE_SYSTEM_PTES
Error Analysis: An error related to system memory management, such as: a problem with memory management due to a large number of input/output operations being performed: a defective driver using memory resources incorrectly; an application program (e.g., backup software) being allocated a large amount of memory resources; or an application program (e.g., backup software) being allocated a large amount of memory resources. ) is allocated a large amount of kernel memory, etc.
Solution: Uninstall all recently installed software (especially those applications and antivirus programs that enhance disk performance) and drivers.
11: 0x00000044:MULTIPLE_IRP_COMPLIETE_REQUESTS
Error analysis: Usually caused by hardware drivers.
Solution: Uninstall the recently installed driver, this fault rarely occurs, what is known is that it occurs when using
/ some software from this company, the culprit of which is the Falstaff.sys file.
12: 0x00000050AGE_FAULT_IN_NONPAGED+AREA
Error analysis: faulty memory (including house memory, L2 cache, video memory), incompatible software (mainly remote control and antivirus software), corrupted NTFS volumes, and faulty hardware (e.g., the CI plug-in card itself has been corrupted ), etc. can trigger this error.
Solution: Please use the regular solutions related to memory, software, hardware, hard disk, etc. for troubleshooting.
13: 0x00000051:REGISTRY_ERROR
Error Analysis: This stop code indicates that there is an error in the registry or System Configuration Manager, due to physical damage to the hard disk itself or a problem with the file system, which results in input/output errors when reading the registration file.
Solution: Use "chkdsk /r" to check and fix the disk error.
14: 0x00000058:FTDISK_INTERNAL_ERROR
Error analysis: An error has occurred in the main driver of the fault tolerance set.
Solution: First try restarting 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: A very important system service startup is recognized.
Solution: If it is new after installing a new hardware, you can remove the hardware and check if it is compatible with Windows 2K/XP through the online list, then start the computer, if the blue screen still occurs, please use the "Last Correct Configuration" to start Windows.
If it still fails, it is recommended to repair the installation or reinstall. or reinstall.
16:0x0000006F:SESSION3_INITIALIZATION-FAILED
Error Analysis: This error usually occurs during Windows startup, and is usually caused by faulty drivers or corrupted system files.
Solution: It is recommended to use the Windows installation CD to repair and install the system.
17: 0x00000076ROCESS_HAS_LOCKED_PAGES
Error Analysis:Usually, a driver fails to free up the memory it occupies after completing an input/output operation.
Solution: 1. Click Start->Run:regedt32, find [HKLM\SYSTEM\Currentcontrol set\control\sessionmanager\memory management], and create a new double-byte value on the right. TrackLockedPages" on the right side, the value is 1, so that Windows will track which driver is the problem when the error occurs again. 2, if the blue screen appears again, then the error message will become: STOP:0x0000000CB(0xY,0xY,0xY,0xY,0xY)DRIVER_LEFT_LOCKED_PAGES_IN_PRPRINTS PAGES_IN_PROCESS, where the fourth "0xY" will be shown as the name of the problematic driver, and then update or delete it. Finally, go to the registry and delete the added "TrackLockedPages".
18:0x00000077:KERNEL_STACK_INPAGE_ERROR
Error analysis: The kernel data that needs to be used is not found in virtual or physical memory. This error is often indicative of a disk problem, corrupted data, or a virus.
Solution: Use antivirus software to scan the system, use the "chkdsk /r" command to check and repair the disk error, 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 the kernel data in the virtual memory can not be read into the memory, the reason may be that there are bad clusters in the virtual memory page file, viruses, disk controller errors, memory problems.
Solution: First of all, use the upgrade to the latest virus database antivirus software to check for viruses, and if there is still 0xC000009C or 0xC000016A code in the promotion of no information, then it means that it is caused by bad clusters and the system's disk detection tool can't fix it automatically, so you have to go to the "Faulty Recovery Console" and use the "chkdsk /r" command to fix it manually.
20:0x0000007B:INACESSIBLE_BOOT_DEVICE
Error analysis: Windows cannot access the system partition or boot volume during the boot process, which usually occurs during the first boot after replacing the motherboard, mainly due to the use of different chipsets for the IDE controllers on the new and old motherboards. Sometimes it can also be caused by viruses or hard disk damage.
Solution: Generally, as long as the installation CD-ROM to start the computer, and then perform the repair and installation can solve the problem, for the virus can use the DOS version of the antivirus software to check (the main battle with the kv2005DOS version of the download). If there is a problem with the hard drive itself, install it on another computer and then use "chkdsk /r" to check and repair the disk error.
21:0x0000007E:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
Error Analysis: The system process generates an error that the Windows error handler is unable to catch, for a variety of reasons, including: hardware compatibility, faulty drivers or system services, or some software.
Solution: Use the Event Viewer to get more information and discover the root cause of the error.
22:0x0000007F:UNEXPECTED_KERNEL_MOED_TRAP
Error analysis: This error is usually caused by faulty hardware (e.g., memory) or some software, and sometimes overclocking can also cause this error.
Solution: Use testing software (such as: Memtest86) to check the memory, if overclocking, please cancel overclocking, the PCI hardware card from the motherboard slot, or replace the slot, in addition, some motherboards (such as: nForce2 motherboards) in the overclocking, the Southbridge chip overheating can also lead to a blue screen, at this time, for the chip to increase the separate heatsink often The newest addition to the list is a new one, which will allow the user to get a better idea of what to expect.
23:0x00000080:NMI_HARDWARE_FAILURE
Error analysis: usually caused by hardware.
Solution: If you have recently installed new hardware, please remove it, then try to replace the slot and install the latest driver, if you have upgraded the driver, please restore the original version; check the memory gold finger is not contaminated and damaged, scanning for viruses; run "chkdsk/r" to check and repair disk errors; check that all the hardware cards have been inserted securely, if all the above attempts have no effect, you have to find a professional If the above attempts are not effective, you have to find a professional computer repair company to ask for help.
24:0x0000008E:KERNEL_MODE_EXCEPTION_NOT_HANDLED
Error analysis: The kernel-level application is generating an error that is not being captured by the Windows error handler, usually a hardware compatibility error.
Solution: Upgrade the driver or upgrade the 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 you have overclocked, please lower the CPU frequency and check the hardware.
26: 0x0000009FRIVER_POWER_STATE_FAILURE
Error analysis: Often related to the power supply, often occurs in the power-related operations, such as: shutdown, standby, or sleep.
Solution: Reinstall the system, if it can not be solved, please replace the power supply.
27:0x000000A5:ACPI_BIOS_ERROR
Error analysis: Usually it is because the motherboard BIOS does not fully support the ACPI specification.
Solution: If you don't have the appropriate BIOS upgrade, you can press the F7 key when installing Windows 2K/XP when the "press F6 if you need to install a third-party SCSI or RAID driver" prompt appears, so that Windows will automatically disable the installation of the ACPI HAL and install the ACPI HAL instead.
28:0x000000B4:VIDEO_DRIVER_INIT_FAILURE
Error analysis: This stop message indicates that Windows cannot enter the graphical interface because it cannot start the graphics driver, which is usually a problem with the graphics card. Or there is a hardware conflict with the graphics card (e.g., with a parallel or serial port).
Solution: Enter Safe Mode to see if the problem is solved, if you can, please upgrade the latest graphics card driver, if it does not work, it is likely that the graphics card and the parallel port there is a conflict, you need to be in Safe Mode by pressing WIN + break key combination to open the "System Properties", in the Hardware - & gt; Device Manager to find and double-click on the connection to the print LPT1 port of the item! In the "Resources" tab, uncheck "Use Auto Configuration", and then change "03BC" to "0378" for "Input/Output Range".
29: 0x000000BE:ATTEMPTED_WRITE_TO_READONLY_MEMORY
Error analysis: A driver attempted to write to read-only memory, usually after installing a new driver, system service, or upgrading the device's firmware.
Solution: If a driver or service file name is included in the error message, uninstall or disable the newly installed driver or software based on this information.
30: 0x000000C2:BAD_POOL_CALLER
Error analysis: A kernel-level process or driver incorrectly attempted to access a memory operation, usually caused by a driver or software with a bug.
Solution: Please refer to the items related to the conventional solutions described earlier for troubleshooting.
31: 0x000000CERIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Error Analysis: Usually caused by a faulty driver or system service.
Solution: Please refer to the items related to the regular solutions described earlier for troubleshooting.
32: 0x000000D1RIVER_IRQL_NOT_LESS_OR_EQUAL
Error analysis: Usually caused by faulty drivers (e.g. Logitech MouseWare version 9.10 and 9.24 drivers for Logitech mice can trigger this fault), as well as defective memory, corrupted virtual memory files, certain software (e.g. multimedia software, antivirus software, backup software, DVD playback software), etc. can also cause this error.
Solution: Check the latest installed or upgraded drivers (if "acpi.sys" or similar filenames appear in the blue screen, you can be very sure that there is a driver problem) and software; test whether there is a problem with the memory; go to the Failure Recovery Console, go to the partition where the virtual memory page file Pagefile.sys is located, and run "del pagefile.sys" command, delete the page file, and then execute the "chkdsk /r" command on the partition where the page file is located; enter Windows and reset the virtual memory. If you encounter this blue screen while surfing the web, and you happen to be downloading and uploading a lot of data (e.g., online games, BT downloads), then it should be a problem with your NIC driver, and you need to upgrade your driver.
33:0x000000EA:THREAD_STUCK_IN_DEVICE_DRIVER
Error analysis: Usually triggered by the graphics card or graphics card driver.
Solution: Upgrade to the latest graphics card driver, and if that doesn't work, you'll need to replace the graphics card to test if the problem still occurs.
34: 0x000000ED:UNMOUNTABLE_BOOT_VOLUME
Error analysis: Generally, it is due to the existence of disk errors, and sometimes it is also recommended to check the hard disk cable to see if it is not in good contact with the hard disk, or do not use the appropriate hard disk transmission specifications of the cable, for example, the ATA-100 is still using ATA-33 connecting cable, which does not matter for low-speed hard disk. For example, ATA-100 still uses ATA-33 cable, which does not matter for low-speed hard disk, but for hard disk (support ATA-66 or above), the requirements are more strict, and the wrong cable specification may cause this kind of malfunction of not being able to turn on the computer. If, after repairing, this error still occurs frequently, it is likely a precursor to hard disk damage.
Solution: In general, a reboot will fix the problem, but in any case it is recommended to run 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, e.g., a device is not releasing the occupied interrupt after completing an operation.
Solution: Upgrade or uninstall the latest installed hardware drivers.
36: 0x00000135:UNABLE_TO_LOCATE_DLL
Error Analysis: Usually indicates that a file is missing or corrupted, or there is a registry error.
Solution: If a file is missing or corrupted, the corresponding file name is usually displayed in the blue screen message, and you can find the corresponding file through the Internet or other computers, and copy it to the SYSTEM32 subfolder under the system folder. If the file name is not shown, it is likely that the registry is corrupted, so please use System Restore or a previous registry backup to restore it.
37: 0x0000021A:STATUS_SYSTEM_PROCESS_TERMINATED
Error analysis: The user-mode subsystems, such as Winlogon or the Customer Service Runtime Subsystem (CSRSS), have been corrupted, and so can no longer be guaranteed secure, resulting in the system failing to boot. Sometimes, when a system administrator incorrectly modifies user account permissions, it prevents them from accessing system files and folders.
Solution: Use the "Last Correct Configuration" or, if that doesn't work, use the installation CD to perform a repair installation.
38: STOP 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
ERROR ANALYSIS: Usually it is due to the corruption of the driver or the system DLL file, and usually the name of the file will appear in the blue screen.
Solution:
(1) Use the Windows Installation CD-ROM to repair the installation;
(2) If you can still enter Safe Mode, you can "Start-->Run": sfc /scannow
(3) You can also use the method of extracting the file to solve the problem, go to the "Failure Recovery Console", and use the "copy or expand command". copy or expand command from the CD-ROM to copy or decompress the damaged files, however, the blue screen is generally a driver file problem, so
expand command will be used in some, for example: blue screen prompted tdi.sys file, because the driver file is generally in the i386 \driver zip, so use: expand % CDROM:\i386\driver CDROM:\i386\driver.cab \f:tdi.sys c:\winnt\system\drivers. (xp for expand %CDROM:\i386\driver.cab \f:tdi.sys c:\windowns\system\drivers).
39: If the following blue screen stop code appears at startup:
If you get a blue screen at Windows startup with the error message in Appendix 1, you most likely have a hardware problem. Use the diagnostic tools provided by the hardware manufacturer to determine if there is a hardware problem, and check their website for the latest BIOS or firmware updater. If there is no hardware problem, reinstall Windows 2K/XP, and if the same problem persists, you will need to call a professional tech support.
If you are experiencing the error message in Appendix 2, you will have to reinstall Windows, but if that does not solve the problem, we recommend that you seek professional technical support. p>/3688798.html