Recently my Windows XP system often unexpected blue screen, originally wanted to reinstall the system, but because of the need to reinstall the software too much, so determined to find out the specific reasons for the blue screen, after some efforts, Finally found a good blue screen fault solution, and share it with everyone below. First, do a few noun explanations before explaining, so that everyone can understand this article: Step 1: Open “small memory dump" function right click “my computer”, select “properties → advanced → And failback & rarr; set & rdquo;, open the "start and fail recovery" tab, in the "write debug information" drop-down list, select the "small memory dump (64KB)" option, as shown in Figure 1. . Tip: Small memory dump Memory dump is used to save the data dump in memory in the dump file when the system crashes, and to provide relevant personnel for troubleshooting analysis. A small memory dump is a memory dump file that only stores 64KB of basic spatial data before the memory. This saves disk space and makes it easy to view files. After selecting it, click “OK”, so that the next time the operating system appears blue screen, it will record the data in the memory at that time, and store it as a dump file, which is stored in the minidump folder of the system disk. Tip: Dump files Dump files are used to debug driver drivers for drivers. Such files must be opened with special tools, such as WinDbg. The second step: download and install WinDbg from Microsoft's website. WinDbg is an excellent source-level debugging tool released by Microsoft. It can debug Dump files. Here we use to find the cause of blue screen failure. The download address is: http://www. Microsoft.com/whdc/devtools/debugging/installx86.mspx. This process will not go into details. When installing, all the way to “ next step & rdquo; on the line. Step 3: Use WinDbg to diagnose blue screen error After the system restarts with blue screen, a .dmp file with the date as the file name will appear in the minidump folder. This is the file we want to analyze. Then click “ Start Menu & Rarr; Programs & Rarr; Debugging tools for windows (x86) - WinDbg & rdquo;, open the WinDbg program, click on the program window "File → Open Crash Dump", open the minidump folder located in the system disk A .dmp file with a date as a file name. After opening, the program will automatically analyze the file. After the analysis, look at the bottom and find the line “Probably caused by”, the file behind it is the culprit causing the blue screen. The fourth step: solve the blue screen failure. We searched the file name that caused the blue screen on the Internet. Basically, we know what the file is. Generally, there are related solutions on the Internet. See what plug-ins, patches, or reinstall software. and many more. For example, the 360antiarp.sys file analyzed in this Chinese is checked online and found to be the 360 security guard's ARP firewall driver. This file will cause a blue screen on the computer because it conflicts with some drivers of this machine. Uninstalling the 360 security guard's ARP firewall, the blue screen problem is solved. After editing: This article can only help you find the culprit that causes blue screen failure. The specific solution has to be found online. The cause of the failure may be that the .sys file may also be a .dll file. If the failure is caused by an unseen .sys file or a .dll file, you should be careful. These files may be viruses, preferably in safe mode. Try it out under the full antivirus!