Blue screen is common when using windows, and it is laborious and time-consuming to reinstall the system frequently because the source of the error is not clear. The following collected some windows crash passwords for your reference.

0 0x0000 job completed.

1 0x000 1 incorrect function.

2 0x0002 The system cannot find the specified file.

3 0x0003 The system cannot find the specified path.

4 0x0004 The system cannot open the file.

5 0x0005 Access denied.

6 0x0006 Invalid code.

7 0x0007 The bank control block has been corrupted.

8 0x0008 There is not enough storage space to process this command.

9 0x0009 The address of the storage control block is invalid.

10 0x000a environment is incorrect.

1 1 0x000b tried to load a malformed program.

Error in 12 0x000c access code.

13 0x000d data error.

14 0x000e does not have enough storage space to complete this operation.

15 0x000f The system cannot find the specified drive.

16 0x00 10 cannot delete the directory.

17 0x00 1 1 The system cannot move files to other drives.

18 0x00 12 has no file.

19 0x00 13 storage medium is write-protected.

20 0x00 14 system cannot find the specified device.

2 1 0x00 15 device is not ready.

22 0x00 16 device cannot recognize this instruction.

23 0x00 17 data error (cyclic redundancy check)

24 0x00 18 program issued a long error instruction.

The 25 0x00 19 drive cannot find a fixed sector or track on the disk.

26 0x00 1a cannot access the specified disk or floppy disk.

27 0x00 1b drive cannot find the required volume.

28 0x00 1c printer has no paper.

29 0x00 1d system cannot write data to the specified drive.

30 0x00 1e system cannot read the specified device.

3 1 0x00 1f The device connected to the system is invalid.

32 0x0020 The process cannot access the file because another process is using it.

Part of the file 33 0x002 1 is locked and cannot be accessed now.

The floppy disk of drive 34 0x0022 is incorrect. Please insert %2 (volume serial number: %3) into drive% 1.

36 0x0024 There are too many open shared files.

38 0x0026 Reached the end of the file.

39 0x0027 Disk is full.

50 0x0032 does not support this network request.

5 1 0x0033 The remote computer cannot be used.

52 0x0034 Duplicate network name.

53 0x0035 The network path cannot be found.

54 0x0036 The network is busy.

55 0x0037 The specified network resource or device is no longer available.

56 0x0038 The network bios command limit has been reached.

57 0x0039 There is something wrong with the network adapter.

The server specified by 58 0x003a cannot perform the requested operation.

An unexpected error occurred in the 59 0x003b network.

The 60 0x003c remote adapter is not compatible.

6 1 0x003d printer queue is full.

The space of the 62 0x003e server cannot store the files waiting to be printed.

63 0x003f The file waiting to be printed has been deleted.

64 0x0040 The specified network name cannot be used.

65 0x004 1 Access to the network is denied.

66 0x0042 The network resource type is wrong.

67 0x0043 The network name cannot be found.

68 0x0044 exceeds the name limit of LAN adapter.

69 0x0045 exceeds the limit of network bios session.

70 0x0046 The remote server has been paused or is starting.

7 1 0x0047 cannot connect to this remote computer at this time because the number of connections has reached the maximum.

72 0x0048 The specified printer or disk device has been suspended.

80 0x0050 file already exists.

82 0x0052 Unable to create directory or file.

83 0x0053 int 24 failed

84 0x0054 The storage used to process this request cannot be used.

85 0x0055 The name of the near-end device has already been used.

86 0x0056 The specified network password is incorrect.

87 0x0057 parameter error.

88 0x0058 A data write error occurred in the network.

89 0x0059 At this time, the system cannot perform other trips.

100 0x0064 Unable to create other system signals.

10 1 0x0065 belongs to the semaphore dedicated to other trips.

102 0x0066 semaphore has been set and cannot be closed.

103 0x0067 Unable to specify semaphore.

104 0x0068 Unable to request a dedicated semaphore during the interrupt.

105 0x0069 The previous ownership of this semaphore has ended.

106 0x006a Please insert the floppy disk into% 1.

107 0x006b The program has stopped because the replacement disk is not inserted.

108 0x006c disk is in use or locked.

109 0x006d pipeline has been aborted.

1 10 0x006e The system cannot open the specified device or file.

The file name of 65438+110x006f is too long.

1 12 0x0070 Insufficient disk space.

