Ananlyzing Blue screen of Death using Windbg tool

By -
Here I am going to show you how to analyze the minidump file to identify the cause of BSOD which  happend in my laptop. The minidump file will be located in C:\Windows\minidump\ where we can find the dump file in date month year time format. eg:150513-22994-01.dmp.

You have to download the Windbg tool from the below link to analyze the minidump file.
http://msdn.microsoft.com/en-US/windows/hardware/gg463009/

After installation of the Windbg tool, you have to configure the sysmbol path before analayzing the dump file. You can set the sysmbol path by going to File menu, Select Symbol file path and add the below line

SRV*c:\localsymbols*http://msdl.microsoft.com/download/symbols


Now your Windbg tool is ready for analyzing the dump file. You can open the dump file by clicking on File menu and then open crashdump. Then enetr the command !analyze -v in the console as shown in the below figure.



After executing the command you can see a lot of information.  If you scrol dwn, you can see the stack memory information during the time of crash. In the below figure you can see that the psfilenc, nt, hal are present in the stack during crash. nt and hal are microsoft drivers and it probably may not be the cause for the crash. We can suspect on psfilenc driver which belongs to Pointsec Encryption software installed in my laptop.


If you scroll down again you can get the diver file information psfilenc.sys.


I have resolved the problem by uninstalling the Pointsec Encryption software and reinstalling it back. Then after I never faced BSOD.

Comments

Post a Comment

Popular posts from this blog

Boot configuration Data Store --BCDEdit /set

By -
The  BCDEdit /set  command sets a boot entry option value in the Windows boot configuration data store (BCD). Use the  BCDEdit /set  command to configure specific boot entry elements, such as kernel debugger settings, data execution protection (DEP) and processor address extension (PAE) options, and to load alternate hardware abstraction layer (HAL) and kernel files. You can use these boot entry options when you are testing and debugging your driver for Windows Vista, Windows 7, and later versions of Windows. bcdedit /set [{ID}] datatype value Parameters [ { ID }] The  { ID }  is the GUID that is associated with the boot entry. If you do not specify an  { ID } , the command modifies the current operating system boot entry. If a boot entry is specified, the GUID associated with the boot entry must be enclosed in braces  { } . To view the GUID identifiers for all of the active boot entries, use the  bcdedit /enum  command. datatype value The fol
Read more

ADSI Edit

By -
Image
ADSI Edit (adsiedit.msc) Updated: March 19, 2010 Applies To: Windows SBS 2008, Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2 Active Directory® Service Interfaces Editor (ADSI Edit) is a Lightweight Directory Access Protocol (LDAP) editor that you can use to manage objects and attributes in Active Directory. ADSI Edit (adsiedit.msc) provides a view of every object and attribute in an Active Directory forest. You can use ADSI Edit to query, view, and edit attributes that are not exposed through other Active Directory Microsoft Management Console (MMC) snap-ins: Active Directory Users and Computers, Active Directory Sites and Services, Active Directory Domains and Trusts, and Active Directory Schema. This topic includes the following sections: Installing ADSI Edit Using ADSI Edit
Read more

Userenv logging (User Environment logging)

By -
When you enable userenv logging, you can perform debug logging of the user profile and the system policy processes. Userenv log files also contain information about the status of each Group Policy extension, such as Application Deployment, Security, and Folder Redirection. Userenv log files reveal what is occurring in the background as a user logs on   Userenv.log file located in the %SystemRoot%\Debug\UserMode folder Userenv log files contains information about the following: Group Policy settings that are not processed or not applied as expected Folder redirection that does not occur Profile or registry hive load, unload, or deletion failures Logon script, or script not applied as expected Default behaviors occurring because a slow link was detected Roaming profile issues Slow logon issues Whether a given GPO is accessible, and if not, why access was denied. The name of the domain controller that is accessing SYSVOL. The Userenv log has a maximum size of 1 megabyt
Read more