I am new to crash dump analysis and would love some help interpreting this dump. Seems like a huge stack and if I had to guess I would think Windows is blaming itself so I would appreciate some opinions and or guidence. Here is the dump:
Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\bentley_k\Desktop
\Nikki Marasco\Mini092508-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*
http://msdl.microsoft.com/download/symbols;C:\SymbolsExecutable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.070227-2
254
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Thu Sep 25 14:21:15.497 2008 (GMT-7)
System Uptime: 0 days 5:16:33.158
Loading Kernel Symbols
..........................
..........
..........
..........
..........
..........
..........
..........
..........
..........
..........
..........
..........
..........
.....
Loading User Symbols
Loading unloaded module list
.................
**************************
**********
**********
**********
**********
**********
***
* *
* Bugcheck Analysis *
* *
**************************
**********
**********
**********
**********
**********
***
Use !analyze -v to get detailed debugging information.
BugCheck 44, {892e9668, d63, 0, 0}
*** WARNING: Unable to verify timestamp for SYMTDI.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMTDI.SYS
Unable to load image dne2000.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dne2000.sys
*** ERROR: Module load completed but symbols could not be loaded for dne2000.sys
Unable to load image b57xp32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for b57xp32.sys
Probably caused by : netbt.sys ( netbt!NTIoComplete+3e )
Followup: MachineOwner
---------
0: kd> !analyze -v
**************************
**********
**********
**********
**********
**********
***
* *
* Bugcheck Analysis *
* *
**************************
**********
**********
**********
**********
**********
***
MULTIPLE_IRP_COMPLETE_REQU
ESTS (44)
A driver has requested that an IRP be completed (IoCompleteRequest()), but
the packet has already been completed. This is a tough bug to find because
the easiest case, a driver actually attempted to complete its own packet
twice, is generally not what happened. Rather, two separate drivers each
believe that they own the packet, and each attempts to complete it. The
first actually works, and the second fails. Tracking down which drivers
in the system actually did this is difficult, generally because the trails
of the first driver have been covered by the second. However, the driver
stack for the current request can be found by examining the DeviceObject
fields in each of the stack locations.
Arguments:
Arg1: 892e9668, Address of the IRP
Arg2: 00000d63
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
IRP_ADDRESS: 892e9668
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x44
PROCESS_NAME: System
DEVICE_OBJECT: 8a255d08
LAST_CONTROL_TRANSFER: from 80520643 to 8053738a
STACK_TEXT:
b71bcd20 80520643 00000044 892e9668 00000d63 nt!KeBugCheckEx+0x1b
b71bcd58 b8b27a99 00000000 b71bcda8 b8b2f5b8 nt!IopfCompleteRequest+0x2
ce
b71bcd64 b8b2f5b8 892e9602 c0000120 00000000 netbt!NTIoComplete+0x3e
b71bcda8 b8b29c10 89787380 c0000120 00000000 netbt!SessionStartupContin
ue+0x333
b71bcdc8 804e18ff 8a1d4ab8 892e9668 89269b30 netbt!TcpConnectComplete+0
x1f
b71bcdf8 b8bd2565 8910c4a0 892e9668 b71bce20 nt!IopfCompleteRequest+0xa
2
WARNING: Stack unwind information not available. Following frames may be wrong.
b71bce08 80505459 8a1ddb08 892e9668 892e9668 SYMTDI+0x2565
b71bce20 b8b2fc22 892e9668 8910c4a0 b71bce48 nt!IoCancelIrp+0x65
b71bce30 80505459 8a1d4ab8 8910c4a0 8a118e68 netbt!NbtCancelConnect+0x5
1
b71bce48 b8a513aa 8910c4a0 8a118e18 8943c970 nt!IoCancelIrp+0x65
b71bce68 b8a51335 8a118e68 890d4e28 8a118e18 rdbss!RxTdiCancelAsynchron
ousConnect
+0x5a
b71bce94 b8a50f64 8a118e68 890d4ee3 890d4e28 rdbss!RxCeCompleteConnectR
equest+0x1
b5
b71bceac 804e18ff 00000000 890d4e28 8a118e18 rdbss!RxTdiAsynchronousCon
nectComple
tion+0x75
b71bcedc b8b27a99 89312ed8 b71bcf04 b8b2cd0f nt!IopfCompleteRequest+0xa
2
b71bcee8 b8b2cd0f 890d4e02 00000000 00000000 netbt!NTIoComplete+0x3e
b71bcf04 b8b2cad4 89312ed8 00000000 899da8b3 netbt!DoneDelayedNbtProces
sConnect+0
x3b
b71bcf20 804e18ff 00000000 899da7f8 89312ed8 netbt!NbtpConnectCompletio
nRoutine+0
x6b
b71bcf50 b8b27a99 89923928 b71bcfa0 b8b2925d nt!IopfCompleteRequest+0xa
2
b71bcf5c b8b2925d 899da702 00000000 00000000 netbt!NTIoComplete+0x3e
b71bcfa0 b8b29c10 8a1d7ae0 89923984 00000000 netbt!SessionStartupContin
ue+0x342
b71bcfc0 804e18ff 8a1ccd30 899da7f8 89a14008 netbt!TcpConnectComplete+0
x1f
b71bcff0 b8c0d8ff 893a9858 899e2df0 00000002 nt!IopfCompleteRequest+0xa
2
b71bd008 b8c13ca6 899da7f8 00000000 00000000 tcpip!TCPDataRequestComple
te+0xa6
b71bd01c b8c14b83 899da7f8 00000000 00000000 tcpip!TCPRequestComplete+0
x12
b71bd03c b8c16a38 899e2df0 b71bd1fc 00000000 tcpip!CompleteConnReq+0x87
b71bd0c0 b8c0aef5 8a25fbc0 43110a0a 09340a0a tcpip!TCPRcv+0xdda
b71bd120 b8c0ab19 00000020 8a25fbc0 b8c0d076 tcpip!DeliverToUser+0x18e
b71bd19c b8c0a836 b8c4a4e0 8a25fbc0 89e0b218 tcpip!DeliverToUserEx+0x95
e
b71bd254 b8c09922 8a25fbc0 89e0b22c 0000001c tcpip!IPRcvPacket+0x6cb
b71bd294 b8c0984d 00000000 89330b18 89e0b20a tcpip!ARPRcvIndicationNew+
0x149
b71bd2d0 f744ef45 8a23be70 00000000 ba572b40 tcpip!ARPRcvPacket+0x68
b71bd324 ba56d01d 00106df0 89445a10 00000001 NDIS!ethFilterDprIndicateR
eceivePack
et+0x307
b71bd338 ba56d1b4 8a42aad0 89445a10 00000001 psched!PsFlushReceiveQueue
+0x15
b71bd35c ba56d5f9 8a2e8dc0 00000000 8a42aad0 psched!PsEnqueueReceivePac
ket+0xda
b71bd374 f744f9ed 8a2e8db8 89fcc868 893305b8 psched!ClReceiveComplete+0
x13
b71bd38c ba641ec5 8a02ab20 89d0bd08 89fcc868 NDIS!EthFilterDprIndicateR
eceiveComp
lete+0x7c
b71bd3bc ba642d03 89fcc868 8a2f0e18 893305b8 dne2000+0x14ec5
b71bd418 f7441c1c 89fcc868 893305b8 00000000 dne2000+0x15d03
b71bd43c ba756139 8a440ad0 893305b8 00000000 NDIS!ndisMSendCompleteX+0x
8d
b71bd45c ba75257a 89e34000 89330868 b71bd4d8 b57xp32!LM_GetAdapterInfo+
0x319
b71bd470 ba75280d 02e34000 00000000 8a440ad0 b57xp32!UM_SetInformation+
0x66a
b71bd4a8 f7445600 00000001 b71bd4d8 00000000 b57xp32!UM_SetInformation+
0x8fd
b71bd4c0 80701c4f 8a4409d0 00000000 892624e8 NDIS!ndisMProcessSGList+0x
90
b71bd4e4 f744556e 00000000 8a4409d0 890b36d8 hal!HalBuildScatterGatherL
ist+0x191
b71bd53c f742ca08 8981abf8 89330868 893308bc NDIS!ndisMAllocSGList+0xd9
b71bd558 f7444986 8a2f0e18 89330868 b71bd5c0 NDIS!ndisMSendX+0x1a0
b71bd568 ba64102d b71bd59c 8a2f0e18 89330868 NDIS!NdisSend+0xf
b71bd5c0 ba633ab9 89fcc868 89d0bed8 b71bd5dc dne2000+0x1402d
b71bd5d8 f742c985 89fcc868 89d0bed8 00000002 dne2000+0x6ab9
b71bd600 ba56e528 8a2e9a98 89d0bed8 89d0bea0 NDIS!ndisMSendX+0x1d6
b71bd63c f742c985 8a2e8db8 89d0bed8 00000002 psched!MpSend+0x706
b71bd664 b8c0cd00 8a2c6b30 89d0bed8 8a23be70 NDIS!ndisMSendX+0x1d6
b71bd68c b8c0c8ce 8a23be70 89d0bed8 89880c68 tcpip!ARPSendData+0x198
b71bd6b8 b8c0c70a 8a23be70 b71bd600 00000001 tcpip!ARPTransmit+0x193
b71bd6e8 b8c0c4a9 8a202ad8 fa110a0a 89d0bed8 tcpip!SendIPPacket+0x18e
b71bd834 b8c170af b8c4a798 00000000 8980e5a0 tcpip!IPTransmit+0x287f
b71bd888 b8c16733 896704ec 00000000 896594a0 tcpip!SendSYN+0x28d
b71bd8cc b8c15ce9 181bd8f0 00000001 00000000 tcpip!TdiConnect+0x3ab
b71bd908 b8c0f038 892b2808 892b2878 892b289c tcpip!TCPConnect+0xa8
b71bd924 804e13d9 8a255d08 892b2808 892b28c0 tcpip!TCPDispatchInternalD
eviceContr
ol+0x13f
b71bd934 b8be4e74 00000000 8912db20 8a0d2c18 nt!IopfCallDriver+0x31
b71bd948 b8bd2e4a 8a0d2c18 8a1f1c10 8912db20 SYMTDI+0x14e74
b71bd96c b8bd2dd2 8a1f1c10 8a0d2c18 00000065 SYMTDI+0x2e4a
b71bd99c b8bd2dd2 8a273df0 8a0d2c18 00000064 SYMTDI+0x2dd2
b71bd9cc b8bd3081 8a238c10 8a0d2c18 00000065 SYMTDI+0x2dd2
b71bda18 b8be5548 8a0d2c18 b71bda3c 8a173af8 SYMTDI+0x3081
b71bda40 b8be55da 8a1ddb08 b8bd2e60 b71bda78 SYMTDI+0x15548
b71bda50 804e13d9 8a1ddb08 892b2808 b8a56ad0 SYMTDI+0x155da
b71bda60 b8b2cc7f 896594a0 895706c0 896593d0 nt!IopfCallDriver+0x31
b71bda78 b8b2c47d 89708c50 b8a56ad0 896594a0 netbt!TdiConnect+0xae
b71bdab0 b8b2b4f4 006593d0 0a0a3318 8a1d4ab8 netbt!TcpSessionStart+0xb5
b71bdb18 b8b2c3d3 89155370 0a0a3318 0049003c netbt!NbtConnectCommon+0x8
aa
b71bdb34 b8b2cb56 b71bdb58 b8a56ad0 89491fc8 netbt!NbtConnect+0xb1
b71bdb84 b8b28cf9 8a1d4ab8 892b2808 89491fb8 netbt!NTConnect+0x119
b71bdba0 804e13d9 e01d4ab8 892b28c0 00000000 netbt!NbtDispatchInternalC
trl+0x101
STACK_COMMAND: kb
FOLLOWUP_IP:
netbt!NTIoComplete+3e
b8b27a99 5e pop esi
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: netbt!NTIoComplete+3e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: netbt
IMAGE_NAME: netbt.sys
DEBUG_FLR_IMAGE_TIMESTAMP:
41107ecc
FAILURE_BUCKET_ID: 0x44_netbt!NTIoComplete+3e
BUCKET_ID: 0x44_netbt!NTIoComplete+3e
Followup: MachineOwner
---------
0: kd> lmvm netbt
start end module name
b8b27000 b8b4ec00 netbt (pdb symbols) c:\websymbols\netbt.pdb\68
363A5520E2
47C5830D7E
67ABA19D07
2\netbt.pd
b
Loaded symbol image file: netbt.sys
Mapped memory image file: c:\websymbols\netbt.sys\41
107ECC27c0
0\netbt.sy
s
Image path: netbt.sys
Image name: netbt.sys
Timestamp: Tue Aug 03 23:14:36 2004 (41107ECC)
CheckSum: 00033EE9
ImageSize: 00027C00
File version: 5.1.2600.2180
Product version: 5.1.2600.2180
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: netbt.sys
OriginalFilename: netbt.sys
ProductVersion: 5.1.2600.2180
FileVersion: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
FileDescription: MBT Transport driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
0: kd> lmvm netbt
start end module name
b8b27000 b8b4ec00 netbt (pdb symbols) c:\websymbols\netbt.pdb\68
363A5520E2
47C5830D7E
67ABA19D07
2\netbt.pd
b
Loaded symbol image file: netbt.sys
Mapped memory image file: c:\websymbols\netbt.sys\41
107ECC27c0
0\netbt.sy
s
Image path: netbt.sys
Image name: netbt.sys
Timestamp: Tue Aug 03 23:14:36 2004 (41107ECC)
CheckSum: 00033EE9
ImageSize: 00027C00
File version: 5.1.2600.2180
Product version: 5.1.2600.2180
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: netbt.sys
OriginalFilename: netbt.sys
ProductVersion: 5.1.2600.2180
FileVersion: 5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)
FileDescription: MBT Transport driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
...many thanks, I appreciate any help.
Start Free Trial
