Windows Vista BugCheck D1 Probably caused by : smb.sys ( smb!SmbTdiDisconnectHandler+18 )

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


Loading Dump File [P:\2008\10 - OCT\74364651 Lx170\memory.dmp]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Longhorn Kernel Version 6000 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6000.16584.x86fre.vista_gdr.071023-1545
Kernel base = 0x81c00000 PsLoadedModuleList = 0x81d11e10
Debug session time: Tue Oct 21 21:35:57.217 2008 (GMT-4)
System Uptime: 3 days 11:59:27.686
Loading Kernel Symbols
....................................................................................................................................................................
Loading unloaded module list
....
Loading User Symbols
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {8, 2, 0, 9010c560}

*** ERROR: Module load completed but symbols could not be loaded for dtcm.sys
Probably caused by : smb.sys ( smb!SmbTdiDisconnectHandler+18 )

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

1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000008, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: 9010c560, address which referenced memory

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


READ_ADDRESS: 00000008

CURRENT_IRQL: 2

FAULTING_IP:
smb!SmbTdiDisconnectHandler+18
9010c560 8b7908 mov edi,[ecx+0x8]

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 900aab15 to 9010c560

TRAP_FRAME: 8be2fb60 -- (.trap ffffffff8be2fb60)
ErrCode = 00000000
eax=00000000 ebx=a5cd7de0 ecx=00000000 edx=8afb1a80 esi=901112c0 edi=81fa4e10
eip=9010c560 esp=8be2fbd4 ebp=8be2fbe0 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
smb!SmbTdiDisconnectHandler+0x18:
9010c560 8b7908 mov edi,[ecx+0x8] ds:0023:00000008=????????
Resetting default scope

STACK_TEXT:
8be2fbe0 900aab15 85249690 00000000 00000000 smb!SmbTdiDisconnectHandler+0x18
WARNING: Stack unwind information not available. Following frames may be wrong.
8be2fc18 900a9e39 88749350 00000000 00000000 dtcm+0x19b15
8be2fc44 900a9ff9 8afb1a80 88749350 00000000 dtcm+0x18e39
8be2fca4 9011e781 8afb1a80 88749350 00000000 dtcm+0x18ff9
8be2fcf0 901731d9 900a9ef0 00000000 901ed080 tdx!TdxCloseConnectionEndpointTlRequestComplete+0x17f
8be2fd08 806114d1 e581726c 81cfde7c 87ce1698 tcpip!TcpCleanupTcbWorkQueueRoutine+0xaf
8be2fd2c 81d8c864 87ce1698 901ed080 87989228 NETIO!NetiopIoWorkItemRoutine+0x2f
8be2fd44 81c78fa0 87989228 00000000 8451a828 nt!IopProcessWorkItem+0x2d
8be2fd7c 81e254e0 87989228 8be24680 00000000 nt!ExpWorkerThread+0xfd
8be2fdc0 81c9159e 81c78ea3 00000001 00000000 nt!PspSystemThreadStartup+0x9d
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16


FOLLOWUP_IP:
smb!SmbTdiDisconnectHandler+18
9010c560 8b7908 mov edi,[ecx+0x8]

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: smb!SmbTdiDisconnectHandler+18

MODULE_NAME: smb

IMAGE_NAME: smb.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 45b6cc3e

STACK_COMMAND: .trap ffffffff8be2fb60 ; kb

FAILURE_BUCKET_ID: 0xD1_smb!SmbTdiDisconnectHandler+18

BUCKET_ID: 0xD1_smb!SmbTdiDisconnectHandler+18

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

 

leojdpa, welcome to the BBS, but you might have trouble getting someone to make a suggestion. You have not included any background information. If this is the only time you have had the problem, it might have just been a "glitch" and would not be worth people's time in researching a possible solution.

Does it happen often? Is the debugging information always similar?

smb.sys is a Microsoft driver from what I can find.

Only maybes, but if you have installed SP1 and it has started since then, uninstall SP1 and see if the problem goes away.

Go to the website of your system (motherboard) manufacturer. Get updated drivers, starting with the chipset drivers. If you find it relates SP1, try installing again after the driver updates.

Matt

 

sp1 was my suggestion, then drivers

Looked to me from the dump that it did not have SP1 installed so my first suggestion was to intall most current bios, if he is not current, then SP1, then Dell drivers.
This is a Dell latititude laptop and this seems to happen every 3 days, sort of like something is leaking but we did not go there yet because I did not see SP1 installed and I felt his issue could already be fixed in it.

I will know in a week or two if Sp1 resolved the issue.