Shulou(Shulou.com)06/03 Report--

A complete collection of computer blue screen codes

0X0000000 operation completed

Incorrect function of 0X0000001

The 0X0000002 system could not find the specified file

The 0X0000003 system could not find the specified path

The 0X0000004 system cannot open the file

0X0000005 denies access

Invalid code for 0X0000006

0X0000007 memory control module is damaged

There is not enough memory space in 0X0000008 to process this instruction

Invalid address of 0X0000009 memory control module

Incorrect 0X000000A environment

0X000000B tried to load a malformed program

0X000000C access code error

0X000000D data error

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

The 0X000000F system could not find the specified hard drive

0X0000010 cannot remove the directory

The 0X0000011 system cannot move files to another hard drive

0X0000012 doesn't have any files.

0X0000019 cannot find the specified sector or track

The disk or disk specified by 0X000001A cannot be accessed

The 0X000001B disk could not find the required device

The 0X000001C printer has no paper

The 0X000001D system cannot write data to the specified disk

The 0X000001E system cannot read the specified device

A device connected to the system by 0X000001F does not work.

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

There are too many shared files enabled by 0X0000024

0X0000026 reaches the end of the file

0X0000027 disk is full

0X0000036 network is busy

Unexpected error occurred in 0X000003B network

0X0000043 network name not found

The 0X0000050 file already exists

0X0000052 cannot create a directory or file

0X0000053 INT24 failure (what do you mean? Also ask the master to guide the stationmaster one or two)

0X000006B the program has stopped because the alternate disk has not been inserted

0X000006C disk is in use or locked

The 0X000006F file name is too long

0X0000070 does not have enough hard disk space

0X000007F could not find the specified program

The 0X000045B system is shutting down

0X000045C cannot abort the system shutdown because no shutdown is in progress.

Insufficient storage space for 0X000046A available server

0X0000475 system BIOS cannot change system power status

The program specified by 0X000047E requires a new version of windows

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

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

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

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

0X0000483 has no application to associate with the specified file for this operation

It is invalid for 0X0000484 to send instructions to the application.

The device name specified by 0X00005A2 is invalid

The 0X00005AA system has insufficient resources to complete the required service.

The 0X00005AB system has insufficient resources to complete the required service.

The 0X00005AC system has insufficient resources to complete the required service.

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

111The 0x006F file name is too long.

There is not enough space on the 0x0070 disk.

There are no internal file identifiers available for 0x0071.

The recognition word of the 0x0072 target internal file is incorrect.

117 0x0075 the IOCTL call performed by the application is incorrect.

118 0x0076 write validation parameter value is incorrect.

The required instructions are not supported on the 119 0x0077 system.

120 0x0078 this feature is only valid in Win32 mode.

121the 0x0079 semaphore timeout period.

The data area sent by 0x007A to the system call is too small.

123 0x007B file name, directory name or storage body name? Grammatical errors?

124The call hierarchy of the 0x007C system is incorrect.

The 125 0x007D disk is not marked? *.

126 0x007E could not find the specified module.

1270x007F could not find the specified program.

128 0x0080 has no subitinerary to wait.

The application 1290x0081 1 cannot be run 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.

1310x0083 attempts to move the file indicator before the beginning of the file.

132 0x0084 cannot set file metrics on the specified device or file.

133The 0x0085 JOIN or SUBST instructions cannot be used to include pre-combined drives.

0x0086 tries to use JOIN or SUBST instructions on already combined drives.

135 0x0087 attempts to use the JOIN or SUBST instruction on the disk drive that has been replaced.

The 0x0088 system attempts to remove connections from unconnected drives.

The 1370x0089 system attempts to remove the replacement relationship from an unreplaced drive.

The 0x008A system attempts to combine the drive into the directory of the drive that has already been combined.

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

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

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

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

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

0x0090 this directory is not a subdirectory of the root directory.

145The 0x0091 catalogue still has information.

The road specified by 1460x0092 has been replaced.

There are insufficient 0x0093 resources to process this directive.

148The Luna specified by 0x0094 cannot be used.

