Computer Blue Screen Code Daquan

1. The meaning of blue screen

1, fault check information

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

KMODE_EXCEPTION_NOT_HANDLED ***The part of the error is the Stop Code (Stop Code), which is 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 parentheses, indicating a random developer definition The parameter (this parameter is not understood by ordinary users at all, only the driver writer or the developer of the Microsoft operating system can understand). The third part is the error name. The information line is usually used to identify the wrong driver or device. This Most of this information is very concise, but the shutdown code can be used as a search item in the Microsoft Knowledge Base and other technical materials

2. Recommended actions

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: go to the vendor's website to find BIOS updates, etc.); sometimes, it is to display a prompt related to the current problem. Generally speaking, the only suggestion is to restart.

3. The debug port tells the user whether the memory dump image has been written to the disk vendor, and the memory dump image can be used to determine the nature of the problem. It also tells the user whether the debugging information is transmitted to another computer vendor, and what port is used Complete this communication. However, the information here is meaningless to ordinary users. Sometimes the Security Department can successfully find out which production team is the problem, and will clarify in the part which file made the mistake, but often it is also Can only look up the approximate scope, but can not clearly indicate the problem. Because the factory was forced to stop, only to reorganize and start, sometimes, the production team will realize the mistakes and will not repeat them. But sometimes they still try to snatch the parts, so the factory The leader had to repeat the shutdown decision (cannot start and display a blue screen message, or the blue screen appears again when the same operation is performed).

2. How to deal with the blue screen

Windows 2K/XP blue screen information is very much, which cannot be fully explained in an article, but the reasons for them are often concentrated in incompatible hardware and drivers, problematic software, *, etc., so first of all, I provide you with some routines. If you encounter a blue screen error, you should first check these solutions to eliminate it.

1. Restart

Sometimes it's just a certain program or driver that makes a mistake for a while, and they will be renewed after restarting. (Note: at this time, please refer to 7. Query the shutdown code)

2. New hardware

First of all, you should check whether the new hardware is firmly inserted. This problem that is ignored by many people often leads to many inexplicable failures. If it is confirmed that there is no problem, unplug it, then try another slot, and install the driver. At the same time, You should 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 get the hardware manufacturer's website for inquiries, or call their consultation number.

Windows XP hardware compatibility list

Windows 2K hardware compatibility category

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 adds corresponding items to the system service (such as: anti-virus software, CPU cooling software, firewall software, etc.), it appears during restart or use Blue screen failures, please go to safe mode to uninstall or disable them.

4. Check *

For example, shock waves and oscillatory waves, etc.* sometimes cause Windows blue screen of death, so it is essential to check and kill*. At the same time, some Trojan horses and spyware can also cause blue screens, so use related tools to scan and check.

5. Check BIOS and hardware compatibility

For newly installed computers often have blue screen problems, you should check and upgrade the BIOS to the version, and turn off the memory-related items, such as: cache and mapping. In addition, you should also check your own hardware against Microsoft's hardware compatibility list. And that is, If the motherboard BIOS cannot support large-capacity hard drives, it will also cause a blue screen, and it needs to be upgraded.

  hint:

BIOS cache and mapping items

Video BIOS Shadowing (Video BIOS Shadowing)

Shadowing address ranges (mapped address column)

System BIOS Cacheable (System BIOS Cacheable)

Video BIOS Cacheable (video BIOS buffer)

Video RAM Cacheable (video memory buffer)

6. Check the system log

Enter: EventVwr.msc in the Start --> menu, and press Enter to display "Event Viewer". Pay attention to check the "System Log" and "Application Log" which indicate "error".

7. Query the shutdown code

Write down the dense E texts in the blue screen, then go online on other computers, enter the Microsoft Help and Support website https://support.microsoft.com?, enter the shutdown code in the "Search (Knowledge Base)" in the upper left corner, If the search results do not have suitable information, you can choose "English Knowledge Base" and search again. Generally, you will find a useful solution here. In addition, use the blue screen shutdown code or the following explanatory text in search engines such as Baidu and Google Search for keywords, there are often other gains.

8. 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 "correct configuration" provided by Windows 2K/XP is a shortcut to solve the blue screen. Restart the system and press when the boot menu appears Press the F8 key and the boot options menu will appear, then select "Correct Configuration".

