none
Server 2012 R2系统每个小时都蓝屏重启问题,BUGCHECK_STR: 0x109 PROCESS_NAME: csrss.exe,这个109错误的原因是什么? RRS feed

  • 问题

  • 详细的dump信息如下:
    Microsoft (R) Windows Debugger Version 10.0.18362.1 AMD64
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\dengzhiqiang5\Desktop\Minidump\Minidump\120219-13406-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 (4 procs) Free x64
    Product: Server, suite: TerminalServer SingleUserTS
    Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
    Machine Name:
    Kernel base = 0xfffff800`fee7b000 PsLoadedModuleList = 0xfffff800`ff13f990
    Debug session time: Tue Dec  3 01:37:08.332 2019 (UTC + 8:00)
    System Uptime: 0 days 9:39:49.969
    Loading Kernel Symbols
    ..

    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.

    .............................................................
    ............................................................
    Loading User Symbols
    Loading unloaded module list
    .......
    For analysis of this file, run !analyze -v
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    CRITICAL_STRUCTURE_CORRUPTION (109)
    This bugcheck is generated when the kernel detects that critical kernel code or
    data have been corrupted. There are generally three causes for a corruption:
    1) A driver has inadvertently or deliberately modified critical kernel code
     or data. See 
    2) A developer attempted to set a normal kernel breakpoint using a kernel
     debugger that was not attached when the system was booted. Normal breakpoints,
     "bp", can only be set if the debugger is attached at boot time. Hardware
     breakpoints, "ba", can be set at any time.
    3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
    Arguments:
    Arg1: a3a01f5895cd27af, Reserved
    Arg2: b3b72bdee84d16b2, Reserved
    Arg3: 0000000000000003, Failure type dependent information
    Arg4: 0000000000000018, Type of corrupted region, can be
     0   : A generic data region
     1   : Modification of a function or .pdata
     2   : A processor IDT
     3   : A processor GDT
     4   : Type 1 process list corruption
     5   : Type 2 process list corruption
     6   : Debug routine modification
     7   : Critical MSR modification
     8   : Object type
     9   : A processor IVT
     a   : Modification of a system service function
     b   : A generic session data region
     c   : Modification of a session function or .pdata
     d   : Modification of an import table
     e   : Modification of a session import table
     f   : Ps Win32 callout modification
     10  : Debug switch routine modification
     11  : IRP allocator modification
     12  : Driver call dispatcher modification
     13  : IRP completion dispatcher modification
     14  : IRP deallocator modification
     15  : A processor control register
     16  : Critical floating point control register modification
     17  : Local APIC modification
     18  : Kernel notification callout modification
     19  : Loaded module list modification
     1a  : Type 3 process list corruption
     1b  : Type 4 process list corruption
     1c  : Driver object corruption
     1d  : Executive callback object modification
     1e  : Modification of module padding
     1f  : Modification of a protected process
     20  : A generic data region
     21  : A page hash mismatch
     22  : A session page hash mismatch
     23  : Load config directory modification
     24  : Inverted function table modification
     25  : Session configuration modification
     26  : An extended processor control register
     27  : Type 1 pool corruption
     28  : Type 2 pool corruption
     29  : Type 3 pool corruption
     2a  : Type 4 pool corruption
     2b  : Modification of a function or .pdata
     2c  : Image integrity corruption
     2d  : Processor misconfiguration
     2e  : Type 5 process list corruption
     2f  : Process shadow corruption
     30  : Retpoline code page corruption
     101 : General pool corruption
     102 : Modification of win32k.sys

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


    KEY_VALUES_STRING: 1


    PROCESSES_ANALYSIS: 1

    SERVICE_ANALYSIS: 1

    STACKHASH_ANALYSIS: 1

    TIMELINE_ANALYSIS: 1


    DUMP_CLASS: 1

    DUMP_QUALIFIER: 400

    BUILD_VERSION_STRING:  9600.16404.amd64fre.winblue_gdr.130913-2141

    SYSTEM_MANUFACTURER: 

    SYSTEM_PRODUCT_NAME: 

    SYSTEM_SKU:  SKU=NotProvided;ModelNam

    BIOS_VENDOR: 

    BIOS_VERSION:  2.5.0

    BIOS_DATE:  05/03/2018

    BASEBOARD_MANUFACTURER:

    BASEBOARD_PRODUCT:  0FRVY0

    BASEBOARD_VERSION:  A06

    DUMP_FILE_ATTRIBUTES: 0x8
      Kernel Generated Triage Dump

    DUMP_TYPE:  2

    BUGCHECK_P1: a3a01f5895cd27af

    BUGCHECK_P2: b3b72bdee84d16b2

    BUGCHECK_P3: 3

    BUGCHECK_P4: 18

    CPU_COUNT: 4

    CPU_MHZ: bb8

    CPU_VENDOR:  GenuineIntel

    CPU_FAMILY: 6

    CPU_MODEL: 5e

    CPU_STEPPING: 3

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

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  BAD_STACK_0x109

    BUGCHECK_STR:  0x109

    PROCESS_NAME:  csrss.exe

    CURRENT_IRQL:  2

    ANALYSIS_SESSION_HOST: 

    ANALYSIS_SESSION_TIME:  12-04-2019 13:48:39.0275

    ANALYSIS_VERSION: 10.0.18362.1 amd64fre

    STACK_TEXT: 
    ffffd000`28b6ef88 00000000`00000000 : 00000000`00000109 a3a01f58`95cd27af b3b72bde`e84d16b2 00000000`00000003 : nt!KeBugCheckEx


    THREAD_SHA1_HASH_MOD_FUNC:  81a83ae0317433a47fcc36991983df3b6e638b71

    THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6e16edd8c7dd677734fdbcd2397a2e35e9fae964

    THREAD_SHA1_HASH_MOD:  76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    STACK_COMMAND:  .thread ; .cxr ; kb

    BUCKET_ID:  BAD_STACK_0x109

    PRIMARY_PROBLEM_CLASS:  BAD_STACK_0x109

    FAILURE_BUCKET_ID:  BAD_STACK_0x109

    TARGET_TIME:  2019-12-02T17:37:08.000Z

    OSBUILD:  9600

    OSSERVICEPACK:  16404

    SERVICEPACK_NUMBER: 0

    OS_REVISION: 0

    SUITE_MASK:  272

    PRODUCT_TYPE:  3

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 8.1

    OSEDITION:  Windows 8.1 Server TerminalServer SingleUserTS

    OS_LOCALE: 

    USER_LCID:  0

    OSBUILD_TIMESTAMP:  2013-09-14 16:23:16

    BUILDDATESTAMP_STR:  130913-2141

    BUILDLAB_STR:  winblue_gdr

    BUILDOSVER_STR:  6.3.9600.16404.amd64fre.winblue_gdr.130913-2141

    ANALYSIS_SESSION_ELAPSED_TIME:  193d

    ANALYSIS_SOURCE:  KM

    FAILURE_ID_HASH_STRING:  km:bad_stack_0x109

    FAILURE_ID_HASH:  {b4d7023a-05c3-49b2-3ea4-6240fe57d90e}

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

    2019年12月4日 6:08

全部回复

  • 您好,

    可能是由于:Unknown_Image(ANALYSIS_INCONCLUSIVE)导致此转储文件无用。当内核检测到关键内核代码或数据已损坏时,将生成此Stop错误。您可以参考以下Microsoft文档获取更多信息:

    https://support.microsoft.com/en-us/help/2902739/stop-error-0x109-critical-structure-corruption-on-a-vmware-virtual-mac

    此外,关于Csrss.exe程序,请以安全模式启动以消除第三者原因,某些不兼容的应用程序或驱动程序可能会导致这种情况。

    希望能帮助到您。祝您生活愉快!
    最好的问候,

    Kiki


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


    2019年12月4日 7:04
  • 您好,

     

    很高兴可以帮助到您,您的问题解决了吗?

     

    如果认为回帖者的回答有所帮助,请将之标记为答复,这样可以帮助更多的用户获取有效信息。

     

    最好的祝福,

    Kiki


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


    2019年12月18日 1:59