none
windows server 2012 r2 频繁重启 RRS feed

  • 问题

  • windows server 2012 r2   服务器频繁重启    

    能帮忙给看看dmp 吗 ,是什么原因造成的

    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\bug\060818-13578-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\mss*http://msdl.microsoft.com/download/symbols Executable search path is: D:\bug Windows 7 Kernel Version 9600 MP (2 procs) Free x64 Product: Server, suite: TerminalServer DataCenter SingleUserTS Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623 Machine Name: Kernel base = 0xfffff803`41484000 PsLoadedModuleList = 0xfffff803`4174b9b0 Debug session time: Fri Jun 8 16:37:41.521 2018 (UTC + 8:00) System Uptime: 0 days 4:46:38.229 Loading Kernel Symbols ............................................................... ................................................................ . Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a01f5891ee7521, b3b72bdee46e6430, fffff80002000000, 19} Map \SystemRoot\System32\drivers\ACPI.sys: Image region 400:40000 does not fit in mapping Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 1: 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 http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 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: a3a01f5891ee7521, Reserved Arg2: b3b72bdee46e6430, Reserved Arg3: fffff80002000000, Failure type dependent information Arg4: 0000000000000019, 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 Debugging Details: ------------------ BUGCHECK_STR: 0x109 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP PROCESS_NAME: csrss.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff803415d40a0 STACK_TEXT: ffffd000`20bdb188 00000000`00000000 : 00000000`00000109 a3a01f58`91ee7521 b3b72bde`e46e6430 fffff800`02000000 : nt!KeBugCheckEx STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: BAD_STACK Followup: MachineOwner --------- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\bug\042118-14640-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\mss*http://msdl.microsoft.com/download/symbols Executable search path is: D:\bug Windows 7 Kernel Version 9600 MP (2 procs) Free x64 Product: Server, suite: TerminalServer DataCenter SingleUserTS Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623 Machine Name: Kernel base = 0xfffff803`ed272000 PsLoadedModuleList = 0xfffff803`ed5399b0 Debug session time: Sat Apr 21 19:22:42.045 2018 (UTC + 8:00) System Uptime: 1 days 3:19:55.752 Loading Kernel Symbols ............................................................... ................................................................ ....... Loading User Symbols Loading unloaded module list ............. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a01f589200f947, b3b72bdee480e856, fffff80002441000, 19} Map \SystemRoot\System32\drivers\ACPI.sys: Image region 400:40000 does not fit in mapping Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 1: 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 http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 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: a3a01f589200f947, Reserved Arg2: b3b72bdee480e856, Reserved Arg3: fffff80002441000, Failure type dependent information Arg4: 0000000000000019, 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 Debugging Details: ------------------ BUGCHECK_STR: 0x109 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP PROCESS_NAME: team.exe CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff803ed3c20a0 STACK_TEXT: ffffd000`207e89c8 00000000`00000000 : 00000000`00000109 a3a01f58`9200f947 b3b72bde`e480e856 fffff800`02441000 : nt!KeBugCheckEx STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 FAILURE_BUCKET_ID: X64_0x109_ANALYSIS_INCONCLUSIVE BUCKET_ID: X64_0x109_ANALYSIS_INCONCLUSIVE Followup: MachineOwner --------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\bug\060818-13234-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\mss*http://msdl.microsoft.com/download/symbols Executable search path is: D:\bug Windows 7 Kernel Version 9600 MP (2 procs) Free x64 Product: Server, suite: TerminalServer DataCenter SingleUserTS Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623 Machine Name: Kernel base = 0xfffff800`f3413000 PsLoadedModuleList = 0xfffff800`f36da9b0 Debug session time: Fri Jun 8 11:50:31.845 2018 (UTC + 8:00) System Uptime: 0 days 17:16:05.553 Loading Kernel Symbols ............................................................... ................................................................ . Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a01f5891ef557b, b3b72bdee46f449a, fffff800021b3000, 19} Map \SystemRoot\System32\drivers\ACPI.sys: Image region 400:40000 does not fit in mapping Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 0: 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 http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx 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: a3a01f5891ef557b, Reserved Arg2: b3b72bdee46f449a, Reserved Arg3: fffff800021b3000, Failure type dependent information Arg4: 0000000000000019, 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 Debugging Details: ------------------ BUGCHECK_STR: 0x109 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP PROCESS_NAME: System CURRENT_IRQL: 2 LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff800f35630a0 STACK_TEXT: ffffd000`209346c8 00000000`00000000 : 00000000`00000109 a3a01f58`91ef557b b3b72bde`e46f449a fffff800`021b3000 : nt!KeBugCheckEx STACK_COMMAND: kb SYMBOL_NAME: ANALYSIS_INCONCLUSIVE FOLLOWUP_NAME: MachineOwner MODULE_NAME: Unknown_Module IMAGE_NAME: Unknown_Image DEBUG_FLR_IMAGE_TIMESTAMP: 0 BUCKET_ID: BAD_STACK Followup: MachineOwner --------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Microsoft (R) Windows Debugger Version 6.12.0002.633 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\bug\042618-14875-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: SRV*C:\mss*http://msdl.microsoft.com/download/symbols Executable search path is: D:\bug Windows 7 Kernel Version 9600 MP (2 procs) Free x64 Product: Server, suite: TerminalServer DataCenter SingleUserTS Built by: 9600.16384.amd64fre.winblue_rtm.130821-1623 Machine Name: Kernel base = 0xfffff802`6e41b000 PsLoadedModuleList = 0xfffff802`6e6e29b0 Debug session time: Thu Apr 26 11:11:06.769 2018 (UTC + 8:00) System Uptime: 0 days 23:00:11.476 Loading Kernel Symbols ............................................................... ................................................................ ........ Loading User Symbols Loading unloaded module list ......... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a01f58942d26e9, b3b72bdee6ad1608, fffff800024ff000, 19} Map \SystemRoot\System32\drivers\ACPI.sys: Image region 400:40000 does not fit in mapping Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE ) Followup: MachineOwner --------- 1: kd>
    2018年6月9日 19:14

全部回复

  • 您好,

    对于蓝屏问题,首先我建议您尝试命令SFC scannow 和DISM online restorehealth以修复可能损坏的系统文件,如果该问题出现在最近有安装更新之后,也可以卸载更新看看是否有帮助。

    请您理解,分析蓝屏dump文件超出了我们论坛的支持范围,我建议您与微软客户服务中心取得联系,以获得更高效的支持。

    https://support.microsoft.com/zh-cn/gp/contactus81?Audience=Commercial

    感谢您的理解和支持。

    Best Regards,

    William


    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 Subscriber Support, contact tnmff@microsoft.com.

    2018年6月11日 8:55
    版主