BSOD with error 0x00000116 accompanied by display driver crashes

Page 1 of 2 12 LastLast

  1. Posts : 11
    Windows 7 Professional x64
       #1

    BSOD with error 0x00000116 accompanied by display driver crashes


    For the past few days I have been plagued by frequent display driver crashes, These crashes usually recover immediately, but sometimes they cause complete system crashes with BSODs (although I cannot see the BSODs because the screen goes to black). Crashes happen for seemingly no reason. Sometimes it takes hours, sometime seconds. Sometimes it crashes on the login screen. Nothing in particular makes it crash more or less.

    I have attempted to diagnose and/or fix the issue with a friend who works in tech support, but we haven't come up with anything so far. Last resort is obviously Windows 7 Upgrade to replace all windows files and then complete re-install after that, but obviously I wish to avoid this.

    I have scanned the machine with multiple virus/spyware/malware scans with nothing coming up. I've changed the system's TDR Delay to 10 seconds via regedit. I've turned off all services and start-up programs. I've re-installed, clean re-installed, and updated my graphics driver to the newest version. Nothing works. Various explorations through out the Event Viewer hasn't lead to anything we can see might be causing the issue.

    The strangest thing is that I have even had the screen crash to black in safe-mode twice today. Safe mode was the only way the machine is usable at this point, but apparently even that isn't safe.
      My Computer


  2. Posts : 4,161
    Windows 7 Pro-x64
       #2

    The video drivers you've been using are causing the problem. Try rolling back to this WHQL version.
      My Computer


  3. Posts : 11
    Windows 7 Professional x64
    Thread Starter
       #3

    The driver you provided will not install since it does not detect compatible hardware. It doesn't look like it supports mobile graphics devices, which mine is (GeForce GTX 580M)
      My Computer


  4. Posts : 4,161
    Windows 7 Pro-x64
       #4

    Ok, go directly to the source: Product Support | Dell US

    I noticed there's also a BIOS update.
      My Computer


  5. Posts : 11
    Windows 7 Professional x64
    Thread Starter
       #5

    Problems still persist. Screen crashed to black and would not recover, and did the same thing immediately after reboot, although no BSOD.

    That is a very old driver on Dell's website, and I'm sure I had it in the past with no issues, but it is now the 3rd driver I've tried with no success.
      My Computer


  6. Posts : 4,161
    Windows 7 Pro-x64
       #6

    Did you update the BIOS?

    The errors are TDR timeouts. This occurs when the driver or video card doesn't respond and Windows attempts to reset the driver. If the driver fails to respond within a period of time (the time you changed), the 0x116 occurs. This is normally a bad driver but it can also be a failing video card since the card must respond to the driver before the driver can respond to Windows.

    Every dump I checked indicated the driver(s) were not matched to the system so we usually start there. There's also some updates on the Dell site you should look into. The BIOS and the Control Center (If you're using it and Aero).

    If the PC is stable, the video card can be tested. We need to get there first.
      My Computer


  7. Posts : 11
    Windows 7 Professional x64
    Thread Starter
       #7

    Sorry, I thought I had updated the VBIOS before, but I recalled that it was for a different machine I had before this one.

    I have now update the VBIOS and I just received a display driver crash and recovery again, but no crash to BSOD after the update yet.

    Edit: 6 or 7 rapid display driver crashes and recoveries immediately after initial response, followed by an additional crash to BSOD. Rebooted to safe mode, which then crashed when I walked away. Error was 0x000000f4. I have included a new zip from the SF Diagnostic Tool after the new BSODs.
      My Computer


  8. Posts : 4,161
    Windows 7 Pro-x64
       #8

    Code:
     
    BugCheck 116, {fffffa80124954e0, fffff8800f3f9e20, ffffffffc00000b5, a}
    *** 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+153e20 )
     
    6: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f2a6000 fffff880`0fefe000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Tue Mar 04 05:07:52 2014 (5315B408)
    BIOS Version/Date Alienware A08, 7/29/2011

    The Nvidia driver is still not correct. The most recent is not always the best driver. Also, this still shows the old BIOS. Did you rerun the diagnostic utility to capture the current system state? You might try forcing a driver update from MS through the device manager. It should download the WHQL version for your system.

    If you are overclocking the video card, Stop. Check and verify your display resolution. This line doesn't look right
    Resolution 1920 x 1080 x 119 hertz
      My Computer


  9. Posts : 11
    Windows 7 Professional x64
    Thread Starter
       #9

    Nothing happened for the past 2 days, until just now when I experience a display driver crash and recovery, shortly followed by a display driver crash and BSOD.

    I realized I did the wrong BIOS update and updated to version A12. Then un-installed my driver and installed the version provided by Dell, and then let Windows update my driver to version 331.65. Again, no problems since that until just now.

    I have attached yet another zip from the SF Diagnostic Tool after today's BSOD.
      My Computer


  10. Posts : 4,161
    Windows 7 Pro-x64
       #10

    It's pretty much saying the same thing. The previous dump indicated a possible disk error.

    Killer-2 is considered a Trojan. I don't remember seeing that last time. You also have a hidden path in your startups.
    Perform a Clean Boot then download and run AdwCleaner. Post the report from it.

    Code:
     
    BugCheck 116, {fffffa80110f14e0, fffff8800fc3f074, 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+994074 )
    Followup: MachineOwner
    ---------
    7: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa80110f14e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8800fc3f074, 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+994074
    fffff880`0fc3f074 803dae0aefff00  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0fb2fb29)],0
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    CUSTOMER_CRASH_COUNT:  1
    BUGCHECK_STR:  0x116
    PROCESS_NAME:  System
    CURRENT_IRQL:  0
    STACK_TEXT:  
    fffff880`077fea48 fffff880`0ff41140 : 00000000`00000116 fffffa80`110f14e0 fffff880`0fc3f074 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`077fea50 fffff880`0ff14867 : fffff880`0fc3f074 fffffa80`0d916000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`077fea90 fffff880`0ff40f4f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`110f14e0 fffff880`0f237f3c : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`077feb40 fffff880`0f23803d : fffffa80`10d877d0 00000000`00000080 00000000`00000000 fffffa80`0d915410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`077febc0 fffff800`03b722ea : 00000000`fffffc32 fffffa80`0d933b50 fffffa80`09cc5890 fffffa80`0d933b50 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`077fec00 fffff800`038c68e6 : fffff800`03a50e80 fffffa80`0d933b50 fffff800`03a5ecc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`077fec40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    STACK_COMMAND:  .bugcheck ; kb
    FOLLOWUP_IP: 
    nvlddmkm+994074
    fffff880`0fc3f074 803dae0aefff00  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`0fb2fb29)],0
    SYMBOL_NAME:  nvlddmkm+994074
    FOLLOWUP_NAME:  MachineOwner
    MODULE_NAME: nvlddmkm
    IMAGE_NAME:  nvlddmkm.sys
    DEBUG_FLR_IMAGE_TIMESTAMP:  52676afe
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    Followup: MachineOwner
    ---------
    7: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f2ab000 fffff880`0fee2000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Wed Oct 23 01:21:50 2013 (52676AFE)
        CheckSum:         00C0CF0F
        ImageSize:        00C37000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


 
Page 1 of 2 12 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 02:51.
Find Us