Blue screen
Recently my Windows XP system often accidentally blue screen, originally wanted to reload the system, but because of the need to reload the software too much, so determined to find out the specific reasons for the blue screen, after a number of efforts, finally found a very good solution to the Blues, the following and everyone to share.
First, make a few noun explanations before you explain, so that you can understand this:
The first step: Turn on the small memory dump feature
Right-click on "My Computer", select "Properties → advanced → startup and recovery → settings", open the Startup and Recovery tab, and select the "Small Memory Dump (64KB)" option in the "Write Debugging Information" Drop-down list, as shown in Figure 1.
Small knowledge: small memory dump
Memory dumps are used to store data dumps in memory in a dump file when the system crashes, and are supplied to people for error analysis. A small memory dump is a memory dump file that only holds the basic space data of 64KB before memory. This saves disk space and makes it easier to view files.
Select the point "OK", so that the next time the operating system appears in the blue screen, it will record the data in memory at that time, and stored as a dump file, the file is stored in the system disk MiniDump folder.
Little knowledge: Dump file
Dump files are used to debug drivers for driver writers, which must be opened with proprietary tool software, such as using WinDbg.
Step two: Download and install WinDbg from Microsoft's website
WinDbg is a Microsoft released a good source-level debugging tool, you can debug dump files, here we use to find the reason for the blue screen failure, download the address is: http://www.microsoft.com/whdc/devtools/debugging/ Installx86.mspx. This process is not to repeat. When installing, choose "Next" on the line.
Step three: Use WinDbg to diagnose blue screen errors
The system appears again after the blue screen reboot, in the MiniDump folder will appear with a date file name of the. dmp file, this is the file we want to analyze. Next click on the "Start menu → program →debugging tools for Windows (x86)-windbg", open the WINDBG program, click the program window "File→open Crash Dump", Open the. dmp file with the date file name located under the MiniDump folder on the system disk.
Open after the program began to automatically analyze the file, after analysis, look at the bottom, find "Probably caused by" this line, the following file is caused by blue screen culprit.
Fourth step: Solve the blue screen failure
We to cause the blue screen of this file name in the Internet search, basically know what file, general online also have related solutions to see what to remove plug-ins, what patches or reload software and so on. For example, this Chinese analysis of the 360antiarp.sys file, a search on the internet, found that it is 360 security defender of the ARP firewall driver. A computer blue screen is caused by a conflict between this file and some of the driver of this machine. The 360 security defender's ARP firewall uninstall, the blue screen problem is solved.
PostScript: This article can only help you find the culprit that led to the blue screen fault, the specific solution also have to search the Internet. The cause of the failure may be that the. sys file may also be a. dll file, and if the failure is caused by a. sys file or a. dll file that is not found, it is possible that these files may be viruses, preferably in a safe mode of overall antivirus try!