1 13 0x007 1 No internal file identifier is available.

1 14 0x0072 The target internal file identifier is incorrect.

1 17 0x0075 The ioctl of the application call is incorrect.

1 18 0x0076 The value of the write verification parameter is incorrect.

1 19 0x0077 The requested command is not supported by the system.

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

12 1 0x0079 semaphore exceeded the timeout period.

122 0x007a The data area passed to the system call is too small.

123 0x007b file name, directory name or storage label syntax error.

124 0x007c system call hierarchy is incorrect.

125 0x007d disk is not marked.

126 0x007e cannot find the specified module.

127 0x007f cannot find the specified program.

128 0x0080 There is no sub-trip to wait.

129 0x0081%1This application cannot run in win32 mode.

130 0x0082 attempted to use the file handle of the open disk partition.

Operations other than original disk I/O.

13 1 0x0083 tried to move the file pointer before the beginning of the file.

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

133 0x0085 join or subst command cannot be used for previously bound disk drives.

134 0x0086 Try to use the join or subst command on a combined disk drive.

135 0x0087 Try to use the join or subst command on the replaced disk drive.

136 0x0088 The system tried to delete the link relationship of the unlinked drive.

137 0x0089 The system tried to delete the replacement relationship of the unreplaced drive.

138 0x008a The system tried to add the drive to the directory where the drive has been added.

139 0x008b The system tried to replace the drive with the directory of the replaced drive.

140 0x008c system tried to replace the drive with the directory of the replaced drive.

14 1 0x008d The system tried to replace the drive with a combined drive directory.

142 0x008e system cannot perform join or subst at this time.

143 0x008f system cannot merge drives or replace directories under the same drive.

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

There is still data in the 145 0x009 1 directory.

The path specified by 146 0x0092 has been replaced.

147 0x0093 Insufficient resources to process this instruction.

The path specified by 148 0x0094 cannot be used at this time.

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

150 0x0096 config.sys file did not specify system tracking information, or the tracking function was cancelled.

15 1 0x0097 The number of semaphore events specified is incorrect.

152 0x0098 dosmuxsemwait not executed; Too many semaphores are set.

153 0x0099 dosmuxsemwait list is incorrect.

154 0x009a The storage medium symbol length limit you entered.

155 0x009b Unable to create another thread.

System crash and blue screen solution!

System crash, blue screen crack

1, 0x000000a: irql _ non _ less than _ or _ equal to.

◆ Error analysis: It is mainly caused by driver failure, defective or incompatible software and hardware. From a technical point of view, it shows that

In kernel mode, some memory addresses are accessed at too high an in-process request level (IRQL).

◇ Solution: Please use the 2, 3, 5, 8 and 9 solutions mentioned above to eliminate them as much as possible.

2. 0x000000 12: trap _ cause _ unknown

Error analysis: If you encounter this error message, unfortunately, the result of KeBudCheck analysis is that the cause of the error is unknown.

Solution: Since Microsoft can't help you, you have to rely on yourself. Please carefully recall when this error occurred; first time

What did you do to the system when it happened? What happened when it happened? Find out the possible reasons from these information and choose the corresponding reasons.

This solution attempts to exclude.

3. 0x000000 1A: memory management

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

Solution: If it appears when installing Windows, it may be because your computer cannot reach the minimum memory for installing Windows and.

Disk requirements.

4、0x 000000 1E:KMODE _ EXCEPTION _ NOT _ HANDLED

◆ Error analysis: The Windows kernel detects illegal or unknown process instructions, which are usually due to memory or

Similar to the previous 0x0000000A.

◇ Solution:

(1) Hardware compatibility problem: Please check whether all the hardware is included in the latest hardware compatibility list mentioned above.

(2) There is something wrong with the device driver, system service or memory conflict and interrupt conflict: if the name of the driver appears in the blue screen information,

Try to disable or remove drivers in installation mode or recovery console, and disable all newly installed drivers and software. If it's wrong,

Error occurred 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 indicates that Win32K.sys is probably caused by a third-party remote control software, it needs to be recovered from the fault.

The service of the software will be shut down in the console.

(4) When you restart for the first time after installing Windows, the biggest possibility is that the disk space of the system partition is insufficient or there is a problem with BIOS compatibility.

(5) If it happens when a software is shut down, it is likely that the software has saved design defects, please upgrade or uninstall it.