9. Installed system patches and service packs

Some blue screens are caused by defects in Windows itself, which can be solved by installing system patches and service packs.

Three, blue screen code meaning and solutions

1、0x0000000A:IRQL_NOT_LESS_OR_EQUAL

◆Error analysis: It is mainly caused by problematic drivers, defective or incompatible hardware and software. From a technical point of view. It indicates that there is too high internal request level (IRQL) access in the kernel mode and it does not have permission to access Memory address.

◇Solution: Please use the solutions 2, 3, 5, 8, and 9 in the previously introduced solutions to try to eliminate.

2, 0x00000012: TRAP_CAUSE_UNKNOWN

◆Error analysis: If you encounter this error message, then unfortunately, the result of KeBudCheck analysis should be the cause of the error

unknown.

◇Solution: Since Microsoft can't help, you have to rely on yourself. Please carefully recall when this error occurred; what operations did you do to the system when it occurred; what operations were in progress when it occurred. From this information Find out the possible reasons in the process, and then choose the corresponding solution to try to eliminate.

3, 0x0000001A: MEMORY_MANAGEMENT

◆Error analysis: This memory management error is often caused by hardware, such as: newly installed hardware, memory itself, etc.

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

4, 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

Error analysis: The Windows kernel has detected an illegal or unknown process instruction. This stop code is generally caused by the problem of memory or the reason similar to the previous 0x0000000A.

◇Solution:

(1) There is a problem with hardware compatibility: please refer to the hardware compatibility list mentioned earlier to see if all hardware is included in the list.

(2) The problematic device driver, system service or memory conflict and interrupt conflict: If the name of the driver appears in the blue screen message, please try to disable or delete the driver in the installation mode or the recovery console, and disable all The driver and software just installed. If an error occurs during system startup, please enter safe mode and rename or delete the file indicated in the blue screen message.

(3) If the error message clearly states that Win32K.sys: It is likely to be caused by a third-party remote control software, you need to close the service of this software from the Recovery Console.

(4) Appears at the next restart after installing Windows: The system partition has insufficient disk space or BIOS compatibility problems.

(5) If it appears when you close a software: It is very likely that the software has a design defect 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, and

0x00000024 is due to an error in the NTFS.sys file (the function of this driver file is to allow the system to read and write

NTFS file system disk). These two blue screen errors are likely to be caused by physical damage to the disk itself, or interruption request packet (IRP) damage. Other reasons include: too much hard disk fragmentation; file read and write operations Too frequent, and the amount of data is very high or it is caused by some disk mirroring software or anti-virus software.

◇Solution:

Step: First open the command line prompt and run "Chkdsk /r" (Note: Not CHKDISK, it feels like this, but...) command to check and repair hard disk errors. If there is a bad track (Bad Track), please use the hard disk manufacturer's offer The inspection tool for inspection and repair.

Step 2: Then disable all software that scans files, such as anti-virus software, firewalls or backup tools.

Step 3: Right-click the C:\winnt\system32\drivers\fastfat.sys file and select "Properties" to check whether its version matches the Windows version used by the current system. (Note: If it is XP, it should be C: \windows\system32

\Drivers\fastfat.sys)

Step 4: Install the motherboard driver, especially IDE driver. If your CD-ROM drive and removable storage also provide drivers, upgrade them to the version.

6, 0x00000027: RDR_FILE_SYSTEM

◆Error analysis: The cause of this error is difficult to determine, but a problem with Windows memory management is likely to cause this shutdown code.

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

7, 0x0000002EATA_BUS_ERROR

◆Error analysis: system memory storage parity error is usually caused by defective memory (including physical memory, secondary cache or graphics card memory) when the device driver accesses non-existent memory addresses. In addition, the hard disk Damaged by * or other problems, this stop code appears.

◇Solution:

(1) check*

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

(3) Use memory test software such as Memtest86 to check the memory.

(4) Check whether the hardware is installed correctly, such as whether it is firm and whether the golden finger is stained.

8, 0x00000035:NO_MORE_IRP_STACK_LOCATI*

◆Error analysis: Literally, 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 in the province, or a quality problem with the memory.

