BSOD After 1 monitor goes blank 0x00000116


  1. Posts : 4
    Win 7 Pro x64
       #1

    BSOD After 1 monitor goes blank 0x00000116


    Hello, I've had my computer crash twice in a similar fashion the past couple of weeks.

    I have 3 monitors:

    Dell 2007FP 1200x1600 (portrait)
    Dell U2412M 1920x1200
    Apple Cinema 1680x1050

    My GeForce GTX 560 Ti powers the 24" and Apple while a GeForce 8400GS powers the portrait monitor.

    Both times I BSOD'd the portrait monitor would act as if I slept my computer while the other 2 monitors still showed my desktop and applications. I would see the dell power save lcd screen and then the computer would freeze then goto BSOD. Attached is output from SF Diagnostic Tool.

    I have been using the 8400 since March 2012 and have recently switched it to portrait mode this past September

    El cheapo gfx card going bad perhaps?
      My Computer


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

    Hi chrisan.

    Please uinistall LogMeIn Mirror.
    Code:
    Name    LogMeIn Mirror Driver
    Driver    c:\windows\system32\drivers\lmimirr.sys (2.50.0.596, 11.28 KB (11,552 bytes), 8/24/2012 2:41 PM)
    Stress test both the Graphics Cards using Furmark.

    • NVIDIA GeForce GTX 560 Ti
    • NVIDIA GeForce 8400GS

    Video Card - Stress Test with Furmark

    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 .

    Update the display driver to the 332.21 WHQL: NVIDIA DRIVERS GeForce 332.21 Driver WHQL

    Let us know the results.
    _________________________________________________________________________________________
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa8018c514e0, fffff8801019e044, ffffffffc000000d, 3}
    
    *** 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+994044 )
    
    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: fffffa8018c514e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff8801019e044, The pointer into responsible device driver module (e.g. owner tag).
    Arg3: ffffffffc000000d, Optional error code (NTSTATUS) of the last failed operation.
    Arg4: 0000000000000003, Optional internal context dependent data.
    
    Debugging Details:
    ------------------
    
    
    FAULTING_IP: 
    nvlddmkm+994044
    fffff880`1019e044 803dde0aefff00  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`1008eb29)],0
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`02bd8848 fffff880`1049e140 : 00000000`00000116 fffffa80`18c514e0 fffff880`1019e044 ffffffff`c000000d : nt!KeBugCheckEx
    fffff880`02bd8850 fffff880`10471569 : fffff880`1019e044 fffffa80`1439c000 00000000`00000000 fffffa80`1438e010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`02bd8890 fffff880`1049deed : fffffa80`18c514e0 fffffa80`18c514e0 fffffa80`18c514e0 fffffa80`1438e010 : dxgkrnl!DXGADAPTER::PrepareToReset+0x109
    fffff880`02bd88d0 fffff880`10544f13 : fffffa80`18c514e0 00000000`00000000 fffffa80`14a5f280 fffffa80`1438e010 : dxgkrnl!TdrIsRecoveryRequired+0x245
    fffff880`02bd8900 fffff880`1056ecf1 : 00000000`ffffffff 00000000`003a2661 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
    fffff880`02bd89e0 fffff880`1056d437 : 00000000`00000102 00000000`00000000 00000000`003a2661 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
    fffff880`02bd8a10 fffff880`105402d2 : ffffffff`ff676980 fffffa80`1438e010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
    fffff880`02bd8ab0 fffff880`1056cff6 : 00000000`00000000 fffffa80`14a5f280 00000000`00000080 fffffa80`1438e010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
    fffff880`02bd8bc0 fffff800`03b642ea : 00000000`03def4ba fffffa80`143b6760 fffffa80`0d383b30 fffffa80`143b6760 : dxgmms1!VidSchiWorkerThread+0xba
    fffff880`02bd8c00 fffff800`038b88e6 : fffff880`009f0180 fffffa80`143b6760 fffff880`009fb0c0 00000000`00000103 : nt!PspSystemThreadStartup+0x5a
    fffff880`02bd8c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+994044
    fffff880`1019e044 803dde0aefff00  cmp     byte ptr [nvlddmkm+0x884b29 (fffff880`1008eb29)],0
    
    SYMBOL_NAME:  nvlddmkm+994044
    
    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
    ---------
    
    2: kd> lmvm nvlddmkm
    start             end                 module name
    fffff880`0f80a000 fffff880`10441000   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 11:51:50 2013 (52676AFE)
        CheckSum:         00C0CF0F
        ImageSize:        00C37000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 4
    Win 7 Pro x64
    Thread Starter
       #3

    Thanks for the reply Arc!

    Uninstalled logmein
    Upgraded to 332.21

    Attached is a Speccy screenshot after me working for past 6 hours for what I could consider normal use when it has crashed in the past.

    When I ran furmark on main display, the 560 went up to 87 degrees.

    I can't figure out how to launch it on the portrait monitor. Even if I put the main screen on that display it still launches in my primary display and since it is portrait the window border is out of view so I'm unable to drag it. I started a custom 1200x1200 window and dragged that over to the portrait monitor, however it still seems to be using the GTX 560 as that temperature increases while my 8400 remains the same temp. I made sure there is no border bleeding over to the primary display.

    Any ideas?
      My Computer


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

    Temps are fine ... not to be worried about it at all :)

    For formark, first test with the NVIDIA GeForce GTX 560 Ti connected only, removing/disconnecting the other. Then test on the NVIDIA GeForce 8400GS only, removing/disconnecting the other.

    If furmark runs on a single monitor, no problem. But it is run the program on both the GPUs individually.
      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 23:31.
Find Us