locked
最近發生 LiveKernelEvent 和 BlueScreen 的問題 RRS feed

  • 問題

  • 筆電最近玩遊戲常發生玩到一半卡住之後就藍屏

    檢查之後是

    描述
    您的視訊硬體發生問題,導致 Windows 停止正常運作。

    問題簽章
    問題事件名稱: LiveKernelEvent
    作業系統版本: 6.1.7600.2.0.0.768.3
    地區設定識別碼: 1028

    有助於描述問題的檔案
    WD-20120716-1123.dmp
    sysdata.xml
    WERInternalMetadata.xml

     檢視這些檔案的暫時複本
    警告: 如果是病毒或其他安全性威脅導致此問題,則開啟檔案的副本可能會對您的電腦造成傷害。

    問題的額外資訊
    BCCode: 117
    BCP1: FFFFFA8004E184E0
    BCP2: FFFFF88010972CEC
    BCP3: 0000000000000000
    BCP4: 0000000000000000
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    -----------------下面還會附帶一個-----------------------

    問題簽章
    問題事件名稱: BlueScreen
    作業系統版本: 6.1.7600.2.0.0.768.3
    地區設定識別碼: 1028

    問題的額外資訊
    BCCode: 116
    BCP1: FFFFFA8004BFD010
    BCP2: FFFFF8801106613C
    BCP3: FFFFFFFFC000009A
    BCP4: 0000000000000004
    OS Version: 6_1_7600
    Service Pack: 0_0
    Product: 768_1

    然後這是DMP 不好意思不太清楚所以一次貼上來

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


    Loading Dump File [C:\Windows\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 ntkrnlmp.exe - 
    Windows 7 Kernel Version 7600 MP (4 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
    Machine Name:
    Kernel base = 0xfffff800`04a00000 PsLoadedModuleList = 0xfffff800`04c3ce70
    Debug session time: Mon Jul 16 11:23:05.636 2012 (UTC + 8:00)
    System Uptime: 0 days 1:16:26.135
    *********************************************************************
    * 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 ntkrnlmp.exe - 
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    .......................................
    Loading User Symbols

    Loading unloaded module list
    ...........
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for dxgkrnl.sys - 
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 116, {fffffa8004e184e0, fffff88010fca13c, ffffffffc000009a, 4}

    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for dxgmms1.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                                     ***
    ***                                                                   ***
    *************************************************************************
    *** ERROR: Symbol file could not be found.  Defaulted to export symbols for nvlddmkm.sys - 
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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                                     ***
    ***                                                                   ***
    *************************************************************************
    Probably caused by : nvlddmkm.sys ( nvlddmkm+7af13c )

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


    懇請各位幫忙,謝謝。

    2012年7月16日 上午 04:33

解答

  • 您好!

    請先更新顯示卡驅動程式看看

    Probably caused by : nvlddmkm.sys ( nvlddmkm+7af13c )

    • 已提議為解答 AChange 2012年7月17日 上午 06:02
    • 已標示為解答 AChange 2012年7月20日 上午 01:17
    2012年7月16日 上午 04:45