The drive directory that 0x0095 tries to combine or replace is the target that has been replaced.

The system tracking information is not specified in the 150 0x0096 CONFIG.SYS file, or the tracking function is disabled.

The number of semaphore event DosMuxSemWait specified by 1510x0097 is incorrect.

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

The 153 0x0099 DosMuxSemWait list is incorrect.

0x009A the storage media symbol length limit you entered.

155 0x009B was unable to create other threads.

1560x009C receive stroke reject signal.

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

The 1580x009E section has been unlocked.

159The address of the 0x009F thread identifier is incorrect.

The quoted digit string passed from 1600x00A0 to DosExecPgm is incorrect.

161The road designated by 0x00A1 is forgiven T.

The 0x00A2 signal is waiting for processing.

164The 0x00A4 system was unable to build a thread.

167 0x00A7 could not lock part of the file range.

The required resources for 170 0x00AA are in use.

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

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

The 180 0x00B4 system found an incorrect section number.

182 the 0x00B6 operating system was unable to execute 1.

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

The flag of 186 0x00BA transmission is wrong? *.

The system flag specified by 0x00BB was not found.

188 the 0x00BC operating system was unable to execute 1.

189The 0x00BD operating system was unable to execute 1.

The 190 0x00BE operating system was unable to execute 1.

191 0x00BF cannot execute 1 in Win32 mode.

192 the 0x00C0 operating system was unable to execute 1.

193 0x00C1 1 is not the correct Win32 application.

The 194 0x00C2 operating system was unable to execute 1.

The 195 0x00C3 operating system was unable to execute 1.

The 0x00C4 operating system cannot run this application.

The 197 0x00C5 operating system currently cannot run this application.

The 198 0x00C6 operating system could not execute 1.

The 199 0x00C7 operating system cannot run this application.

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

The 2010x00C9 operating system was unable to execute 1.

202The 0x00CA operating system was unable to execute 1.

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

205 0x00CD in the instruction subdirectory, no travel has a signal sub-processor.

The 0x00CE file name or filename is too long.

207 0x00CF ring 2 stack set off Bachou C

The common file name entered by 2080x00D0 is meta or? Incorrect or too many common file name elements specified.

The signal transmitted by 209 0x00D1 is incorrect.

The signal processing program could not be set by the 2100x00D2.

The 0x00D4 section is locked and cannot be reconfigured.

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

215 0x00D7 Can't nest calls to LoadModule.

230 0x00E6 The pipe state is invalid.

231 0x00E7 all the 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 has more information available.

The 2400x00F0 job phase was cancelled.

The extension property name specified by 2540x00FE is invalid.

The properties of the 255 0x00FF extension are inconsistent.

259 0x0103 has no information available.

266 0x010A cannot use Copy API.

267 0x010B directory name error?

The 0x0113 extension property does not apply to buffers.

The extended attribute file of 0x0114 on the plug-in file system has been corrupted.

277 0x0115 extended properties table is full.

The extension property code specified by 278 0x0116 is invalid.

This file system with 282 0x011A plug-ins does not support extended properties.

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

The number of 0x012A semaphore transmissions is too many.

299 0x012B fulfills only part of the Read/WriteProcessMemory requirements.

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

487 0x01E7 attempted to access an invalid address.

The result of 534 0x0216 operation exceeds 32 bits.

There is a journey at the other end of the 535 0x0217 channel to pick up and pick up data.

536 0x0218 waits for the itinerary to open the other end of the passage.

The property of 994 0x03E2 access extension is denied.

995 0x03E3 terminates the Icano operation abnormally due to thread termination or application requirements.

The 996 0x03E4 reread? Istroke O event is not set to the notification state.

997 0x03E5 is processing a reread? Icano job.

Invalid access to memory location by 998 0x03E6.

999 0x03E7 error executing inpage job?

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

That is, CPU is broken.

WIN XP Blue screen Code Collection

I. the meaning of blue screen

1. Fault check information

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

