subject: Laptop Computer Blue Screen Fault Code Preliminary Analysis Share [print this page] Laptop computers when the black and white, the amount of wrong, is the time of the blue and white, white - a string of numbers and letters, is the error code, error code, can determine the reasons of the computer blue screen. However, this time shown by the blue and white short, most people remember.
In fact, windows system error every time, there will be corresponding log record, I find the log, analyze the reasons to find a blue screen can be easily handled.
Step1: Find the log, XP and Vista, the steps almost
Right My Computer - Advanced (Vista Advanced System Settings) - Startup and Recovery settings. The log of the blue screen in the Minidump folder is also possible that MEMORY.DMP file, Startup and files can be judged.
The bottom of this interface, there will be a path, if the display is: Small memory dump (64K), the corresponding path is% SystemRoot% / Minidump log of the blue screen is saved in the Minidump folder. The real address is: system tray-windows folder-Minidump folder inside.
There is a possibility, is the blue screen by the operating system data memory (including virtual memory) to be written directly to the file to generate MEMORY.DMP file, the file in the Windows directory.
Step2: find a log viewing software
Log file of the blue screen, only using specialized software to be able to view, I tried to use TXT is not enough. Recommended to use WinDbg to download Microsoft's official address: http://www.microsoft.com/whdc/devtools/debugging/default.mspx
Install Debugging Tools for Windows 32-bit Version
Install Debugging Tools for Windows 64-bit Versions
These two correspond to 32 and 64 of the system, go download the latest version can be.
Step3: View Log
Running WinDbg to-open crash dump, you can open the log file, this time you can see a blue screen log, which is a blue screen when the error code. At this time, however, can not see which program is causing the blue screen. Also need to enter WinDbg below analyze-v to remember to bring an exclamation point, then will display all the log files.
