none
蓝屏 RRS feed

  • 问题

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


    Loading Dump File [I:\新建文件夹\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is: 
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
    Windows 7 Kernel Version 7600 MP (16 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.17273.x86fre.win7_gdr.130318-1532
    Machine Name:
    Kernel base = 0x84a41000 PsLoadedModuleList = 0x84b89810
    Debug session time: Wed May  2 18:27:11.010 2018 (GMT+8)
    System Uptime: 0 days 7:45:40.946
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for ntkrpamp.exe - 
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........Page 10fd9 not present in the dump file. Type ".hh dbgerr004" for details
    ..........Page 42080 not present in the dump file. Type ".hh dbgerr004" for details
    .........................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffda00c).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ......
    0: kd> !analyze -v
           ^ Syntax error in '!analyze -v'
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
    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.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: 80000004, The exception code that was not handled
    Arg2: ffdff2a5, The address that the exception occurred at
    Arg3: a5154d48, Trap Frame
    Arg4: 00000000

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

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    Page 10fd9 not present in the dump file. Type ".hh dbgerr004" for details
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Your debugger is not using the correct symbols                 ***
    ***                                                                   ***
    ***    In order for this command to work properly, your symbol path   ***
    ***    must point to .pdb files that have full type information.      ***
    ***                                                                   ***
    ***    Certain .pdb files (such as the public OS symbols) do not      ***
    ***    contain the required information.  Contact the group that      ***
    ***    provided you with these symbols if you need this command to    ***
    ***    work.                                                          ***
    ***                                                                   ***
    ***    Type referenced: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************

    MODULE_NAME: nt

    FAULTING_MODULE: 84a41000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  5147d3b2

    EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - <Unable to get error code text>

    FAULTING_IP: 
    +ffffffffffdff2a5
    ffdff2a5 c3              ret

    TRAP_FRAME:  a5154d48 -- (.trap 0xffffffffa5154d48)
    ErrCode = 00000000
    eax=00000000 ebx=84a835b0 ecx=00000000 edx=00000000 esi=02f7fbac edi=00135701
    eip=ffdff2a5 esp=a5154dbc ebp=801ec000 iopl=0         ov dn di ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00044c86
    ffdff2a5 c3              ret
    Resetting default scope

    DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

    BUGCHECK_STR:  0x8E

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 84afe532 to 84b1db3c

    STACK_TEXT:  
    WARNING: Stack unwind information not available. Following frames may be wrong.
    a51548b4 84afe532 0000008e 80000004 ffdff2a5 nt!KeBugCheckEx+0x1e
    a5154cd8 84a842c6 a5154cf4 00000000 a5154d48 nt!EtwProviderEnabled+0xa16
    a5154d48 ffdff2a5 badb0d00 00000000 ffffffff nt!Kei386EoiHelper+0x1de
    a5154d4c badb0d00 00000000 ffffffff 0000003b 0xffdff2a5
    a5154d50 00000000 ffffffff 0000003b 00000000 0xbadb0d00


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    nt!EtwProviderEnabled+a16
    84afe532 cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!EtwProviderEnabled+a16

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  ntkrpamp.exe

    BUCKET_ID:  WRONG_SYMBOLS

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

    0: kd> lmvm nt
    start    end        module name
    84a41000 84e51000   nt         (export symbols)       ntkrpamp.exe
        Loaded symbol image file: ntkrpamp.exe
        Image path: ntkrpamp.exe
        Image name: ntkrpamp.exe
        Timestamp:        Tue Mar 19 10:55:46 2013 (5147D3B2)
        CheckSum:         003D2DD9
        ImageSize:        00410000
        File version:     6.1.7600.17273
        Product version:  6.1.7600.17273
        File flags:       0 (Mask 3F)
        File OS:          40004 NT Win32
        File type:        1.0 App
        File date:        00000000.00000000
        Translations:     0409.04b0
        CompanyName:      Microsoft Corporation
        ProductName:      Microsoft® Windows® Operating System
        InternalName:     ntkrpamp.exe
        OriginalFilename: ntkrpamp.exe
        ProductVersion:   6.1.7600.17273
        FileVersion:      6.1.7600.17273 (win7_gdr.130318-1532)
        FileDescription:  NT Kernel & System
        LegalCopyright:   © Microsoft Corporation. All rights reserved.
    2018年5月3日 5:43

全部回复

  • Hi ,

    通常,大多蓝屏问题是由以下原因造成的:

    不稳定的硬件设备、设备驱动过期、三方程序干扰、系统异常。

    建议先在安全模式下时,观察蓝屏是否出现,如果未出现蓝屏,我们就可以推断事件原因为驱动软件过期、三方程序干扰。

    请检查最近是否有做过什么特殊的操作,比如说更新了驱动或者是安装了补丁/软件,请撤销之前的更改,再检查是否有相同的问题。

    若蓝屏仍旧在安全模式下出现, 问题就可能是由于硬件不稳定导致的或者是系统异常导致的。建议联系电脑厂商对硬件进行排查.

    同时请尝试运行sfc/scannow进行一个系统文件检测和修复。

    以下是一些硬件蓝屏的排错常规步骤,你可以尝试一下:

    1.如果最近有更换硬件,请您将新硬件更换回之前的硬件或是其他新硬件
    2.如果您有多根内存条,请您只保留一根,将其余的拔除
    3.确认接线等是否疏松,机箱内的灰尘是否过多,进行固定和清理
    4.更换其他的电源

    由于分析蓝屏文件超出了论坛的支持范围,如果以上的常规排错没有解决问题同时问题比较紧急的话,建议您选用微软电话技术支持服务:800-820-3800。

    此致

    Candy


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

    2018年5月3日 8:14
    版主
  • Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [I:\新建文件夹\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is available

    Symbol search path is: SRV*d:\DebugSymbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    Windows 7 Kernel Version 7600 MP (16 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7600.17273.x86fre.win7_gdr.130318-1532
    Machine Name:
    Kernel base = 0x84a41000 PsLoadedModuleList = 0x84b89810
    Debug session time: Wed May  2 18:27:11.010 2018 (GMT+8)
    System Uptime: 0 days 7:45:40.946
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .........Page 10fd9 not present in the dump file. Type ".hh dbgerr004" for details
    ..........Page 42080 not present in the dump file. Type ".hh dbgerr004" for details
    .........................
    Loading User Symbols
    PEB is paged out (Peb.Ldr = 7ffda00c).  Type ".hh dbgerr001" for details
    Loading unloaded module list
    ......
    0: kd> !analvze -v
    No export analvze found
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
    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.
    Some common problems are exception code 0x80000003.  This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG.  This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but ...
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG.  This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: 80000004, The exception code that was not handled
    Arg2: ffdff2a5, The address that the exception occurred at
    Arg3: a5154d48, Trap Frame
    Arg4: 00000000

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

    Page 10fd9 not present in the dump file. Type ".hh dbgerr004" for details
    Page 10fd9 not present in the dump file. Type ".hh dbgerr004" for details
    Page 42080 not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 7ffda00c).  Type ".hh dbgerr001" for details
    Page 10fd9 not present in the dump file. Type ".hh dbgerr004" for details
    Page 42080 not present in the dump file. Type ".hh dbgerr004" for details
    PEB is paged out (Peb.Ldr = 7ffda00c).  Type ".hh dbgerr001" for details

    EXCEPTION_CODE: (HRESULT) 0x80000004 (2147483652) - <Unable to get error code text>

    FAULTING_IP: 
    +ffffffffffdff2a5
    ffdff2a5 c3              ret

    TRAP_FRAME:  a5154d48 -- (.trap 0xffffffffa5154d48)
    ErrCode = 00000000
    eax=00000000 ebx=84a835b0 ecx=00000000 edx=00000000 esi=02f7fbac edi=00135701
    eip=ffdff2a5 esp=a5154dbc ebp=801ec000 iopl=0         ov dn di ng nz na pe nc
    cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00044c86
    ffdff2a5 c3              ret
    Resetting default scope

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x8E

    PROCESS_NAME:  360sd.exe

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 84afe532 to 84b1db3c

    STACK_TEXT:  
    a51548b4 84afe532 0000008e 80000004 ffdff2a5 nt!KeBugCheckEx+0x1e
    a5154cd8 84a842c6 a5154cf4 00000000 a5154d48 nt!KiDispatchException+0x1ac
    a5154d40 84a84262 801ec000 ffdff2a5 badb0d00 nt!CommonDispatchException+0x4a
    a5154d48 ffdff2a5 badb0d00 00000000 ffffffff nt!Kei386EoiHelper+0x17a
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    a5154d4c badb0d00 00000000 ffffffff 0000003b 0xffdff2a5
    a5154d50 00000000 ffffffff 0000003b 00000000 0xbadb0d00


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    nt!KiDispatchException+1ac
    84afe532 cc              int     3

    SYMBOL_STACK_INDEX:  1

    SYMBOL_NAME:  nt!KiDispatchException+1ac

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: nt

    IMAGE_NAME:  ntkrpamp.exe

    DEBUG_FLR_IMAGE_TIMESTAMP:  5147d3b2

    FAILURE_BUCKET_ID:  0x8E_nt!KiDispatchException+1ac

    BUCKET_ID:  0x8E_nt!KiDispatchException+1ac

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

    0: kd> !process
    PROCESS 89b4e0e8  SessionId: 1  Cid: 0dcc    Peb: 7ffda000  ParentCid: 065c
        DirBase: 779af7e0  ObjectTable: a11c9e40  HandleCount: 292.
        Image: 360sd.exe
        VadRoot 897e4130 Vads 423 Clone 0 Private 8430. Modified 98082. Locked 0.
        DeviceMap 97939c78
        Token                             a11ba978
        ElapsedTime                       07:44:59.431
        UserTime                          00:00:00.000
        KernelTime                        00:00:00.046
        QuotaPoolUsage[PagedPool]         0
        QuotaPoolUsage[NonPagedPool]      0
        Working Set Sizes (now,min,max)  (413, 122, 244) (1652KB, 488KB, 976KB)
        PeakWorkingSetSize                11883
        VirtualSize                       174 Mb
        PeakVirtualSize                   192 Mb
        PageFaultCount                    317066
        MemoryPriority                    BACKGROUND
        BasePriority                      8
        CommitCharge                      10847

    2018年5月4日 5:33
  • 您好 ,

    由于分析蓝屏文件超出了论坛的支持范围,如果以上的常规排错没有解决问题同时问题比较紧急的话,建议您选用微软电话技术支持服务:800-820-3800。

    此致

    Candy


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

    2018年5月4日 6:23
    版主