BSOD win7 gtx 560ti


  1. Posts : 7
    win 7 64bit
       #1

    BSOD win7 gtx 560ti


    i keep getting bsod after running pc games so i ran msi afterburner and started the combustor to make sure it wasnt a cooling problem the bsod happend while it was steady at 61 degrees (firmware kicks in @75 i think)

    the drivers are all the latest for the graphics card, I assume its a graphics related problem as it happens while running 'performance games '

    thank you for any help

    alex :)



    ------------------------

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

    Additional information about the problem:
    BCCode: 116
    BCP1: FFFFFA800A30E4E0
    BCP2: FFFFF88007926F50
    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\092113-14258-01.dmp
    C:\Users\Phantom\AppData\Local\Temp\WER-23868-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


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

    It is a continuing stop 0x116 BSOD here. Changing / updating display driver did not do anything good there. So It is the time to guess that the issue is not with the driver only, but somewhere else.

    I would suggest again to follow these steps and report back accordingly and elaborately.
    Code:
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    Use !analyze -v to get detailed debugging information.
    
    BugCheck 116, {fffffa800a30e4e0, fffff88007926f50, 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+8f0f50 )
    
    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: fffffa800a30e4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff88007926f50, 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+8f0f50
    fffff880`07926f50 803db205f0ff00  cmp     byte ptr [nvlddmkm+0x7f1509 (fffff880`07827509)],0
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    CUSTOMER_CRASH_COUNT:  1
    
    BUGCHECK_STR:  0x116
    
    PROCESS_NAME:  System
    
    CURRENT_IRQL:  0
    
    STACK_TEXT:  
    fffff880`04e06a48 fffff880`05aaa054 : 00000000`00000116 fffffa80`0a30e4e0 fffff880`07926f50 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`04e06a50 fffff880`05a7d867 : fffff880`07926f50 fffffa80`0d4f7000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`04e06a90 fffff880`05aa9e63 : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0a30e4e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`04e06b40 fffff880`05b7903d : fffffa80`0f56c710 00000000`00000080 00000000`00000000 fffffa80`0d4eb010 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`04e06bc0 fffff800`0352fbae : 00000000`01d862cb fffffa80`0d513060 fffffa80`09d589e0 fffffa80`0d513060 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`04e06c00 fffff800`032828c6 : fffff800`0340ce80 fffffa80`0d513060 fffff800`0341acc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
    fffff880`04e06c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    FOLLOWUP_IP: 
    nvlddmkm+8f0f50
    fffff880`07926f50 803db205f0ff00  cmp     byte ptr [nvlddmkm+0x7f1509 (fffff880`07827509)],0
    
    SYMBOL_NAME:  nvlddmkm+8f0f50
    
    FOLLOWUP_NAME:  MachineOwner
    
    MODULE_NAME: nvlddmkm
    
    IMAGE_NAME:  nvlddmkm.sys
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  52314e10
    
    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`07036000 fffff880`07b2d000   nvlddmkm T (no symbols)           
        Loaded symbol image file: nvlddmkm.sys
        Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
        Image name: nvlddmkm.sys
        Timestamp:        Thu Sep 12 10:46:00 2013 (52314E10)
        CheckSum:         00AC9E83
        ImageSize:        00AF7000
        Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
      My Computer


  3. Posts : 7
    win 7 64bit
    Thread Starter
       #3

    psu wattage needed 675 w > actual 850 w, ok

    carefully took out gpu no signs of dust/ blockages, generaly the pc is very dust free

    bios flash, battery removed and reinserted, need to restart, once re entered windows system clock reads wrong time, display keeps changing mode (game, cinematic etc..)every few seconds, restarted windows again everything seems ok,

    bios 3603 updated ok, makes for slighty quicker startup

    checked air throughflow air is comming out (NZXT phantom case) 7 fans total all blowing


    ram test on usb stick pass, nothing out the ordinary, ok

    burn in test done reached 73/74 degrees and steadied no real hor air coming out of pc? however no crashing either. also noticed fan speed doesnt rise about 75%
    Last edited by alexthepie; 23 Sep 2013 at 07:20.
      My Computer


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

    As you have taken some steps, now let us wait and see how it goes there.
      My Computer


  5. Posts : 7
    win 7 64bit
    Thread Starter
       #5

    Arc said:
    As you have taken some steps, now let us wait and see how it goes there.

    thanks for your help and patience once again il mark this as done for now it seems a lot better :)
      My Computer


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

    Its OK mate :) You are welcome as always :)
    If it starts causing issues again, let us know.
      My Computer


  7. Posts : 7
    win 7 64bit
    Thread Starter
       #7

    high again i tihnk i have a problem that is following on from the original problem the computer now randomly stops or glitches this happens anyone of 3 ways randomly during standard browsing:

    the screen/audio stop but the mouse still moves
    the screen/ audo stop and the mouse doesnot move
    the mouse changes to irregular cursors and the pc slows down

    in each instance it requires a soft or hard restart the frequency is about once every few hours.
      My Computer


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

    Test your RAM modules for possible errors.
    How to Test and Diagnose RAM Issues with Memtest86+
    Run memtest for at least 8 passes, preferably overnight.

    If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

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

    Stress test the CPU.
    Hardware - Stress Test With Prime95

    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.

    Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
    eXtreme Power Supply Calculator
      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 17:20.
Find Us