locked
每次開啟遊戲後一會兒就會黑屏 RRS feed

  • 問題

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

    與問題相關的其他資訊:
      BCCode: 116
      BCP1: FFFFFA800AFFC4E0
      BCP2: FFFFF8801027CE2C
      BCP3: FFFFFFFFC000009A
      BCP4: 0000000000000004
      OS Version: 6_1_7601
      Service Pack: 1_0
      Product: 768_1

    https://drive.google.com/file/d/0B6PaDrtrREPPTXVDYWZ2c05GWTA/edit?usp=sharing

    我已經更新了顯示卡及最新windows update


    • 已編輯 Yipzi 2014年5月1日 下午 05:12
    • 已編輯 AskaSuModerator 2014年5月3日 上午 02:06 編輯標題,原始標題:每次開啟遊戲後,等一會兒就會黑屏,然後需手動重開電腦~ 問題事件名稱:BlueScreen 請幫手解決!!~thx
    2014年5月1日 下午 05:09

解答

  • Hi Yipzi

    你可以參考底下的討論串的最後一篇回覆

    裡面是他們官方的資訊看來是很常見的硬體問題了

    建議你假如是新買的話拿去換一張吧

    https://forums.geforce.com/default/topic/616783/nvidia-geforce-gtx-560-ti-crashes-with-video_tdr_error/

    2014年5月9日 上午 07:58

所有回覆

  • Hi Yipzi

    看了你的dmp後發現是nvlddmkm.sys檔案在記憶體中搬來搬去的時候出問題

    可是這一個檔案是顯示卡的驅動程式,所以想要請問你你安裝的驅動程式是從nvidia官網抓下來的

    還是透過Windows Update來安裝的,建議妳可以抓幾個不同版本的驅動程式來測試看看

    看看哪一個版本比較穩定

    3: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800affc4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8801027ce2c, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000004, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.
    
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that   ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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:  
    You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
    
    FAULTING_MODULE: fffff80004656000 nt
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5315b408
    
    FAULTING_IP: 
    nvlddmkm+9bbe2c
    fffff880`1027ce2c 803db68aeeff00  cmp     byte ptr [nvlddmkm+0x8a48e9 (fffff880`101658e9)],0
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    fffff880`08df7a48 fffff880`08319140 : 00000000`00000116 fffffa80`0affc4e0 fffff880`1027ce2c ffffffff`c000009a : nt+0x75bc0
    fffff880`08df7a50 00000000`00000116 : fffffa80`0affc4e0 fffff880`1027ce2c ffffffff`c000009a 00000000`00000004 : dxgkrnl+0x5d140
    fffff880`08df7a58 fffffa80`0affc4e0 : fffff880`1027ce2c ffffffff`c000009a 00000000`00000004 00000000`00000001 : 0x116
    fffff880`08df7a60 fffff880`1027ce2c : ffffffff`c000009a 00000000`00000004 00000000`00000001 fffffa80`0affc4e0 : 0xfffffa80`0affc4e0
    fffff880`08df7a68 ffffffff`c000009a : 00000000`00000004 00000000`00000001 fffffa80`0affc4e0 fffff880`082ec867 : nvlddmkm+0x9bbe2c
    fffff880`08df7a70 00000000`00000004 : 00000000`00000001 fffffa80`0affc4e0 fffff880`082ec867 fffff880`1027ce2c : 0xffffffff`c000009a
    fffff880`08df7a78 00000000`00000001 : fffffa80`0affc4e0 fffff880`082ec867 fffff880`1027ce2c fffffa80`098be000 : 0x4
    fffff880`08df7a80 fffffa80`0affc4e0 : fffff880`082ec867 fffff880`1027ce2c fffffa80`098be000 00000000`00000000 : 0x1
    fffff880`08df7a88 fffff880`082ec867 : fffff880`1027ce2c fffffa80`098be000 00000000`00000000 ffffffff`c000009a : 0xfffffa80`0affc4e0
    fffff880`08df7a90 fffff880`1027ce2c : fffffa80`098be000 00000000`00000000 ffffffff`c000009a fffffa80`097ff410 : dxgkrnl+0x30867
    fffff880`08df7a98 fffffa80`098be000 : 00000000`00000000 ffffffff`c000009a fffffa80`097ff410 ffffffff`ff676980 : nvlddmkm+0x9bbe2c
    fffff880`08df7aa0 00000000`00000000 : ffffffff`c000009a fffffa80`097ff410 ffffffff`ff676980 fffffa80`0a8fe010 : 0xfffffa80`098be000
    
    
    STACK_COMMAND:  kb
    
    FOLLOWUP_IP: 
    nvlddmkm+9bbe2c
    fffff880`1027ce2c 803db68aeeff00  cmp     byte ptr [nvlddmkm+0x8a48e9 (fffff880`101658e9)],0
    
    SYMBOL_STACK_INDEX:  4
    
    SYMBOL_NAME:  nvlddmkm+9bbe2c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    BUCKET_ID:  WRONG_SYMBOLS
    
    FAILURE_BUCKET_ID:  WRONG_SYMBOLS
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:wrong_symbols
    
    FAILURE_ID_HASH:  {70b057e8-2462-896f-28e7-ac72d4d365f8}
    
    Followup: MachineOwner
    ---------
    
    3: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f8c1000 fffff880`10519000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Tue Mar 04 19:07:52 2014 (5315B408)
        CheckSum:         00C20523
        ImageSize:        00C58000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    

    2014年5月5日 上午 06:57
  • 多謝回答~!~
    我是從nvidia官網抓下來的,我嘗試過用舊版295.73和最新版本335.23分別安裝過,都出現同樣問題~
    我是否應該嘗試其他版本,還是其他方法呢?
    感激~
    2014年5月5日 下午 08:04
  • Hi Yipzi

    因為這算是驅動程式

    從作業系統層面比較沒有解決方式

    所以你可以讓我知道硬體的型號嗎?

    我看看是否可以幫你找到其他的解決方式

    2014年5月7日 上午 07:48
  • https://drive.google.com/file/d/0B6PaDrtrREPPczBlSjF5cWZjVlE/edit?usp=sharing
    以下是我資料~

    多謝解答!~
    2014年5月7日 下午 08:23
  • Hi Yipzi

    你可以參考底下的討論串的最後一篇回覆

    裡面是他們官方的資訊看來是很常見的硬體問題了

    建議你假如是新買的話拿去換一張吧

    https://forums.geforce.com/default/topic/616783/nvidia-geforce-gtx-560-ti-crashes-with-video_tdr_error/

    2014年5月9日 上午 07:58
  • 多謝你解答~
    看來只好換一下displaycard了~
    2014年5月10日 下午 07:54