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.

Server 2008 Blue Screen 6.0.6002.2.2.0.16.7

Discussion in 'Windows Server System' started by oecgroup, 2013/10/22.

  1. 2013/10/22
    oecgroup

    oecgroup Inactive Thread Starter

    Joined:
    2013/10/22
    Messages:
    1
    Likes Received:
    0
    Hello,

    Our server is crashed almost everyday and got the blue screen 6.0.6002.2.2.0.16.7
    Below is the mini dump file from our server.
    Can anyone help us to find out what's wrong with our server?
    Thanks

    ---------------------------------------------------------------------------
    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\rchan\Desktop\Mini102213-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:
    Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (4 procs) Free x86 compatible
    Product: LanManNt, suite: TerminalServer
    Built by: 6002.18881.x86fre.vistasp2_gdr.130707-1535
    Machine Name:
    Kernel base = 0x83a14000 PsLoadedModuleList = 0x83b2bc70
    Debug session time: Tue Oct 22 13:20:03.238 2013 (UTC - 7:00)
    System Uptime: 0 days 22:32:11.015
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ....
    Loading User Symbols
    Loading unloaded module list
    .........
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {fffffff8, 2, 1, 9350847e}

    Unable to load image \SystemRoot\system32\DRIVERS\E1G60I32.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for E1G60I32.sys
    *** ERROR: Module load completed but symbols could not be loaded for E1G60I32.sys
    Probably caused by : smb.sys ( smb!SmbPrepareReceiveIrp+70 )

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

    0: 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: fffffff8, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: 9350847e, address which referenced memory

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


    WRITE_ADDRESS: GetPointerFromAddress: unable to read from 83b4b874
    Unable to read MiSystemVaType memory at 83b2b420
    fffffff8

    CURRENT_IRQL: 2

    FAULTING_IP:
    smb!SmbPrepareReceiveIrp+70
    9350847e 89481c mov dword ptr [eax+1Ch],ecx

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR: 0xD1

    PROCESS_NAME: System

    TRAP_FRAME: 83b09530 -- (.trap 0xffffffff83b09530)
    ErrCode = 00000002
    eax=ffffffdc ebx=8956ce28 ecx=93507c3a edx=89da411c esi=89da4008 edi=00000000
    eip=9350847e esp=83b095a4 ebp=83b095b0 iopl=0 nv up ei ng nz ac po cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010293
    smb!SmbPrepareReceiveIrp+0x70:
    9350847e 89481c mov dword ptr [eax+1Ch],ecx ds:0023:fffffff8=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER: from 9350847e to 83a61ecd

    STACK_TEXT:
    83b09530 9350847e badb0d00 89da411c 00000000 nt!KiTrap0E+0x1c5
    83b095b0 93508629 0000090b 83b09660 89da4008 smb!SmbPrepareReceiveIrp+0x70
    83b095cc 93508234 870622f8 89da411c 00000c20 smb!SmbPartialRcv+0x141
    83b0960c 934f19d8 870622f8 89da4018 00000c20 smb!SmbTdiReceiveHandler+0x162
    83b096ec 8e6d0607 89aa6008 83b09758 89728b70 tdx!TdxEventReceiveConnection+0x230
    83b0977c 8e6d00a1 87111064 8805c738 83b097fc tcpip!TcpIndicateData+0x1af
    83b097c4 8e6d0291 89728b70 00000000 83b097fc tcpip!TcpDeliverDataToClient+0x162
    83b097ec 8e6ce996 89728b70 89728c5c 8859d770 tcpip!TcpDeliverReceive+0x76
    83b0982c 8e6cf26d 89728b70 83b0984c 83b09880 tcpip!TcpTcbFastDatagram+0x2d1
    83b0988c 8e6cd6a6 86c7cf40 00728b70 83b098f0 tcpip!TcpTcbReceive+0xf8
    83b098e4 8e6cf0b9 86c7cf40 86c7900c 00000000 tcpip!TcpMatchReceive+0x1ec
    83b0992c 8e6fc8ea 86c7cf40 86c7900c 86c79018 tcpip!TcpPreValidatedReceive+0x22d
    83b09940 8e7177ba 83b0995c 00000001 00000000 tcpip!TcpNlClientReceivePreValidatedDatagrams+0x15
    83b09964 8e712fdf 83b09970 00000000 00000001 tcpip!IppDeliverPreValidatedListToProtocol+0x33
    83b099f8 8e6e30b6 887b1480 00000036 83af7837 tcpip!IpFlcReceivePreValidatedPackets+0x3b1
    83b09a14 8e2cf0b0 89711ad8 00000000 00000000 tcpip!FlReceiveNetBufferListChain+0xe1
    83b09a48 8e2c1d25 00cdb9b8 8859d770 00000000 NDIS!ndisMIndicateNetBufferListsToOpen+0xab
    83b09a70 8e2c1c9c 00000000 8e20252a 86e86160 NDIS!ndisIndicateSortedNetBufferLists+0x4a
    83b09bec 8e20257f 89b7b438 00000000 00000000 NDIS!ndisMDispatchReceiveNetBufferLists+0x129
    83b09c08 8e2c18f9 89b7b438 8859d770 00000000 NDIS!ndisMTopReceiveNetBufferLists+0x2c
    83b09c24 8e20254a 89b7b438 8859d770 00000000 NDIS!ndisMIndicateReceiveNetBufferListsInternal+0x27
    83b09c40 a575471f 89b7b438 8859d770 00000000 NDIS!NdisMIndicateReceiveNetBufferLists+0x20
    WARNING: Stack unwind information not available. Following frames may be wrong.
    83b09c88 a575377e 00000000 a57536fe 00000000 E1G60I32+0x171f
    83b09ca0 8e2c1204 01e86160 00000000 00000000 E1G60I32+0x77e
    83b09cc4 8e202468 8973a5fc 00000000 00000000 NDIS!ndisMiniportDpc+0x81
    83b09ce8 83abe5a2 8973a5fc 89b7b438 00000000 NDIS!ndisInterruptDpc+0xc4
    83b09d50 83abc77d 00000000 0000000e 00000000 nt!KiRetireDpcList+0x147
    83b09d54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x49


    STACK_COMMAND: kb

    FOLLOWUP_IP:
    smb!SmbPrepareReceiveIrp+70
    9350847e 89481c mov dword ptr [eax+1Ch],ecx

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: smb!SmbPrepareReceiveIrp+70

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: smb

    IMAGE_NAME: smb.sys

    DEBUG_FLR_IMAGE_TIMESTAMP: 49e02062

    FAILURE_BUCKET_ID: 0xD1_smb!SmbPrepareReceiveIrp+70

    BUCKET_ID: 0xD1_smb!SmbPrepareReceiveIrp+70

    Followup: MachineOwner
    ---------
     
  2. 2013/10/28
    Arie

    Arie Administrator Administrator Staff

    Joined:
    2001/12/27
    Messages:
    15,174
    Likes Received:
    412
    Try running your dump trough our Dump Data collection tool

    Only one dump available? If more then one, all pointing to the same fault or all different. If all different that'll suggest a hardware failure.
     
    Arie,
    #2

  3. to hide this advert.

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.