BSOD 0x116, not sure if because of NVIDIA drivers


  1. Posts : 373
    Windows 7 Ultimate x6
       #1

    BSOD 0x116, not sure if because of NVIDIA drivers


    Here's the SF Diagnostic Tool results of my latest BSOD. Can you guys tell me if it is due to the latest NVIDIA driver or not?

    Also, my pagefile is just set to a minimum of 400MB. Is setting the write debug information to Kernel Memory Dump better than Small Memory Dump? Which is recommended?
      My Computer


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

    If you are overclocking your hardware, revert back to the normal settings.

    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.

    Try a dismantle. Clean up the inside of the computer carefully. Clean the fan grills and air vents. When re-seating, dont forget to apply thermal paste to the CPU.

    Check the Power supply. Is it supplying enough power that is necessary?
    eXtreme Power Supply Calculator

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Let us know the results.
    ________________________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800bac1010, fffff8800440a6ac, 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+9336ac )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800bac1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800440a6ac, 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`0440a6ac 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`03077a48 fffff880`038f9000 : 00000000`00000116 fffffa80`0bac1010 fffff880`0440a6ac ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`03077a50 fffff880`038cc867 : fffff880`0440a6ac fffffa80`0a4ba000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`03077a90 fffff880`038f8e0f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`0bac1010 00000000`00000010 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`03077b40 fffff880`039c7ec1 : fffffa80`0a536220 00000000`00000080 00000000`00000000 fffffa80`0a377010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`03077bc0 fffff800`02b6434a : 00000000`02a01fda fffffa80`0a4d3200 fffffa80`066ae890 fffffa80`0a4d3200 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`03077c00 fffff800`028b4946 : fffff880`0245e180 fffffa80`0a4d3200 fffff880`02468fc0 00000000`00000004 : nt!PspSystemThreadStartup+0x5a
    fffff880`03077c40 00000000`00000000 : fffff880`03078000 fffff880`03072000 fffff880`03076d30 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+9336ac
    fffff880`0440a6ac 4055            push    rbp
    
    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
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`03ad7000 fffff880`04582000   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
      My Computer


  3. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #3

    Arc said:
    If you are overclocking your hardware, revert back to the normal settings.

    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.

    Try a dismantle. Clean up the inside of the computer carefully. Clean the fan grills and air vents. When re-seating, dont forget to apply thermal paste to the CPU.

    Check the Power supply. Is it supplying enough power that is necessary?
    eXtreme Power Supply Calculator

    Stress test the Graphics Card using Furmark.
    Video Card - Stress Test with Furmark

    Let us know the results.
    ________________________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800bac1010, fffff8800440a6ac, 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+9336ac )
    
    Followup: MachineOwner
    ---------
    
    2: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa800bac1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800440a6ac, 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`0440a6ac 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`03077a48 fffff880`038f9000 : 00000000`00000116 fffffa80`0bac1010 fffff880`0440a6ac ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`03077a50 fffff880`038cc867 : fffff880`0440a6ac fffffa80`0a4ba000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`03077a90 fffff880`038f8e0f : 00000000`ffffd84d ffffffff`fffe7960 fffffa80`0bac1010 00000000`00000010 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`03077b40 fffff880`039c7ec1 : fffffa80`0a536220 00000000`00000080 00000000`00000000 fffffa80`0a377010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`03077bc0 fffff800`02b6434a : 00000000`02a01fda fffffa80`0a4d3200 fffffa80`066ae890 fffffa80`0a4d3200 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`03077c00 fffff800`028b4946 : fffff880`0245e180 fffffa80`0a4d3200 fffff880`02468fc0 00000000`00000004 : nt!PspSystemThreadStartup+0x5a
    fffff880`03077c40 00000000`00000000 : fffff880`03078000 fffff880`03072000 fffff880`03076d30 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+9336ac
    fffff880`0440a6ac 4055            push    rbp
    
    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
    
    Followup: MachineOwner
    ---------
    
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`03ad7000 fffff880`04582000   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
    The first results I've sent you are with stock settings already.

    No, it is definitely not hot. I use a high-end air cooler (Thermalright Silver Arrow) for my CPU and a water cooling AIO cooler (Arctic Cooling) for my GPU For my CPU, I get around 70C for Prime95 tests. For my GPU, I get around 51C for Furmark tests. Do you still need a Speccy screenshot?

    My computer is already clean. I have all dust filters for my intake fans and I have a lot of fans in this case. Here's my case for your reference:

    http://cdn.overclock.net/5/58/58211305_DSC_2573.jpeg

    My PSU is more than enough for my system and it is also a high-end one (Seasonic X660 PSU).

    Before posting here, I've already done a 20-minute Furmark tests and like I said above everything is good and my GPU temps are 51C only.

    I just reverted to NVIDIA driver 314.07 to see if all goes well. In the meantime, what else can I do?

    And how about for my second question here:

    Also, my pagefile is just set to a minimum of 400MB. Is setting the write debug information to Kernel Memory Dump better than Small Memory Dump? Which is recommended?
      My Computer


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

    You are getting a display related error, and for which small mini dumps are enough.

    I hope you have answered my questions carefully, and after being sure. So I am assuming that there are no problem with those. Next, try a driver swap.


    Let us know how the computer is working on this particular driver.
      My Computer


  5. Posts : 373
    Windows 7 Ultimate x6
    Thread Starter
       #5

    Arc said:
    You are getting a display related error, and for which small mini dumps are enough.

    I hope you have answered my questions carefully, and after being sure. So I am assuming that there are no problem with those. Next, try a driver swap.


    Let us know how the computer is working on this particular driver.
    Oh ok. Thanks. When do you need a Kernel dump?

    Ok, so 306.23 is known to be stable?
      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 19:14.
Find Us