none
win7系统蓝屏,求帮助,已上传dump文件:http://pan.baidu.com/s/1i31NwpB RRS feed

  • 问题

  • 笔记本蓝屏,用windbg分析结果,请帮忙分析下,谢谢!

    已上传dump文件:

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


    Loading Dump File [C:\Users\cn4e67\Desktop\Minidump\101614-36348-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are 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+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Built by: 7601.18044.x86fre.win7sp1_gdr.130104-1431
    Machine Name:
    Kernel base = 0x84a1c000 PsLoadedModuleList = 0x84b654d0
    Debug session time: Thu Oct 16 16:38:40.530 2014 (UTC + 8:00)
    System Uptime: 0 days 3:16:16.168
    *********************************************************************
    * 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+                                    *
    *********************************************************************
    Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ................................................................
    ...
    Loading User Symbols
    Loading unloaded module list
    ...............
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    VIDEO_SCHEDULER_INTERNAL_ERROR (119)
    The video scheduler has detected that fatal violation has occurred. This resulted
    in a condition that video scheduler can no longer progress. Any other values after
    parameter 1 must be individually examined according to the subtype.
    Arguments:
    Arg1: 00000001, The driver has reported an invalid fence ID.
    Arg2: 0003b2a5
    Arg3: 0003b454
    Arg4: 0003b452

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

    *** WARNING: Unable to verify timestamp for dxgmms1.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys
    *** WARNING: Unable to verify timestamp for dxgkrnl.sys
    *** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
    *** WARNING: Unable to verify timestamp for igdkmd32.sys
    *** ERROR: Module load completed but symbols could not be loaded for igdkmd32.sys
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************

    ADDITIONAL_DEBUG_TEXT:  
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: dxgmms1

    FAULTING_MODULE: 84a1c000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  4d4a24c1

    CUSTOMER_CRASH_COUNT:  1

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    BUGCHECK_STR:  0x119

    CURRENT_IRQL:  0

    LAST_CONTROL_TRANSFER:  from 90cc0276 to 84afabdc

    STACK_TEXT:  
    WARNING: Stack unwind information not available. Following frames may be wrong.
    832966f4 90cc0276 00000119 00000001 0003b2a5 nt+0xdebdc
    8329671c 9a560b2c 09000000 87a6dd98 89bde000 watchdog+0x1276
    83296738 9a56690f 000011ac 0003b2a5 00000000 dxgmms1+0x6b2c
    8329676c 9a566f6d 89bde000 832968d0 00000001 dxgmms1+0xc90f
    83296788 9a4a4ea5 87a80920 832968d0 832967b0 dxgmms1+0xcf6d
    83296798 9a4a4f0e 8758efd0 87a80920 832968d0 dxgkrnl+0x1ea5
    832967b0 99ead832 87a80920 832968d0 00000000 dxgkrnl+0x1f0e
    83296930 99eac664 87a7d000 881fd0d4 c0000001 igdkmd32+0x83832
    83296978 99e3d360 87a7d000 00000000 00000000 igdkmd32+0x82664
    832969c0 9a4a4b14 87a7d000 00000000 832969e4 igdkmd32+0x13360
    832969d0 84aa5f70 897c9780 87a80920 00000000 dxgkrnl+0x1b14
    832969e4 84a55e3d 897c9780 87a80920 83296a10 nt+0x89f70
    83296a10 9a5855bb badb0d00 00000000 83296a44 nt+0x39e3d
    83296a90 9a57fcdb d4cb27c0 89ece000 d7a4c230 dxgmms1+0x2b5bb
    83296aa4 9a570cd7 d7a4c230 878d6114 89ece000 dxgmms1+0x25cdb
    83296abc 9a57424c 868c9328 00000001 00000000 dxgmms1+0x16cd7
    83296bb8 9a58b850 ba36bf20 00000000 b7f91c08 dxgmms1+0x1a24c
    83296d18 9a58c141 b7e03740 b7e03840 83296d3c dxgmms1+0x31850
    83296d28 9a58c3de b7e03740 84a52b89 886bf788 dxgmms1+0x32141
    83296d3c 9a58c485 886bf788 00000000 89ecdd48 dxgmms1+0x323de
    83296d50 84c2505d 886bf788 9d6217e5 00000000 dxgmms1+0x32485
    83296d90 84acc529 9a58c406 886bf788 00000000 nt+0x20905d
    00000000 00000000 00000000 00000000 00000000 nt+0xb0529


    STACK_COMMAND:  kb

    FOLLOWUP_IP: 
    dxgmms1+6b2c
    9a560b2c ??              ???

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  dxgmms1+6b2c

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  dxgmms1.sys

    BUCKET_ID:  WRONG_SYMBOLS

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


    2014年10月17日 2:41

答案

全部回复

  • 显示驱动程序配置有问题。一直有此问题还是最近出现的问题?如果是新出现的,最近有没有添加、更改、删除过任何驱动?


    Alexis Zhang

    http://mvp.support.microsoft.com/profile/jie
    http://blogs.itecn.net/blogs/alexis

    推荐以 NNTP Bridge 桥接新闻组方式访问论坛。

    本帖是回复帖,原帖作者是楼上的 <Diego-Milito>;

    | 笔记本蓝屏,用windbg分析结果,请帮忙分析下,谢谢!
    | 已上传dump文件: <http://pan.baidu.com/s/1i31NwpB>

    2014年10月17日 22:23
  • 您好,

    在您提供的dump分析结果中,看到了大量的错误报告“Your debugger is not using the correct symbols .”. 这说明分析工具Windows debugger的symbol path没有正确设置。
    希望可以向我们提供dump源文件,以便于分析蓝屏原因。

    另外,请根据MVP Alexis Zhang的建议更新显卡驱动。

    谢谢,


    Fangzhou CHEN
    TechNet Community Support

    2014年10月20日 6:00
    版主