Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD Commands - WinDbg


BSOD Commands - WinDbg

Command and Extensions for WinDbg
Published by x BlueRobot
23 Oct 2012
Published by

Commands and Extensions for WinDbg

!analyze

Performs analysis of the dump file, and displays information about the current exception or bugcheck.

Parameters for !analyse extension:

-v Displays verbose output of the analysis.

!analyze -v

-f Performs a fast and very brief analysis of the dump file.

!analyze -f

-show [bugcheckcode] Displays information about the specified bug check code.

!analyze -show

!cpuid

Displays information about the processors within the system.

Parameters for !cpuid extension:

[Processor] Specifies the processor whose information will be displayed; will give information specific to that processor.

!cpuid [Processor]

!sysinfo

Displays system information, such as the ACPI, CPU information and BIOS.

Parameters for !sysinfo:

cpuinfo Displays information about the processor.

cpuspeed Displays the maximum and current processor speeds.

machineid Displays information about the system, such as: SMBIOS, BIOS, firmware, system and baseboard.

smbios Displays the SMBIOS table, and provides information about the system (Memory, BIOS and CPU).

lm (Load Listed Modules)

Displays information about the listed modules.

Parameters for lm command:

e Lists modules which have symbol problems, and displays the 3rd party drivers.

n t Lists modules with a name and time; symbol information is not included.

lm n t [Module Name] The module name is usually the driver without the file extension.

f Lists the modules full image path.

i [Module Name] Gives detailed information about a specific module.

lmi [Module Name]

v Lists the modules verbose, and displays information which includes: symbol file name; image file name; checksum information; version information; date stamps; time stamps and information regarding if the module is managed code (CLR).

lmv [Module Name]

.hh

Displays help for WinDbg.

.time

Displays the time of dump generation.

More Commands and Extensions (WinDbg)

1) Open WinDbg program and go to Help and then Contents.

-capture.jpg

2) Expand Debugger Reference, and then expand the Debugger Commands.

Name:  Capture#2.JPG
Views: 1465
Size:  90.8 KB

3) Expand General Extension Commands and Kernel-Mode Extension Commands, and then click which command/extension you would like to view for detailed information about that extension/command.

-capture-3.jpg

Hope this helps,

Harry





23 Oct 2012   #1
Arc

Microsoft Community Contributor Award Recipient

Microsoft Windows 10 Pro Technical Preview 64-bit 9926 Multiprocessor Free
 
 

Well done, Harry! It will be helpful, for sure.


My System SpecsSystem Spec
23 Oct 2012   #2
x BlueRobot

 

Quote   Quote: Originally Posted by Arc View Post
Well done, Harry! It will be helpful, for sure.
Thanks Arc, I just edited a few lines due to formatting mistakes and some spelling

Hope the tutorial helps people with some of the debugging commands (:
My System SpecsSystem Spec
Comment

 BSOD Commands - WinDbg




Tutorial Tools





Similar help and support threads
Windows 7 Tutorial Category
WinDBG - Install and Configure for BSOD Analysis
How to Install and Configure WinDBG for BSOD Analysis WinDBG (Windows DeBuGger) is a Microsoft software tool that is needed to load and analyse the .dmp files that are created when a system BSOD's. The latest version of WinDBG allows debugging of Windows 10.x, Windows 8.x, Windows 7 and...
Tutorials
BSOD, Windows 7 New Install - WinDbg says ntoskrnl.exe
Hi, I have had a BSOD twice now over the last 2 days. Both times analysis of minidump file says that probable cause is ntoskrnl.exe. I have run your diagnostic tool and have attached the output. Any help here would be much appreciated. I am sure the attached files give you the...
BSOD Help and Support
BSOD. Windbg indicates Csrss.exe. F4 Code. Can't Figure it out.
Hi all. This is my first post here, so I'll try and make it a good one. I've built my first Enthusiast PC (detailed specs are in my profile) and have had only 1 issue. I've been getting a random BSOD since day 1 of uptime. I've used Windbg, Whocrashed, Memtest, Intelburn Test, Chkdsk /f...
BSOD Help and Support
WinDBG vs BSOD exe
I'm slightly familiar with the BSOD_Windows7_....exe provided on this forum, but I also see reference to the Microsoft-provided WinDBG and would like to understand their purposes. The BSOD thing seems to be mostly a data collection tool, but doesn't have much built in debugging. Is that correct,...
BSOD Help and Support
BSOD WinDbg info
Hello- I have been receiving a BSOD while away from my computer. I downloaded WinDbg to analyze the information but I am unsure of what it is telling me. First I would like to make sure: Is it safe (meaning- no personal info, location info) to copy and paste the information in a thread and ask...
BSOD Help and Support
windbg help for BSOD
Good evening, I have recently been having BSOD issues while playing a game of mine that has been frustrating. Because of this I am trying to learn more about the dmp files and how to read them. From what I see in windbg it keeps saying that the probable cause is ntkrnlmp.exe ( nt! ??...
BSOD Help and Support

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:03.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App