The first part of the error in KMODE_EXCEPTION_NOT_HANDLED is the Stop Code, that 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 random developer-defined parameters (this parameter is incomprehensible to ordinary users and can only be understood by driver writers or developers of Microsoft operating systems). The third part is the wrong name. The first line of information is usually used to identify the driver or device that is in error. Most of this information is simple, but the stop code can be used as a search term in the Microsoft knowledge base and other technical materials.

two。 Recommended action

The second part of the blue screen is the operation information recommended by the user. Sometimes, the recommended action is just general advice (for example, go to the vendor's website to find updates to BIOS, etc.); sometimes, it is to display a prompt related to the current problem. Generally speaking, the only advice is to restart.

3. The debug port tells the user whether the memory dump image has been written to the disk dealer, and the use of the memory dump image can determine the nature of the problem, and will also tell the user whether the debug information has been transmitted to another computer vendor and what port is used to complete this communication. However, the information here makes no sense to ordinary users. Sometimes the Security Section can successfully find out which production team is at fault, and it will clearly report which document is at fault in the first part, but often it can only check the approximate scope, but it can not clearly identify the problem. As the factory was forced to stop completely, it had to be reorganized and restarted, and sometimes the production team realized the mistake and did not repeat it. But sometimes they still try to grab the parts, so the factory leader has to repeat the shutdown decision (cannot start and display the blue screen message, or reappear the blue screen when doing the same operation).

Second, the treatment method of blue screen

There is a lot of Windows 2K/XP blue screen information, which can not be fully explained in an article, but their causes often focus on incompatible hardware and drivers, problematic software, viruses, etc., so we first provide you with some conventional solutions. When you encounter blue screen errors, you should first eliminate them against these solutions.

1. Restart

Sometimes a program or driver makes a mistake and they turn over a new leaf after restarting. (note: see 7. Query the outage code)

two。 New hardware

First of all, we should check whether the new hardware is plugged in. This problem, which is ignored by many people, often causes many inexplicable failures. If you are sure there is no problem, unplug it, then try a different slot and install the latest driver. At the same time, you should check whether the hardware is compatible with the operating system against the hardware compatibility category of the Microsoft website. If your hardware is not on the list, check the hardware manufacturer's website or call their inquiry number.

Hardware compatibility list for Windows XP

Hardware compatibility categories for Windows 2K

3. New drivers and new services

If you have just installed a new driver for some hardware, or installed some software, and it has added corresponding items to the system service (such as antivirus software, CPU cooling software, firewall software, etc.), and there is a blue screen failure during restart or use, please go to safe mode to uninstall or disable them.

4. Check for virus

Viruses such as shock waves and oscillating waves sometimes cause Windows blue screens to crash, so virus detection is essential. At the same time, some spyware can also cause blue screen, so it is best to scan with relevant tools.

5. Check BIOS and hardware compatibility

For newly installed computers that often have blue screen problems, you should check and upgrade BIOS to the latest version and turn off memory-related items, such as caching and mapping. In addition, you should check your hardware against Microsoft's hardware compatibility list. In addition, if the motherboard BIOS can not support large-capacity hard drives will also lead to blue screen, it needs to be upgraded.

Tips:

Cache and mapping entries for BIOS

Video BIOS Shadowing (video BIOS mapping)

Shadowing address ranges (mapped address column)

System BIOS Cacheable (system BIOS buffer)

Video BIOS Cacheable (video BIOS buffer)

Video RAM Cacheable (video memory buffer)

6. Check the system log

Enter: EventVwr.msc in the start-> menu, enter the event Viewer, and check the Syslog and Application Log items that indicate errors.

7. Query outage code

Write down the dense E text in the blue screen, then go to other computers to surf the Internet, go to Microsoft help and support website http://support.microsoft.com?, and enter the stop 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" to search again. In general, useful cases will be found here. In addition, in baidu, Google and other search engines, the use of blue screen stop code or the following description text for keyword search, there are often other gains.

8. Correct configuration for the last time

In general, the blue screen appears after the hardware driver has been updated or the new hardware has been installed, and the "last correct configuration" provided by Windows 2K/XP is a shortcut to solve the blue screen. Restart the system, press F8 when the boot menu appears, the advanced startup options menu will appear, and then select "Last correct configuration".

9. Install the latest system patches and Service Pack

Some blue screens are caused by defects in Windows itself, which can be resolved by installing the latest system patches and Service Pack.

Third, the blue screen code meaning and the solution

1 、 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 a memory address in kernel mode that is accessed with too high an intra-process request level (IRQL) that it does not have permission to access.

◇ solution: please try to exclude with 2, 3, 5, 8, 9 of the above solution.

2 、 0x00000012:TRAP_CAUSE_UNKNOWN

◆ error analysis: if you encounter this error message, then unfortunately, the result of KeBudCheck analysis is the cause of the error

Unknown.

◇ solution: since Microsoft can't help you, you're on your own. Remember carefully when this error occurred, what you did to the system when it first happened, and what you were doing when it happened. Find out the possible reasons from this information and choose the appropriate solution to try to rule it out.

3 、 0x0000001A:MEMORY_MANAGEMENT

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

◇ solution: if you are installing Windows, it may be because your computer does not meet the minimum memory and disk requirements for installing Windows.

4 、 0x0000001E:KMODE_EXCEPTION_NOT_HANDLED

◆ error analysis: the Windows kernel detects an illegal or unknown process instruction, which is usually caused by faulty memory or something similar to the previous 0x0000000A.

◇ solution:

(1) there is a problem with hardware compatibility: please check whether all hardware is included in the latest hardware compatibility list mentioned earlier.

(2) problematic device drivers, system services, or memory and interrupt conflicts: if the name of the driver appears in the blue screen message, try disabling or removing the driver in installation mode or in the recovery console. And disable all newly installed drivers and software. If the error occurs during system startup, enter safe mode and rename or delete the file indicated in the blue screen message.

(3) if the Win32K.sys is clearly indicated in the error message: it is likely to be caused by the third-party remote control software, the service to the software needs to be turned off from the recovery console.

(4) when rebooting for the first time after installing Windows: the most suspected reason is that the disk space of the system partition is insufficient or there is a problem with BIOS compatibility.

(5) if it occurs when a software is closed: it is very likely that there is a design defect in the software 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 a FAT16 or FAT32 file system, while

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

Disk of the NTFS file system). These two blue screen errors are most likely caused by physical damage to the disk itself or IRP damage caused by interrupts. Other reasons include too much fragmented hard disk, frequent file reading and writing, and a large amount of data or caused by some disk mirroring software or antivirus software.

