BSOD Playing Secret World, unknown error.


  1. Posts : 1
    Windows 7 Ultimate x64
       #1

    BSOD Playing Secret World, unknown error.


    Long story short, This game run's flawlessly, But maybe into 10-15 minutes of gameplay time. It forcefully bluescreens, no key functions and also no self reboot, It creates the .dmp files before I have to literally pull the plug on the tower. Any advice is welcome, Thank you in advance.

    Edit: I've discovered it is not only just this game in particular, Diablo 3 has the same issue happen, Possible hardware failure coming along?
    Last edited by Sorrowfold; 23 Feb 2013 at 21:29.
      My Computer


  2. Posts : 15,026
    Windows 10 Home 64Bit
       #2

    Please post the following report:

    For a stop 116 go through: STOP 0x116: VIDEO_TDR_ERROR troubleshooting
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8002cec4e0, fffff8800520c6c4, ffffffffc000009a, 4}
    
    Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for nvlddmkm.sys
    *** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
    Probably caused by : nvlddmkm.sys ( nvlddmkm+9316c4 )
    
    Followup: MachineOwner
    ---------
    
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8002cec4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800520c6c4, 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:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+9316c4
    fffff880`0520c6c4 4055            push    rbp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`02e14b48 fffff880`03ee7000 : 00000000`00000116 fffffa80`02cec4e0 fffff880`0520c6c4 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`02e14b50 fffff880`03eba867 : fffff880`0520c6c4 fffffa80`04ecd000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02e14b90 fffff880`03ee6e0f : fffffa80`ffffd84d 00000000`00000000 fffffa80`02cec4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`02e14c40 fffff880`03fb5ec1 : fffffa80`05a63520 00000000`00000080 00000000`00000000 fffffa80`04eb2410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`02e14cc0 fffff800`02f3134a : 00000000`03bbef0b fffffa80`04eb8b50 fffffa80`024ab5f0 fffffa80`04eb8b50 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`02e14d00 fffff800`02c81946 : fffff880`009e7180 fffffa80`04eb8b50 fffff880`009f1f40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`02e14d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+9316c4
    fffff880`0520c6c4 4055            push    rbp
    
    SYMBOL_NAME:  nvlddmkm+9316c4
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5116d804
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    Followup: MachineOwner
    ---------
    
    1: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`048db000 fffff880`05383000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Sun Feb 10 05:13:08 2013 (5116D804)
        CheckSum:         00A90CB0
        ImageSize:        00AA8000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:56.
Find Us