Problem solving and analyzing the Blue Screens of Death
Within this phase-by-phase guideline I teach you how to diagnose and examine the accident dump file which is the direct consequence of the famous Blue Screen of Death in just about every Windows edition from Windows 2000, Windows XP, Windows Vista and Server 2003 or 2008 to Windows 7, 8 and Windows 10 (and also Windows Server 2012, 2012 R2 and 2016 operating systems).
Once you the very least count on it your laptop or computer may well reveal to you a what are known as Blue Screen of Death (BSOD) and reboot the laptop or computer quickly. The BSOD is usually caused by a critical system problem and Windows can no longer go on operating when that take place and rather collisions. About 80 percent of security shield virus take place because of bad drivers. Components troubles such as corrupt memory components or a cracked tough drive usually also produce a BSOD once in a while.
Cease the laptop or computer from restarting quickly
The typical establishing for when an accident takes place is the fact that Windows restarts quickly, which means you are unable to read the problem meaning within the true blue screen ahead of the laptop or computer restarts. You can modify this establishing in Process > Innovative system options > Startup and recovery options and uncheck “automatically restart”. But even when you then have the opportunity to read the problem meaning on the blue screen it does not always mean that you can comprehend it and locate the main cause of the issue. That’s exactly where this informative guide is useful.
Set up the required software go get going
We are going to be working with all the Microsoft tool Windows Debugging Instruments which may be saved at no cost from Microsoft part of the Windows SDK. After setting up Windows Debugging Instruments, begin it from the Start menus, it is known as WinDbg (x86) or WinDbg (x64). To be able to get a originate from the debugging of MEMORY.DMP and locate the main cause of the issue you will want the icon data files. These may be saved as one package deal yet it is much easier to arrange Windows Debugging Instruments to download data files as necessary. To create this up, in WinDbg, head to Available and select Symbol file route. Now sort a road to a listing on the tough drive, as an example:
You can with all the earlier mentioned details no less than find out what the main cause of the accident is and many occasions the collisions occur as a result of bad drivers. Which driver is causing the accident can be obtained out by possibly the driver brand or by using your favorite search engine to lookup the file brand refer to within the analysis. As an example, nv4_disp.sys is related to Nvidia and ati2dvag.sys is related to ATI. If you find out that a certain driver is causing the accident right away check out the equipment vendor’s web site and discover when there is an up-to-date driver accessible, or even publish a bug report with all the equipment vendor or laptop or computer producer.