◇ solution:

Step 1: first open a command prompt and run "Chkdsk / r" (Note: it's not CHKDISK, it feels like this, but...) Command to check and repair hard disk errors, if the existence of Bad Track is reported, please use the inspection tool provided by the hard drive manufacturer to check and repair.

Step 2: then disable all software that scans files, such as antivirus software, firewalls, or backup tools.

Step 3: right-click the C:\ winnt\ system32\ drivers\ fastfat.sys file and select Properties to see if its version matches the Windows version currently used by the system. (note: if it is XP, it should be C:\ windows\ system32

\ drivers\ fastfat.sys)

Step 4: install the latest motherboard driver, especially the IDE driver. If your optical drive and removable memory also provide drivers, it is best to upgrade them to the latest 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 lead to this downcode.

◇ solution: if it's memory management, adding memory will usually solve the problem.

7 、 0x0000002EATA_BUS_ERROR

◆ error analysis: system memory parity errors are usually caused by defective memory (including physical memory, secondary cache or graphics card memory) when the device driver accesses the memory address that does not exist. In addition, the hard disk is damaged by viruses or other problems to produce this stop code.

◇ solution:

(1) check for virus

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

(3) check the memory with Memtest86 and other memory testing software.

(4) check whether the hardware is installed correctly, such as whether the hardware is firm and whether the gold finger is stained.

8 、 0x00000035:NO_MORE_IRP_STACK_LOCATIONS

◆ error analysis: literally, the driver or some software should have stack problems. In fact, the real cause of this failure should be a problem with the driver or the quality of the memory.

◇ solution: please use the driver and memory related solutions in the general solution described above to exclude.

9 、 0x0000003F:NO_MORE_SYSTEM_PTES

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

◇ solution: uninstall all newly installed software (especially disk performance-enhancing applications and antivirus software) and drivers.

10 、 0x00000044:MULTIPLE_IRP_COMPLIETE_REQUESTS

◆ error analysis: it is usually caused by hardware drivers.

◇ solution: uninstall recently installed drivers. This failure is rare, and what is known so far is that it is in use

Www.in-system.com/ this company's some software will appear, of which the culprit is the Falstaff.sys file. (isn't the author afraid to file a lawsuit and publish the company's website?)

11 、 0x00000050: PAGE_FAULT_IN_NONPAGED+AREA

◆ error analysis: this error can be caused by faulty memory (including house memory, secondary cache, video memory), incompatible software (mainly remote control and antivirus software), damaged NTFS volumes and faulty hardware (for example, the PCI card itself has been damaged).

◇ solution: please use the solutions related to memory, software, hardware, hard disk, etc., in the general solutions described above.

OK, rule it out.

12 、 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 problems with the file system, resulting in input / output errors when reading registration files.

◇ solution: use "chkdsk / r" to check and fix disk errors.

13 、 0x00000058:FTDISK_INTERNAL_ERROR

◆ error analysis: indicates that an error occurred in the main driver of the fault-tolerant set.

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

14 、 0x0000005E:CRITICAL_SERVICE_FAILED

◆ error analysis: caused by the startup identification of a very important system service.

◇ solution: if you install a new hardware, you can first remove the hardware, and through the online list to check whether it is compatible with Windows 2K/XP, 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 the installation or reinstall.

15 、 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.

16 、 0x00000076ROCESS_HAS_LOCKED_PAGES

◆ error analysis: usually because a driver does not release the occupied memory correctly after completing an input / output operation

◇ solution:

Step 1: click start-> run: regedt32, find [HKLM\ SYSTEM\ Currentcontrol set\ control\ session manager\ memory management], and create a new double-byte value "TrackLockedPages" on the right, with a value of 1. In this way, Windows will track which driver it is when the error occurs again. Step 2: if the blue screen appears again, the error message will become: STOP:0x0000000CB (0xY 0xY 0xY) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS where the fourth "0xY" will be displayed as the name of the problem driver, and then update or delete it. Step 3: enter the registry and delete the added "TrackLockedPages".

17 、 0x00000077:KERNEL_STACK_INPAGE_ERROR

◆ error analysis: indicates that the kernel data you need is not found in virtual memory or physical memory. This error often causes problems with the disk, resulting in data corruption or virus erosion.

◇ solution: use antivirus software to scan the system; use the "chkdsk / r" command to check and repair disk errors, and if not, use tools provided by disk manufacturers to check and repair.

18 、 0x0000007A:KERNEL_DATA_INPAGE_ERROR

◆ error analysis: this error is often caused by the kernel data in virtual memory can not be read into memory. The reason may be bad clusters, viruses, disk controller errors and memory problems in virtual memory page files.

◇ solution: first check and kill the virus by upgrading to the latest virus database antivirus software, and return 0xC000009C if there is no information.

Or 0xC000016A code, then it means that it is caused by a bad cluster, and the system's disk detection tool cannot repair it automatically, so go to 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 startup. It usually occurs when the motherboard is started for the first time after the motherboard is replaced, mainly because the IDE controllers of the new motherboard and the old motherboard use different chipsets. Sometimes it can be caused by a virus or hard disk damage.

◇ solution: generally, just use the installation CD to start the computer, and then perform a repair installation to solve the problem. For the virus, you can use the DOS version of the antivirus software to check and kill (the main battle has kv2005DOS version download). If there is a problem with the hard drive itself, install it to another computer, and then use "chkdsk / r" to check and fix the disk error.

20 、 0x0000007E:SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

◆ error analysis: the system process produces an error, but the Windows error processor cannot catch it. There are many reasons, including hardware compatibility, faulty drivers or system services, or some software.

◇ solution: use the event Viewer to get more information and find the root cause of the error. It seems that it is not a solution. It seems that everyone here is going to be self-reliant.

21 、 0x0000007F:UNEXPECTED_KERNEL_MOED_TRAP

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

◇ solution: check memory with detection software (such as Memtest86) and cancel overclocking if overclocking occurs. Unplug the PCI hardware card from the motherboard slot, or replace the slot. In addition, after overclocking on some motherboards (such as nForce2 motherboard), the overheating of Nanqiao chip will also lead to blue screen, so adding heat sink for the chip can effectively solve the problem.

22 、 0x00000080:NMI_HARDWARE_FAILURE

◆ error analysis: it is usually caused by hardware. (it seems that the blue screen is inextricably linked to hardware errors)

◇ solution: if you have recently installed new hardware, remove it, then try changing the slot and installing the latest driver, if you upgraded the driver, restore the original version; check the memory gold finger for contamination and damage; scan for viruses; run "chkdsk / r" to check and repair disk errors; check that all hardware cards are plugged in. If the above attempts do not work, you will have to ask a professional computer maintenance company for help.

23 、 0x0000008E:KERNEL_MODE_EXCEPTION_NOT_HANDLED

◆ error analysis: kernel-level applications generate errors, but Windows error handlers do not catch. It is usually a hardware compatibility error.

◇ solution: upgrade the driver or upgrade BIOS.

24 、 0x0000009C:MACHINE_CHECK_EXCEPTION

◆ error analysis: usually caused by hardware. It is usually due to overclocking or hardware problems (memory, CPU, bus, electricity)

Source).

