130 likes | 302 Views
How to Use Ms Debugger to Resolve Blue Screen Errors. Prepared By : Joeffrey Palatino of Team DOC All Stars. Overview.
E N D
How to Use Ms Debugger to ResolveBlue Screen Errors Prepared By : Joeffrey Palatino of Team DOC All Stars
Overview • Windows Debugger is used to analyze crash and memory dump file whenever blue screen error happens. When blue screen errors occur it usually displays a STOP message identified by an 8-digit hexadecimal number such as STOP 0x00000050. When a stop message occurs it also creates a Memory.dmp file which will serve as a log to diagnose the cause of the blue screen and is more accurate than searching the STOP error code in Google.
What to do if there is no Memory.dmp file saved in the computer? • If the customer is getting always getting blue screen errors and you cant search for the dump file make sure the option to save it is enabled (which is usually enabled) by checking these steps: • 1.Right-click on My Computer • 2.Select Properties • 3.Select Advanced • 4.In the Start up and Recovery section, select Settings: this displays the Start up and Recovery dialog box • 5.In the Write debugging information selection make sure it is set to Kernel memory dump and the Dump file location is set to %SystemRoot%\MEMORY.DMP
Where to download? Download and Install Ms Debugger 32 bit version 6.10.3.233 in http://tinyurl.com/628335 (Good for XP and Vista)
How to Launch Windows Debugger • Go to Start - Programs - Debugging Tools for Windows (x86) and choose WinDbg
Specifying the Symbol Path to obtain the symbol files in Microsoft’s website • Click File - Choose Symbol File Path and paste "srv*c:\symbols*http://msdl.microsoft.com/download/symbols" in the box and click Ok to install the WinDbg • *Needs Internet Connection*
How to open crash dump • To open crash dump file select File - Open Crash Dump - browse to C:\Windows\Minidump and choose the minidump file
Browse to C:\Windows\Minidump and choose a dumpfile and choose ‘Open’
Wait for the message that says "Debuggee not connected" to disappear and for the message that says Bugcheck Analysis and then type "!analyze –v“ and press enter. Wait again for the Debuggee not connected to disappear and check for the “Image Name” or “Probably caused by”. Search the name of the file in Google to determine if what application or driver caused the problem
Exercise • Go to www.docallstars1.wikispaces.com and go to the exercises page. • Download the 4 minidumps as well as the windows debugger tool and analyze the cause of the blue screen errors.