1. Restart
Sometimes a program or driver just made a mistake for a while, and they will turn over a new leaf after restarting. (Note: See 7. Inquire about the stop code at this time)
2. New hardware
First of all, we should check whether the new hardware is plugged in firmly, which is ignored by many people and often leads to many inexplicable failures. If it is confirmed that there is no problem, Unplug it, try another slot, and install the latest driver. At the same time, you should check whether the hardware is compatible with the operating system according to the hardware compatibility category of Microsoft website. If your hardware is not in the table, you should get the website of the hardware manufacturer to inquire or call their consultation number.
3. New drivers and new services
If you just installed a new driver for a certain hardware, Or a certain software is installed, and it adds corresponding items (such as anti-virus 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. Check for viruses
Viruses such as shock waves and oscillation waves sometimes cause Windows blue screen of death. Therefore, it is necessary to kill viruses. At the same time, some Trojan spyware can also cause blue screen, so it is best to scan and check with related tools.
5. Check the compatibility of BIOS and hardware
For newly installed computers, you should check and upgrade the BIOS to the latest version, and at the same time close the memory-related items. For example: caching and mapping. In addition, you should check your hardware against Microsoft's hardware compatibility list. Also, if the motherboard BIOS can't support large-capacity hard disks, it will also lead to a blue screen, which needs to be upgraded.
6. Run "sfc /scannow" to check whether the system files have been replaced. Then use the system installation disk to restore.
Tip:
BIOS caching and mapping items
Video BIOS Shadowing
Shading address ranges
System BIOS Cacheable.
video BIOS cache
video ram cache
7. check the system log
at the beginning --> Enter: EventVwr.msc in the menu, and press enter to open "Event Viewer". Pay attention to the items in the "System Log" and "Application Log" indicating "errors".
8. Inquire about the stop code
Write down the dense E-texts in the blue screen, and then surf the Internet in other computers and enter the Microsoft Help and Support website? Enter the downtime code in the "Search (Knowledge Base)" in the upper left corner. If the search results are not suitable for information, you can choose "English Knowledge Base" to search again. In general, you will find useful solutions here. In addition, use the downtime code of blue screen or the explanatory text behind it as keyword search in search engines such as baidu and Google. There are often gains.
9. The last correct configuration
In general, the blue screen is after the hardware driver or the newly added hardware and the driver is installed. At this time, the "last correct configuration" provided by Windows 2K/XP is a shortcut to solve the blue screen. Restart the system, and press F8 when the startup menu appears, and an advanced startup options menu will appear. Then choose "last correct configuration".
1. 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.
Meaning and solution of blue screen code
It is common to use Windows to have blue screens, and it is laborious and time-consuming to reinstall the system frequently because the source of errors is not clear. The following collected some windows crash passwords for your reference.
1, xa: IRQL _ not _ less _ or _ equal
◆ Error analysis: It is mainly caused by faulty drivers, defective or incompatible hardware and software. From a technical point of view, it shows that there is level process request (IRQL) in kernel mode. Access the memory address that it does not have permission to access.
◇ Solution: Please try to exclude it by using the 2, 3, 5, 8 and 9 schemes in the solution introduced earlier.
2, x12: trap _ cause _ unknown
◆ Error analysis: If you encounter this error message, it is unfortunate. Because the result of KeBudCheck analysis is that the cause of the error is
unknown.
◇ Solution: Since Microsoft can't help, it's up to itself, please carefully recall when this error occurred; What did you do to the system when it first happened? What was going on when it happened? Find out the possible reasons from this information, and then choose the corresponding solution to try to eliminate it.
3, x1a: memory _ management
◆ Error analysis: This memory management error is often caused by hardware. For example, there is something wrong with the newly installed hardware and memory itself.
◇ Solution: If it appears when installing Windows, It may be because your computer can't meet the minimum memory and disk requirements for installing Windows.
4, x1e: kmode _ exception _ not _ handled
◆ Error analysis: The Windows kernel has detected an illegal or unknown process instruction. This shutdown code is generally caused by faulty memory or similar reasons to the previous xA.
◇ Solution:
(1) There is something wrong with hardware compatibility: please refer to the latest hardware compatibility list mentioned above. Check whether all the hardware is included in the list.
(2) Conflicts and interruptions of problematic device drivers, system services or memory: 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 recovery console, and disable all the newly installed drivers and software. If the error appears during the system startup, please enter the safe mode. Rename or delete the file indicated in the blue screen information.
(3) If the error message clearly indicates that Win32K.sys: is probably caused by a third-party remote control software, The service of the software needs to be turned off from the fault recovery console.
(4) It appears at the first restart after installing Windows: the most probable time is that the disk space of the system partition is insufficient or there is a problem with BIOS compatibility.
(5) If it appears at the time of turning off a software: it is very likely that the software originally exists in a design defect. Please upgrade or uninstall it.
5, x23: fat _ file _ system
x24: NTFS _ file _ system
◆ Error analysis: x23 usually occurs when reading and writing the system partition of FAT16 or FAT32 file systems. x24 is caused by an error in the NTFS.sys file (this driver file is used to allow the system to read and write). These two blue screen errors are probably caused by physical damage of the disk itself or the damage of the interrupt request packet (IRP). Other reasons include: excessive fragmentation of the hard disk; File reading and writing operations are too frequent, and the amount of data is very large or caused by some disk mirroring software or antivirus software.
◇ Solution:
Step 1: First, open the command prompt and run the "Chkdsk /r" command to check and repair hard disk errors. If a Bad Track is reported, please use the inspection tools provided by the hard disk manufacturer to check and repair it.
Step 2: Then disable all software that scans files, such as antivirus software, firewall or backup tools.
Step 3: Right-click the file C: \ winnt \ system32 \ drivers \ fastfat.sys and select "Properties". Check whether its version is consistent with 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 driver, especially IDE driver. If your CD-ROM drive and mobile storage also provide drivers, It is best to upgrade them to the latest version.
6, x27:RDR_FILE_SYSTEM
◆ Error analysis: It is difficult to judge the cause of this error, but a problem with Windows memory management is likely to lead to the appearance of this stop code.
◇ Solution: If it is due to memory management, Generally, increasing memory will solve the problem.
7, x2EATA_BUS_ERROR
◆ Error analysis: The parity check of system memory produces errors, which are usually caused by device drivers accessing nonexistent memory addresses when there is defective memory (including physical memory, secondary cache or video card memory). In addition, the hard disk is damaged by viruses or other problems.
◇ Solution:
(1) Check the virus
(2) Check all disk partitions with the "chkdsk /r" command.
(3) Check the memory with memory testing software such as Memtest86.
(4) Check whether the hardware is installed correctly. For example, whether it is firm or not, and whether the golden finger is stained.
8, x35: no _ more _ IRP _ stack _ locations
◆ Error analysis: Literally, there should be a stack problem in the driver or some software. In fact, the real cause of this failure should be a problem in the driver itself. Or there is a quality problem with the memory.
◇ Solution: Please use the scheme related to drivers and memory in the conventional solution described above to eliminate it.
9, x3f: no _ more _ system _ ptes
◆ Error analysis: an error related to system memory management, such as: due to a large number of input/output operations. An application (such as backup software) is allocated a lot of kernel memory, etc.
◇ Solution: uninstall all the latest installed software (especially those applications and antivirus software that enhance disk performance) and drivers.
1, x44: multiple _ IRP _ comprite _ requests
◆ Error analysis: It is usually caused by hardware drivers.
◇ Solution: Uninstall the recently installed drivers. This fault rarely occurs, but it is known that it will occur when using some software of this company in www.in-system.com/. The culprit is the Falstaff.sys file. (Isn't the author afraid of taking a lawsuit? Publish the company website)
11, x5: page _ fault _ in _ unpaged+area
◆ Error analysis: faulty memory (including physical memory, secondary cache and video memory), incompatible software (mainly remote control and antivirus software), damaged NTFS volume and faulty hardware (such as PCI plug-in) , etc. will cause this error.
◇ Solution: Please use the solutions related to memory, software, hardware, hard disk, etc. in the conventional solutions introduced earlier to eliminate it.
12, x51:REGISTRY_ERROR
◆ Error analysis: This stop code indicates that there is an error in the registry or system configuration manager. There is a physical damage to the hard disk itself or a problem with the file system, resulting in an input/output error when reading the registration file.
◇ Solution: use "chkdsk /r" to check and repair the disk error.
13, x58: ftdisk _ internal _ error
◆ Error analysis: explain the main driver in the fault-tolerant set.
◇ Solution: First try to restart the computer to see if it can solve the problem. If not, Then try "last correct configuration" to solve it.
14, x5e: critical _ service _ failed
◆ Error analysis: caused by the identification of a very important system service startup.
◇ Solution: If a new hardware is installed, you can remove it first. And check whether it is compatible with Windows 2K/XP through the online list, and 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 it.
15, x6f: Session3 _ initializat.