◇ solution: if overclocking, please lower the CPU original frequency and check the hardware.

25 、 0x0000009FRIVER_POWER_STATE_FAILURE

◆ error analysis: often related to power supply, often occurs in power-related operations, such as shutdown, standby or sleep.

◇ solution: reinstall the system, if it cannot be solved, please replace the power supply.

26 、 0x000000A5:ACPI_BIOS_ERROR

◆ error analysis: usually because the motherboard BIOS can not fully support the ACPI specification.

◇ solution: if there is no corresponding BIOS upgrade, press the F7 key when installing Windows 2K/XP, when prompted by "press F6 if you need to install a third-party SCSI or RAID driver", so that Windows will automatically disable the installation of ACPI HAL and install Standard PC HAL.

27 、 0x000000B4:VIDEO_DRIVER_INIT_FAILURE

◆ error analysis: this stop message indicates that Windows cannot enter the graphical interface because it cannot start the graphics card driver. It is usually the problem with the video card, or there is a hardware conflict with the video card (for example, with parallel or serial ports).

◇ solution: enter safe mode to see if the problem is solved. If you can, upgrade the latest graphics card driver. If not, it is likely that there is a conflict between the video card and the parallel port. You need to press the WIN+break key combination in safe mode to open the "system Properties". Find and double-click the item connected to the printed LPT1 port in the hardware-> device Manager. On the Resources tab, uncheck use autoconfiguration, and then change the 03BC for input / output range to 0378.

