none
Microsoft Windows Server 2008 R2 Standard 意外关闭 RRS feed

  • 问题

  • 日志名称:          System
    来源:            EventLog
    日期:            2014/6/20 19:53:53
    事件 ID:         6008
    任务类别:          无
    级别:            错误
    关键字:           经典
    用户:            暂缺
    计算机:           mr003
    描述:
    上一次系统的 19:49:31 在 ?2014/?6/?20 上的关闭是意外的。
    事件 Xml:
    <Event xmlns=
      <System>
        <Provider Name="EventLog" />
        <EventID Qualifiers="32768">6008</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-06-21T07:53:53.000000000Z" />
        <EventRecordID>88026</EventRecordID>
        <Channel>System</Channel>
        <Computer>mr003</Computer>
        <Security />
      </System>
      <EventData>
        <Data>19:49:31</Data>
        <Data>?2014/?6/?20</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>697757</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Binary>DE07060005001400130031001F001B00DE07060006001500070031001F001B003C0000003C000000000000000000000000000000000000000100000000000000</Binary>
      </EventData>
    </Event>
    日志名称:          System
    来源:            Microsoft-Windows-WER-SystemErrorReporting
    日期:            2014/6/20 19:53:55
    事件 ID:         1001
    任务类别:          无
    级别:            错误
    关键字:           经典
    用户:            暂缺
    计算机:           MR003
    描述:
    计算机已经从检测错误后重新启动。检测错误: 0x000000d1 (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xfffff88000e106fd)。已将转储的数据保存在: C:\Windows\MEMORY.DMP。报告 ID: 062014-41745-01。
    事件 Xml:
    <Event xmlns=
      <System>
        <Provider Name="Microsoft-Windows-WER-SystemErrorReporting" Guid="{ABCE23E7-DE45-4366-8631-84FA6C525952}" EventSourceName="BugCheck" />
        <EventID Qualifiers="16384">1001</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-06-21T07:53:55.000000000Z" />
        <EventRecordID>88030</EventRecordID>
        <Correlation />
        <Execution ProcessID="0" ThreadID="0" />
        <Channel>System</Channel>
        <Computer>MR003</Computer>
        <Security />
      </System>
      <EventData>
        <Data Name="param1">0x000000d1 (0x0000000000000028, 0x0000000000000002, 0x0000000000000000, 0xfffff88000e106fd)</Data>
        <Data Name="param2">C:\Windows\MEMORY.DMP</Data>
        <Data Name="param3">062014-41745-01</Data>
      </EventData>
    </Event>
    2014年6月23日 2:16

答案