5、0x00000023:FAT_FILE_SYSTEM

0x00000024:NTFS_FILE_SYSTEM

◆ Error analysis: 0x00000023 generally occurs when reading and writing the system partition of FAT 16 or FAT32 file system, while 0x00000024 does.

Because there are errors in the NTFS.sys file (the function of this driver file is to allow the system to read and write the disk using the NTFS file system), these two blue screen errors are probably caused by the physical damage of the disk itself or the damage of the interrupt request package (IRP). Other reasons include: too many hard disk fragments; File reading and writing operations are too frequent, and the amount of data is very large, or it is 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 ...) to check.

Check and repair hard disk errors. If bad tracks are reported, please use the inspection tools provided by the hard disk manufacturer to check and repair them.

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" to see if its version is the latest.

The Windows version used by the system is consistent. (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 removable storage also provide drivers,

It is best to upgrade them to the latest version.

6. 0x00000027:RDR file system

Error analysis: it is difficult to determine the cause of this error, but there is a problem with Windows memory management, which is likely to lead to this shutdown code.

The emergence of.

Solution: If it is because of memory management, usually increasing memory can solve the problem.

7、0x0000002EATA_BUS_ERROR

◆ Error analysis: The parity check of system memory produces errors, usually due to memory defects (including physical memory and secondary cache).

Or video card memory). In addition, the hard disk is infected by virus or other problems.

This stop code will only appear if it is damaged.

◇ Solution:

(1) Check for viruses

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

(3) Check the memory with memory test software such as Memtest86.

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

8. 0x00000035: There are no more IRP stack locations.

Error analysis: Literally, there should be a stack problem in the driver or some software. In fact, the real reason for this failure should be

At this time, there is either a problem with the driver or a problem with the memory.

◇ Solution: Please use the solution related to driver and memory in the conventional solution introduced earlier.

9、0x0000003F:NO_MORE_SYSTEM_PTES

Error analysis: errors related to system memory management, such as memory management caused by a large number of input/output operations.

There are problems in management: defective drivers misuse memory resources; Applications (such as backup software) are allocated a large number of

Kernel memory and so on.

◇ Solution: Uninstall all newly installed software (especially those applications and antivirus software that enhance disk performance) and drivers.

10, 0x00000044: Multiple _ IRP _ complete _ requests.

Error analysis: generally caused by hardware drivers.

◇ Solution: Uninstall the recently installed driver. This kind of failure rarely happens. What is known at present is that it is in use.

& lta href="/" target="_blank">。 /& lt； /a & gt； Some software of this company will appear from time to time, and the culprit is the Falstaff.sys file.

Don't be afraid to go to court and publish the company website)

1 1、0x 00000050:PAGE _ FAULT _ IN _ non paged AREA

Error analysis: memory failure (including indoor memory, secondary cache and video memory) and software incompatibility (mainly remote control and antivirus)

Software), damaged NTFS volumes, and faulty hardware (for example, the PCI card itself is damaged) can all cause this error.

Solution: Please use related solutions such as memory, software, hardware and hard disk. To eliminate them.

12, 0x0000005 1: Registry error.

Error analysis: This shutdown code indicates that there is an error in the registry or system configuration manager, because the hard disk itself has physical damage or file system.

There is a problem in the system, resulting in an input/output error when reading the registration file.

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

13、0x 00000058:ft disk _ INTERNAL _ ERROR

◆ Error analysis: It indicates that the main driver of the fault-tolerant set has an error.

◇ Solution: Try to restart the computer first to see if it can solve the problem. If not, please try "Last Good Configuration" to solve it.

14、0x 0000005 e:CRITICAL _ SERVICE _ FAILED

◆ Error analysis: It is caused by a very important system service startup logo.

◇ Solution: If new hardware is installed, you can remove it first and check whether it is through the online list.

Compatible with Windows 2K/XP, and then start the computer. If the blue screen still appears, please use Last Known Good Configuration to start Windows.

If it still fails, it is recommended to repair and install or reinstall.

15, 0x0000006F: Session 3 _ Initialization-Failed.

◆ Error analysis: This error usually occurs when Windows starts, which is usually caused by driver failure or system file damage.

Yes

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

16, 0x00000076: The process has locked the page.

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

◇ Solution:

Step 1: Click Start-