28 、 0x000000BE:ATTEMPTED_WRITE_TO_READONLY_MEMORY

◆ error analysis: caused by a driver trying to write data to read-only memory. Usually 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, uninstall or disable the newly installed driver or software according to this information.

29 、 0x000000C2:BAD_POOL_CALLER

◆ error analysis: a kernel layer process or driver mistakenly attempts to enter memory operations. It is usually caused by drivers or software with BUG.

◇ solution: please refer to the general solution related projects described above for exclusion.

30 、 0x000000CERIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

◆ error analysis: it is usually caused by faulty drivers or system services.

◇ solution: please refer to the general solution related projects described above for exclusion.

31 、 0x000000D1RIVER_IRQL_NOT_LESS_OR_EQUAL

◆ error analysis: it is usually caused by faulty drivers (for example, Logitech Mouse Logitech MouseWare 9.10 and 9.24 drivers can cause this failure). At the same time, defective memory, damaged virtual memory files, and some software (such as multimedia software, antivirus software, backup software, DVD playback software) can also cause this error.

◇ solution: check the newly installed or upgraded drivers (if a similar file name such as "acpi.sys" appears in the blue screen, you can be sure of the driver problem) and software; test if 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, execute the "del pagefile.sys" command, and 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 you encounter this blue screen while surfing the Internet, and you happen to be downloading and uploading a lot of data (for example, online games, BT downloads), then it should be the problem with the Nic driver, and you need to upgrade its driver.

