Error 116 while playing LoL


  1. Posts : 26
    Windows 7 Home 32 bit
       #1

    Error 116 while playing LoL


    (Used driver sweeper for the old version NVIDIA driver and installed the latest GeForce GTX 430 Driver)
    I think it has a specific time while in game. After the 1:30 mark at the game, the computer will suddenly go to the "NO SIGNAL" Sign w/ stuttering sounds(looping) then crash. The computer will restart after this.
    Error 116

    Attached Dump files
      My Computer


  2. Arc
    Posts : 35,373
    Microsoft Windows 10 Pro Insider Preview 64-bit
       #2

    Hi BlueSOD.

    Stop 0x116 is a display/graphics related issue, and yours is an old branded desktop.

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
    Also let us know the wattage of the PSU.

    Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

    Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

    Also, Install the NVIDIA DRIVERS 314.22WHQL only.

    • Uninstall All nvidia items in Control Panel > Programs and features
      • 3D Vision Control Driver
      • 3D Vision Driver
      • Graphics Driver
      • HD Audio Driver
      • PhysX
      • nvidia Update

      (Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
    • Now follow Drivers - Clean Left over Files after Uninstalling
    • Download 314.22 WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:


    Let us know the results.
    _________________________________________________________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {862df230, 90044c2c, c000009a, 4}
    
    *** 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+807c2c )
    
    Followup: MachineOwner
    ---------
    
    0: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: 862df230, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: 90044c2c, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: c000009a, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 00000004, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+807c2c
    90044c2c 55              push    ebp
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
    
    STACK_TEXT:  
    8a76ecb0 902fc0ff 00000116 862df230 90044c2c nt!KeBugCheckEx+0x1e
    8a76ecd4 902f4ea7 90044c2c c000009a 00000004 dxgkrnl!TdrBugcheckOnTimeout+0x8d
    8a76ed18 902f530a 862df230 86fca490 8a76ed3c dxgkrnl!DXGADAPTER::Reset+0xee
    8a76ed28 90356343 862df230 86fca490 00000000 dxgkrnl!TdrResetFromTimeout+0x12
    8a76ed3c 903595bd 86fca490 00000000 86b07210 dxgmms1!VidSchiRecoverFromTDR+0x15
    8a76ed50 8382313d 86fca490 a0d91423 00000000 dxgmms1!VidSchiWorkerThread+0x7f
    8a76ed90 836ca559 9035953e 86fca490 00000000 nt!PspSystemThreadStartup+0x9e
    00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+807c2c
    90044c2c 55              push    ebp
    
    SYMBOL_NAME:  nvlddmkm+807c2c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  52b3261b
    
    FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:0x116_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
    
    Followup: MachineOwner
    ---------
    
    0: kd> lmvm nvlddmkm
    start    end        module name
    8f83d000 9026f000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Thu Dec 19 22:30:11 2013 (52B3261B)
        CheckSum:         00A09834
        ImageSize:        00A32000
        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 20:28.
Find Us