BSOD 116 just started

Page 1 of 5 123 ... LastLast

  1. Posts : 84
    Windows 7 Ultimate x64
       #1

    BSOD 116 just started


    Hi,

    This has just started happening very recently, I have a 12 month old PC, I have not had a problem until recently when I had a black screen freeze with a noise (like a repetitive stuck noise) and I had to hold the power button down to reset the PC.

    It came back tonight again.

    I have attached the requested info below, if someone could take a look it would be greatly appreciated.

    P.S. System specs are filled out on link below and link to 2x Dump files via SkyDrive

    https://onedrive.live.com/?cid=F6349...14D867BA%21115

    This has happened 3 more times since this post and I cannot figure out why, I haven't made any major changes to my PC in a while (hardware or programs).

    I have the latest Nvidia drivers.
    I have the latest Sound drivers.
    Everything else I keep up to date and patched as quick as I can.

    I know 116 related to graphics usually so I am pushing my graphics card to test it but it crashes in games and out of games, just browsing the internet, so it's hard to pinpoint the cause.
    Last edited by ProdigyGamer; 05 Apr 2014 at 10:57. Reason: Added information
      My Computer


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

    Hi ProdigyGamer.

    A stop 0x116 is a display/graphics related issue.

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark
    Run Furmark on both the GPU, one by one.

    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 computer. It must be sufficient as I guess, still.

    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 .

    Install the NVIDIA DRIVERS 314.22WHQL only, at least as a test about how the computer is running with this driver. This test is needed to determine whether it is a hardware or a software related issue.

    • 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, {fffffa8023cc9010, fffff8801029ce2c, ffffffffc000009a, 4}
    
    Unable to load image 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+9bbe2c )
    
    Followup: MachineOwner
    ---------
    
    11: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8023cc9010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8801029ce2c, 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+9bbe2c
    fffff880`1029ce2c ??              ???
    
    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:  
    fffff880`0416ea48 fffff880`058f8140 : 00000000`00000116 fffffa80`23cc9010 fffff880`1029ce2c ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`0416ea50 fffff880`058cb867 : fffff880`1029ce2c fffffa80`24cc3000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`0416ea90 fffff880`058f7f4f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`23cc9010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`0416eb40 fffff880`059c703d : fffffa80`23d9a740 00000000`00000080 00000000`00000000 fffffa80`24cc2410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`0416ebc0 fffff800`033162ea : 00000000`07bc0e71 fffffa80`23931060 fffffa80`19409b30 fffffa80`23931060 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`0416ec00 fffff800`0306a8e6 : fffff880`03b42180 fffffa80`23931060 fffff880`03b4d1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`0416ec40 00000000`00000000 : fffff880`0416f000 fffff880`04169000 fffff880`0416e480 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+9bbe2c
    fffff880`1029ce2c ??              ???
    
    SYMBOL_NAME:  nvlddmkm+9bbe2c
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  5315b408
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}
    
    Followup: MachineOwner
    ---------
    
    11: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f8e1000 fffff880`10539000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Tue Mar 04 16:37:52 2014 (5315B408)
        CheckSum:         00C20523
        ImageSize:        00C58000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 84
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Hi Arc,

    Thank you for replying, here is the information and test result you asked for:

    FurMark stress test was as follows:

    1x 10 minute test - normal setting =45 fps, GPU 1 98 degrees, GPU 2 94 degrees
    1x 10 minute test - extreme setting = 24 fps, GPU 1 98 degrees, GPU 2 95 degrees

    No tearing or problems on screen at all, very smooth picture, temps within 105 degree as per Nvidia limits.

    Extreme Power Supply - All fine and within my 850 power supply limits.

    Speccy - has been attached (taken with old Nvida drivers before uninstall)

    Display Driver Uninstall - was performed and removed files after I had fully uninstalled Nvidia 335 drivers, I followed your instructions and installed the very old 314 drivers from last year.

    I have uploaded another Dump file from turning my PC on this morning, it crashed on start up before I was able to do anything.

    https://onedrive.live.com/?cid=F6349...14D867BA%21115

    May I ask the reason for going back so far in graphics drivers?
    What are you wanting to see specifically?

    I only ask because I play a few new games that benefit from having the latest drivers, so I am unable to play them properly now until I can reinstall a later version, I was finding that my PC was fine and working without any issues up to 332.21 Nvidia drivers (released Jan this year)
    Last edited by ProdigyGamer; 05 Apr 2014 at 21:45. Reason: Added more information
      My Computer


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

    ProdigyGamer said:

    May I ask the reason for going back so far in graphics drivers?
    Because, it is the last driver released by nvidia which worked stable. It never failed on itself.

    After that one, from the time nvidia started concentrating on 700 series GPUs and started bloating their drivers even more (GeForce Experience), there is not any single version which works stable at its own, in all systems.

    Whereas, any driver later it fails by the driver only.

    So, with a known failing display driver installed, it is not possible to determine the cause of a BSOD.

    If the BSODs stop after installing 314.22 WHQL and no other difficulties are found (which happens in a lot of cases; for more than 50% of stop 0x116 BSODs), then the conclusion will be it is oly the display driver that was causing the issue.

    Clear now?

    If you have any more questions, you may ask.
      My Computer


  5. Posts : 84
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Yes that is clear, thank you for the explanation, I was curious, I knew it would be for a good reason, I wasn't doubting you at all, I just wanted to know for my own personal knowledge to help me understand why you wanted to test it and so I can learn more about it.

    So far, after rolling back to that previous 314.22 driver and testing it on the exact same programs and games that crashed multiple times last night, I have had no issues at all.

    The game I was playing when the first (and next 3 crashes) occurred, was Skyrim (with 160+ mods) and it has worked flawlessly up until last night.

    I have been able to play and keep it running today for over 3 hours without a single crash so far, so I will keep testing but it seems to be better so far.

    Thank you for your help Arc, I will keep testing and post back here with any issues that may arise over the next few days or to close the thread and mark it as solved, if everything remains stable for the next few days.

    I appreciate your help, thanks friend. :)
      My Computer


  6. Posts : 84
    Windows 7 Ultimate x64
    Thread Starter
       #6

    I just had another black screen freeze with the stuttering sound then crash but it didn't produce a Dump file on start up this time.

    I checked the Event Viewer but I couldn't see what caused it to crash.

    I have uploaded another DM Log incase that will help you see the problem.

    I have not installed/uninstalled or changed anything since following your instructions earlier, I was playing the same game (Skyrim) when the game had 3 crashes to desktop, which is not unusual for that game with a lot of mods but then while in game I got a system hang/freeze then crash like before.
      My Computer


  7. Posts : 84
    Windows 7 Ultimate x64
    Thread Starter
       #7

    As soon as I started the game back up again it crashed within 60 seconds, this time is generated a Dump file on startup.

    Uploaded to SkyDrive: https://onedrive.live.com/?cid=F6349...14D867BA%21115

    Problem signature:
    Problem Event Name: BlueScreen
    OS Version: 6.1.7601.2.1.0.256.1
    Locale ID: 3081

    Additional information about the problem:
    BCCode: 116
    BCP1: FFFFFA805966F4E0
    BCP2: FFFFF880076186AC
    BCP3: FFFFFFFFC000009A
    BCP4: 0000000000000004
    OS Version: 6_1_7601
    Service Pack: 1_0
    Product: 256_1

    Files that help describe the problem:
    C:\Windows\Minidump\040714-43633-01.dmp
    C:\Users\A5ASIN\AppData\Local\Temp\WER-128186-0.sysdata.xml

    Read our privacy statement online:
    Windows 7 Privacy Statement - Microsoft Windows

    If the online privacy statement is not available, please read our privacy statement offline:
    C:\Windows\system32\en-US\erofflps.txt
      My Computer


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

    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa805966f4e0, fffff880076186ac, ffffffffc000009a, 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+9336ac )
    
    Followup: MachineOwner
    ---------
    
    11: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa805966f4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880076186ac, 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+9336ac
    fffff880`076186ac ??              ???
    
    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:  
    fffff880`08270a48 fffff880`04689140 : 00000000`00000116 fffffa80`5966f4e0 fffff880`076186ac ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`08270a50 fffff880`0465c867 : fffff880`076186ac fffffa80`255a5000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`08270a90 fffff880`04688f4f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`5966f4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`08270b40 fffff880`0475803d : fffffa80`1fd96450 00000000`00000080 00000000`00000000 fffffa80`254d7410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`08270bc0 fffff800`033762ea : 00000000`07bff4c1 fffffa80`25594a00 fffffa80`19409b30 fffffa80`25594a00 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`08270c00 fffff800`030ca8e6 : fffff880`03b42180 fffffa80`25594a00 fffff880`03b4d1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`08270c40 00000000`00000000 : fffff880`08271000 fffff880`0826b000 fffff880`082704d0 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+9336ac
    fffff880`076186ac ??              ???
    
    SYMBOL_NAME:  nvlddmkm+9336ac
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  51427b3c
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    ANALYSIS_SOURCE:  KM
    
    FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys
    
    FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}
    
    Followup: MachineOwner
    ---------
    
    11: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`06ce5000 fffff880`07790000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Fri Mar 15 07:07:00 2013 (51427B3C)
        CheckSum:         00A8D47C
        ImageSize:        00AAB000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    As it BSODs in the same way, even with 314.22 WHQL installed, I would suggest you to use one GPU only, not as SLI. Observe the situation then.
      My Computer


  9. Posts : 84
    Windows 7 Ultimate x64
    Thread Starter
       #9

    Ok I will try that, i also uninstalled a program called "TuneUp Utilities 2014" thinking it may be mismanaging something and causing these issues, plus I have heard that a lot of techs say to just use windows tools and not 3rd party programs like this, so it can't hurt to remove it and test too.

    Time for bed but I will switch to single GPU and test more tomorrow, thank you for your reply. :)
      My Computer


  10. Posts : 84
    Windows 7 Ultimate x64
    Thread Starter
       #10

    2 more crashes, I have uploaded the Dump files to SkyDrive again:

    https://onedrive.live.com/?cid=F6349...14D867BA%21115

    1 x crash with 1x GPU only
    1 x crash with 2x GPUs active

    I am out of idea's, any help would be appreciated.
      My Computer


 
Page 1 of 5 123 ... LastLast

  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 01:41.
Find Us