When testing software, there will always be a little damage to the computer. If it is difficult to do it, it will be a blue screen. Even if the sandbox is used, it may be a hardware problem. I have been searching for this code for a long time. It seems that I still find a part of the code, but it is enough. It is also very useful and well analyzed. Blue screen, first look at the corresponding code error, and then solve the cause of the error.
Original document:
Common blue screen cases
The blue screen I often encounter is 0X0000008E, 0X0000000A, 0X00000050, 0X0000009F
│ 1 │
Accept-distinct 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
◆ Error Analysis: mainly caused by problematic drivers, defective or incompatible hardware and software. from a technical point of view. 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: Upgrade the driver or BIOS to check the memory.
Accept-Encoding
│ 2 │
Required-bytes 0x00000012: TRAP_CAUSE_UNKNOWN
◆ Error Analysis: If this error message is returned, it is unfortunate that the analysis result of KeBudCheck is that the cause of the error is 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.
Accept-Encoding
│ 3 │
Memory-memory 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.
Accept-Encoding
│ 4 │
Export-00000x0000001e: 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 the driver in installation mode or fault recovery console and disable all newly installed drivers and software. if the error occurs during system startup, go to secure mode and 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.
Accept-Encoding
│ 5 │ 0x00000023: FAT_FILE_SYSTEM
Accept-limit 0x00000024: NTFS_FILE_SYSTEM
◆ Error Analysis: 0x00000023 usually occurs when reading and writing the system partition of the FAT16 or FAT32 file system, while 0x00000024 is caused by NTFS. sys File error (this driver file is used to allow the system to read and write the disk using the NTFS file system ). these two blue screen errors may be caused by physical damage to the disk, or the failure of the interrupt request 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 the report contains a Bad Track, use the checking 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 C: winntsystem32driversfastfat. sys File and select "properties" to check whether the version matches the Windows version used by the current system. (Note: If it is XP, it should be C: windowssystem32driversfastfat. 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.
Accept-Encoding
│ 6 │
Required-bytes 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.
Accept-Encoding
│ 7│
Invalid-0x0000002EATA_BUS_ERROR
◆ Error analysis: the system memory parity error is usually caused by defective memory (including physical memory, secondary cache, or video card memory) when the device driver accesses a non-existent memory address. in addition, the hard disk is damaged by viruses or other problems to see 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.
Accept-Encoding
│ 8 │
Executor-nodes 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.
Accept-Encoding
│ 9 │
Bytes-bytes 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 improperly use memory resources. An application (such as backup software) is allocated 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.
Accept-Encoding
│ 10 │
Required-bytes 0x00000044: MULTIPLE_IRP_COMPLIETE_REQUESTS
◆ Error Analysis: usually caused by hardware drivers.
◇ Solution: uninstall the recently installed driver. this fault rarely occurs. What we know now is that some software in this company will appear when we use http://www.in-system.com/, where the fault is Falstaff. sys File. (I am not afraid of a lawsuit. I will publish the company website)
Accept-Encoding
│ 11 │
Executor-cores 0x00000050
AGE_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) damage to NTFS volumes and faulty hardware (for example, the CI plug-in card itself is damaged) will cause this error.
◇ Solution:
1. unmount all recently installed hardware.
2. Run all system diagnostic software provided by computer manufacturers, especially Memory checks.
3. check whether all new hardware or software is correctly installed. If this is a completely new installation, contact the hardware or software manufacturer for any Windows updates or drivers that may be required.
4. Disable or Uninstall all anti-virus programs.
5. Disable BIOS memory options, such as cache or shadow.
In the solution, not every line is required, but every line is possible! The blue screen code 50 is the most troublesome and may be caused by many reasons! Even if you have done these five things, you may not be able to solve them. At least I have solved them once and not in these cases. Please try them first!
Accept-Encoding
│ 12 │
Accept-Errors 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.
Accept-Encoding
│ 13 │
Counter-Errors 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.
Accept-Encoding
│ 14 │
Invalid-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 problem and install or reinstall it.
Accept-Encoding
│ 15 │
Cost-00000x0000006f: 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.
Accept-Encoding
│ 16 │
Failed-Unlock 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, find [HKLMSYSTEMCurrentcontrol setcontrolsession managermemory management], and create a double byte value "TrackLockedPages" on the right. The value is 1. in this way, Windows will track the driver 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" is displayed as the name of the problematic driver, which is then updated or deleted.
Step 3: Go to the Registry and delete the added "TrackLockedPages ".
Accept-Encoding
│ 17 │
Counter-Errors 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.
Accept-Encoding
│ 18 │
Kernel-bytes 0x0000007A: KERNEL_DATA _