none
window 2008 蓝屏,请求帮助分析一下memory.dmp,请大神帮助 RRS feed

  • 问题

  • window 2008 R2 sp1

    Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64

    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [F:\BaiduNetdiskDownload\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*C:\Symbols*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`0221a000 PsLoadedModuleList = 0xfffff800`0245fe90
    Debug session time: Thu Feb 14 09:50:54.998 2019 (UTC + 8:00)
    System Uptime: 28 days 19:30:08.396
    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 1E, {ffffffffc000001d, fffffab024d15196, 0, ffffff00}

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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

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

    KMODE_EXCEPTION_NOT_HANDLED (1e)
    This is a very common bugcheck.  Usually the exception address pinpoints
    the driver/function that caused the problem.  Always note this address
    as well as the link date of the driver/image that contains this address.
    Arguments:
    Arg1: ffffffffc000001d, The exception code that was not handled
    Arg2: fffffab024d15196, The address that the exception occurred at
    Arg3: 0000000000000000, Parameter 0 of the exception
    Arg4: 00000000ffffff00, Parameter 1 of the exception

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


    EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {

    FAULTING_IP: 
    +6161623531633832
    fffffab0`24d15196 ff              ???

    EXCEPTION_PARAMETER1:  0000000000000000

    EXCEPTION_PARAMETER2:  00000000ffffff00

    ERROR_CODE: (NTSTATUS) 0xc000001d - {

    BUGCHECK_STR:  0x1E_c000001d

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 0000000000000000 to 0000000000000000

    FAILED_INSTRUCTION_ADDRESS: 
    +6161623531633832
    fffffab0`24d15196 ff              ???

    STACK_TEXT:  
    00000000 00000000 00000000 00000000 00000000 0x0


    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:  INVALID_KERNEL_CONTEXT

    Followup: MachineOwner
    ---------
    2019年2月18日 15:26

全部回复

  • 您好,

    从你贴的信息无法看出原因,请参考以下链接做一下基本的检查: 

    https://support.microsoft.com/zh-cn/help/14238/windows-10-troubleshoot-blue-screen-errors

    导致bugcheck 0x1E 可能有以下原因:

    1. 硬件不兼容, 确认安装的所有新硬件与已安装的Windows版本兼容。

    2. 此外,有故障的设备驱动程序或系统服务可能会导致此错误。硬件问题也可能会生成此错误。

    禁用或删除最近添加的任何驱动程序或服务。如果在启动序列期间发生错误并且使用NTFS文件系统格式化系统分区,则可以使用安全模式在设备管理器中禁用驱动程序。

    检查事件查看器中的系统日志,查找可能有助于查明导致错误检查0x1E的设备或驱动程序的其他错误消息。您还应该运行系统制造商提供的硬件诊断程序,尤其是内存扫描程序。有关这些步骤的详细信息,请参阅计算机的用户手册。

    3. 生成此消息的错误可能在Windows安装过程中首次重新启动后或安装完成后发生。可能的错误原因是系统BIOS不兼容。升级系统BIOS版本可以解决BIOS问题。

    Best regards,

    Yilia 


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2019年2月19日 6:26
    版主
  • 您好,

    请问您的问题进展的怎么样了?

    我十分乐意帮助解决您的问题,希望您能及时给我一个反馈。

    Best regards,

    Yilia


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    2019年2月22日 6:01
    版主