My computer always has a blue screen with two codes, one is 0x000000D 1 and the other is 0x0000000A. Can someone teach me how to fix it?

┌—┐

│ 1│

└—┘0x0000000a:irql_not_less_or_equal

◆ 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│

└—┘0x000000 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.

Due to an error in the NTFS.sys file (the purpose of this driver file is to allow the system to read and write disks using the NTFS file system), these two blue screens.

This error is probably caused by the physical damage of the disk itself or the damage of the interrupt request packet (IRP). Other reasons include: hard disk magnetism.

Too many 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: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_compliete_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.

/some software of this company will appear from time to time, and the culprit is the Falstaff.sys file. (the author is difficult.

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

┌—┐

│ 1 1│

└—┘0x00000050:page_fault_in_nonpaged+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│

└—┘0x00000058:ftdisk_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│

└—┘0x0000005e: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 the hardware 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:session3_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:process_has_locked_pages

◆ 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-> Run: regedt32 and find [hklm \ system \ currentcontrolset \ control \ session.

Manager\memory management], and create a new double-byte value "TrackLockedPages" on the right with the value of 1. This will cause Windows to make an error.

When the error reappears, track which driver problem.

Step 2: If the blue screen appears 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 a problem-driven name and will be updated or deleted later.

Step 3: Enter the registry and delete the added "TrackLockedPages".

┌—┐

│ 17│

└—┘0x00000077:kernel_stack_inpage_error

Error analysis: it means that the required kernel data cannot be found in virtual memory or physical memory. This error is usually caused by a disk.

There is a problem, the corresponding data is destroyed or eroded by the virus.

◇ Solution: Scan the system with antivirus software; Use the "chkdsk /r" command to check and repair disk errors. If it fails, please use this disk.

Check and repair the tools provided by the manufacturer.

┌—┐

│ 18│

└—┘0x0000007a:kernel_data_inpage_error

Error analysis: This kind of error is often caused by the fact that the kernel data in virtual memory cannot be read into memory. The reason may be virtual memory pages.

There are bad clusters, viruses, disk controller errors and memory problems in the file.

Solution: First, use anti-virus software upgraded to the latest virus database to kill viruses. If there is no information, there is 0xC000009C or

0xC0000 16A code, then it is caused by a bad cluster, and the system's disk detection tool cannot automatically repair it. At this time, you need to enter "fault recovery"

Console ",use the" chkdsk /r "command for manual repair.

┌—┐

│ 19│

└—┘0x0000007b:inacessible_boot_device

◆ Error analysis: Windows can't access the system partition or the boot volume during the boot process, which usually happens at the first boot after replacing the motherboard.

, mainly because the new motherboard and the IDE controller of the old motherboard use different chipsets. Sometimes it may be caused by virus or hard disk damage.

Up.

◇ Solution: Generally, just start the computer with the installation CD, and then repair and install it to solve the problem. For viruses, you can use DOS.

Version of antivirus software for killing (main battle with kv2005DOS version download). If there is something wrong with the hard disk itself, please install it on another computer.

Then use "chkdsk /r" to check and repair disk errors.

┌—┐

│20│

└—┘0x0000007e:system_thread_exception_not_handled

◆ Error analysis: The system process generates an error, but the Windows error handler cannot catch it. There are many reasons, including: hardware compatibility.

Sex, faulty drivers or system services, or some software.

◇ Solution: Please use Event Viewer to get more information and find out the root cause of the error. (It doesn't seem to be the way to find it. Look.

Come on, let's all be self-reliant! )

┌—┐

│2 1│

└—┘0x0000007f:unexpected_kernel_moed_trap

Error analysis: Generally, it is caused by the failure of hardware (such as memory) or some software. Sometimes overclocking can also produce this error.

Solution: Check the memory with test software (such as Memtest86). If overclocking occurs, please cancel overclocking. Insert PCI hardware.

Unplug from the motherboard slot or replace the slot. In addition, some motherboards (such as nForce2 motherboards) will overheat after overclocking.

Lead to blue screen, at this time, adding an independent heat sink for the chip can often effectively solve the problem.

┌—┐

│22│

└—┘0x00000080:nmi_hardware_failure

Error analysis: generally caused by hardware. (It seems that the blue screen is inextricably linked with hardware errors. )

◇ Solution: If new hardware has been installed recently, please remove it, and then try to replace the slot and install the latest driver. if

The driver has been upgraded, please restore the original version; Check whether the memory golden finger is polluted or damaged; Scan for viruses; Run chkdsk

/r "Check and repair disk errors; Check that all hardware cards are plugged in. If all the above attempts fail, you'll have to find a professional computer repairer.

The company asked for help.

┌—┐

│23│

└—┘0x0000008e:kernel_mode_exception_not_handled

Error analysis: kernel-level applications have errors, but Windows error handlers have not caught them. This is usually a hardware compatibility error.

◇ Solution: Upgrade driver or BIOS.

┌—┐

│24│

└—┘0x0000009c:machine_check_exception

Error analysis: usually caused by hardware. Generally, it is due to overclocking or hardware problems (memory, CPU, bus, power supply).

◇ Solution: If overclocking, please reduce the original frequency of CPU and check the hardware.

┌—┐

│25│

└—┘0x0000009friver_power_state_failure

◆ Error analysis: It is often related to the power supply, and it often happens in the operation related to the power supply, such as shutdown, standby or sleep shutdown.

◇ Solution: reinstall the system. If it cannot 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, a prompt "If you press F6" will appear when installing Windows 2K/XP.

Need to install a third-party SCSI or RAID driver ",press F7 and Windows will automatically ban it.

Install ACPI Hal and install standard PC Hal.

┌—┐

│27│

└—┘0x000000b4:video_driver_init_failure

Error analysis: This stop message indicates that Windows can't enter the graphical interface because it can't start the graphics driver. Usually a graphics card.

Or the graphics card has hardware conflict (for example, parallel port or serial port conflict).

◇ Solution: Enter the safe mode to see if the problem is solved. If so, please upgrade the latest graphics driver. If not,

It is likely that there is a conflict between the graphics card and the parallel port. You need to press WIN+break in safe mode to open "System Properties". In hardware->;

Locate and double-click the project connecting the printed LPT 1 port in the device manager, deselect "Use automatic configuration" in the Resources tab, and then

Change "03BC" of Input/Output Range to "0378".

┌—┐

│28│

└—┘0x000000be:attempted_write_to_readonly_memory

Error analysis: The driver tried to write data into read-only memory. Usually, new drivers and system servers are installed.

After upgrading the firmware program of the device.

Solution: If the error message contains the name of the driver or service file, please install the newly installed driver according to this information.

The program or software is uninstalled or disabled.

┌—┐

│29│

└—┘0x000000C2:BAD_POOL_CALLER

Error analysis: A process or driver in the kernel layer mistakenly tries to enter the memory operation. Usually there is a bug in the driver or software.

Caused by a piece.

◇ Solution: Please refer to the related items of the conventional solution mentioned above for elimination.

┌—┐

│30│

└—┘0x000000ceriver_unloaded_without_cancelling_pending_operations

Error analysis: It is usually caused by the wrong driver or system service.

◇ Solution: Please refer to the related items of the conventional solution mentioned above for elimination.

┌—┐

│3 1│

└—┘0x000000d 1river_irql_not_less_or_equal

◆ Error analysis: It is usually caused by a faulty driver (for example, Logitech MouseWare 9. 10 and Logitech mouse 9.24).

The driver will cause this failure). At the same time, defective memory, damaged virtual memory files, some software (such as multimedia software,

Antivirus software, backup software, DVD player software, etc. Will also lead to this error.

◇ Solution: Check the latest installed or upgraded drivers (if a file name similar to "acpi.sys" appears in the blue screen, you can be very willing.

Timing driver problems) and software; Test whether there is a problem with the memory; Go to the Recovery Console and go to the virtual memory paging file.

Pagefile.sys partition, execute the "del pagefile.sys" command to delete the page file; Then execute it in the partition where the page file is located.

"chkdsk /r" command; Reset 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 (such as online games and BT downloads),

Then it should be the problem of the network card driver, and its driver needs to be upgraded.

┌—┐

│32│

└—┘0x000000ea:thread_stuck_in_device_driver

◆ Error analysis: Generally, it is caused by the video card or the video card driver.

◇ Solution: Upgrade the latest graphics driver first. If not, you need to replace the graphics card to test whether the fault will occur again.

┌—┐

│33│

└—┘0x000000ed:unmountable_boot_volume

◆ Error analysis: Generally, it is caused by a disk error, and sometimes it is recommended to check whether the hard disk connection is in poor contact.

It doesn't matter if you use a cable that conforms to the hard disk transmission specification, such as ATA- 100 or ATA-33 cable, but tell the hard disk (

The requirements for supporting ATA-66 and above are strict, and the wrong connection sometimes leads to failures such as failure to boot. If it's fixed,

This error still occurs frequently, which may be a precursor to hard disk damage.

◇ Solution: In general, restarting will solve the problem. In any case, 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 has detected an interrupt storm in the system, for example, a device failed to release the occupied interrupt after completing the operation.

Usually this is caused by a defective driver.

Solution: Upgrade or uninstall the newly installed hardware driver.

┌—┐

│35│

└—┘0x00000 135:unable_to_locate_dll

Error analysis: It usually means that the file is lost 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 information. You can use the Internet or

Other computers find the corresponding files and copy them to the SYSTEM32 subfolder under the System folder. If the file name is not displayed, then

The registry is probably corrupted. Please use system restore or previous registry backup to restore.

┌—┐

│36│

└—┘0x000002 1a:status_system_process_terminated

◆ Error analysis: User mode subsystem, such as Winlogon or customer service runtime subsystem (CSRSS), has been damaged and cannot be insured.

The certificate is secure, which prevents the system from starting. Sometimes, when a system administrator mistakenly modifies the permissions of a user account, it cannot access the system text.

Files and folders.

◇ Solution: Use Last Known Good Configuration. If it fails, you can use the installation CD to repair and install it.

┌—┐

│37│

└—┘STOP 0xC000022 1 or Status _ Image _ Checksum _ Mismatch.

◆ Error analysis: Generally, it is caused by the damage of drivers or system DLL files. In general, the file name will appear in the blue screen.

.

◇ Solution:

(1) Use the Windows installation CD for repair and 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 enter the "Recovery Console" and use the copy or expand command to recover from the CD.

System or extract the damaged file. However, the blue screen is generally a driver file problem, so the expand command will use some, such as:

The blue screen prompts tdi.sys file, because the driver file is usually in the i386\driver compressed package, so use: expand %CDROM:\i386.

\ driver . cab \ f:TDI . sysc:\ win nt \ system \ drivers。 (XP is expanding% cdrom: \ i386 \ driver.cab.

\ f:TDI . sys c:\ windowns \ system \ drivers)

┌—┐

│38│

└-┘ If these blue screen shutdown codes appear at startup,

If a blue screen appears when Windows starts, and an error message of schedule 1 appears, then most of the time there is something wrong with the hardware. Please use the hard disk.

Diagnostic tools provided by the manufacturer to determine whether there is a problem with the hardware, and go to its website to check whether there is the latest BIOS or firmware update program, such as

If the hardware is ok, reinstall Windows 2K/XP. If the same problem still occurs, you can only ask professional technical support.

If you encounter an error message in Schedule 2, you can only reinstall Windows. If you can't solve the problem, I suggest you seek professional help.

Technical support.

Schedule 1:

Stop code error name

0x 3 1 PHASEO _ initialization _ FAILED

0x5C HAL _ INITIALITAION _ FAILED

0x5D heap initialization failed.

0x5E object initialization failed.

0x5F security initialization failed.

0x60 process initialization failed.

Schedule 2:

Stop code error name

0x 32 phase 1 _ Initialization _ failed.

0x 6 1 Hal 1 _ Initialization _ failed.

0x62 Object 1 _ Initialization _ failed.

0x63 Security 1 _ Initialization _ failed.

0x64 symbol initialization failed.

0x65 Memory 1 _ Initialization _ failed.

0x66 Cache initialization failed.

0x67 Configuration initialization failed.

0x68 file initialization failed.

0x 69 io 1 _ Initialization _ failed.

0x6A LPC _ INITALIZATION _ FAILED

0x6B process 1 _ initialization _ failed.

0x6C ref mon _ initialization _ FAILED

0x6D session 1 _ initialization _ failed.

0x6E Session 2 _ Initialization _ Failed.

0x6F Session 3 _ Initialize _ Failed.

0x70 Session 4 _ Initialization _ Failed

0x7 1 Session 5 _ Initialization _ Failed.