none
windows server 2008 r2报错0x00000050, 0x000000C5 RRS feed

  • 问题

  • 80 Critical OS 10/24/2019 19:58 10/24/2019 19:58 1 Operating System failure (Windows bug check, S 0xFFFFF80001C10611))
    79 Critical OS 10/23/2019 10:38 10/23/2019 10:38 1 Operating System failure (Windows bug check, S (0xFFFFFAB024A75000, 0x0000000000000001, 0xFFFFF88006D89585, 0x0000000000000000))
    2019年10月27日 13:22

全部回复

  • 您好,

    一般情况,对于错误:0x00000050,发生该错误的原因可能是由安装错误的系统服务或错误的驱动程序代码引起的。防病毒软件也会触发此错误,NTFS卷损坏也会触发此错误。更多细节您可以参考以下Microsoft文档:

    Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA

    对于错误:0x000000C5,该错误表示设备驱动程序有问题,正在运行的驱动程序错误或不兼容的最新驱动程序更新。如果最近更新了PC上的驱动程序,则可能要以安全模式重启PC并回滚到原始驱动程序。或者,如果您安装了原始驱动程序,请尝试将其更新为最新版本。此外,尝试禁用驱动验证程序,再重新运行Windows看错误是否还存在。

    希望能帮助到您!祝您生活愉快!

    最好的问候,

    Kiki Shi


    针对Windows 2008/2008R2的扩展支持将于2020年结束,之后微软将不再为其提供安全更新。点击此处或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》,把握良机完成云迁移并实现业务现代化。



    2019年10月28日 9:31
  • 您好!下面是windbg的内容!请帮分析一下具体原因!

    Loading Dump File [D:\3-4 JGT MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is: 
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (32 procs) Free x64
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`01a0c000 PsLoadedModuleList = 0xfffff800`01c51e90
    Debug session time: Thu Oct 24 20:15:54.834 2019 (UTC + 8:00)
    System Uptime: 1 days 3:42:54.390
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............
    Loading User Symbols

    Loading unloaded module list
    ....
    The context is partially valid. Only x86 user-mode context is available.
    The wow64exts extension must be loaded to access 32-bit state.
    .load wow64exts will do this if you haven't loaded it already.
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 50, {fffffab028431000, 1, fffff880073bb585, 0}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *** ERROR: Module load completed but symbols could not be loaded for srv.sys
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : srv.sys ( srv+6d585 )

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

    16.6: kd:x86> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

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

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

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT:  
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: srv

    FAULTING_MODULE: fffff80001a0c000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce794a5

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     fffffab028431000 

    FAULTING_IP: 
    srv+6d585
    fffff880`073bb585 c60300          mov     byte ptr [ebx],0

    MM_INTERNAL_CODE:  0

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

    STACK_TEXT:  
    00000000 00000000 00000000 00000000 00000000 0x0


    STACK_COMMAND:  .bugcheck ; kb

    FOLLOWUP_IP: 
    srv+6d585
    fffff880`073bb585 c60300          mov     byte ptr [ebx],0

    SYMBOL_NAME:  srv+6d585

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  srv.sys

    BUCKET_ID:  WRONG_SYMBOLS

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


    • 已编辑 beelitree 2019年10月28日 13:05
    2019年10月28日 12:54
  • ADDITIONAL_DEBUG_TEXT:  
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: srv

    FAULTING_MODULE: fffff80001a0c000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce794a5

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
     fffffab028431000 

    FAULTING_IP: 
    srv+6d585
    fffff880`073bb585 c60300          mov     byte ptr [ebx],0

    MM_INTERNAL_CODE:  0

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x50

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

    STACK_TEXT:  
    00000000 00000000 00000000 00000000 00000000 0x0


    STACK_COMMAND:  .bugcheck ; kb

    FOLLOWUP_IP: 
    srv+6d585
    fffff880`073bb585 c60300          mov     byte ptr [ebx],0

    SYMBOL_NAME:  srv+6d585

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  srv.sys

    BUCKET_ID:  WRONG_SYMBOLS

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

    16.6: kd:x86> 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............
    Loading User Symbols

    Loading unloaded module list
    ....
    16.6: kd:x86> 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............
    Loading User Symbols

    Loading unloaded module list
    ....
    16.6: kd:x86> 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............
    Loading User Symbols

    Loading unloaded module list
    ....
    16.6: kd:x86> 
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrnlmp.exe - 
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ............
    Loading User Symbols

    Loading unloaded module list
    ....
    16.6: kd:x86> lmvm srv
    start             end                 module name
    fffff880`0734e000 fffff880`073e7000   srv        (deferred)             
        Image path: \SystemRoot\System32\DRIVERS\srv.sys
        Image name: srv.sys
        Timestamp:        Sat Nov 20 17:28:05 2010 (4CE794A5)
        CheckSum:         00079B5F
        ImageSize:        00099000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    16.6: kd:x86> lmvm nt
    start             end                 module name
    fffff800`01a0c000 fffff800`01ff6000   nt         (export symbols)       ntkrnlmp.exe
        Loaded symbol image file: ntkrnlmp.exe
        Image path: ntkrnlmp.exe
        Image name: ntkrnlmp.exe
        Timestamp:        Sat Nov 20 17:30:02 2010 (4CE7951A)
        CheckSum:         0055CE0C
        ImageSize:        005EA000
        File version:     6.1.7601.17514
        Product version:  6.1.7601.17514
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrnlmp.exe
        OriginalFilename: ntkrnlmp.exe
        ProductVersion:   6.1.7601.17514
        FileVersion:      6.1.7601.17514 (win7sp1_rtm.101119-1850)
        FileDescription:  NT Kernel & System
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    2019年10月28日 14:28
  • 您好,

    请理解,根据论坛的安全政策,论坛不提供dump/log文件的分析。对于此类文件的分析诊断,您可能需要新开一个case,链接如下所示:

    https://support.microsoft.com/zh-cn/supportforbusiness/productselection

    希望能帮助到您!

    Kiki Shi


    针对Windows 2008/2008R2的扩展支持将于2020年结束,之后微软将不再为其提供安全更新。点击此处或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》,把握良机完成云迁移并实现业务现代化。



    2019年10月29日 6:13
  • 这个是从新安装windbg分析出来的,请看看信息够不够!
    16.6: kd:x86> !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: 28431000, memory referenced.
    Arg2: 00000001, value 0 = read operation, 1 = write operation.
    Arg3: 073bb585, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 00000000, (reserved)

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


    Could not read faulting driver name

    KEY_VALUES_STRING: 1


    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 401

    BUILD_VERSION_STRING:  7601.17514.amd64fre.win7sp1_rtm.101119-1850

    SYSTEM_MANUFACTURER:  HP

    SYSTEM_PRODUCT_NAME:  ProLiant DL388 Gen9

    SYSTEM_SKU:  827007-AA1

    BIOS_VENDOR:  HP

    BIOS_VERSION:  P89

    BIOS_DATE:  07/21/2019

    BASEBOARD_MANUFACTURER:  HP

    BASEBOARD_PRODUCT:  ProLiant DL388 Gen9

    DUMP_TYPE:  1

    BUGCHECK_P1: fffffab028431000

    BUGCHECK_P2: 1

    BUGCHECK_P3: fffff880073bb585

    BUGCHECK_P4: 0

    WRITE_ADDRESS: Unable to get MmSystemRangeStart
    Unable to get NonPagedPoolStart
    Unable to get PagedPoolStart
     28431000 

    FAULTING_IP: 
    srv!SrvOs2FeaToNt+45
    fffff880`073bb585 c60300          mov     byte ptr [ebx],0

    MM_INTERNAL_CODE:  0

    CPU_COUNT: 20

    CPU_MHZ: 831

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 4f

    CPU_STEPPING: 1

    CPU_MICROCODE: 6,0,0,0 (F,M,S,R)  SIG: B000038'00000000 (cache) B000038'00000000 (init)

    BUGCHECK_STR:  0x50

    CURRENT_IRQL:  0

    ANALYSIS_SESSION_HOST:  BEELI-THINK

    ANALYSIS_SESSION_TIME:  10-29-2019 14:26:06.0971

    ANALYSIS_VERSION: 10.0.17134.12 amd64fre

    IP_IN_FREE_BLOCK: 0

    LAST_CONTROL_TRANSFER:  from 00000000 to 00000000

    STACK_TEXT:  
    00000000 00000000 00000000 00000000 00000000 0x0


    FOLLOWUP_IP: 
    srv!SrvOs2FeaToNt+45
    fffff880`073bb585 c60300          mov     byte ptr [ebx],0

    FAULT_INSTR_CODE:  f0003c6

    SYMBOL_NAME:  srv!SrvOs2FeaToNt+45

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: srv

    IMAGE_NAME:  srv.sys

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ce794a5

    STACK_COMMAND:  .thread ; .cxr ; kb

    BUCKET_ID:  INVALID_KERNEL_CONTEXT_0x50

    DEFAULT_BUCKET_ID:  INVALID_KERNEL_CONTEXT_0x50

    PRIMARY_PROBLEM_CLASS:  INVALID_KERNEL_CONTEXT_0x50

    FAILURE_BUCKET_ID:  INVALID_KERNEL_CONTEXT_0x50

    TARGET_TIME:  2019-10-24T12:15:54.000Z

    OSBUILD:  7601

    OSSERVICEPACK:  1000

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  274

    PRODUCT_TYPE:  3

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 7

    OSEDITION:  Windows 7 Server (Service Pack 1) Enterprise TerminalServer SingleUserTS

    OS_LOCALE:  

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2010-11-20 17:30:02

    BUILDDATESTAMP_STR:  101119-1850

    BUILDLAB_STR:  win7sp1_rtm

    BUILDOSVER_STR:  6.1.7601.17514.amd64fre.win7sp1_rtm.101119-1850

    ANALYSIS_SESSION_ELAPSED_TIME:  58d

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:invalid_kernel_context_0x50

    FAILURE_ID_HASH:  {d2a21836-63d3-2ded-43fb-6fd9ff7f67d0}

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

    16.6: kd:x86> lmvm srv
    Browse full module list
    start    end        module name
    fffff880`0734e000 fffff880`073e7000   srv        (pdb symbols)          c:\mylocalsymbols\srv.pdb\3428624C8A6349449D13166A74208A902\srv.pdb
        Loaded symbol image file: srv.sys
        Image path: \SystemRoot\System32\DRIVERS\srv.sys
        Image name: srv.sys
        Browse all global symbols  functions  data
        Timestamp:        Sat Nov 20 02:28:05 2010 (4CE794A5)
        CheckSum:         00079B5F
        ImageSize:        00099000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
        Information from resource tables:
    2019年10月29日 6:29
  • 您好,

    我建议您尝试以下方法并检查是否有帮助:

    方法1:运行Microsoft安全扫描程序。

    Microsoft安全扫描程序是可免费下载的安全工具,可提供按需扫描并帮助删除病毒,间谍软件和其他恶意软件。它可以与您现有的防病毒软件一起使用。

    请参考以下链接:

    http://www.microsoft.com/security/scanner/zh-CN/default.aspx

    方法2:

    请参阅以下文章,并尝试故障排除方法:

    PAGE_FAULT_IN_NONPAGED_AREA

    https://msdn.microsoft.com/zh-CN/library/windows/hardware/ff559023(v=vs.85).aspx

    VIDEO_SCHEDULER_INTERNAL_ERROR

    https://msdn.microsoft.com/zh-CN/library/windows/hardware/ff557275(v=vs.85).aspx


    如果以上方法不起作用,那么建议您新开一个case以便更高效的解决您的问题,链接如下所示:

    https://support.microsoft.com/zh-cn/supportforbusiness/productselection

    希望能帮助到您!

    Kiki Shi



    针对Windows 2008/2008R2的扩展支持将于2020年结束,之后微软将不再为其提供安全更新。点击此处或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》,把握良机完成云迁移并实现业务现代化。


    2019年10月31日 7:59