none
Server 2012 R2 Hyper-V VM频繁蓝屏 RRS feed

  • 问题

  • 最近Server 2012 R2 Hyper-V中的server 2012 R2虚机经常运行过程中蓝屏重启,频率1-3小时一次。大部分报错都是PAGE_FAULT_IN_NONPAGED_AREA (50) srv.sys

    下面是debug信息,谁能指导一下怎样修复该问题:


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


    Loading Dump File [D:\Minidump\052619-15390-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: srv*
    Executable search path is: 
    Windows 8.1 Kernel Version 9600 MP (16 procs) Free x64
    Product: LanManNt, suite: TerminalServer SingleUserTS
    Built by: 9600.17415.amd64fre.winblue_r4.141028-1500
    Machine Name:
    Kernel base = 0xfffff802`a1276000 PsLoadedModuleList = 0xfffff802`a154f250
    Debug session time: Sun May 26 07:51:31.095 2019 (UTC + 8:00)
    System Uptime: 0 days 0:06:49.443
    Loading Kernel Symbols
    ...............................................................
    ............................................................
    Loading User Symbols
    Loading unloaded module list
    ......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {ffffe0013aab7000, 1, fffff80016b74360, 0}


    Could not read faulting driver name
    Probably caused by : srv.sys ( srv!SrvOs2FeaToNt+48 )

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

    1: kd> 
    Implicit thread is now ffffe800`0b344880
    1: kd> 
    Implicit thread is now ffffe800`0b344880
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except.
    Typically the address is just plain bad or it is pointing at freed memory.
    Arguments:
    Arg1: ffffe0013aab7000, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff80016b74360, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000000, (reserved)

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


    Could not read faulting driver name

    KEY_VALUES_STRING: 1


    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  9600.17415.amd64fre.winblue_r4.141028-1500

    SYSTEM_MANUFACTURER:  Microsoft Corporation

    VIRTUAL_MACHINE:  HyperV

    SYSTEM_PRODUCT_NAME:  Virtual Machine

    SYSTEM_SKU:  None

    SYSTEM_VERSION:  Hyper-V UEFI Release v1.0

    BIOS_VENDOR:  Microsoft Corporation

    BIOS_VERSION:  Hyper-V UEFI Release v1.0

    BIOS_DATE:  11/26/2012

    BASEBOARD_MANUFACTURER:  Microsoft Corporation

    BASEBOARD_PRODUCT:  Virtual Machine

    BASEBOARD_VERSION:  Hyper-V UEFI Release v1.0

    DUMP_TYPE:  2

    BUGCHECK_P1: ffffe0013aab7000

    BUGCHECK_P2: 1

    BUGCHECK_P3: fffff80016b74360

    BUGCHECK_P4: 0

    WRITE_ADDRESS: GetUlongPtrFromAddress: unable to read from fffff802a15d9298
    GetUlongPtrFromAddress: unable to read from fffff802a15d9520
     ffffe0013aab7000 Nonpaged pool

    FAULTING_IP: 
    srv!SrvOs2FeaToNt+48
    fffff800`16b74360 c60300          mov     byte ptr [rbx],0

    MM_INTERNAL_CODE:  0

    CPU_COUNT: 10

    CPU_MHZ: 834

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 3e

    CPU_STEPPING: 4

    CPU_MICROCODE: 6,3e,4,0 (F,M,S,R)  SIG: FFFFFFFF'00000000 (cache) FFFFFFFF'00000000 (init)

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT_SERVER

    BUGCHECK_STR:  AV

    PROCESS_NAME:  System

    CURRENT_IRQL:  0

    ANALYSIS_SESSION_HOST:  WIN10

    ANALYSIS_SESSION_TIME:  05-26-2019 09:39:22.0948

    ANALYSIS_VERSION: 10.0.17134.12 amd64fre

    TRAP_FRAME:  ffffd0014bfbe700 -- (.trap 0xffffd0014bfbe700)
    NOTE: The trap frame does not contain all registers.
    Some register values may be zeroed or incorrect.
    rax=0000000000000000 rbx=0000000000000000 rcx=ffffe0013aab7000
    rdx=ffffc0002d5ed082 rsi=0000000000000000 rdi=0000000000000000
    rip=fffff80016b74360 rsp=ffffd0014bfbe890 rbp=ffffc0002d5ed07d
     r8=0000000000000000  r9=0000000000000000 r10=0000000000000200
    r11=ffffe0013aab7000 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei ng nz na po nc
    srv!SrvOs2FeaToNt+0x48:
    fffff800`16b74360 c60300          mov     byte ptr [rbx],0 ds:00000000`00000000=??
    Resetting default scope

    LAST_CONTROL_TRANSFER:  from fffff802a13f4bd2 to fffff802a13c69a0

    STACK_TEXT:  
    ffffd001`4bfbe498 fffff802`a13f4bd2 : 00000000`00000050 ffffe001`3aab7000 00000000`00000001 ffffd001`4bfbe700 : nt!KeBugCheckEx
    ffffd001`4bfbe4a0 fffff802`a12ce2b9 : 00000000`00000001 ffffe001`38a99900 ffffd001`4bfbe700 fffff802`a1364bc2 : nt! ?? ::FNODOBFM::`string'+0x1dd22
    ffffd001`4bfbe540 fffff802`a13d0c2f : 00000000`00000001 ffffe001`3aab7000 00000000`00000200 fffff802`a151a4d3 : nt!MmAccessFault+0x769
    ffffd001`4bfbe700 fffff800`16b74360 : 00000000`00000000 00000000`00000010 ffffd001`4bfbe9b8 ffffd001`4bfbe9b0 : nt!KiPageFault+0x12f
    ffffd001`4bfbe890 fffff800`16b742a5 : ffffc000`2d5ed07d ffffe001`3aab6ff8 00000000`00000010 ffffc000`2d5f5138 : srv!SrvOs2FeaToNt+0x48
    ffffd001`4bfbe8c0 fffff800`16b9569b : ffffe001`3a9a1010 00000000`00000000 ffffc000`2d5e5010 ffffd001`4d646180 : srv!SrvOs2FeaListToNt+0x125
    ffffd001`4bfbe910 fffff800`16b9e8ba : 00000000`00000000 fffff800`00008fe8 ffffe001`3aaae010 ffffe001`3a9a1010 : srv!SrvSmbOpen2+0xc3
    ffffd001`4bfbe9b0 fffff800`16ba1b2e : ffffe800`0b3d1240 ffffe001`3a9a1010 ffffc000`2d5e5010 00000000`00000002 : srv!ExecuteTransaction+0x2ca
    ffffd001`4bfbe9f0 fffff800`16b2f84f : ffffe800`00000000 ffffe001`00000000 00000000`00000038 00000000`0000f149 : srv!SrvSmbTransactionSecondary+0x40b
    ffffd001`4bfbea90 fffff800`16b2fa20 : ffffe001`3a9a1010 00000000`00000000 ffffe001`3a9a1a80 fffff800`16b3d010 : srv!SrvProcessSmb+0x237
    ffffd001`4bfbeb10 fffff800`16b6eac8 : ffffe800`0b355340 ffffe001`3a9a1010 00000000`00000000 ffffe001`3a9a1020 : srv!SrvRestartReceive+0x114
    ffffd001`4bfbeb50 fffff802`a178ed92 : 00000000`00000000 ffffe800`0b355340 00000000`00000080 ffffe001`39da4e00 : srv!WorkerThread+0x5248
    ffffd001`4bfbebd0 fffff802`a1377c70 : ffffe800`0b344880 ffffe800`0b344880 1fbafffa`deb2058d 8de8cb8b`44000000 : nt!IopThreadStart+0x26
    ffffd001`4bfbec00 fffff802`a13ccfc6 : ffffd001`4d68c180 ffffe800`0b344880 ffffd001`4d6985c0 fffa58e8`e8cf8b48 : nt!PspSystemThreadStartup+0x58
    ffffd001`4bfbec60 00000000`00000000 : ffffd001`4bfbf000 ffffd001`4bfb9000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


    THREAD_SHA1_HASH_MOD_FUNC:  9fc67a809a80c1143874aa0b8e74457296ca0384

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  5338ea5633c7cc4256ea37dbe681dc446cb13b44

    THREAD_SHA1_HASH_MOD:  8f10e91895468b5b2a56df2106350f23f731e5ce

    FOLLOWUP_IP: 
    srv!SrvOs2FeaToNt+48
    fffff800`16b74360 c60300          mov     byte ptr [rbx],0

    FAULT_INSTR_CODE:  f0003c6

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  srv!SrvOs2FeaToNt+48

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: srv

    IMAGE_NAME:  srv.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  53d0f15f

    IMAGE_VERSION:  6.3.9600.17238

    STACK_COMMAND:  .thread ; .cxr ; kb

    BUCKET_ID_FUNC_OFFSET:  48

    FAILURE_BUCKET_ID:  AV_srv!SrvOs2FeaToNt

    BUCKET_ID:  AV_srv!SrvOs2FeaToNt

    PRIMARY_PROBLEM_CLASS:  AV_srv!SrvOs2FeaToNt

    TARGET_TIME:  2019-05-25T23:51:31.000Z

    OSBUILD:  9600

    OSSERVICEPACK:  17415

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  272

    PRODUCT_TYPE:  2

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 8.1

    OSEDITION:  Windows 8.1 LanManNt TerminalServer SingleUserTS

    OS_LOCALE:  

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2014-10-29 08:38:48

    BUILDDATESTAMP_STR:  141028-1500

    BUILDLAB_STR:  winblue_r4

    BUILDOSVER_STR:  6.3.9600.17415.amd64fre.winblue_r4.141028-1500

    ANALYSIS_SESSION_ELAPSED_TIME:  985

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:av_srv!srvos2featont

    FAILURE_ID_HASH:  {d5f1a37d-2c94-f55b-5042-7a5dbaa092e1}

    Followup:     MachineOwner
    ---------
    2019年5月26日 1:46

全部回复

  • 你好,

    根据您提供的dump文件,查看错误提示和栈的信息。请关闭smb1.0协议查看。

    对于客户端操作系统:
    1. 打开 "控制面板", 单击 "程序", 然后单击 "打开或关闭 Windows 功能"。
    2. 在 Windows 功能窗口中, 清除 SMB1.0/cifs 文件共享支持复选框, 然后单击 "确定" 关闭窗口。
    3. 重新启动系统。

    对于服务器操作系统:
    1. 打开服务器管理器, 然后单击 "管理" 菜单, 然后选择 "删除角色和功能"。
    2. 在 "功能" 窗口中, 清除 SMB1.0/cifs 文件共享支持复选框, 然后单击 "确定" 关闭窗口。
    3. 重新启动系统。

    希望对您有帮助,如果回答是有帮助的, 请将其标记为答案, 可以帮助其他有相同问题的社区成员, 并快速找到有用的答复。


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

    2019年5月26日 10:10
  • 你好,
    几天没收到你的留言了, 请问问题有什么进展吗?
    我正在建议有帮助的答复为 "答案"。请随时尝试一下, 让我知道结果。如果回答是有帮助的, 请将其标记为答案, 可以帮助其他有相同问题的社区成员, 并快速找到有用的答复。

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

    2019年5月31日 9:43