◇Solution: Please use the driver and memory-related solutions in the conventional solutions described above to eliminate them.

9, 0x0000003F:NO_MORE_SYSTEM_PTES

◆Error analysis: an error related to system memory management, such as: due to a large number of input/output operations, memory management problems: defective driver incorrectly uses memory resources; an application (such as: Backup software) is allocated a lot of kernel memory, etc.

◇Solution: Uninstall all installed software (especially those applications and anti-virus software that enhance disk performance) and drivers.

10, 0x00000044: MULTIPLE_IRP_COMPLIETE_REQUESTS

Analysis of errors: usually caused by hardware drivers.

◇Solution: Uninstall the recently installed driver. This fault rarely occurs. What is known at present is that it is in use

www.in-system.com/Some software of this company will appear, and the culprit is the Falstaff.sys file. (Isn't the author afraid of lawsuits? Publish the company website)

11, 0x00000050: PAGE_FAULT_IN_NONPAGED+AREA

◆Error analysis: problematic memory (including indoor memory, secondary cache, and video memory), incompatible software (mainly remote control and anti-virus software), damaged NTFS volume, and problematic hardware (such as: PCI card Itself is damaged), etc. will cause this error.

◇Solution: Please use the conventional solutions described above related to memory, software, hardware, hard disk, etc. to exclude.

12, 0x00000051
:REGISTRY_ERROR

◆Error analysis: This shutdown code indicates that there is an error in the registry or the system configuration manager, due to the physical damage of the hard disk itself or the problem of the file system, which causes an input/output error when reading the registration file.

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

13, 0x00000058: FTDISK_INTERNAL_ERROR

◆Error analysis: It means that an error has occurred in the main drive of the fault-tolerant set.

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

14, 0x0000005E: CRITICAL_SERVICE_FAILED

◆Error analysis: It is caused by the identification of a very important system service.

◇Solution: If a new hardware is installed after a new hardware is installed, you can remove the hardware 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 "Proper configuration" to start Windows, if this still fails, it is recommended to repair or reinstall.

15, 0x0000006F: SESSION3_INITIALIZATION-FAILED

◆Error analysis: This error usually appears when Windows starts, and is usually caused by a problematic driver or a damaged system file.

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

16, 0x00000076ROCESS_HAS_LOCKED_PAGES

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

◇Solution:

Step: Click Start-->Run: regedt32, find [HKLM\SYSTEM\Currentcontrol set\control\session manager\memory management], and create a double-byte value "TrackLockedPages" on the right side, with a value of 1. Then Windows will be in When the error occurs again, track which driver is the problem. Step 2: If the blue screen occurs 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, then update or delete it. Step 3: Enter the registry and delete the added "TrackLockedPages".

17, 0x00000077: KERNEL_STACK_INPAGE_ERROR

◆Error analysis: It means that the kernel data that needs to be used is not found in virtual memory or physical memory. This error often results in disk problems, corresponding data corruption or *erosion.

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

18, 0x0000007A: KERNEL_DATA_INPAGE_ERROR

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

◇Solution: First use the upgrade to *library anti-virus software to check and kill*, if there is no information, return 0xC000009C

or 0xC000016A code, then it means that it is caused by bad clusters, and the system's disk detection tool cannot automatically repair it. At this time, enter the "Recovery Console" and use the "chkdsk /r" command to repair it manually.

19, 0x0000007B: INACESSIBLE_BOOT_DEVICE

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

◇Solution: Generally, you only need to start the computer with the installation CD, and then perform a repair installation to solve the problem. For *, you can use the DOS version of antivirus software to check and kill (the main battle has kv2005DOS version). If there is a problem with the hard disk itself, please Install it on other computers, and then use "chkdsk /r" to check and repair disk errors.

20, 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

◆Error analysis: System processes produce errors, but the Windows error processor cannot catch them. There are many reasons for them, including: hardware compatibility, problematic drivers or system services, or some software.

◇Solution: Please use the "Event Viewer" to get more information, and find the source of the error. (It doesn't seem to be the solution, it seems that everyone has to be self-reliant here!)

21, 0x0000007F: UNEXPECTED_KERNEL_MOED_TRAP

◆Error analysis: Generally, it is caused by faulty hardware (such as memory) or some software. Sometimes overclocking can also cause this error.

◇Solution: Check the memory with detection software (for example: Memtest86), if you have overclocked, please cancel the overclocking. Unplug the PCI hardware card from the motherboard slot, or replace the slot. In addition, some motherboards (such as: nForce2 motherboard ) After overclocking, overheating of the South Bridge chip will also cause a blue screen. At this time, adding a heat sink to the chip can often effectively solve the problem.

22, 0x00000080: NMI_HARDWARE_FAILURE

◆Error analysis: It is usually caused by hardware. (It seems that the blue screen is indissoluble with hardware errors)

◇Solution: If you have recently installed new hardware, please remove it, and then try to replace the slot and installed driver, if you upgrade the driver, please restore the original version; check whether the memory gold finger is polluted and Damaged; Scan*; Run "chkdsk /r" to check and repair disk errors; Check that all hardware cards have been inserted firmly. If the above attempts have no effect, you have to find a computer repair company for help.

23, 0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED

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

◇Solution: Upgrade the driver or upgrade the BIOS.

24, 0x0000009C:MACHINE_CHECK_EXCEPTION

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

源).

◇Solution: If you have overclocked, please lower the original frequency of the CPU 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 it can't be solved, please replace the power supply.

26, 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, then when installing Windows 2K/XP, when the "press F6 if you need to install a third-party SCSI or RAID driver" prompt appears, press the F7 key, so that Windows is convenient The installation of ACPI HAL is automatically prohibited, and Standard PC HAL is installed.

27, 0x000000B4: VIDEO_DRIVER_INIT_FAILURE

◆Error analysis: This stop message means 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, conflicts with parallel or serial ports).

