1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Windows Vista SMB.SYS Blue Screen

Discussion in 'Legacy Windows' started by KyleSutherland, 2009/07/29.

  1. 2009/07/29
    KyleSutherland

    KyleSutherland Inactive Thread Starter

    Joined:
    2009/07/29
    Messages:
    18
    Likes Received:
    0
    Greetings:

    I've had this problem for several months on many workstations so hopefully community minds will be able to help where the companies that make this stuff has failed.

    The setup: My office has approximately 20 Dell Precision 690 workstations. The environment is mixed between Windows XP Professional and Windows Vista Business. All of these are on Gigabit ethernet along with several servers that provide various services not involved with the problem. All of our storage is network attached storage on an EMC Celerra which archives files older than six months to an EMC Centera.

    The problem:
    I am a user at a Vista workstation. My workstation is up to date with all the latest Windows updates, service packs, and drivers available through windows update. I am navigating through folders on network attached storage. Suddenly, I navigate to a folder which has contents that have been archived to the centera. My computer blue screens saying that smb.sys is the culprit and restarts. Upon restarting, I browse to that same folder and no error occurs.

    This error occurs with every one of our workstations on Vista. After a restart, the problem goes away for the offending folder, but could happen again hours or days later. It is very random, but frequent. This occurs when browsing through folders using windows explorer or using a program to browse while opening or saving files for example.

    For those that are not familiar with EMC technology. The celerra has a file system which is able to present itself as a folder structure, and when files are archived down to the centera, the users are none the wiser. It is completely transparent unless you go looking at the centera itself.

    Does anyone have any ideas and is there any information I can provide? I have tried talking to EMC and Dell about this with no help.
     
  2. 2009/07/29
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4
    EDIT: Please follow the instructions posted by Arie in the next post.

    The smb.sys likely belongs to your Intel SMBus controller - and can be updated by updating the chipset drivers for your system. We'll be able to get more information about this from the minidump files.

    Please post the exact model number of your Dell system also
     
    Last edited: 2009/07/30

  3. to hide this advert.

  4. 2009/07/30
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    We don't recommend that course here, we ask users to follow these procedures:

    Follow these instructions to post a Dump Data Log.

    If you do not have a dump, ensure that your machine is configured to write out a dump by following the directions from microsoft
     
    Arie,
    #3
  5. 2009/07/30
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4
    Sorry, won't happen again. :0(
    Edited it out of my post.
     
  6. 2009/07/30
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    KyleSutherland - Scotland?? ....

    Welcome to WindowsBBS :)

    We encourage all members to complete their System Specifications which help us to help you :)
     
  7. 2009/07/30
    KyleSutherland

    KyleSutherland Inactive Thread Starter

    Joined:
    2009/07/29
    Messages:
    18
    Likes Received:
    0
    Dump log

    Opened log file 'c:debuglog.txt'

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


    Loading Dump File [C:\debugger\Mini072909-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: C:\Windows;C:\Windows\system32;C:\Windows\system32\drivers
    Windows Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 6001.18226.x86fre.vistasp1_gdr.090302-1506
    Kernel base = 0x81c38000 PsLoadedModuleList = 0x81d4fc70
    Debug session time: Wed Jul 29 08:36:40.966 2009 (GMT-4)
    System Uptime: 1 days 22:59:19.370
    Loading Kernel Symbols
    ...............................................................................................................................................
    Loading User Symbols
    Loading unloaded module list
    ........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {23, 2, 1, 807aa3f1}



    Probably caused by : smb.sys ( smb!SmbTdiReceiveHandler+323 )

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

    1: kd> !analyze -v;r;kv;lmtn;.logclose;q
    *******************************************************************************
    * *
    * 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: 00000023, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 807aa3f1, address which referenced memory

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




    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 81d6f868
    Unable to read MiSystemVaType memory at 81d4f420
    00000023

    CURRENT_IRQL: 2

    FAULTING_IP:
    smb!SmbTdiReceiveHandler+323
    807aa3f1 fe4823 dec byte ptr [eax+23h]

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: acad.exe

    TRAP_FRAME: 803f0640 -- (.trap 0xffffffff803f0640)
    .trap 0xffffffff803f0640
    ErrCode = 00000002
    eax=00000000 ebx=00000000 ecx=867b3702 edx=00000000 esi=867b37a0 edi=803f070c
    eip=807aa3f1 esp=803f06b4 ebp=803f06cc iopl=0 nv up ei pl nz na po nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
    smb!SmbTdiReceiveHandler+0x323:
    807aa3f1 fe4823 dec byte ptr [eax+23h] ds:0023:00000023=??
    .trap
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 807aa3f1 to 81c92d24

    STACK_TEXT:
    803f0640 807aa3f1 badb0d00 00000000 803f06e4 nt!KiTrap0E+0x2ac
    803f06cc 823df944 875312f8 867b37b0 00000c20 smb!SmbTdiReceiveHandler+0x323
    803f07ac 82a4d763 86745a08 803f0818 851a5648 tdx!TdxEventReceiveConnection+0x230
    803f083c 82a4d43a 877e6034 8690d278 803f08b8 tcpip!TcpIndicateData+0x1af
    803f0884 82a4d8c4 851a5648 00000000 803f08b8 tcpip!TcpDeliverDataToClient+0x162
    803f08a8 82a499eb 851a5648 851a5734 87179270 tcpip!TcpDeliverReceive+0x71
    803f08e8 82a4a418 851a5648 803f0908 803f093c tcpip!TcpTcbFastDatagram+0x2b9
    803f0948 82a49f1b 86359f40 001a5648 803f09ac tcpip!TcpTcbReceive+0xf8
    803f09a0 82a49d14 86359f40 86351000 00000000 tcpip!TcpMatchReceive+0x1ec
    803f09e8 82a4a310 86359f40 86351000 86351018 tcpip!TcpPreValidatedReceive+0x2b0
    803f0a04 82a4a913 86359f40 86351000 803f0a40 tcpip!TcpReceive+0x32
    803f0a14 82a74fef 803f0a28 c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12
    803f0a40 82a74db2 82acbe50 803f0a94 c000023e tcpip!IppDeliverListToProtocol+0x49
    803f0a60 82a74cd9 82acbc68 00000006 803f0a94 tcpip!IppProcessDeliverList+0x2a
    803f0ab8 82a744cc 82acbc68 00000006 00000000 tcpip!IppReceiveHeaderBatch+0x1eb
    803f0b48 82a72fc6 873cf4d0 00000000 81d1b401 tcpip!IpFlcReceivePackets+0xbe1
    803f0bc4 82a7350e 8741cd70 87179270 00000000 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x6e3
    803f0bec 8293f0b0 8741cd70 87179270 00000000 tcpip!FlReceiveNetBufferListChain+0x104
    803f0c20 82931919 0041c9b8 87179270 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0xab
    803f0c48 82931890 00000000 00000001 87171000 ndis!ndisIndicateSortedNetBufferLists+0x4a
    803f0dc4 8287257f 86f7d438 00000000 00000000 ndis!ndisMDispatchReceiveNetBufferLists+0x129
    803f0de0 82931aba 86f7d438 87179270 00000000 ndis!ndisMTopReceiveNetBufferLists+0x2c
    803f0dfc 8287254a 86f7d438 87179270 00000000 ndis!ndisMIndicateReceiveNetBufferListsInternal+0x27
    803f0e18 8e927827 86f7d438 87179270 00000000 ndis!NdisMIndicateReceiveNetBufferLists+0x20
    803f0e5c 8e927cf8 00000000 87179270 00000001 b57nd60x!shoot_nbls_up+0xa9
    803f0ec8 8e924648 00000125 00000000 00000000 b57nd60x!nd6x_ServiceRxRetProdRing+0x42a
    803f0ee8 8e907537 87171000 00000001 8e907a56 b57nd60x!LM_ServiceInterrupts+0x1f6
    803f0f14 8e907aad 00000001 87167000 803f0f3c b57nd60x!SetAdapterDefaultLinkState+0x3ed
    803f0f24 8e907bfc 87171000 00000000 00000000 b57nd60x!UM_Dpc+0x57
    803f0f3c 82931115 87171000 00000000 00000000 b57nd60x!UM_DpcMsi+0x14
    803f0f64 82872468 87167e34 8e907be8 00000000 ndis!ndisMiniportDpc+0x7a
    803f0f88 81cee450 87167e34 86f7d438 00000000 ndis!ndisInterruptDpc+0xc4
    803f0ff4 81cec935 c1a8c844 00000000 00000000 nt!KiRetireDpcList+0x147
    803f0ff8 c1a8c844 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x45
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    803f0ffc 00000000 00000000 00000000 00000000 0xc1a8c844


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    smb!SmbTdiReceiveHandler+323
    807aa3f1 fe4823 dec byte ptr [eax+23h]

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: smb!SmbTdiReceiveHandler+323

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: smb

    IMAGE_NAME: smb.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 479190cf

    FAILURE_BUCKET_ID: 0xD1_W_smb!SmbTdiReceiveHandler+323

    BUCKET_ID: 0xD1_W_smb!SmbTdiReceiveHandler+323

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

    eax=803d1120 ebx=00000002 ecx=81d381f8 edx=00011d92 esi=803d113c edi=803f02b8
    eip=81c92d24 esp=803f0628 ebp=803f0640 iopl=0 nv up ei pl nz na pe nc
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000206
    nt!KiTrap0E+0x2ac:
    81c92d24 833d646cd68100 cmp dword ptr [nt!KiFreezeFlag (81d66c64)],0 ds:0023:81d66c64=????????
    ChildEBP RetAddr Args to Child
    803f0640 807aa3f1 badb0d00 00000000 803f06e4 nt!KiTrap0E+0x2ac (FPO: [0,0] TrapFrame @ 803f0640)
    803f06cc 823df944 875312f8 867b37b0 00000c20 smb!SmbTdiReceiveHandler+0x323 (FPO: [Non-Fpo])
    803f07ac 82a4d763 86745a08 803f0818 851a5648 tdx!TdxEventReceiveConnection+0x230 (FPO: [Non-Fpo])
    803f083c 82a4d43a 877e6034 8690d278 803f08b8 tcpip!TcpIndicateData+0x1af (FPO: [Non-Fpo])
    803f0884 82a4d8c4 851a5648 00000000 803f08b8 tcpip!TcpDeliverDataToClient+0x162 (FPO: [Non-Fpo])
    803f08a8 82a499eb 851a5648 851a5734 87179270 tcpip!TcpDeliverReceive+0x71 (FPO: [Non-Fpo])
    803f08e8 82a4a418 851a5648 803f0908 803f093c tcpip!TcpTcbFastDatagram+0x2b9 (FPO: [Non-Fpo])
    803f0948 82a49f1b 86359f40 001a5648 803f09ac tcpip!TcpTcbReceive+0xf8 (FPO: [Non-Fpo])
    803f09a0 82a49d14 86359f40 86351000 00000000 tcpip!TcpMatchReceive+0x1ec (FPO: [Non-Fpo])
    803f09e8 82a4a310 86359f40 86351000 86351018 tcpip!TcpPreValidatedReceive+0x2b0 (FPO: [Non-Fpo])
    803f0a04 82a4a913 86359f40 86351000 803f0a40 tcpip!TcpReceive+0x32 (FPO: [Non-Fpo])
    803f0a14 82a74fef 803f0a28 c000023e 00000000 tcpip!TcpNlClientReceiveDatagrams+0x12 (FPO: [Non-Fpo])
    803f0a40 82a74db2 82acbe50 803f0a94 c000023e tcpip!IppDeliverListToProtocol+0x49 (FPO: [Non-Fpo])
    803f0a60 82a74cd9 82acbc68 00000006 803f0a94 tcpip!IppProcessDeliverList+0x2a (FPO: [Non-Fpo])
    803f0ab8 82a744cc 82acbc68 00000006 00000000 tcpip!IppReceiveHeaderBatch+0x1eb (FPO: [Non-Fpo])
    803f0b48 82a72fc6 873cf4d0 00000000 81d1b401 tcpip!IpFlcReceivePackets+0xbe1 (FPO: [Non-Fpo])
    803f0bc4 82a7350e 8741cd70 87179270 00000000 tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x6e3 (FPO: [Non-Fpo])
    803f0bec 8293f0b0 8741cd70 87179270 00000000 tcpip!FlReceiveNetBufferListChain+0x104 (FPO: [Non-Fpo])
    803f0c20 82931919 0041c9b8 87179270 00000000 ndis!ndisMIndicateNetBufferListsToOpen+0xab (FPO: [Non-Fpo])
    803f0c48 82931890 00000000 00000001 87171000 ndis!ndisIndicateSortedNetBufferLists+0x4a (FPO: [Non-Fpo])
    start end module name
    80404000 8040c000 kdcom kdcom.dll Sat Jan 19 02:31:53 2008 (4791A769)
    8040c000 8046c000 mcupdate_GenuineIntel mcupdate_GenuineIntel.dll Sat Jan 19 02:29:43 2008 (4791A6E7)
    8046c000 8047d000 PSHED PSHED.dll Sat Jan 19 02:31:21 2008 (4791A749)
    8047d000 80485000 BOOTVID BOOTVID.dll Sat Jan 19 02:27:15 2008 (4791A653)
    80485000 804c6000 CLFS CLFS.SYS Sat Jan 19 00:28:01 2008 (47918A61)
    804c6000 805a6000 CI CI.dll Fri Feb 22 00:00:56 2008 (47BE5708)
    805a6000 805d8000 netbt netbt.sys Sat Jan 19 00:55:33 2008 (479190D5)
    805d8000 805ee000 pacer pacer.sys Fri Apr 04 21:21:42 2008 (47F6D426)
    8060e000 8068a000 Wdf01000 Wdf01000.sys Sat Jan 19 00:52:21 2008 (47919015)
    8068a000 80697000 WDFLDR WDFLDR.SYS Sat Jan 19 00:52:19 2008 (47919013)
    80697000 806dd000 acpi acpi.sys Sat Jan 19 00:32:48 2008 (47918B80)
    806dd000 806e6000 WMILIB WMILIB.SYS Sat Jan 19 00:53:08 2008 (47919044)
    806e6000 806ee000 msisadrv msisadrv.sys Sat Jan 19 00:32:51 2008 (47918B83)
    806ee000 80715000 pci pci.sys Sat Jan 19 00:32:57 2008 (47918B89)
    80715000 80724000 partmgr partmgr.sys Sat Jan 19 00:49:54 2008 (47918F82)
    80724000 80733000 volmgr volmgr.sys Sat Jan 19 00:49:51 2008 (47918F7F)
    80733000 8077d000 volmgrx volmgrx.sys Sat Jan 19 00:50:00 2008 (47918F88)
    8077d000 80784000 pciide pciide.sys Sat Jan 19 00:49:42 2008 (47918F76)
    80784000 80792000 PCIIDEX PCIIDEX.SYS Sat Jan 19 00:49:40 2008 (47918F74)
    80792000 807a2000 mountmgr mountmgr.sys Sat Jan 19 00:49:13 2008 (47918F59)
    807a2000 807b6000 smb smb.sys Sat Jan 19 00:55:27 2008 (479190CF)
    807b6000 807fe000 afd afd.sys Sat Jan 19 00:57:00 2008 (4791912C)
    81c05000 81c38000 hal halmacpi.dll Sat Jan 19 00:27:20 2008 (47918A38)
    81c38000 81ff1000 nt ntkrpamp.exe Mon Mar 02 21:02:28 2009 (49AC8FB4)
    82204000 822cb000 iastor iastor.sys Thu Jul 26 21:17:40 2007 (46A947B4)
    822cb000 822d3000 atapi atapi.sys Sat Jan 19 00:49:40 2008 (47918F74)
    822d3000 822f1000 ataport ataport.SYS Sat Jan 19 00:49:40 2008 (47918F74)
    822f1000 8230d000 lsi_sas lsi_sas.sys Wed Jul 09 15:56:26 2008 (487517EA)
    8230d000 8234e000 storport storport.sys Sat Jan 19 00:49:49 2008 (47918F7D)
    8234e000 82380000 fltmgr fltmgr.sys Sat Jan 19 00:28:10 2008 (47918A6A)
    82380000 82390000 fileinfo fileinfo.sys Sat Jan 19 00:34:27 2008 (47918BE3)
    82390000 82394e20 PxHelp20 PxHelp20.sys Mon Apr 25 15:48:02 2005 (426D4972)
    82395000 823b6000 VIDEOPRT VIDEOPRT.SYS Sat Jan 19 00:52:10 2008 (4791900A)
    823b6000 823c1000 Msfs Msfs.SYS unavailable (00000000)
    823c1000 823cf000 Npfs Npfs.SYS Sat Jan 19 00:28:09 2008 (47918A69)
    823cf000 823d8000 rasacd rasacd.sys Sat Jan 19 00:56:31 2008 (4791910F)
    823d8000 823ee000 tdx tdx.sys Sat Jan 19 00:55:58 2008 (479190EE)
    823ee000 823fc000 netbios netbios.sys Sat Jan 19 00:55:45 2008 (479190E1)
    82800000 82871000 ksecdd ksecdd.sys Sat Jan 19 00:41:20 2008 (47918D80)
    82871000 8297c000 ndis ndis.sys Sat Jan 19 00:55:51 2008 (479190E7)
    8297c000 829a7000 msrpc msrpc.sys unavailable (00000000)
    829a7000 829e1000 NETIO NETIO.SYS Sat Jan 19 00:56:19 2008 (47919103)
    829e1000 829ed000 vga vga.sys Sat Jan 19 00:52:06 2008 (47919006)
    829ed000 829f5000 RDPCDD RDPCDD.sys Sat Jan 19 01:01:08 2008 (47919224)
    829f5000 829fd000 rdpencdd rdpencdd.sys Sat Jan 19 01:01:09 2008 (47919225)
    82a06000 82aed000 tcpip tcpip.sys Sat Apr 26 02:00:17 2008 (4812C4F1)
    82aed000 82b08000 fwpkclnt fwpkclnt.sys Sat Jan 19 00:55:44 2008 (479190E0)
    82b24000 82b33000 intelppm intelppm.sys Sat Jan 19 00:27:20 2008 (47918A38)
    82b33000 82b43000 HIDCLASS HIDCLASS.SYS Sat Jan 19 00:53:16 2008 (4791904C)
    82b43000 82b71000 msiscsi msiscsi.sys Sat Jan 19 00:50:44 2008 (47918FB4)
    82b71000 82b88000 rasl2tp rasl2tp.sys Sat Jan 19 00:56:33 2008 (47919111)
    82b88000 82b93000 ndistapi ndistapi.sys Sat Jan 19 00:56:24 2008 (47919108)
    82b93000 82bb6000 ndiswan ndiswan.sys Sat Jan 19 00:56:32 2008 (47919110)
    82bb6000 82bc5000 raspppoe raspppoe.sys Sat Jan 19 00:56:33 2008 (47919111)
    82bc5000 82bd9000 raspptp raspptp.sys Sat Jan 19 00:56:34 2008 (47919112)
    82bd9000 82bee000 rassstp rassstp.sys Sat Jan 19 00:56:43 2008 (4791911B)
    82bee000 82bf5000 Null Null.SYS unavailable (00000000)
    82bf5000 82bfc000 Beep Beep.SYS Sat Jan 19 00:49:10 2008 (47918F56)
    8a400000 8a40b000 TDI TDI.SYS Sat Jan 19 00:57:10 2008 (47919136)
    8a40d000 8a51c000 Ntfs Ntfs.sys Sat Jan 19 00:28:54 2008 (47918A96)
    8a51c000 8a555000 volsnap volsnap.sys Sat Jan 19 00:50:10 2008 (47918F92)
    8a555000 8a55d000 spldr spldr.sys Thu Jun 21 20:29:17 2007 (467B17DD)
    8a55d000 8a56c000 mup mup.sys Sat Jan 19 00:28:20 2008 (47918A74)
    8a56c000 8a593000 ecache ecache.sys Sat Jan 19 00:50:47 2008 (47918FB7)
    8a593000 8a5a4000 disk disk.sys Sat Jan 19 00:49:47 2008 (47918F7B)
    8a5a4000 8a5c5000 CLASSPNP CLASSPNP.SYS Sat Jan 19 00:49:36 2008 (47918F70)
    8a5c5000 8a5ce000 crcdisk crcdisk.sys Thu Nov 02 04:52:27 2006 (4549B1CB)
    8a5e5000 8a5f0000 tunnel tunnel.sys Sat Jan 19 00:55:50 2008 (479190E6)
    8a5f0000 8a5f9000 tunmp tunmp.sys Sat Jan 19 00:55:40 2008 (479190DC)
    8a5f9000 8a5fa680 WacomVKHid WacomVKHid.sys Thu Feb 15 18:11:07 2007 (45D4E88B)
    8e400000 8e406380 HIDPARSE HIDPARSE.SYS Sat Jan 19 00:53:16 2008 (4791904C)
    8e407000 8e846fe0 nvlddmkm nvlddmkm.sys Thu Dec 07 23:40:09 2006 (4578ECA9)
    8e847000 8e8e6000 dxgkrnl dxgkrnl.sys Fri Aug 01 21:01:19 2008 (4893B1DF)
    8e8e6000 8e8f3000 watchdog watchdog.sys Sat Jan 19 00:35:29 2008 (47918C21)
    8e8f3000 8e905000 HDAudBus HDAudBus.sys Tue Nov 27 18:18:41 2007 (474CA5D1)
    8e905000 8e934000 b57nd60x b57nd60x.sys Mon Feb 26 17:50:32 2007 (45E36438)
    8e934000 8e93f000 usbuhci usbuhci.sys Sat Jan 19 00:53:20 2008 (47919050)
    8e93f000 8e97d000 USBPORT USBPORT.SYS Sat Jan 19 00:53:23 2008 (47919053)
    8e97d000 8e98c000 usbehci usbehci.sys Sat Jan 19 00:53:21 2008 (47919051)
    8e98c000 8e99b200 ohci1394 ohci1394.sys Sat Jan 19 00:53:33 2008 (4791905D)
    8e99c000 8e9a9080 1394BUS 1394BUS.SYS Sat Jan 19 00:53:27 2008 (47919057)
    8e9aa000 8e9c2000 parport parport.sys Sat Jan 19 00:49:32 2008 (47918F6C)
    8e9c2000 8e9dc000 serial serial.sys Sat Jan 19 00:49:34 2008 (47918F6E)
    8e9dc000 8e9e6000 serenum serenum.sys Sat Jan 19 00:49:29 2008 (47918F69)
    8e9e6000 8e9fe000 cdrom cdrom.sys Sat Jan 19 00:49:50 2008 (47918F7E)
    8e9fe000 8e9ffc00 wacomvhid wacomvhid.sys Fri Feb 16 12:29:54 2007 (45D5EA12)
    8ec00000 8ec09000 Fs_Rec Fs_Rec.SYS unavailable (00000000)
    8ec0a000 8ec93000 rdpdr rdpdr.sys Sat Jan 19 01:02:27 2008 (47919273)
    8ec93000 8eca3000 termdd termdd.sys Sat Jan 19 01:01:06 2008 (47919222)
    8eca3000 8ecae000 kbdclass kbdclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
    8ecae000 8ecb9000 mouclass mouclass.sys Sat Jan 19 00:49:14 2008 (47918F5A)
    8ecb9000 8ecba380 swenum swenum.sys Sat Jan 19 00:49:20 2008 (47918F60)
    8ecbb000 8ece5000 ks ks.sys Sat Jan 19 00:49:21 2008 (47918F61)
    8ece5000 8ecef000 mssmbios mssmbios.sys Sat Jan 19 00:32:55 2008 (47918B87)
    8ecef000 8ecfc000 umbus umbus.sys Sat Jan 19 00:53:40 2008 (47919064)
    8ecfc000 8ed30000 usbhub usbhub.sys Sat Jan 19 00:53:40 2008 (47919064)
    8ed30000 8ed38000 mouhid mouhid.sys Sat Jan 19 00:49:16 2008 (47918F5C)
    8ed38000 8ed40000 wacommousefilter wacommousefilter.sys Fri Feb 16 13:12:29 2007 (45D5F40D)
    8ed40000 8ed49000 kbdhid kbdhid.sys Sat Jan 19 00:49:17 2008 (47918F5D)
    8ed49000 8ed5a000 NDProxy NDProxy.SYS Sat Jan 19 00:56:28 2008 (4791910C)
    8ed5a000 8edad000 stwrt stwrt.sys Sat May 05 20:40:01 2007 (463D23E1)
    8edad000 8edda000 portcls portcls.sys Sat Jan 19 00:53:17 2008 (4791904D)
    8edda000 8edff000 drmk drmk.sys Sat Jan 19 01:53:02 2008 (47919E4E)
    8ee0a000 8ee1d000 wanarp wanarp.sys Sat Jan 19 00:56:31 2008 (4791910F)
    8ee1d000 8ee59000 rdbss rdbss.sys Sat Jan 19 00:28:34 2008 (47918A82)
    8ee59000 8ee63000 nsiproxy nsiproxy.sys Sat Jan 19 00:55:50 2008 (479190E6)
    8ee63000 8ee666a0 ckldrv ckldrv.sys Thu Feb 03 15:53:11 2000 (3899EAB7)
    8ee67000 8eec1000 csc csc.sys Sat Jan 19 00:28:54 2008 (47918A96)
    8eec1000 8eed8000 dfsc dfsc.sys Sat Jan 19 00:28:20 2008 (47918A74)
    8eed8000 8eeea000 USBSTOR USBSTOR.SYS Sat Jan 19 00:53:22 2008 (47919052)
    8eeea000 8eeeb700 USBD USBD.SYS Sat Jan 19 00:53:17 2008 (4791904D)
    8eeec000 8ef02000 cdfs cdfs.sys Sat Jan 19 00:28:02 2008 (47918A62)
    8ef02000 8ef0f000 crashdmp crashdmp.sys Sat Jan 19 00:49:43 2008 (47918F77)
    8ef0f000 8ef19000 dump_diskdump dump_diskdump.sys Sat Jan 19 00:49:43 2008 (47918F77)
    8ef19000 8ef35000 dump_LSI_SAS dump_LSI_SAS.sys Wed Jul 09 15:56:26 2008 (487517EA)
    8ef35000 8ef3f000 Dxapi Dxapi.sys Sat Jan 19 00:36:12 2008 (47918C4C)
    8ef3f000 8ef48000 hidusb hidusb.sys Sat Jan 19 00:53:17 2008 (4791904D)
    8ef48000 8ef57000 monitor monitor.sys Sat Jan 19 00:52:19 2008 (47919013)
    8ef57000 8ef72000 luafv luafv.sys Sat Jan 19 00:30:35 2008 (47918AFB)
    8ef7a000 8efb3000 mrxsmb10 mrxsmb10.sys Tue Aug 26 21:05:40 2008 (48B4A864)
    8efb3000 8efda000 srv2 srv2.sys Sat Jan 19 00:29:14 2008 (47918AAA)
    970a0000 972a2000 win32k win32k.sys Sun Feb 08 22:10:21 2009 (498F9E9D)
    972c0000 972c9000 TSDDD TSDDD.dll unavailable (00000000)
    972f0000 9733c000 ATMFD ATMFD.DLL unavailable (00000000)
    97370000 9737e000 cdd cdd.dll unavailable (00000000)
    9ee09000 9eeb8000 spsys spsys.sys Thu Jun 21 20:33:02 2007 (467B18BE)
    9eeb8000 9eec8000 lltdio lltdio.sys Sat Jan 19 00:55:03 2008 (479190B7)
    9eec8000 9eedb000 rspndr rspndr.sys Sat Jan 19 00:55:03 2008 (479190B7)
    9eedb000 9ef46000 HTTP HTTP.sys Sat Jan 19 00:55:21 2008 (479190C9)
    9ef46000 9ef63000 srvnet srvnet.sys Sat Jan 19 00:29:11 2008 (47918AA7)
    9ef63000 9ef7c000 bowser bowser.sys Sat Jan 19 00:28:26 2008 (47918A7A)
    9ef7c000 9ef91000 mpsdrv mpsdrv.sys Sat Jan 19 00:54:45 2008 (479190A5)
    9ef91000 9efb1000 mrxdav mrxdav.sys Sat Jan 19 00:28:44 2008 (47918A8C)
    9efb1000 9efd0000 mrxsmb mrxsmb.sys Sat Jan 19 00:28:33 2008 (47918A81)
    9efd0000 9efe8000 mrxsmb20 mrxsmb20.sys Sat Jan 19 00:28:35 2008 (47918A83)
    9fe06000 9fe52000 srv srv.sys Mon Dec 15 21:42:35 2008 (4947159B)
    9fe52000 9fe59000 parvdm parvdm.sys unavailable (00000000)
    9fe59000 9fe6dc00 SENTINEL SENTINEL.SYS Thu Feb 01 06:38:53 2007 (45C1D14D)
    9fe6e000 9fe96000 fastfat fastfat.SYS Sat Jan 19 00:28:00 2008 (47918A60)
    9fe96000 9ff74000 peauth peauth.sys Mon Oct 23 04:55:32 2006 (453C8384)
    9ff74000 9ff7e000 secdrv secdrv.SYS Wed Sep 13 09:18:32 2006 (45080528)
    9ff7e000 9ff8a000 tcpipreg tcpipreg.sys Sat Jan 19 00:56:07 2008 (479190F7)
    9ff8a000 9ff9e580 WUDFRd WUDFRd.sys Sat Jan 19 00:53:04 2008 (47919040)
    9ff9f000 9ffb1000 WUDFPf WUDFPf.sys Sat Jan 19 00:52:49 2008 (47919031)

    Unloaded modules:
    9ffd7000 9ffe1000 hiber_storpo
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    9ffe1000 9fffd000 hiber_LSI_SA
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    9ffb1000 9ffbb000 hiber_storpo
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    9ffbb000 9ffd7000 hiber_LSI_SA
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    8ef72000 8ef7a000 drmkaud.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    8a5ce000 8a5db000 crashdmp.sys
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    8a5db000 8a5e5000 dump_storpor
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    82b08000 82b24000 dump_LSI_SAS
    Timestamp: unavailable (00000000)
    Checksum: 00000000
    Closing open log file c:debuglog.txt
     
  8. 2009/07/30
    KyleSutherland

    KyleSutherland Inactive Thread Starter

    Joined:
    2009/07/29
    Messages:
    18
    Likes Received:
    0
    Just some information about what you see in the dump file there. The user that had this crash yesterday was using AutoCAD 2008 to browse to open a file when it occured.

    Pete: Not from Scotland sadly :( But Scottish heritage, naturally. I'm from Rhode Island, United States.

    Edit: Hmm, the board said that my debuglog that I posted needed to be approved. Should I trim a part of it off to circumvent this?
     
  9. 2009/07/30
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4
    I live in Montville, CT (about 3 miles from the Mohegan Sun Casino).
     
  10. 2009/07/30
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
    No .....
    The Kyle of Lochalsh came to mind - which I mistakenly thought was in Sutherland :) Have visited both in past years :)
     
  11. 2009/07/30
    KyleSutherland

    KyleSutherland Inactive Thread Starter

    Joined:
    2009/07/29
    Messages:
    18
    Likes Received:
    0
    Ah, ok. So next time I'll just cut out the symbol search path line :) I thought it might have been due to the length of post.

    Also, it seems the log is here now. Pick away!
     
  12. 2009/07/30
    KyleSutherland

    KyleSutherland Inactive Thread Starter

    Joined:
    2009/07/29
    Messages:
    18
    Likes Received:
    0
    More Information

    I am trying to locate updated drivers for my chipset and having an extremely obnoxious time doing it. Dell's piecemeal motherboards make me furious.

    The motherboard model is 0MY171 from Dell

    The northbridge is Intel 5000x
    The southbridge is Intel 6321ESB - This is where the smbus controller identifies itself in the device manager.

    I have already gone to Dell's website and run the latest updates on the chipset and network adapter (broadcom). But I have a feeling there is a later update out there for the SMBus controller that I am not seeing.
     
  13. 2009/07/30
    PeteC

    PeteC SuperGeek Staff

    Joined:
    2002/05/10
    Messages:
    28,896
    Likes Received:
    389
  14. 2009/07/30
    KyleSutherland

    KyleSutherland Inactive Thread Starter

    Joined:
    2009/07/29
    Messages:
    18
    Likes Received:
    0
    Unfortunately I have installed that already and this problem still occurs.
     
  15. 2009/07/30
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4
    Way down deep in the stack text is this b57nd60x.sys (the only non-Microsoft entry in the stack). We presume that the Microsoft stuff is good - so we look for the 3rd party stuff first.
    This belongs to your Broadcom NetXtreme Gigabit Ethernet NDIS6.0 Driver. And this falls in line with the suspicion that this is a networking problem.

    Visit here to get the latest version: http://www.broadcom.com/support/ethernet_nic/downloaddrivers.php
    Then uninstall the current version from Control Panel...Programs...Uninstall a program
    Then install the one that you downloaded.

    Please post back and let us know how it works out.

    BTW - your mobo/chipset/storage and your video drivers appear to be a bit outdated also. Once the BSOD problem is solved, I'd suggest updating them also.
     
  16. 2009/07/30
    KyleSutherland

    KyleSutherland Inactive Thread Starter

    Joined:
    2009/07/29
    Messages:
    18
    Likes Received:
    0
    I installed it on one of the offending machines about 2 hours ago, so we'll see how it ends up working out.

    For my own personal learning experience, how did you pick that out as a non-microsoft entry?
     
  17. 2009/07/30
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4
    Also, in a recent conversation with Microsoft I was able to learn that disabling the pagefile will probably decrease the frequency of the IRQL crashes - because the crash occurs when accessing memory that's paged out (and has to be pulled back into the physical RAM) in order to access it. Having no pagefile reduces the likelyhood of the data being paged out, so it reduces the likelyhood of having an error because it isn't present in paged memory.
     
  18. 2009/07/30
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4
    I review the entire report that you submitted and keep an eye open for networking stuff.

    If there's nothing evident, then I scan the stack text for 3rd party drivers. The ndis, tcpip, smb, and nt (for ntoskrnl.exe) entries are all Windows components - so that leaves the Broadcom as the only remaining suspect.

    Finally, I scan the drivers list at the end, looking for stuff that's over a year or so old.
     
  19. 2009/08/07
    KyleSutherland

    KyleSutherland Inactive Thread Starter

    Joined:
    2009/07/29
    Messages:
    18
    Likes Received:
    0
    Hello friends:

    Well, the problem is still occuring. Back to the drawing board. Using updated graphics, chipset, and network drivers.

    Anyone think they can find the smbus updated driver?
     
  20. 2009/08/08
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4
    I'd suggest running Driver Verifier on the "crankiest" system to see if it tells us anything different. Please read the following instructions thoroughly before starting (as it may render the system unbootable). See the NOTE below it for a suggested procedure also.

    I'll keep looking for updated smbus drivers.

    NOTE:
    Once you've run it as mentioned above, if you don't get a Driver Verifier BSOD within 24 hours, then select all non-Micorosft drivers and run it again for 24 hours.

    If that doesn't give a Driver Verifier BSOD within 24 hours, then select ALL drivers and run it again for 24 hours. This will slow the system to a crawl, but it's the best way to stress all of the drivers.

    Good luck!
     
  21. 2009/08/08
    usasma

    usasma Inactive

    Joined:
    2006/12/17
    Messages:
    225
    Likes Received:
    4

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.