The following content is a personal summary of Baidu Knows Ctangel. It is not a copy of the Internet. It is all encountered in personal daily work and the reasons are clearly determined. If you need to copy, please indicate the source.
Here are some typical causes and solutions of blue screen failures.
1. 0X0000000A
If this blue screen code generally has nothing to do with the hardware, it is caused by a conflict between the driver and the software. This code was first discovered because of the USB keyboard of the company's DELL machine and This problem was discovered due to a conflict with the keyboard encryption program of QQ2007. Driver installation errors have also occurred on IBM T series notebooks.
If your machine has a blue screen and this code appears every time, please think about whether any software or drivers have been updated recently, uninstall it and take a look again. Under normal circumstances, it can be solved. If you really can't remember it and it happens very frequently, then you have no choice but to redo the system.
If this code not only appears, but also 8E, 7E, 50, D1, 24 and other codes will appear after restarting and blue screen, then you must first consider memory damage
2. 0X0000007B
p>This code is related to the hard disk, but don’t be afraid. It’s not bad sectors, it’s a setting problem or a hard disk boot partition error caused by a virus.
If this problem occurs when you use the original system disk to install the system, it means that your machine configuration is still relatively new. As an old system disk, it does not recognize such a new hard disk interface, so you have to enter The BIOS changes the hard disk mode to IDE compatibility mode. Of course, people now use the ghost version of the operating system, and relatively new ghost disks do not have this problem. Regarding the problem that people can't find the IDE item, because many motherboards mark this item with different wordings, some say AHCI and Compatibility. AHCI is equivalent to SATA mode, and Compatibility is equivalent to IDE mode.
If your operating system has been used for a period of time and suddenly this problem occurs one day, then I'm sorry, it is caused by a virus. Press F8 on boot and select the last known correct configuration. If you cannot restore to normal mode. Then please redo the system.
3. 0X000000ED
This fault is related to the hard disk. The system probability is relatively high, but the probability of the hard disk being really bad is relatively small. I have had no fewer than twenty blue screen machines with this code, and only one of them had bad sectors on the hard disk. The rest are all problems and can be repaired. This is also one of the few blue screen codes that can be repaired.
The repair method is to find the original system installation disk (or the PE startup interface of Goldfinger V6 has a console to repair it). Here is the method of using the system disk. Put the system disk into the CD-ROM drive, boot to the installation interface, select and press R to enter the console for repair. After entering the console, the prompt C:\ will appear. Enter chkdsk -r here and it will The problem has been automatically detected and repaired. After the repair is completed, restart the computer and you can enter the system. After entering the system, it is best to kill the virus first and then restart it to try. If it is normal, then there is no problem. If this code still appears, That means there is something wrong with the hard disk and needs to be replaced, or the problematic area needs to be partitioned separately to make it a hidden partition, and the space behind it can be used to install the system.
4. 0X0000007E, 0X0000008E
These two codes are mostly caused by viruses and can only be disinfected. If you can't enter normal mode, you can boot into safe mode by pressing F8. Of course, it may also be caused by the memory. You can try to re-plug and unplug the memory. Generally, the probability of memory damage in this code is low.
5. 0X00000050
Hardware failure, the hard disk is very likely. If the 50 restart is accompanied by codes like 0A, 7E, and 8E, then in all likelihood the memory is broken. If this code appears every time, first change a hard disk and test whether the machine can start normally. If the hard disk is ok, try the memory again. If the memory has also been tried, change the CPU. In short, this must be a hardware failure.
6. 0X000000D1
This code is generally related to the graphics card. It may be that the graphics card is damaged, or it may just be caused by the installation of an incompatible graphics card driver. It is recommended to cause screen distortion. First, ask a friend to borrow a graphics card and plug it in to try it out. Or if the host has an integrated graphics card, use the integrated graphics card to try it out. If there is no blurry screen phenomenon, try changing the graphics card driver that comes with the machine when you buy it.
7. coooo21a
The error reported by the fault starting with C is very strange, reporting an unknown hardware fault, but the code starting with C is mostly irrelevant to the hardware. Basically, they are some drivers that are started at the same time as the system! Or there is a service problem. For example, once I changed the F drive of a laptop to the E drive. As a result, when I started it again, codes starting with C appeared. Finally, I found that plugging in a U disk can start normally. There is an F drive in the USB flash drive system, and then I found hidden files, which were written by the system when booting up. The problem reappeared when I unplugged the U disk. Later, I changed the E disk back to F and the problem disappeared. I think some software that was started together with the system left some files on the F disk. Without it, it would build itself, but the connection failed. The F drive is gone, so we can only report an error, so you can compare it when you see this kind of blue screen.
8. The blue screen code is different every time
This kind of problem is basically caused by the hardware, especially the memory as the first object to be suspected. Try replacing the memory. , the second possibility is that although the CPU does not like to break down, I have encountered two of them from 2006 to now. Other hardware basically does not cause the blue screen code to change at will.
9. Occasionally blue screen, and the problem of code flashing and restarting
There are two possibilities for this
1. Taking XP as an example, Right-click on My Computer and select Properties, find the Advanced tab, find the Startup and Fault Repair item below, and click Settings. In the pop-up window, find three options in the middle of 'System Failure'. The third option is to automatically restart. If you uncheck this option, the blue screen will stop if there is a problem in the future.
2. You have made the above settings, but it still restarts in a flash. It is caused by overheating of the graphics card or CPU. Open the chassis and check the status of the cooling fan and radiator.
In addition, when booting up, the blue screen cannot be seen and the code flashes past and then restarts by itself. At this time, it is no longer possible to perform the first step of settings in the system. Then you must press F8 when the machine starts, and select Disable restart after startup fails. After selecting, if the startup fails, the system will stop at the blue screen code. There, you can follow the blue screen code to check the problem.
10. Other blue screen codes
Refer to item 7. Generally, first do the system to confirm whether it is a system problem, and then test the hardware in the following order. First, the memory is most likely, and then It's the CPU, then the hard drive, and finally the graphics card. The motherboard will basically not have a blue screen.