jcgriff2 Co-Founder / AdminBSOD Instructor/ExpertMicrosoft MVP (Ret.) Staff member Joined Feb 19, 2012 Posts 21,541 Location New Jersey Shore May 31, 2015 #1 Pranav mentioned this file in a post and I felt the immediate need to comment because I did not know of its existence for several months after first learning Windbg several years ago. Error - BleepingComputer.com There is a help file that comes with Windbg (located in the same directory) called debugger.chm. It is probably one of the most underused and mostly unknown sources of information for Windbg itself as well as BSOD information in general. It contains every Windbg command and every bugcheck (STOP ERROR) - or at least those know at the time of publication. To look up a bugcheck - bring up debugger.chm, click on "Search" and enter the bugcheck - full or abbreviated. Example: 0x0000000a can be entered as 0xa -- leading zeroes are not required. Last edited: Jun 9, 2015
Pranav mentioned this file in a post and I felt the immediate need to comment because I did not know of its existence for several months after first learning Windbg several years ago. Error - BleepingComputer.com There is a help file that comes with Windbg (located in the same directory) called debugger.chm. It is probably one of the most underused and mostly unknown sources of information for Windbg itself as well as BSOD information in general. It contains every Windbg command and every bugcheck (STOP ERROR) - or at least those know at the time of publication. To look up a bugcheck - bring up debugger.chm, click on "Search" and enter the bugcheck - full or abbreviated. Example: 0x0000000a can be entered as 0xa -- leading zeroes are not required.
blueelvis BSOD Kernel Dump Senior Analyst Joined Apr 14, 2014 Posts 970 Location India Jun 9, 2015 #2 The manual is written in a really lucid manner. Plus it is very interesting to keep on reading... -Pranav
The manual is written in a really lucid manner. Plus it is very interesting to keep on reading... -Pranav