Yes,livekd.exe opened up the kd.exe,but after this, it loaded c: windows system32 livekd.dmp, I checked the file is 0kb. Then it loaded symbols,looks the kernel symbols is ok, load the user symbols. I installed retail symbols in D. Downloaded symbol files for WinDbg.exe do not load. *** ERROR: Symbol file could not be found.
This tutorial will show you how to download, install, configure and test WinDBG in preparation for analysing BSOD's.
Dumps from C:Windows and C:WindowsMinidump cannot be opened unless you move them to another location first.
1. Download the WinDBG sdksetup.exe setup file.
2. Run
sdksetup.exe, and specify the installation location (this example uses the default location):3. Once you have accepted the licence agreement, you will be prompted to select the features to install. Select only the Debugging Tools for Windows option, as shown. Proceed with installation.
4. The debugging tools will be downloaded and installed.
If configured correctly, Windows will write information to a .dmp file when the host system BSOD's. In order to read the information within the .dmp file, it needs to be associated with WinDBG.
1. Open an elevated command prompt by right-clicking on the Windows Start Button and selecting Command Prompt (Admin).
2. Copy the highlighted text below, and paste it into the command prompt window using Ctrl+V and hit enter to change directory to the installation location path.
3. Now copy this highlighted text, paste it into the command prompt window, and hit enter to make the association.
4. This is how it looks when executed in the command prompt window.
If done correctly, a new blank instance of WinDBG will open with a confirmation box. WinDBG can now be closed.
The symbol path is the location in which WinDBG searches for symbols each time it reads a binary in the BSOD .dmp file. It is critical to get this step correct.
You can specify any location to create a cache/store of downloaded symbols, but I recommend using the default location (as used in this tutorial).
To create and set a symbol path, do the following.
1. Start a blank instance of WinDBG by going to:
2. In the WinDBG panel, go to:
What that line means is :
- Create a folder called C:SymCache
- Download new symbols from the msdl site and save them to C:SymCache
You can specify any path you like, for example SRV*E:My_Symbols*http://msdl.microsoft.com/download/symbolswill also work.
4. Save the symbol path by going to:
1. Download this small zip file.2. Open it, and double click the .dmp file.
3 WinDBG should open automatically and you should see some text appearing in the workspace. Since this is the first .dmp file being read on your system, WinDBG appears to be slow do not interrupt it. What is happening is:
- A folder called Symcache is being created on C:
- Symbols are being downloaded and saved to C:Symcache
The next time a .dmp is opened, it will be quicker since it already has some symbols. Over time the C:Symcache folder will grow in size as more symbols are added. My current Symcache folder is 1.07GB in size.
You will know the reading of the .dmp file is complete when our output looks like this. Note the breakpoint that I have highlighted in bold text red - that means the .dmp file has been completely read.
To close WinDBG go to File > Exit
You are done. WinDBG has been installed, .dmp file associations created, and symbol path correctly setup.
By Mark Russinovich and Ken JohnsonAdobe get serial number.
Published: May 16, 2017
Download LiveKd(494 KB)
Introduction
LiveKD, a utility I wrote for the CD included with Inside Windows2000, 3rd Edition, is now freely available. LiveKD allows you to runthe Kd and Windbg Microsoft kernel debuggers, which are part of theDebugging Tools for Windowspackage,locally on a live system. Execute all the debugger commands that work oncrash dump files to look deep inside the system. See the Debugging Toolsfor Windows documentation and our book for information on how to explorea system with the kernel debuggers.
While the latest versions of Windbg and Kd have a similar capability onWindows Vista and Server 2008, LiveKD enables more functionality, suchas viewing thread stacks with the !thread command, than Windbg and Kd'sown live kernel debugging facility.
Installation
First download and install the Debugging Tools for Windows package fromMicrosoft's web site:
If you install the tools to their default directory of ProgramFilesMicrosoftDebugging Tools for Windows, you can run LiveKD fromany directory; otherwise you should copy LiveKD to the directory inwhich the tools are installed.
If you haven't installed symbols for the system on which you runLiveKD, LiveKD will ask if you want it to automatically configurethe system to use Microsoft's symbol server (see the Debugging Tools forWindows documentation for information on symbol files and the Microsoftsymbol server).
NOTE: The Microsoft debugger will complain that it can't find symbolsfor LIVEKDD.SYS. This is expected, since I have not made symbols forLIVEKDD.SYS available, and does not affect the behavior of the debugger.
Using LiveKd
usage:
** liveKd [[-w] [-k <debugger>] [-o filename]] [-vsym][-m[flags] [[-mp process] [pid]]][debugger options]
liveKd [[-w] [-k <debugger>] [-o filename]] -ml[debugger options]
liveKd [[-w] [-k <debugger>] [-o filename]][[-hl] [-hv <VM name> [[-p] [-hvd]]]] [debuggeroptions]**
| Parameter | Description |
|---|---|
| -hv | Specifies the name or GUID of the Hyper-V VM to debug. |
| -hvd | Includes hypervisor pages (Windows 8.1 and above only). |
| -hvl | Lists the names and GUIDs of running Hyper-V VMs. |
| -k | Specifies complete path and filename of debugger image to execute |
| -m | Creates a mirror dump, which is a consistent view of kernel memory. Only kernel mode memory will be available, and this option may need significant amounts of available physical memory. A flags mask that specifies which regions to include may optionally be provided (drawn from the following table, default 0x18F8): 0001 - process private, 0002 - mapped file, 0004 - shared section, 0008 - page table pages, 0010 - paged pool, 0020 - non-paged pool, 0040 - system PTEs, 0080 - session pages, 0100 - metadata files, 0200 - AWE user pages, 0400 - driver pages, 0800 - kernel stacks, 1000 - WS metadata, 2000 - large pages The default captures most kernel memory contents and is recommended. This option may be used with -o to save faster, consistent dumps. Mirror dumps require Windows Vista or Windows Server 2008 or above. Sysinternals RamMap provides a graphical summary of the distribution of the available memory regions that can be selected for inclusion. |
| -ml | Generate live dump using native support (Windows 8.1 and above only). |
| -mp | Specifies a single process whose user mode memory contents should be included in a mirror dump. Only effective with the -m option. |
| -o | Saves a memory.dmp to disk instead of launching the debugger. |
| -p | Pauses the target Hyper-V VM while LiveKd is active (recommended for use with -o). Specifies the name or GUID of the Hyper-V VM to debug. |
| -hvl | Lists the names and GUIDs of running Hyper-V VMs. |
| -vsym | Displays verbose debugging information about symbol load operations. |
| -w | Runs windbg instead of kd |
Resolve Symbols
All other options are passed through to the debugger.
A series of WWE games which began after WWE Smackdown! RAW 2011 is the twelfth installment of the popular wrestling series and introduces a brand new. Free and safe download. Download the latest version of the top software, games, programs and apps in 2018. All the adrenaline of WWE Raw on your PC. Download WWE SmackDown VS Raw 2009 fighting mobile game absolutely for free. Enjoy in this cool and addictive java game! Waptrick wwe raw game download. Feb 27, 2018 - Waptrick WWE Smackdown Game: Download WWE Smackdown Game Free Android, Play WWE Smackdown game. November 22, 2011. Superb graphics and realistic action aren't enough to make up for a very stingy demo in this head-to-head fighting game. WWE Raw only allows a one-on-one.
Note: Use Ctrl-Break to terminate and restart the debugger if ithangs.
By default LiveKd runs kd.exe.
Download LiveKd(494 KB)
Runs on:
- Client: Windows Vista and higher.
- Server: Windows Server 2008 and higher.