A Blue Screen mistake occurs on Windows organisation after a organisation crash. The bluish covert pops upwards unexpectedly forcing you lot to restart the organisation inwards the middle of your work. The mistake is an unpremeditated sign together with is quite frustrating when you lot notice it difficult to debug the problem. Fortunately, at that topographic point are many handy tools similar the Windows Debugger Tool (Windbg) which allows you lot to read the mistake written report for troubleshooting together with solve the BSOD error.
Causes of BSOD error
The BSOD mistake is displayed when your operating organisation reaches a threshold restrict where the organisation is vulnerable together with tin no longer component safely. BSOD normally occurs because of several reasons similar faulty drivers, corrupted windows registries, overheating, misconfigured device drivers, corrupted files, outdated driver, overclocking, bad software together with other organisation hardware issues.
Fixing BSOD error
The Blue Screen mistake also called every bit Stop Error causes your Windows organisation to halt completely together with you lot may bring to reboot the organisation to proceed to operate.
However, earlier the reboot, it is recommended that the users brand a banking concern annotation of the mistake code displayed on the bluish screen. That beingness said, the BSOD mistake pops upwards generally when your organisation is unable to recover the kernel-level error. The mistake message normally displays a whole charge of crash information amongst driver information associated amongst the mistake together with other information amongst their possible fixes.
When the organisation crashes, the Windows creates minidump files together with all the retention information amongst the mistake details is dumped to a difficult drive for hereafter debugging. There are many handy tools similar Bluescreen persuasion together with Windbg that allows you lot to read the minidump files for troubleshooting. You tin job Bluescreen persuasion to chop-chop together with easily analyze the error. For to a greater extent than advanced research, you lot tin job Windbg to solve the BSOD issue.
What is Windows Debugger Tool (Windbg)
WinDbg also called every bit Windows debugging tool is a multipurpose debugger that automatically scans all the minidump files which were created after the BSOD crash. The tool is used for to a greater extent than advanced analysis for a tricky mistake together with is available to download for costless every bit component of the Windows 10 SDK. For every crash occurance, the debugging tool gives details nearly the driver that was loaded during the crash, together with other advanced crash information to diagnose the origin drive of the bluish covert mistake together with eventually aids to figure out the problematic drivers. In this article, nosotros explicate how to job the Windows debugging tool (WinDbg) to read the crash report.
How to job Windbg
Installing Windbg
Download the standalone Windows 10 SDK here.
Run the installer together with direct the default installation path.
Accept the license together with select the characteristic Debugging tools for Windows to install the debugger.
Click on the Install button.
Using Windbg to debug a Blue Screen error
Go to Start together with type WinDbg (x86).
Right click on WinDbg tool together with select Run every bit administrator.
Go to File together with click on Open Crash Dump from the menu.
Navigate to the path C:\Windows\Minidump together with click Minidump folder.
In the Minidump folder, click the dmp file you lot desire to open.
WinDbg volition right away analyze the file together with Wait till the Debuggee non connected disappears at the bottom of the window.
Click on !analyze -v inwards the ascendance prompt together with hold back till the analyze is complete.
To become to a greater extent than driver information, locate the MODULE_NAME from the analysis results together with click on driver link.
Once you lot position the problematic driver, you lot tin direct to either update or reinstall the problematic driver from the manufacturer’s spider web page inwards lodge the cook the problem.
Hope this helps!
PS: John Carrona Sr adds: You’ll become symbol errors if you lot don’t laid a valid symbol path. The easiest method is to click on File…Symbol File Path together with enter:
srv*c:\symbols*https://msdl.microsoft.com/download/symbols
This has to live on done each fourth dimension you lot opened upwards WinDbg – unless you lot salve the Workspace for later on use.
Example of errors that you lot become when non using symbols is here: https://stackoverflow.com/questions/30019889/how-to-set-up-symbols-in-windbg.
Source: https://www.thewindowsclub.com/
comment 0 Comments
more_vert