Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Vista Drivers > Windbg crash debug settings and issues

Reply
Thread Tools Display Modes

Windbg crash debug settings and issues

 
 
Zaheer Khan
Guest
Posts: n/a

 
      12-08-2009
While debugging windows crash I am getting the
following log:

======================================


Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Complete Dump File: Full address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: c:\windows\
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
Unable to read PsLoadedModuleList
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
KdDebuggerData.KernBase < SystemRangeStart
Windows XP Kernel Version 2600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x00000000 PsLoadedModuleList = 0x8055c700
Debug session time: Tue Dec 8 13:35:33.218 2009 (GMT+5)
System Uptime: 0 days 0:02:44.854
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
Unable to read PsLoadedModuleList
************************************************** ************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable.
************************************************** ************************
KdDebuggerData.KernBase < SystemRangeStart
Loading Kernel Symbols
Unable to read PsLoadedModuleList
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
CS descriptor lookup failed
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get program counter
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

Use !analyze -v to get detailed debugging information.

BugCheck 8E, {c0000005, edc2cc2c, edcf7880, 0}

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
Unable to read selector for PCR for processor 0
Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner
---------

GetContextState failed, 0x80004002
GetContextState failed, 0x80004002

?: kd> !analyze -v
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get program counter
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************

KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: edc2cc2c, The address that the exception occurred at
Arg3: edcf7880, Trap Frame
Arg4: 00000000

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 0
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 0
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 1
GetContextState failed, 0x80004002
Unable to read selector for PCR for processor 0

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".

FAULTING_IP:
+0
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
edc2cc2c ?? ???

TRAP_FRAME: edcf7880 -- (.trap 0xffffffffedcf7880)
Unable to read trap frame at edcf7880

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x8E

STACK_TEXT:
GetContextState failed, 0x80004002
Unable to get current machine context, HRESULT 0x80004002


STACK_COMMAND: kb

SYMBOL_NAME: ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: CORRUPT_MODULELIST

Followup: MachineOwner
---------

GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
GetContextState failed, 0x80004002
================================================== =


My doubts are as follows:

1)What exactly does
Symbol search path ,Executable search path ,Source search path mean and where should they point to ?

2) I am not sure if the symbols have
been correctly installed in Winxp package. How do I
confirm the symbols installation.

3)Also where should the Executable search path point
to ? Is it the .sys driver file path which is used to
run the device.

4) The log gives the following error
"************************************************* *************************
THIS DUMP FILE IS PARTIALLY CORRUPT.
KdDebuggerDataBlock is not present or unreadable."

I tried to change the virtual memory setting given in the blog :
http://blogs.msdn.com/dougste/archiv...y-corrupt.aspx

This also did not work and I got the same error.

Please help me with your valuable replies,

Thanks,
Zaheer.






Submitted via EggHeadCafe - Software Developer Portal of Choice
SQL Server 2005 Msg 6505 - Could not find Type in Assembly
http://www.eggheadcafe.com/tutorials...-msg-6505.aspx
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Move \Users folder once for all Peter Meinl Windows Vista Installation 25 03-03-2010 02:37 AM
Dear Microsoft - UAC (.png & wmp) issues should be addressed. JSandPC Windows Vista Administration 120 12-02-2008 05:42 PM
Activesync 4.5 is so slow PD ActiveSync 4 04-03-2008 12:59 AM
How to contact Microsoft C.B. Windows Vista Hardware 23 03-12-2008 03:06 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59