32 、 0x000000EA:THREAD_STUCK_IN_DEVICE_DRIVER

◆ error analysis: is usually caused by the video card or video card driver.

◇ solution: first upgrade the latest graphics card driver, if not, you need to replace the video card to test whether the failure still occurs.

33 、 0x000000ED:UNMOUNTABLE_BOOT_VOLUME

◆ error analysis: generally due to disk errors, it is sometimes recommended to check whether the hard disk connection is not in good contact, or not to use a cable that conforms to the transmission specifications of the hard disk. For example, ATA-100 still uses the ATA-33 cable, which is indifferent to the low-speed hard disk, but tells the hard disk (support ATA-66 or above) that the requirements are more stringent. Wiring with incorrect specifications can sometimes cause this kind of failure that can not be turned on. If this error occurs frequently after repair, it is likely to be a precursor of hard disk damage.

◇ solution: in general, a restart will solve the problem, and it is recommended that you execute the "chkdsk / r" command to check and repair the hard drive anyway

34, 0x000000F2:HARDWARE) INTERRUPT_STORM

◆ error analysis: the kernel layer detects an interruption storm in the system, for example, a device does not release its occupancy after completing the operation.

The interruption. Usually this is caused by a defective driver.

◇ solution: upgrade or uninstall the newly installed hardware drivers.

35 、 0x00000135:UNABLE_TO_LOCATE_DLL

◆ error analysis: usually indicates that a file is missing or corrupted, or that there is an error in the registry.

◇ solution: if the file is missing or corrupted, the corresponding file name is usually displayed in the blue screen message. You can find the corresponding file through the network or other computer and copy it to the system 32 subfolder under the system folder. If the file name is not displayed, it is likely that the registry is corrupted. Please use system restore or previous registry backup to restore.

36 、 0x0000021A:STATUS_SYSTEM_PROCESS_TERMINATED

◆ error analysis: user mode subsystems, such as Winlogon or customer service runtime subsystem (CSRSS), are corrupted, so security can no longer be guaranteed and the system cannot be started. Sometimes, when a system administrator mistakenly modifies the permissions of a user's account, he or she cannot access system files and folders.

◇ solution: use the Last correct configuration, if not, use the installation CD to repair the installation.

37 、 STOP 0xC0000221 or STATUS_IMAGE_CHECKSUM_MISMATCH

◆ error analysis: usually due to driver or system DLL file corruption. Normally, it will appear on the blue screen.

File name

◇ solution:

(1) use Windows installation CD for repair installation

(2) if you can still enter safe mode, you can "start-> run": sfc / scannow

(3) it can also be solved by extracting files, go to the "failure recovery console" and use copy or expand commands to copy or decompress damaged files from the CD. However, the blue screen is usually a problem with the driver file, so the expand command will be used. For example, the tdi.sys file is prompted on the blue screen, because the driver file is usually in the i386\ driver 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 at startup

If there is a blue screen when Windows starts and the error message in schedule 1 appears, then most of the time there is a hardware problem, please use the diagnostic tools provided by the hardware manufacturer to determine whether there is a problem with the hardware, and go to its website to see if there is the latest BIOS or firmware update. If there is no problem with the hardware, reinstall Windows 2K/XP, if the same problem still occurs, you can only turn to professional technical support.

If you encounter the error message in schedule 2, you can only reinstall Windows. If you can't solve the problem, you are advised to ask for professional technical support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.