询问者
windows 2008R2 企业版 在vaware环境中,最近一个礼拜一直频繁无故重启,在重启的时候CPU飙高占满,分配的cpu是4个sorcket,每个8核心,总共32核,内存64G。下面是debug的文件

问题
-
Kernel Summary Dump File: Kernel address space is available, User address space may not be available. Symbol search path is: srv* Executable search path is: 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`01c64000 PsLoadedModuleList = 0xfffff800`01ea9e90 Debug session time: Wed Sep 12 20:14:23.787 2018 (UTC + 8:00) System Uptime: 0 days 0:14:38.428 Loading Kernel Symbols ............................................................... ................................................................ .... Loading User Symbols Loading unloaded module list ..... ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck 109, {a3a039db8cbf959b, b3b74661df3de025, 13c0000082, 7} Probably caused by : ntkrnlmp.exe ( nt!KiSystemCall64+0 ) Followup: MachineOwner --------- nt!KeBugCheckEx: fffff800`01ce4640 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff880`02d9a5e0=0000000000000109 31: kd> Implicit thread is now fffffa82`f921ab60 31: 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: a3a039db8cbf959b, Reserved Arg2: b3b74661df3de025, Reserved Arg3: 00000013c0000082, Failure type dependent information Arg4: 0000000000000007, 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 101 : General pool corruption 102 : Modification of win32k.sys Debugging Details: ------------------ KEY_VALUES_STRING: 1 STACKHASH_ANALYSIS: 1 TIMELINE_ANALYSIS: 1 DUMP_CLASS: 1 DUMP_QUALIFIER: 401 BUILD_VERSION_STRING: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 SYSTEM_MANUFACTURER: VMware, Inc. VIRTUAL_MACHINE: VMware SYSTEM_PRODUCT_NAME: VMware Virtual Platform SYSTEM_VERSION: None BIOS_VENDOR: Phoenix Technologies LTD BIOS_VERSION: 6.00 BIOS_DATE: 04/14/2014 BASEBOARD_MANUFACTURER: Intel Corporation BASEBOARD_PRODUCT: 440BX Desktop Reference Platform BASEBOARD_VERSION: None DUMP_TYPE: 1 BUGCHECK_P1: a3a039db8cbf959b BUGCHECK_P2: b3b74661df3de025 BUGCHECK_P3: 13c0000082 BUGCHECK_P4: 7 FAULTING_IP: nt!KiSystemCall64+0 fffff800`01ce3640 0f01f8 swapgs CPU_COUNT: 20 CPU_MHZ: 855 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 25 CPU_STEPPING: 1 CPU_MICROCODE: 6,25,1,0 (F,M,S,R) SIG: 37'00000000 (cache) 37'00000000 (init) DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT BUGCHECK_STR: 0x109 PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_SESSION_HOST: DESKTOP-CURUCMK ANALYSIS_SESSION_TIME: 09-13-2018 10:42:57.0009 ANALYSIS_VERSION: 10.0.18206.1001 amd64fre STACK_TEXT: fffff880`02d9a5d8 00000000`00000000 : 00000000`00000109 a3a039db`8cbf959b b3b74661`df3de025 00000013`c0000082 : nt!KeBugCheckEx THREAD_SHA1_HASH_MOD_FUNC: 81a83ae0317433a47fcc36991983df3b6e638b71 THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 6e16edd8c7dd677734fdbcd2397a2e35e9fae964 THREAD_SHA1_HASH_MOD: 76cd06466d098060a9eb26e5fd2a25cb1f3fe0a3 FOLLOWUP_IP: nt!KiSystemCall64+0 fffff800`01ce3640 0f01f8 swapgs FAULT_INSTR_CODE: 65f8010f SYMBOL_NAME: nt!KiSystemCall64+0 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4ce7951a IMAGE_VERSION: 6.1.7601.17514 STACK_COMMAND: .thread ; .cxr ; kb FAILURE_BUCKET_ID: X64_0x109_7_c0000082__nt!KiSystemCall64+0 BUCKET_ID: X64_0x109_7_c0000082__nt!KiSystemCall64+0 PRIMARY_PROBLEM_CLASS: X64_0x109_7_c0000082__nt!KiSystemCall64+0 TARGET_TIME: 2018-09-12T12:14:23.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: 5c1 ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0x109_7_c0000082__nt!kisystemcall64+0 FAILURE_ID_HASH: {d1854b81-81de-8aca-b1ad-a0cd43922759} Followup: MachineOwner --------- 烦请大神解答一下问题是在什么地方,是否是cpu分配过高?
全部回复
-
您好,
感谢您的发帖。
请理解,为了彻底解决性能问题,我们通常需要调试日志文件。 不幸的是,调试超出了我们在论坛中所能做的。 我们这里只能提供一些通用的建议。如果问题仍然存在,则调试服务需要支持我们的产品服务团队。 我们建议您与Microsoft客户支持服务(CSS)联系以获得帮助,以便有效解决此问题。 要获取特定技术请求的电话号码,请查看下面列出的网站: https://support.microsoft.com/en-us/help/4051701/global-customer-service-phone-numbers
· 感谢您的理解和支持。
Best regards,
Lavilian
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. -
您好,
感谢您的回复。
通常,无故重启是由以下原因造成的:
不稳定的硬件设备、设备驱动过期、三方程序干扰、系统异常。在几天的时间内,是否有做过什么特殊的操作?比如说安装了某些驱动,更新了某些补丁/安装了某些软件。建议可以一步步的撤销之前的更改。
首先排除是由于驱动或者是补丁/应用程序导致的重启。
若在此期间并没有做过什么特殊的操作,并且排错之后还是依旧会出现无故重启的现象。那么就要考虑系统问题了。
另外,由于分析dump文件超出了论坛的支持范围,如果以上的常规排错没有解决问题同时问题比较紧急的话,建议您选用微软电话技术支持服务:800-820-3800。
请注意:由于论坛是公共开放的,任何人都可以看到您分享的信息,为了防止隐私信息被泄露,建议您把dump文件删除或者是涂黑。
感谢您的理解与支持。
Best regards,
Lavilian
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.- 已建议为答案 Lavilian LiModerator 2018年11月5日 8:59
-
您好,
不知以上信息是否对您有所帮助。
如果您需要我们的继续协助,您可以随时在该帖下回复。
Best Regards,
Lavilian
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. -
您好,
请问您的问题解决了吗?
如果您使用我们的解决方案解决了问题,请“标记为答案”以帮助其他社区成员快速找到有用的回复。
如果您使用自己的解决方案解决问题,请在此处分享您的经验和解决方案。 对于有类似问题的其他社区成员来说,这将非常有益。
如果不是,请回复并告诉我们当前的情况,以便提供进一步的帮助。
Best regards,Lavilian
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.