I. Blue Screen meaning
1. fault check information
* ** STOP 0x0000001E (0xC0000005, 0xFDE38AF9, 0x0000001, 0x7E8B0EB4)
KMODE_EXCEPTION_NOT_HANDLED *** the first part of the error is the Stop Code, that is, STOP 0x0000001E,
This parameter is used to identify the type of an error that has occurred. The second part of the error is the four number sets enclosed in parentheses, indicating the parameters defined by random developers (this parameter is not understandable to common users at all,
Only drivers or developers of the Microsoft operating system can understand it ). the third part is the error name. the first line of information is usually used to identify the driver or device that produces errors. this information is mostly concise,
However, the downtime code can be used as a search item in the Microsoft Knowledge Base and other technical materials.
2. Recommended operations
The second part of the blue screen is the operation information recommended by the user. Sometimes, the recommended operation is only a general suggestion (for example, checking for BIOS updates on the seller's website). Sometimes,
That is, a prompt related to the current problem is displayed. Generally, the only suggestion is to restart.
3. the debugging port tells the user whether the memory dump image has been written to the disk vendor, uses the memory dump image to determine the nature of the problem, and tells the user whether the debugging information has been transferred to another computer vendor,
And what ports are used to complete the communication. However, the information here is meaningless for common users. Sometimes, the security department can check which production team the problem is,
In the first part, the system will clearly report which file made the mistake, but often it can only check the approximate scope, rather than explicitly specifying the problem. because the factory was forced to stop all over, it was only necessary to rebuild and start work. Sometimes,
The production team will realize the mistake and will not repeat it again. But sometimes it will still try to snatch parts, so the factory leaders have to repeat the shutdown decision (cannot start and display the blue screen information,
Or the blue screen is displayed again when the same operation is performed ).
Ii. Solution to the Blue Screen
Windows 2 K/XP has a lot of blue screen information and cannot be fully explained in an article, however, they are often caused by incompatible hardware and drivers, problematic software, and viruses,
Therefore, we first provide some common solutions. When encountering a blue screen error, we should first eliminate these solutions.
1. Restart
Sometimes only a program or driver makes a mistake at the moment. After the restart, they will change themselves. (Note: see 7. query the shutdown code at this time)
2. New hardware
First, check whether the new hardware is firmly inserted. The problem that many people ignore may lead to many inexplicable faults. If you confirm that there is no problem, unplug it and try another slot,
Install the latest driver. Check whether the hardware is compatible with the operating system against the hardware compatibility category on the Microsoft website. If your hardware is not in the table,
Then you can get the hardware vendor's website for query or call their consulting phone number.
Windows XP hardware compatibility list
2 k hardware compatibility for Windows
3. New drivers and services
If you have just installed a new hardware driver or a software, and it has added the corresponding project to the System Service (for example: anti-Virus Software, CPU cooling software, firewall software, etc ),
Blue Screen failure occurs during restart or use. please uninstall or disable them in safe mode.
4. Check for viruses
For example, viruses such as shock waves and ripple waves may sometimes cause Windows blue screens to crash, so virus detection and removal are essential. At the same time, some Trojan spyware may also cause blue screens,
Therefore, it is best to use related tools for scanning and checking.
5. Check BIOS and hardware compatibility
For newly installed computers that often encounter blue screen problems, you should check and upgrade the BIOS to the latest version, and disable memory related items, such as cache and ing. In addition,
Check your hardware against Microsoft's hardware compatibility list. In addition, if the motherboard BIOS does not support a large-capacity hard disk, blue screen may occur and you need to upgrade it.
TIPS:
BIOS cache and ing items
Video BIOS Shadowing (Video BIOS ing)
Shadowing address ranges (ing address column)
System BIOS Cacheable (System BIOS buffer)
Video BIOS Cacheable (Video BIOS buffer)
Video RAM Cacheable (Video memory buffer)
6. Check System Logs
Enter EventVwr In the start --> menu. msc. When you press enter, the "Event Viewer" appears. Check "system log" and "Application log" for "error" items.
7. query the shutdown code
The blue screen in the dense E text down, and then to other computers to access the Internet, enter the Microsoft Help and Support website http://support.microsoft.com ?,
In the "Search (Knowledge Base)" in the upper-left corner, enter the stop code. If the search result does not have any suitable information, you can select "English knowledge base" to search again. Generally,
Here, we will find useful solutions. In addition, the blue screen shutdown code or subsequent instructions are used as keywords for search engines such as baidu and Google, and there will often be additional gains.
8. The last correct configuration
Generally, the blue screen appears after the hardware driver is updated or the hardware is added and the driver is installed, in this case, the "Last correct configuration" provided by Windows 2 K/XP is the blue screen shortcut.
Restart the system. When the boot menu appears, press F8 to display the advanced boot option menu, and then select "Last correct configuration ".
9. Install the latest system patch and Service Pack
Some blue screens are caused by defects in Windows, which can be solved by installing the latest system patches and Service packs.
Iii. blue screen code meaning and Solution
1. 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
◆ Error Analysis: mainly caused by problematic drivers, defective or incompatible hardware and software.
It indicates that there is an Ethernet internal request level (IRQL) in kernel mode to access the memory address that is not authorized to access.
◇ Solution: Use solution 2, 3, 5, 8, and 9 in the preceding solution to try to eliminate this problem.
2. 0x00000012: TRAP_CAUSE_UNKNOWN
◆ Error Analysis: If this error message is returned, it is unfortunate that the analysis result of KeBudCheck is the cause of the error.
Unknown.
◇ Solution: Since Microsoft is not able to help, you have to rely on yourself. Please think carefully about when this error occurred. What operations did you perform on the system when it first occurred; what operations are being performed at the time of occurrence.
Find out the possible causes from the information and select the corresponding solution to try to eliminate them.
3. 0x0000001A: MEMORY_MANAGEMENT
◆ Error Analysis: This memory management error is often caused by hardware, such as the newly installed hardware and memory problems.
◇ Solution: If it appears during Windows installation, it may be because your computer does not meet the minimum memory and disk requirements for Windows installation.
4. 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
◆ Error Analysis: an invalid or unknown process command is detected in the Windows Kernel. The shutdown code is generally caused by the faulty memory or similar causes as 0x0000000A.
◇ Solution:
(1) hardware compatibility problems: Check whether all hardware is included in the list against the latest hardware compatibility list mentioned above.
(2) Problematic device drivers, system services, or memory conflicts and interruptions: if the driver name appears in the blue screen information,
Please try to disable or delete drivers in installation mode or fault recovery console, and disable all newly installed drivers and software. If an error occurs during system startup, enter safe mode,
Rename or delete the files marked in the blue screen information.
(3) If the error message clearly states that Win32K. sys is likely to be caused by a third-party remote control software, you need to disable the service of the software from the fault recovery console.
(4) The first restart after Windows is installed: The maximum suspicion may be caused by insufficient disk space or BIOS compatibility.
(5) If a software is disabled: the software may have design defects in this province, please upgrade or uninstall it.
5. 0x00000023: FAT_FILE_SYSTEM
0x00000024: NTFS_FILE_SYSTEM
◆ Error Analysis: 0x00000023 usually occurs when reading and writing the system partition of the FAT16 or FAT32 file system
0x00000024 is caused by an error in the NTFS. sys file (this driver file is used to allow the system to read and write data.
NTFS file system disk). These two blue screen errors may be caused by physical damage to the disk, or damage to the interrupt packet (IRP.
Other causes include: Too Many disk fragments, too frequent file read/write operations, and extremely high data volume, or caused by some disk image software or anti-virus software.
◇ Solution:
Step 1: First open the command line prompt and run "Chkdsk/r" (Note: It is not CHKDISK, it feels like this, ......) Command to check and fix hard disk errors,
If a Bad Track exists in the report, use the inspection tool provided by the hard disk vendor to check and fix the problem.
Step 2: Disable all software that scans files, such as anti-virus software, firewall, or backup tools.
Step 3: Right-click the C: winntsystem32driversfastfat. sys file and select "properties ",
Check whether the version is consistent with the Windows version used by the current system. (Note: if it is XP, it should be C: windowssystem32.
Driversfastfat. sys)
Step 4: Install the latest motherboard driver, especially the IDE driver. If your drive and removable storage have drivers, upgrade them to the latest version.
0x00000027: RDR_FILE_SYSTEM
◆ Error Analysis: it is difficult to judge the cause of this error. However, a problem with Windows Memory Management may cause this shutdown code.
◇ Solution: If it is memory management, increasing the memory will solve the problem.
7. 0x0000002EATA_BUS_ERROR
◆ Error Analysis: system memory parity error,
This is usually because the device driver accesses a memory address that does not exist when there is a defective memory (including physical memory, secondary cache, or video card memory. in addition, the hard disk is damaged by viruses or other problems,
To display the shutdown code.
◇ Solution:
(1) Check for viruses
(2) run the "chkdsk/r" command to check all disk partitions.
(3) Use memory testing software such as Memtest86 to check the memory.
(4) check whether the hardware is correctly installed, for example, whether it is solid or whether there are stains on the golden finger.
8. 0x00000035: NO_MORE_IRP_STACK_LOCATIONS
◆ Error Analysis: literally, the driver or some software has a stack problem. In fact, the real cause of this fault should be that the driver has a problem in this province, or the memory has a quality problem.
◇ Solution: Use the drivers and memory-related solutions described above to eliminate them.
9. 0x0000003F: NO_MORE_SYSTEM_PTES
◆ Error Analysis: An error related to system memory management. For example, a large number of input/output operations may cause memory management problems: defective drivers use memory resources incorrectly;
An application (such as backup software) is allocated with a large amount of kernel memory.
◇ Solution: Uninstall all newly installed software (especially those applications and anti-virus software that enhance disk performance) and drivers.
10. 0x00000044: MULTIPLE_IRP_COMPLIETE_REQUESTS
◆ Error Analysis: usually caused by hardware drivers.
◇ Solution: uninstall the recently installed driver. This fault rarely occurs. It is known that
Www.in-system.com/some software of this company will appear, and the token is the Falstaff. sys file. (The author is not afraid of a lawsuit,
Publish the company website)
11. 0x00000050: PAGE_FAULT_IN_NONPAGED + AREA
◆ Error Analysis: problematic memory (including in-house memory, secondary cache, and video memory) and incompatible software (mainly remote control and anti-virus software), damaged NTFS Volume and faulty hardware (for example:
The PCI card itself is damaged.
◇ Solution: Use the memory, software, hardware, hard disk, and other related solutions described above.
Row exclusion.
12, 0x00000051: REGISTRY_ERROR
◆ Error analysis: the shutdown code indicates that the Registry or System Configuration Manager is incorrect. The hard disk is physically damaged or the file system is faulty, this results in an input/output error when reading the registered file.
◇ Solution: Use "chkdsk/r" to check and fix disk errors.
13. 0x00000058: FTDISK_INTERNAL_ERROR
◆ Error Analysis: It indicates that an error occurs in the master drive of the fault tolerance set.
◇ Solution: first, restart the computer to see if the problem can be solved. If not, try "Last correct configuration.
14. 0x0000005E: CRITICAL_SERVICE_FAILED
◆ Error analysis: a very important system service startup identification result.
◇ Solution: if a new hardware is installed, You can first remove it and check whether it is compatible with Windows 2 K/XP through the online list, start the computer,
If the blue screen still appears, use "Last correct configuration" to start Windows. If this still fails, we recommend that you fix the installation or reinstall it.
15, 0x0000006F: SESSION3_INITIALIZATION-FAILED
◆ Error Analysis: this error is usually caused by a faulty driver or damaged system file when Windows is started.
◇ Solution: We recommend that you use the Windows installation CD to repair and install the system.
16. 0x00000076ROCESS_HAS_LOCKED_PAGES
◆ Error analysis: a driver does not properly release the occupied memory after an input/output operation.
◇ Solution:
Step 1: Click start --> Run: regedt32, and find [HKLMSYSTEMCurrentcontrol setcontrolsession
Managermemory management], create a dual-byte value "TrackLockedPages" on the right. The value is 1.
In this way, Windows will track the driver problem when the error occurs again. Step 2: If the blue screen appears again,
The error message will be: STOP: 0x0000000CB (0xY, 0xY, 0xY, 0xY) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS. The fourth "0xY" will display the name of the problematic driver,
Then update or delete it. Step 3: Go to the Registry and delete the added "TrackLockedPages ".
17. 0x00000077: KERNEL_STACK_INPAGE_ERROR
◆ Error Analysis: It indicates that the kernel data to be used is not found in the virtual memory or physical memory. This error is often caused by disk problems, data corruption or virus erosion.
◇ Solution: Use anti-virus software to scan the system. Use the "chkdsk/r" command to check and fix disk errors. If not, use the tools provided by the disk manufacturer to check and fix the errors.
18. 0x0000007A: KERNEL_DATA_INPAGE_ERROR
◆ Error Analysis: this error is often caused by kernel data in the virtual memory being unable to be read into the memory. the possible cause is that the virtual memory page file contains bad clusters, viruses, disk controller errors, and memory problems.
◇ Solution: first, use the latest antivirus software to scan and kill viruses.
Or 0xC000016A code, it indicates that it is caused by a bad cluster, and the system's disk detection tool cannot be automatically repaired. In this case, you need to go to the "fault recovery console" and use "chkdsk
/R "command for manual repair.
19. 0x0000007B: INACESSIBLE_BOOT_DEVICE
◆ Error Analysis: Windows cannot access system partitions or start volumes during startup. Generally, this occurs when the system is started for the first time after the motherboard is changed,
This is mainly because the new motherboard and the old motherboard IDE controller use different chipset, sometimes caused by virus or hard disk damage.
◇ Solution: Generally, you only need to use the installation disc to start the computer, and then perform repair and installation to solve the problem.
For viruses, you can use anti-virus software of the DOS version to scan and kv2005DOS version. If there is a problem with the hard disk, install it on another computer,
Then, use "chkdsk/r" to check and fix disk errors.
20. 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
◆ Error Analysis: system process errors are generated, but cannot be captured by the Windows Error processor. There are many causes, including hardware compatibility, problematic drivers or system services,
Or some software.
◇ Solution: please use the "Event Viewer" to obtain more information and find the root cause of the Error. (It seems that this is not a solution. It seems that we have to be self-reliant here !)
21. 0x0000007F: UNEXPECTED_KERNEL_MOED_TRAP
◆ Error Analysis: this error is generally caused by faulty hardware (such as memory) or some software. Sometimes this error is caused by overclock.
◇ Solution: Use the detection software (such as Memtest86) to check the memory. If the memory is too frequently, cancel the overclock. Unplug the PCI hardware card from the motherboard slot or change the slot.
In addition, some motherboard (such as nForce2 motherboard) after the frequency is too high, the south bridge chip overheating will also lead to a blue screen, at this time for the chip to add a heat sink alone can effectively solve the problem.
22, 0x00000080: NMI_HARDWARE_FAILURE
◆ Error Analysis: it is usually caused by hardware. (It seems that blue screen and hardware errors do not exist)
◇ Solution: If you have recently installed new hardware, remove it, try replacing the slot, and install the latest driver. If you have upgraded the driver, restore the original version;
Check whether the memory golden finger is contaminated and damaged; scan the virus; Run "chkdsk/r" to check and fix disk errors; Check that all hardware plug-ins are inserted. If the above attempts are ineffective,
You have to seek help from a professional computer service company.
23. 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
◆ Error Analysis: kernel-level applications produce errors, but Windows Error processors are not captured. This is usually due to hardware compatibility errors.
◇ Solution: Upgrade the driver or BIOS.
24. 0x0000009C: MACHINE_CHECK_EXCEPTION
◆ Error Analysis: it is usually caused by hardware. It is generally caused by overclock or hardware problems (memory, CPU, bus, electricity
Source ).
◇ Solution: If overclocking is performed, reduce the CPU usage and check the hardware.
25. 0x0000009FRIVER_POWER_STATE_FAILURE
◆ Error Analysis: It is often related to the power supply and often occurs in power-related operations, such as shutdown, standby or sleep.
◇ Solution: reinstall the system. If the problem cannot be solved, change the power supply.
26. 0x000000A5: ACPI_BIOS_ERROR
◆ Error Analysis: Generally, the main board BIOS does not fully support ACPI specifications.
◇ Solution: if there is no corresponding BIOS upgrade, you can install Windows 2 K/XP When "press F6 if you need
When the prompt "install a third-party SCSI or RAID driver" is displayed, press F7,
In this way, the installation of acpi hal and Standard pc hal will be disabled automatically in Windows.
27. 0x000000B4: VIDEO_DRIVER_INIT_FAILURE
◆ Error analysis: the stop information indicates that the graphics card driver cannot be started in Windows, and thus the graphic interface cannot be accessed. This is usually a problem with the graphics card,
Or there is a hardware conflict with the video card (such as a parallel or serial port conflict ).
◇ Solution: Go to security mode to check whether the problem is resolved. If yes, upgrade the latest graphics card driver. If not, it is likely that the video card conflicts with the parallel port,
You need to press WIN + break in safe mode to open "System Properties", find and double-click the Device Manager in hardware --> Device Manager to connect to the printed LPT1 port,
On the "Resources" tab, deselect "use automatic configuration" and change "03BC" in "input/output range" to "0378 ".
28. 0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
◆ Error analysis: a driver attempts to write data to the read-only memory, usually after a new driver, system service, or firmware program is installed.
◇ Solution: if the error message contains the driver or service file name, uninstall or disable the newly installed driver or software.
29. 0x000000C2: BAD_POOL_CALLER
◆ Error analysis: a kernel-layer process or driver attempts to operate in memory by mistake. This is usually caused by a driver or software with bugs.
◇ Solution: Please refer to the general solution-related items described above for troubleshooting.
30. 0x000000CERIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
◆ Error Analysis: usually caused by problematic drivers or system services.
◇ Solution: Please refer to the general solution-related items described above for troubleshooting.
31. 0x000000D1RIVER_IRQL_NOT_LESS_OR_EQUAL
◆ Error Analysis: it is usually caused by problematic drivers (for example, the Logitech MouseWare 9.10 and 9.24 drivers of the Logitech mouse will cause this fault ).
At the same time, defective memory, corrupted virtual memory files, and some software (such as multimedia software, anti-virus software, backup software, and DVD player software) will also cause this error.
◇ Solution: Check the latest installed or upgraded drivers (if "acpi. sys" and other similar file names appear on the blue screen, you can be very certain about the driver issues) and software;
Test whether the memory is faulty. Go to the "fault recovery console", go to the partition where the file Pagefile. sys is located on the Virtual Memory Page, and run "del
Pagefile. sys "command to delete the page file, and then execute" chkdsk "in the partition where the page file is located
/R "command; reset the virtual memory after entering Windows. if you encounter this blue screen while surfing the Internet, and you are downloading and uploading a large amount of data (such as online games and BT downloads ),
The NIC driver problem should be solved, and the driver needs to be upgraded.
32. 0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
◆ Error Analysis: it is usually caused by a video card or video card driver.
◇ Solution: first upgrade the latest graphics card driver. If not, you need to change the graphics card to test whether the fault still occurs.
33. 0x000000ED: UNMOUNTABLE_BOOT_VOLUME
◆ Error Analysis: this error is generally caused by a disk error. Sometimes it is recommended to check whether the hard disk connection is in poor contact or whether the connection line meets the hard disk transmission specifications,
For example, the ATA-100 still uses the connection line of the ATA-33, does not matter to the low speed hard disk, but tell the hard disk (Support ATA-66 or above) more stringent requirements,
Wrong specifications may cause such failures that cannot be started. If this error occurs frequently after repair, it may be a precursor to hard disk damage.
◇ Solution: Generally, restart will solve the problem. In any case, we recommend that you run the "chkdsk/r" command to check and fix the hard disk.
34. 0x000000F2: HARDWARE) INTERRUPT_STORM
◆ Error analysis: the kernel layer checks that the system has an interrupted storm. For example, a device is not released after the operation.
Usually this is caused by the defective driver.
◇ Solution: upgrade or uninstall the latest installed hardware driver.
35, 0x00000135: UNABLE_TO_LOCATE_DLL
◆ Error Analysis: It usually indicates that a file is lost or damaged, or the Registry has an error.
◇ Solution: if the file is lost or damaged, the corresponding file name is usually 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 in the system folder. If the file name is not displayed, it is likely that the Registry is corrupted,
Please use system restoration or previous registry backup for restoration.
36. 0x0000021A: STATUS_SYSTEM_PROCESS_TERMINATED
◆ Error analysis: the user mode subsystem, such as Winlogon or CSRSS, is damaged, so security cannot be ensured, resulting in system startup failure. Sometimes,
When the system administrator mistakenly modifies the user account permissions, the user cannot access system files and folders.
◇ Solution: Use "The Last correct configuration". If the configuration is invalid, use the installation CD to fix and install it.
37. STOP 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH
◆ Error Analysis: it is usually caused by driver or system DLL file damage. Generally, it appears on the blue screen.
File Name
◇ Solution:
(1) Use the Windows installation CD for restoration and installation;
(2) If you can still enter security mode, you can "start --> Run": sfc/scannow
(3) You can also Extract files to solve the problem. Go to the "fault recovery console" and use the copy or expand command to copy or decompress the damaged files from the disc. However,
The blue screen is generally a driver file problem, so the expand command will use some, for example, the blue screen prompts the tdi. sys file,
Because the driver file is generally in the iplusdriver package, use: expand % CDROM: iplusdriver. cab f: tdi. sys
C: winntsystemdrivers. (xp is expand % CDROM: imo-driver. cab f: tdi. sys
C: windownssystemdrivers)
38. If these blue screen shutdown codes appear at startup
If a blue screen appears during Windows Startup and an error message in Appendix 1 is displayed, most of the time there is a hardware problem. Use the diagnostic tool provided by the hardware vendor to determine whether the hardware is faulty,
Check whether the latest BIOS or firmware update program is available on the website. If the hardware is correct, reinstall Windows 2 K/XP. If the problem persists,
You can only seek help from professional technical support.
If you encounter an error message in Appendix 2, and you only need to reinstall Windows, if the problem cannot be solved, we recommend that you ask for professional technical support.
Appendix 1:
Downtime code error name
0x31 PHASEO_INITALIZATION_FAILED
0x5C HAL_INITIALITAION_FAILED
0x5D HEAP_INITIALITAION_FAILED
0x5E OBJECT_INITIALITAION_FAILED
0x5F SECURITY_INITIALITAION_FAILED
0x60 PROCESS_INITIALITAION_FAILED
Appendix 2:
Downtime code error name
0x32 phaseappsinitalization_failed
0x61 HAL1_INITALIZATION_FAILED
0x62 OBJECT1_INITALIZATION_FAILED
0x63 securityappsinitalization_failed
0x64 SYMBOLIC_INITALIZATION_FAILED
0x65 memoryreceivinitalization_failed
0x66 CACHE_INITALIZATION_FAILED
0x67 CONFIG_INITALIZATION_FAILED
0x68 FILE_INITALIZATION_FAILED
0x69 IO1_INITALIZATION_FAILED
0x6A LPC_INITALIZATION_FAILED
0x6B PROCESS1_INITALIZATION_FAILED
0x6C REFMON_INITALIZATION_FAILED
0x6D SESSION1_INITALIZATION_FAILED
0x6E SESSION2_INITALIZATION_FAILED
0x6F SESSION3_INITALIZATION_FAILED
0x70 SESSION4_INITALIZATION_FAILED
0x71 SESSION5_INITALIZATION_FAILED
Let's share it with you.