全部回复

  • *******************************************************************************
    *                                                                             *
    *                        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: 0000000000000028, memory referenced
    Arg2: 0000000000000002, IRQL
    Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
    Arg4: fffff88000e106fd, address which referenced memory

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


    READ_ADDRESS:  0000000000000028

    CURRENT_IRQL:  2

    FAULTING_IP:
    NETIO!RtlCopyBufferToMdl+1d
    fffff880`00e106fd 448b5228        mov     r10d,dword ptr [rdx+28h]

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    BUGCHECK_STR:  0xD1

    PROCESS_NAME:  System

    TRAP_FRAME:  fffff8800d20c720 -- (.trap 0xfffff8800d20c720)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=fffff8800d20c940 rbx=0000000000000000 rcx=0000000000000000
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff88000e106fd rsp=fffff8800d20c8b0 rbp=fffff8800d20c9d8
     r8=00000000fffffea4  r9=000000000000015c r10=0000000000000000
    r11=fffffa802a77dc00 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    NETIO!RtlCopyBufferToMdl+0x1d:
    fffff880`00e106fd 448b5228        mov     r10d,dword ptr [rdx+28h] ds:6000:00000000`00000028=????????
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff800018c2169 to fffff800018c2bc0

    STACK_TEXT: 
    fffff880`0d20c5d8 fffff800`018c2169 : 00000000`0000000a 00000000`00000028 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
    fffff880`0d20c5e0 fffff800`018c0de0 : fffffa80`2859adb0 00000000`00000006 fffffa80`2859adb0 00000000`0000015c : nt!KiBugCheckDispatch+0x69
    fffff880`0d20c720 fffff880`00e106fd : fffffa80`29e36c10 00000000`00000000 00000000`00000000 fffff880`0184a825 : nt!KiPageFault+0x260
    fffff880`0d20c8b0 fffff880`018a84eb : fffffa80`1033e150 fffff880`01876802 00000000`00000000 fffffa80`179ed2d0 : NETIO!RtlCopyBufferToMdl+0x1d
    fffff880`0d20c910 fffff880`018740f6 : fffffa80`2a77dc00 00000000`00000000 fffffa80`179ed2d0 00000000`c0e82e7e : tcpip! ?? ::FNODOBFM::`string'+0x1bb3f
    fffff880`0d20c980 fffff880`018636b8 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`00f3b17b : tcpip!TcpTcbCarefulDatagram+0x1a46
    fffff880`0d20cb30 fffff880`0186297a : fffffa80`179ed2d0 fffff880`0185b800 fffffa80`101f7a00 00000000`00000000 : tcpip!TcpTcbReceive+0x37c
    fffff880`0d20cc40 fffff880`01863aeb : fffffa80`11fbaa22 fffffa80`10389000 00000000`00000000 00000000`00000000 : tcpip!TcpMatchReceive+0x1fa
    fffff880`0d20cd90 fffff880`0185bf17 : fffffa80`10382200 fffffa80`101f0e90 fffffa80`00005000 00000000`00000000 : tcpip!TcpPreValidatedReceive+0x36b
    fffff880`0d20ce60 fffff880`0185ba8a : 00000000`00000000 fffff880`0196e9a0 fffff880`0d20d020 fffffa80`1178b2a0 : tcpip!IppDeliverListToProtocol+0x97
    fffff880`0d20cf20 fffff880`0185b089 : 00000000`00000000 00000000`00000000 fffff880`0d20cf00 fffff880`0d20d010 : tcpip!IppProcessDeliverList+0x5a
    fffff880`0d20cfc0 fffff880`01858d2f : 00000000`774c2465 fffff880`0196e9a0 fffff880`0196e9a0 00000000`00000000 : tcpip!IppReceiveHeaderBatch+0x23a
    fffff880`0d20d0a0 fffff880`01858302 : fffffa80`117f6ed0 00000000`00000000 fffffa80`117e0400 fffff880`00000001 : tcpip!IpFlcReceivePackets+0x64f
    fffff880`0d20d2a0 fffff880`018cabca : 00000000`00000000 fffff880`0d20d420 fffffa80`117e0400 fffff880`068300bd : tcpip!FlpReceiveNonPreValidatedNetBufferListChain+0x2b2
    fffff880`0d20d380 fffff800`018ce878 : 00000000`00000002 00000000`00000018 fffffa80`24fe4060 00000000`00000001 : tcpip! ?? ::FNODOBFM::`string'+0x49ca2
    fffff880`0d20d3d0 fffff880`01857e22 : fffff880`01857650 00000000`00001000 00000000`00000800 fffffa80`11e86001 : nt!KeExpandKernelStackAndCalloutEx+0xd8
    fffff880`0d20d4b0 fffff880`00f3b0eb : fffffa80`117f2010 00000000`00000000 fffffa80`116ce1a0 fffff880`0d20d5b9 : tcpip!FlReceiveNetBufferListChain+0xb2
    fffff880`0d20d520 fffff880`00f04ad6 : fffffa80`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NDIS!ndisMIndicateNetBufferListsToOpen+0xdb
    fffff880`0d20d590 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : NDIS!ndisMDispatchReceiveNetBufferLists+0x1d6


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    NETIO!RtlCopyBufferToMdl+1d
    fffff880`00e106fd 448b5228        mov     r10d,dword ptr [rdx+28h]

    SYMBOL_STACK_INDEX:  3

    SYMBOL_NAME:  NETIO!RtlCopyBufferToMdl+1d

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: NETIO

    IMAGE_NAME:  NETIO.SYS

    DEBUG_FLR_IMAGE_TIMESTAMP:  5294760d

    FAILURE_BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d

    BUCKET_ID:  X64_0xD1_NETIO!RtlCopyBufferToMdl+1d

    Followup: MachineOwner

    2014年6月23日 2:52
  • 您好,

    根据您提供的信息,很可能是由网卡驱动导致的。请至官网下载安装最新的驱动程序。

    Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

    http://msdn.microsoft.com/zh-cn/library/windows/hardware/ff560244(v=vs.85).aspx

    谢谢。


    Jeremy Wu

    TechNet Community Support

    2014年6月25日 9:12
    版主