◇Solution: Enter the safe mode to check whether the problem is solved, if it can, please upgrade the graphics card driver, if it still does not work, it is likely that there is a conflict between the graphics card and the parallel port, you need to press the WIN+break combination key to open in the safe mode" "System Properties", find and double-click the item of the LPT1 port connected to the printer in the Hardware --> Device Manager, cancel the "Use automatic configuration" option in the "Resources" tab, and then set the "Input/Output Range" "03BC" was changed to "0378".

28, 0x000000BE:ATTEMPTED_WRITE_TO_READONLY_MEMORY

◆Error analysis: A certain driver tried to write data to the read-only memory. Usually it is after installing a new driver, system service or upgrading the firmware 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 based on this information.

29, 0x000000C2: BAD_POOL_CALLER

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

◇Solution: Please refer to the conventional solution related items introduced above to exclude.

30, 0x000000CERIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATI*

Error analysis: usually caused by a problematic driver or system service.

◇Solution: Please refer to the conventional solution related items introduced above to exclude.

31, 0x000000D1RIVER_IRQL_NOT_LESS_OR_EQUAL

◆Error analysis: usually caused by problematic drivers (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, some software ( Such as multimedia software, anti-virus software, backup software, DVD playback software, etc. can also cause this error.

◇Solution: Check the installed or upgraded driver (if "acpi.sys" and other similar file names appear in the blue screen, you can be very sure that the driver is a problem) and software; test whether there is a problem with the memory; enter the "recovery console" , Go to the partition where the virtual memory page file Pagefile.sys is located, and execute the "del pagefile.sys" command to delete the page file; then execute the "chkdsk /r" command in the partition where the page file is located; reset the virtual memory after entering Windows. If When you encounter this blue screen when you are online, and you are doing a lot of data and uploading (such as online games, BT), then it should be a problem with the network card driver, and you need to upgrade its driver.

32, 0x000000EA:THREAD_STUCK_IN_DEVICE_DRIVER

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

◇Solution: First upgrade the graphics card driver, if it does not work, you need to replace the graphics card to test whether the failure still occurs.

33, 0x000000ED: UNMOUNTABLE_BOOT_VOLUME

◆Error analysis: Generally, it is caused by an error in the disk. Sometimes it is recommended to check whether the hard disk connection is poorly connected or not using a cable that meets the hard disk transmission specifications. For example, ATA-100 still uses ATA-33 cable. It doesn’t matter to low-speed hard drives, but tell the hard drives (supporting ATA-66 and above) that the requirements are stricter. Incorrect connections can sometimes cause such failures that cannot be booted. If this error occurs frequently after the repair, it is very likely It is a precursor of hard disk damage.

◇Solution: Under normal circumstances, restarting will solve the problem, no matter what, it is recommended to execute the "chkdsk /r" command to check and repair the hard disk

34, 0x000000F2:HARDWARE)INTERRUPT_STORM

◆Error analysis: The kernel layer detects that the system has an interrupt storm, such as: a device is not released after the operation is completed

interruption. Usually this is caused by a defective driver.

◇Solution: Upgrade or uninstall the installed hardware driver.

35, 0x00000135: UNABLE_TO_LOCATE_DLL

◆Error analysis: It usually means that a certain 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 usually be displayed in the blue screen message. You can find the corresponding file through the network or other computers and copy it to the SYSTEM32 subfolder under the system folder Medium. If the file name is not displayed, it is likely that the registry is damaged. Please use system restore or a previous registry backup to restore.

36, 0x0000021A: STATUS_SYSTEM_PROCESS_TERMINATED

◆Error analysis: use
User mode subsystem, such as Winlogon or Customer Service Runtime Subsystem (CSRSS) has been damaged, so the security can no longer be guaranteed, causing the system to fail to start. Sometimes, when the system administrator incorrectly modifies the user account permissions, it cannot be accessed System files and folders.

◇Solution: Use the "correct configuration", if it doesn't work, you can use the installation CD to repair the installation.

37, STOP 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH

◆Error analysis: usually caused by damage to the driver or system DLL file. Under normal circumstances, it will appear in the blue screen

  file name

◇Solution:

(1) Use the Windows installation CD to repair the installation;

(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, enter the "Recovery Console", use the copy or expand command to copy or decompress the damaged files from the CD. However, the blue screen is generally a driver file problem, so The expand command will use a few, for example: the blue screen prompts the tdi.sys file, because the driver file is usually in the i386\driver compressed package, so use: expand %CDROM:\i386\driver.cab \f:tdi.sys c :\winnt\system\drivers.(xp is expand %CDROM:\i386\driver.cab \f:tdi.sys c:\windowns\system\drivers)

38, if these blue screen stop codes appear during startup

If a blue screen appears when Windows starts, and the error message in Appendix 1 appears, then most of the time there is a problem with the hardware. Please use the diagnostic tool provided by the hardware manufacturer to determine whether there is a problem with the hardware, and go to its website to check whether there is a 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 ask for technical support.

If you encounter the error message in the second table, you only have to reinstall Windows. If the problem cannot be solved, please call for technical support.

39. Use the same system blue screen to solve different motherboards (0*0000007E)

Disk engraving on the INTEL board to AMD blue screen solution: code: 0*0000007E

Since we can't enter the system, we can press F8 to enter the safe mode. Modify the registry to solve the problem, so there is no need to reinstall the system. And the real masters generally don't use the method of reinstalling the system to solve the problem.

Modify in safe mode [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001

\Services\intelppm]"Start"=dword:00000001

change this to "Start"=dword:00000004

Computer Blue Screen Code Collection

0X0000000 Operation completed

0X0000001 Incorrect function

0X0000002 The system cannot find the specified file

0X0000003 The system cannot find the specified path

0X0000004 The system cannot open the file

0X0000005 Access denied

0X0000006 invalid code

0X0000007 The memory control module is damaged

0X0000008 There is not enough memory space to process this command

0X0000009 The address of the memory control module is invalid

0X000000A The environment is incorrect

0X000000B Attempt to load a program with the wrong format

0X000000C Access code error

0X000000D Data error

0X000000E There is not enough memory space to complete this operation

0X000000F The system cannot find the specified hard disk

0X0000010 Unable to remove the directory

0X0000011 The system cannot move the file to another hard disk

0X0000012 No files

0X0000019 Cannot find the specified sector or track

0X000001A The specified disk or floppy cannot be accessed

0X000001B The disk cannot find the requested device

0X000001C The printer has no paper

0X000001D The system cannot write data to the specified disk

0X000001E The system cannot read the specified device

0X000001F A device connected to the system does not work

0X0000021 A part of the file is locked and cannot be accessed now

0X0000024 Too many open shared files

0X0000026 reached the end of the file

0X0000027 The disk is full

0X0000036 The network is busy

0X000003B An unexpected error occurred on the network

0X0000043 The network name cannot be found

0X0000050 file already exists

0X0000052 Cannot create directory or file

0X0000053 INT24 failed (what do you mean? Please also expert advice on the webmaster one or two)

0X000006B The program has been stopped because the substitute disk has not been inserted yet

0X000006C The disk is in use or locked

0X000006F File name is too long

0X0000070 Insufficient hard disk space

0X000007F The specified program cannot be found

0X000045B The system is shutting down

0X000045C System shutdown cannot be aborted because no shutdown action is in progress

0X000046A The available server storage space is insufficient

0X0000475 The system BIOS cannot change the system power state

0X000047E The specified program requires a new windows version

0X000047F The specified program is not a windwos or ms-dos program

The program specified by 0X0000480 has been started and cannot be restarted

The program specified by 0X0000481 is written for the old version of windows

0X0000482 One of the library files required to execute this application is damaged

0X0000483 No application is associated with the specified file of this operation

0X0000484 Sending instructions to the application program is invalid

0X00005A2 The specified device name is invalid

0X00005AA The system resources are insufficient to complete the requested service

0X00005AB insufficient system resources, unable to complete the requested service

0X00005AC Insufficient system resources, unable to complete the requested service

110 0x006E The system cannot open the specified device or file.

111 0x006F The file name is too long.

112 0x0070 The disk space is insufficient.

113 0x0071 There is no internal file identifier available.

114 0x0072 The target internal file identification word is incorrect.

117 0x0075 The IOCTL call executed by the application is incorrect.

118 0x0076 The write verification parameter value is incorrect.

119 0x0077 The system does not support the requested command.

120 0x0078 This function is only valid in Win32 mode.

121 0x0079 semaphore exceeded the timeout period.

122 0x007A The data area transferred to the system call is too small.

123 0x007B File name, directory name or storage label?*** Syntax error?***.

124 0x007C The system call level is incorrect.

125 0x007D The disk is not set with the label?***.

126 0x007E The specified module cannot be found.

127 0x007F The specified program cannot be found.

128 0x0080 There are no sub-schedules to wait for.

129 0x0081 %1 This application cannot be executed in Win32 mode.

130 0x0082 Attempt to use a file handle to an open disk partition for an

Operation other than raw disk I/O.

131 0x0083 Attempt to move the file pointer before the beginning of the file.

132 0x0084 Unable to set the file index on the specified device or file.

133 0x0085 JOIN or SUBST commands cannot be used for drives that contain previously combined drives.

134 0x0086 Try to use the JOIN or SUBST command on the drive that has been combined.

135 0x0087 Try to use the JOIN or SUBST command on the replaced drive.

136 0x0088 The system tries to delete the link relationship of the drive that has not been linked.

137 0x0089 The system tries to delete the replacement relationship of the drive that has not been replaced.

138 0x008A The system tries to combine the drive to the directory of the drive that has been combined.

139 0x008B The system tries to replace the drive with the directory of the drive that has been replaced.

140 0x008C The system tries to replace the drive with the directory of the drive that has been replaced.

141 0x008D The system tries to SUBST the drive into a combined drive directory.

142 0x008E The system cannot execute JOIN or SUBST at this moment.

143 0x008F The system cannot combine the drives or replace the directories under the same drive.

144 0x0090 This directory is not a subdirectory of the root directory.

145 0x0091 There is still information in the directory.

146 0x0092 The specified route has been replaced.

147 0x0093 Insufficient resources, unable to process this instruction.

148 0x0094 The specified way cannot be used when it takes o.

149 0x0095 The drive directory that you are trying to combine or replace is the target that has been replaced.

150 0x0096 CONFIG.SYS file does not specify system tracking information, or the tracking function is cancelled.

151 0x0097 The specified number of semaphore events DosMuxSemWait is incorrect.

152 0x0098 DosMuxSemWait is not executed; too many semaphores are set.

153 0x0099 DosMuxSemWait list is incorrect.

154 0x009A The length of the storage media standard element you entered is limited.

155 0x009B Cannot create other threads.

156 0x009C The receiving process refuses to accept the signal.

157 The 0x009D section has been discarded and cannot be locked.

158 0x009E The section has been unlocked.

159 0x009F The thread ID address is incorrect.

160 0x00A0 The quoted string passed to DosExecPgm is incorrect.

161 0x00A1 The designated Lu Shu ㄔ Xiao T.

162 0x00A2 The signal is waiting to be processed.

164 0x00A4 The system cannot create a thread.

167 0x00A7 Cannot lock part of the file.

170 0x00AA The requested resource is in use.

173 0x00AD The locking requirement of the cancellation range is not obvious.

174 0x00AE file system does not support automatic change of lock type.

180 0x00B4 The system found an incorrect section number.

182 0x00B6 The operating system cannot execute %1.

183 0x00B7 The file already exists, the same file cannot be created.

186 0x00BA The transmitted flag is wrong?***.

187 The system flag specified by 0x00BB cannot be found.

188 0x00BC The operating system cannot execute %1.

189 0x00BD The operating system cannot execute %1.

190 0x00BE The operating system cannot execute %1.

191 0x00BF Cannot execute %1 in Win32 mode.

192 0x00C0 The operating system cannot execute %1.

193 0x00C1 %1 is not a correct Win32 application.

194 0x00C2 The operating system cannot execute %1.

195 0x00C3 The operating system cannot execute %1.

196 0x00C4 The operating system cannot execute this application.

197 0x00C5 The operating system is currently unable to run this application.

198 0x00C6 The operating system cannot execute %1.

199 0x00C7 The operating system cannot execute this application.

200 0x00C8 The section of the program code cannot be greater than or equal to 64KB.

201 0x00C9 The operating system cannot
Execute %1.

202 0x00CA The operating system cannot execute %1.

203 0x00CB The system cannot find the environment option entered. \r

205 0x00CD In the command subdirectory, there is no signal sub-processing program for any itinerary.

206 0x00CE The file name or extension is too long.

207 0x00CF ring 2 Heap lining fault C

208 0x00D0 The input common file name element * or? Is incorrect, or too many common file name elements are specified.

209 0x00D1 The transmitted signal is incorrect.

210 0x00D2 Cannot set the signal processing program.

212 0x00D4 The section is locked and cannot be reconfigured.

214 0x00D6 There are too many dynamic link modules attached to this program or dynamic link module.

215 0x00D7 Can't nest calls to LoadModule.

230 0x00E6 The pipe state is invalid.

231 0x00E7 All pipe instances are busy.

232 0x00E8 The pipe is being closed.

233 0x00E9 No process is on the other end of the pipe.

234 0x00EA There is more information available.

240 0x00F0 The operation phase was cancelled.

254 0x00FE The specified extended attribute name is invalid.

255 0x00FF The extended attributes are inconsistent.

259 0x0103 No data available.

266 0x010A Copy API cannot be used.

267 0x010B The directory name is wrong?***.

275 0x0113 The extended attribute is not applicable to the buffer.

276 0x0114 The extended attribute file on the external file system has been damaged.

277 0x0115 The extended attribute table file is full.

278 0x0116 The specified extended attribute code is invalid.

282 0x011A The external file system does not support extended attributes.

288 0x0120 Intention to release mutex that does not belong to the caller.

298 0x012A semaphore transmission times are too many.

299 0x012B Only part of the requirements of Read/WriteProcessMemory is completed.

317 0x013D The system could not find the message numbered 0x%1 in the message file %2.

487 0x01E7 Attempt to access an invalid address.

534 0x0216 The operation result exceeds 32 bits.

535 0x0217 There is an itinerary at the other end of the channel to pick up and drop off information.

536 0x0218 Waiting for the itinerary to open the other end of the channel.

994 0x03E2 Access to extended attributes is denied.

995 0x03E3 The I/O operation was abnormally terminated due to the end of the thread or the request of the application program.

996 0x03E4 Reread? The I/O event is not set to the notification state.

997 0x03E5 Rereading? I/O operations are being processed.

998 0x03E6 Invalid access to memory location.

999 0x03E7 An error occurred during inpage operation?***.

If the blue screen code: 0x000007F (0X000000D 0X0000000 0X0000000 0X0000000)

is the CPU is broken

WIN XP blue screen code Daquan