none
windows2008R2不定期自动重启,debug日志,请各位帮忙看看是否是驱动引起的,谢谢~~ RRS feed

  • 常规讨论

  •  以下为DEBUG工具分析结果,请问是否是Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys这个驱动不兼容造成的,谢谢~~

    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Users\hpms\Desktop\服务器重启动\Minidump\070612-285918-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*d:/temp/*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (64 procs) Free x64
    Product: Server, suite: Enterprise TerminalServer SingleUserTS
    Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
    Machine Name:
    Kernel base = 0xfffff800`0260f000 PsLoadedModuleList = 0xfffff800`02854e90
    Debug session time: Fri Jul  6 12:49:48.940 2012 (GMT+8)
    System Uptime: 0 days 14:16:38.892
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........
    Loading User Symbols
    Loading unloaded module list
    .......
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 124, {0, fffffa801abc3028, b6000000, 115}

    Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for intelppm.sys
    *** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
    Probably caused by : hardware

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

    51: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    WHEA_UNCORRECTABLE_ERROR (124)
    A fatal hardware error has occurred. Parameter 1 identifies the type of error
    source that reported the error. Parameter 2 holds the address of the
    WHEA_ERROR_RECORD structure that describes the error conditon.
    Arguments:
    Arg1: 0000000000000000, Machine Check Exception
    Arg2: fffffa801abc3028, Address of the WHEA_ERROR_RECORD structure.
    Arg3: 00000000b6000000, High order 32-bits of the MCi_STATUS value.
    Arg4: 0000000000000115, Low order 32-bits of the MCi_STATUS value.

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


    BUGCHECK_STR:  0x124_GenuineIntel

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  DRIVER_FAULT_SERVER_MINIDUMP

    PROCESS_NAME:  System

    CURRENT_IRQL:  f

    STACK_TEXT: 
    fffff880`0387b958 fffff800`02c0ba3b : 00000000`00000124 00000000`00000000 fffffa80`1abc3028 00000000`b6000000 : nt!KeBugCheckEx
    fffff880`0387b960 fffff800`0279c7d3 : 00000000`00000001 fffffa80`1a5ffa50 00000000`00000000 fffffa80`1a5ffaa0 : hal!HalBugCheckSystem+0x1e3
    fffff880`0387b9a0 fffff800`02c0b700 : 00000000`00000728 fffffa80`1a5ffa50 fffff880`0387bd30 fffff880`0387bd00 : nt!WheaReportHwError+0x263
    fffff880`0387ba00 fffff800`02c0b052 : fffffa80`1a5ffa50 fffff880`0387bd30 fffffa80`1a5ffa50 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff880`0387bb50 fffff800`02c0af0d : 00000000`00000040 00000000`00000001 fffff880`0387bdb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff880`0387bb90 fffff800`02bfee88 : 00000000`00000002 fffff880`03872180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff880`0387bbc0 fffff800`0268df2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff880`0387bbf0 fffff800`0268dd93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`0387bd30 fffff880`013e1c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    fffff880`0389bc98 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x2c61


    STACK_COMMAND:  kb

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME:  hardware

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

    BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

    51: kd> lmvm hardware
    start             end                 module name
    51: kd> kb
    RetAddr           : Args to Child                                                           : Call Site
    fffff800`02c0ba3b : 00000000`00000124 00000000`00000000 fffffa80`1abc3028 00000000`b6000000 : nt!KeBugCheckEx
    fffff800`0279c7d3 : 00000000`00000001 fffffa80`1a5ffa50 00000000`00000000 fffffa80`1a5ffaa0 : hal!HalBugCheckSystem+0x1e3
    fffff800`02c0b700 : 00000000`00000728 fffffa80`1a5ffa50 fffff880`0387bd30 fffff880`0387bd00 : nt!WheaReportHwError+0x263
    fffff800`02c0b052 : fffffa80`1a5ffa50 fffff880`0387bd30 fffffa80`1a5ffa50 00000000`00000000 : hal!HalpMcaReportError+0x4c
    fffff800`02c0af0d : 00000000`00000040 00000000`00000001 fffff880`0387bdb0 00000000`00000000 : hal!HalpMceHandler+0x9e
    fffff800`02bfee88 : 00000000`00000002 fffff880`03872180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
    fffff800`0268df2c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
    fffff800`0268dd93 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
    fffff880`013e1c61 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
    00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x2c61
    51: kd> analyze -v
    *** WARNING: Unable to verify timestamp for ds4utm.sys
    *** ERROR: Module load completed but symbols could not be loaded for ds4utm.sys
    *** WARNING: Unable to verify timestamp for ds4dsm.sys
    *** ERROR: Module load completed but symbols could not be loaded for ds4dsm.sys
    *** WARNING: Unable to verify timestamp for bxvbda.sys
    *** ERROR: Module load completed but symbols could not be loaded for bxvbda.sys
    *** WARNING: Unable to verify timestamp for amdxata.sys
    *** ERROR: Module load completed but symbols could not be loaded for amdxata.sys
    *** WARNING: Unable to verify timestamp for SYMEVENT64x86.SYS
    *** ERROR: Module load completed but symbols could not be loaded for SYMEVENT64x86.SYS
    *** WARNING: Unable to verify timestamp for ql2300.sys
    *** ERROR: Module load completed but symbols could not be loaded for ql2300.sys
    *** WARNING: Unable to verify timestamp for dump_ql2300.sys
    *** ERROR: Module load completed but symbols could not be loaded for dump_ql2300.sys
    *** WARNING: Unable to verify timestamp for

    2012年7月18日 2:36

全部回复

  • 您好!

    由于对于自动重启问题进行排错的步骤比较复杂,很可能需要分析dump文件,我们无法在论坛中为您提供技术支持。为了让您的问题得到及时解决,我建议您使用微软为正版用户提供的8008203800技术支持专线,以便于更好的沟通和交流。以下我提供一些建议,仅供您参考:

    1. 我建议您尝试一次Clean Boot,如果启动的程序太多,这使系统资源消耗殆尽,使个别程序需要的数据在内存或虚拟内存中找不到,也会出现异常错误。

    Clean Boot具体步骤:

    a. 运行MSCONFIG

    b. 在常规下选择 选择性启动。

    c. 然后清除Process System.ini File, Process Win.ini FileLoad Startup Items 的复选框,但是保留使用原始Boot.ini

    d. 在服务下,先点隐藏所有windows 服务,然后选择 disable all

    e. 然后重新启动。观察问题是否依旧发生。

    2. 有些应用程序需调用特定版本的动态链接库DLL,如果在安装软件时,旧版本的DLL覆盖了新版本的DLL,或者删除应用程序时,误删了有用的DLL文件,就可能使上述调用失败,从而出现“蓝屏”。不妨重新安装试一试。如果安装了新的硬件常常出现“蓝屏”,那多半与主板的BIOS或驱动程序太旧有关,以致不能很好支持硬件。如果你的主板支持BIOS升级,应尽快升级到最新版本或安装最新的设备驱动程序。

    3. 硬件故障也会引起的蓝屏问题,建议您先卸载最近安装的硬件,察看问题是否依然存在。

    4. 到以下网站做一个病毒的在线扫描,这些在线扫描有时候是非常有用的,因为机器上的防病毒软件也有可能被感染,但是在线查毒的引擎不会被感染:
    Trend
    http://www.housecall.antivirus.com

    MacAfee:
    http://www.mcafee.com

    感谢您的理解和支持。


    如果您对我们的论坛在线支持服务有任何的意见或建议,请通过邮件告诉我们。
    Description: Description: TechNet 论坛好帮手立刻免费下载  TechNet 论坛好帮手

    2012年7月18日 8:34
    版主
  • WHEA_UNCORRECTABLE_ERROR,发生了Machine Check Exception。。。硬件问题!

    把内存的位置fffffa801abc3028的数据dump出来吧,长度为WHEA_ERROR_RECORD structure的长度,试试看命令dt /r WHEA_ERROR_RECORD fffffa801abc3028

    不行的话直接dd L长度,具体长度自己MSDN里读一下这个结构体算一下吧。

    然后找硬件厂商,进而找Intel翻译这段信息吧。

    弱弱补一句,如果是我遇到这种问题,硬件没过保的话直接找厂商换硬件,查问题比较累,因为大多数人都不懂。。。

    • 已编辑 Finy 2012年7月19日 3:00
    2012年7月19日 2:57