none
望高手解答 以下用windbg.exe所显示的 不知道是不是显卡坏了 RRS feed

  • 问题

  • 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 ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055d700
    Debug session time: Fri Apr 23 21:47:23.109 2010 (GMT+8)
    System Uptime: 0 days 3:31:19.840
    *********************************************************************
    * 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 ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ............................................................................................................
    Loading User Symbols
    Loading unloaded module list
    .........
    Unable to load image win32k.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for win32k.sys
    *** ERROR: Module load completed but symbols could not be loaded for win32k.sys
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000EA, {88d3bda8, 89768be0, b84ebcbc, 1}

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

    *** WARNING: Unable to verify timestamp for nv4_disp.dll
    *** ERROR: Module load completed but symbols could not be loaded for nv4_disp.dll
    *********************************************************************
    * 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 - could not read driver name for bugcheck parameter 3

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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+                                    *
    *********************************************************************
    Probably caused by : nv4_disp.dll ( nv4_disp+27c1d )

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

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

    THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
    The device driver is spinning in an infinite loop, most likely waiting for
    hardware to become idle. This usually indicates problem with the hardware
    itself or with the device driver programming the hardware incorrectly.
    If the kernel debugger is connected and running when watchdog detects a
    timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
    and detailed message including bugcheck arguments will be printed to the
    debugger. This way we can identify an offending thread, set breakpoints in it,
    and hit go to return to the spinning code to debug it further. Because
    KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck
    information in this case. The arguments are already printed out to the kernel
    debugger. You can also retrieve them from a global variable via
    "dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
    On MP machines it is possible to hit a timeout when the spinning thread is
    interrupted by hardware interrupt and ISR or DPC routine is running at the time
    of the bugcheck (this is because the timeout's work item can be delivered and
    handled on the second CPU and the same time). If this is the case you will have
    to look deeper at the offending thread's stack (e.g. using dds) to determine
    spinning code which caused the timeout to occur.
    Arguments:
    Arg1: 88d3bda8, Pointer to a stuck thread object.  Do .thread then kb on it to find
     the hung location.
    Arg2: 89768be0, Pointer to a DEFERRED_WATCHDOG object.
    Arg3: b84ebcbc, Pointer to offending driver name.
    Arg4: 00000001, Number of times "intercepted" bugcheck 0xEA was hit (see notes).

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

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

    *********************************************************************
    * 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 - could not read driver name for bugcheck parameter 3

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

    FAULTING_MODULE: bd012000 nv4_disp

    DEBUG_FLR_IMAGE_TIMESTAMP:  4ba021e9

    FAULTING_THREAD:  88d3bda8

    FAULTING_IP:
    nv4_disp+27c1d
    bd039c1d ??              ???

    IMAGE_NAME:  nv4_disp.dll

    MODULE_NAME: nv4_disp

    DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

    CUSTOMER_CRASH_COUNT:  1

    BUGCHECK_STR:  0xEA

    LAST_CONTROL_TRANSFER:  from bf8871da to 8054598b

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    b26a9674 bf8871da 00000000 00000000 00000000 nt+0x6d98b
    b26a9690 bd039c1d 8978a1c0 b26a96c4 00000000 win32k+0x871da
    b26a9694 8978a1c0 b26a96c4 00000000 b26a9754 nv4_disp+0x27c1d
    b26a9698 b26a96c4 00000000 b26a9754 b26a97ec 0x8978a1c0
    b26a969c 00000000 b26a9754 b26a97ec 00000000 0xb26a96c4


    STACK_COMMAND:  .thread 0xffffffff88d3bda8 ; kb

    FOLLOWUP_IP:
    nv4_disp+27c1d
    bd039c1d ??              ???

    SYMBOL_STACK_INDEX:  2

    SYMBOL_NAME:  nv4_disp+27c1d

    FOLLOWUP_NAME:  MachineOwner

    BUCKET_ID:  WRONG_SYMBOLS

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

    1: kd> lmvm nv4_disp
    start    end        module name
    bd012000 bd635c00   nv4_disp T (no symbols)          
        Loaded symbol image file: nv4_disp.dll
        Image path: nv4_disp.dll
        Image name: nv4_disp.dll
        Timestamp:        Wed Mar 17 08:27:21 2010 (4BA021E9)
        CheckSum:         00626820
        ImageSize:        00623C00
        Translations:     0000.04b0 0000.04e0 0409.04b0 0409.04e0

    2010年4月24日 1:57

全部回复

  • 很有可能,0x000000EA 是显示系统的专门错误,显卡硬件或显示驱动引起的问题。
    Alexis Zhang (Microsoft MVP 2004' 2007' 2008' 2009')
    2010年4月24日 10:18
    版主
  • nv4_disp.dll为NVidia某驱动程序,罪魁祸首应该是就是NVDIA驱动或显卡了。

    个人名字乃古代三豪杰之名各自取一组合而成:
    天人三策称圣意 董生一举天下知—董仲舒;
    人生自古谁无死,留取丹心照汗青—文天祥;
    一片丹心昭日月,满腔铁血莽昆仑—龙且。
    2010年4月26日 11:12
    版主
  • 请更换显卡驱动。或检测显卡是否松动温度是否正常。
    在IT的路上,You'll never walk alone
    2010年4月26日 13:24
  • 感谢答复啊 现在用着用着常会卡住就死掉了 3dmark06倒还能测试通过 但估计硬件问题比较大了 看来换的这块显卡质量不行啊 
    2010年4月26日 16:19