The following are some typical causes and solutions of blue screen failure.
I. 0X0000000A
This blue screen code has nothing to do with hardware, but is caused by the conflict between driver and software. This code was first discovered because the USB keyboard of Dell machine conflicts with the keyboard encryption program of QQ2007. IBM T-series notebooks have also experienced driver errors.
If your machine has a blue screen and uses this code every time, please think about whether you have updated any software or drivers recently, and then uninstall it and have a look. It can be solved under normal circumstances. If you really can't remember it, and it is very frequent, then there is no way to do it again.
Second, 0X0000007B.
This code has something to do with the hard disk, but don't be afraid, it's not a bad track, it's a hard disk setup problem or a boot partition error caused by a virus.
If this problem occurs when you install the system with the original system disk, your machine configuration is still relatively new. As an old system disk, you don't recognize such a new hard disk interface. You have to enter the BIOS and change the hard disk mode to IDE compatible mode. Of course, people now use the ghost version of the operating system, and the relatively new ghost disk does not have this problem.
If your operating system has been used for some time, and this problem suddenly appears one day, then I'm sorry, it's caused by a virus. Press F8 when turning on the machine to select the correct configuration for the last time. If the normal mode cannot be restored, please do the system again.
Third, 0x0000000 ed.
This fault is related to the hard disk, the system probability is relatively high, and the probability that the hard disk is really bad is relatively small. I can't come up with more than 20 blue screen machines for this code, only one of which is really bad on the hard disk. The rest is the volume problem, which can be fixed. 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 bring the console to repair in the pe startup interface of Goldfinger V6). What is said here is that by using the system disk, put the system disk into the CD-ROM drive, boot to the installation interface, and select R to enter the console for repair. After entering the console, a prompt C will appear: \ You can enter chkdsk -r here, and it will automatically detect and fix the problem. After the repair is completed, restart the computer and enter the system. After entering the system, it is best to kill virus first and then restart. If it's normal, it's fine. If this code is still issued, it means that there is something wrong with the hard disk and it needs to be replaced, or the problematic place is partitioned separately as a hidden partition, and the system is installed in the back space.
Four. 0X0000007E and 0x000008e
These two codes are mostly caused by viruses, and antivirus is enough. If you can't enter normal mode, you can start the machine and press F8 to enter safe mode. Of course, it may also be caused by memory, so you can try to plug and unplug the memory again. Generally, the memory damage probability of this code is not great.
Verb (abbreviation of verb) 0X00000050
Hardware failure, hard disk is very likely. If this code is printed every time, first change the hard disk to see if the machine can start normally. If the hard disk is ok, try the memory again. If the memory has been tried, change the CPU. In short, this must be a hardware failure.
Six, coooo2 1a
The fault at the beginning of C, which reports a fantastic fault and an unknown hardware fault, but most of the code at the beginning of C has nothing to do with hardware. Basically just some drivers that start at the same time as the system! Or service problems, for example, once I replaced the F disk of a notebook with the E disk, and found this C code when I restarted. Finally, I found that plugging a USB flash drive can start normally, because there is an F drive in the USB flash drive system, and then I found a hidden file, which was written by the system when I started. I unplugged this USB flash drive, and the problem appeared again. Later, I changed the E disk back to the F disk, and there was no problem. I thought all the software started by the system was left in the F disk and some files. I built it myself without it, but even the F disk is gone, so I can only report an error, which can be compared with this blue screen.
Seven, the blue screen code is different every time.
This kind of problems are basically caused by hardware, especially taking memory as the first suspect. The second possibility is that CPU doesn't like bad, but I have encountered two since 2006. Other hardware basically won't cause the blue screen code to be changed casually.
Eight, occasionally blue screen, code flashing restart.
There are two possibilities.
1. Take XP as an example. Right-click my computer, select Properties, find the Advanced tab, find the following startup and troubleshooting items, and then click Settings. In the pop-up window, I found that there are three options in the middle of' system failure'. The third option will automatically restart, and the check of this item will be cancelled. If there is any problem in the future, the blue screen will stop.
2. All the above settings have been made, but it will be restarted instantly, which 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, the blue screen can't see the situation that the code flashes past and then restarts itself. At this time, the first step cannot be set in the system. You need to press F8 when the machine starts, and choose to disable restart after the startup fails. After the startup fails, the system will stop at the blue screen code, so that everyone can see the problem according to the blue screen code.
Nine, other blue screen code
Refer to item 7. Generally, the system is confirmed first to see if there is a system problem, and then the hardware is tested in the following order: memory is the most likely, then CPU, then hard disk, and finally graphics card. There will be basically no blue screen on the motherboard.