StackTrace Failed from new windbg

WINDBG
1

I’m trying to analyze a kernel dump and windbg will not give me a stack
trace. I’ve got version 1.0.0006.0 of windbg and it comes up with the
following when I open the crash dump file:

KdDebuggerDataBlock not available - must be an NT4 dump file
KdDebuggerData.KernBase < g_SystemRangeStart
Windows 2000 Kernel Version 2195 MP (2 procs) Free x86 compatible
Kernel base = 0x00000000 PsLoadedModuleList = 0x80480320
Could not get the KiProcessorBlock address
WaitForEvent failed
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000
edi=00000000
eip=00000000 esp=00000000 ebp=00000000 iopl=0 nv up di pl nz na pe
nc
cs=0000 ss=0000 ds=0000 es=0000 fs=0000 gs=0000
efl=00000000
0000:0000 ?? ???
StackTrace failed

I’m running W2000 on the system that generated the crash dump. So I can’t
understand why it is saying it must be a NT4 dump file. When I open the
file under the 2295 version of windbg, I can get a stack trace.

Any ideas? We’ve been seeing this right along, sometimes you get a stack
trace, other times you don’t.

2

This is usually indicative of a symbol problem. Verify you are pointing
to the right symbols. Using the -n option should help.

-----Original Message-----
From: xxxxx@giganet.com [mailto:xxxxx@giganet.com]
Sent: Tuesday, September 26, 2000 7:16 AM
To: Kernel Debugging Interest List
Subject: [windbg] StackTrace Failed from new windbg

I’m trying to analyze a kernel dump and windbg will not give me a stack
trace. I’ve got version 1.0.0006.0 of windbg and it comes up with the
following when I open the crash dump file:

KdDebuggerDataBlock not available - must be an NT4 dump file
KdDebuggerData.KernBase < g_SystemRangeStart
Windows 2000 Kernel Version 2195 MP (2 procs) Free x86 compatible
Kernel base = 0x00000000 PsLoadedModuleList = 0x80480320
Could not get the KiProcessorBlock address
WaitForEvent failed
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000000
edi=00000000
eip=00000000 esp=00000000 ebp=00000000 iopl=0 nv up di pl nz na
pe
nc
cs=0000 ss=0000 ds=0000 es=0000 fs=0000 gs=0000
efl=00000000
0000:0000 ?? ???
StackTrace failed

I’m running W2000 on the system that generated the crash dump. So I
can’t
understand why it is saying it must be a NT4 dump file. When I open the
file under the 2295 version of windbg, I can get a stack trace.

Any ideas? We’ve been seeing this right along, sometimes you get a stack

trace, other times you don’t.

You are currently subscribed to windbg as: xxxxx@microsoft.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)