none
windows server2012 R2重启问题,想各位帮忙系统重启的原因,以及解决方法,谢谢。 RRS feed

  • 问题

  • windows server2012 R2重启问题,想各位帮忙系统重启的原因,以及解决方法,谢谢。

    操作系统:windows server2012 R2

    问题描述:服务器重启

    想请教下,是什么原因导致系统重启。

    用WINDbg查看dmp文件如下:

    Use !analyze -v to get detailed debugging information.

    BugCheck 44, {fffffa800fe7e7d0, eae, 0, 0}

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

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

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

    MULTIPLE_IRP_COMPLETE_REQUESTS (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: fffffa800fe7e7d0, Address of the IRP
    Arg2: 0000000000000eae
    Arg3: 0000000000000000
    Arg4: 0000000000000000

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


    IRP_ADDRESS:  fffffa800fe7e7d0

    FOLLOWUP_IP:
    NETIO!NetioDereferenceNetBufferListChain+f3
    fffff880`00e60173 4c8b742440      mov     r14,qword ptr [rsp+40h]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR:  0x44

    PROCESS_NAME:  System

    CURRENT_IRQL:  2

    LAST_CONTROL_TRANSFER:  from fffff80001aa6b95 to fffff80001abcf00

    STACK_TEXT:  
    fffff800`03937718 fffff800`01aa6b95 : 00000000`00000044 fffffa80`0fe7e7d0 00000000`00000eae 00000000`00000000 : nt!KeBugCheckEx
    fffff800`03937720 fffff880`02ea94d2 : fffffa80`0f31e030 fffff800`01ac19fa 00000000`00000000 fffff880`00e604fb : nt! ?? ::FNODOBFM::`string'+0x3ed4e
    fffff800`03937800 fffff880`01e7b98e : fffffa80`12282a10 00000000`00000000 fffffa80`12282a10 00000000`00000000 : afd!WskProTLSendOrDisconnectComplete+0x72
    fffff800`03937860 fffff880`00e60173 : fffffa80`12216e00 fffffa80`0f5cfbb0 00000000`00000001 00000000`00000002 : tcpip!TcpTcbSendDatagramsComplete+0x1b4
    fffff800`039378c0 fffff880`01e75837 : fffffa80`122827d0 fffffa80`10fbb101 00000000`00000001 00000000`00000004 : NETIO!NetioDereferenceNetBufferListChain+0xf3
    fffff800`03937940 fffff880`00fa646f : fffff800`01c35e80 00000000`00000000 fffffa80`0f4591a0 fffff800`01ac55f7 : tcpip!FlSendNetBufferListChainComplete+0x37
    fffff800`03937970 fffff880`00fa65ad : fffffa80`00000000 fffffa80`1116c750 fffffa80`00000001 fffff880`00000000 : NDIS!ndisMSendCompleteNetBufferListsInternal+0x10f
    fffff800`03937a10 fffff880`034b6635 : 00000000`00000006 00000000`00000099 fffffa80`0f57b740 00000000`00000002 : NDIS!NdisMSendNetBufferListsComplete+0x6d
    fffff800`03937a50 00000000`00000006 : 00000000`00000099 fffffa80`0f57b740 00000000`00000002 fffffa80`1116c750 : e1r62x64+0x2c635
    fffff800`03937a58 00000000`00000099 : fffffa80`0f57b740 00000000`00000002 fffffa80`1116c750 fffffa80`0f594e20 : 0x6
    fffff800`03937a60 fffffa80`0f57b740 : 00000000`00000002 fffffa80`1116c750 fffffa80`0f594e20 fffffa80`00000002 : 0x99
    fffff800`03937a68 00000000`00000002 : fffffa80`1116c750 fffffa80`0f594e20 fffffa80`00000002 00000000`00000001 : 0xfffffa80`0f57b740
    fffff800`03937a70 fffffa80`1116c750 : fffffa80`0f594e20 fffffa80`00000002 00000000`00000001 00000000`00000000 : 0x2
    fffff800`03937a78 fffffa80`0f594e20 : fffffa80`00000002 00000000`00000001 00000000`00000000 fffff800`00000000 : 0xfffffa80`1116c750
    fffff800`03937a80 fffffa80`00000002 : 00000000`00000001 00000000`00000000 fffff800`00000000 00000100`00000001 : 0xfffffa80`0f594e20
    fffff800`03937a88 00000000`00000001 : 00000000`00000000 fffff800`00000000 00000100`00000001 00000000`00000001 : 0xfffffa80`00000002
    fffff800`03937a90 00000000`00000000 : fffff800`00000000 00000100`00000001 00000000`00000001 00000000`00000000 : 0x1


    STACK_COMMAND:  kb

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  NETIO!NetioDereferenceNetBufferListChain+f3

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: NETIO

    IMAGE_NAME:  NETIO.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc18a

    FAILURE_BUCKET_ID:  X64_0x44_NETIO!NetioDereferenceNetBufferListChain+f3

    BUCKET_ID:  X64_0x44_NETIO!NetioDereferenceNetBufferListChain+f3

    Followup: MachineOwner
    2016年1月25日 8:28

答案

  • 您好,

    由于DUMP文件的分析已经超出本论坛的支持范围,如果您需要进一步的解答,可以通过电话联系Microsoft Customer Support and Services (CSS)以获取相应的技术支持。

    根据DUMP 文件显示BugCheck 44。以下是关于该问题的建议,供您参考:
    1. 检查/安装Windows Update/hotfix,这将有助于一些已知问题的修复,以及系统性能的改善,参考MS14-031:适用于 Windows 的 TCP 安全更新说明:2014 年 6 月 10 日(包含NETIO.SYS的更新):https://support.microsoft.com/zh-cn/kb/2957189
    2. 检查/安装驱动更新。
    3. 如果问题之前有过更改操作,例如安装程序等,建议将更改撤销以确认情况。或者通过系统还原(如果有可用的备份)将设备还原到之前可以正常使用的某个时间状态。
    4. 执行全盘扫描/检查。
    5. 通过 “sfc /scannow”或其他工具检查/修复系统文件。

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    2016年1月26日 6:58
    版主