No crash in safe mode, otherwise random crashes. Update of nvidia drivers leads to BSOD on startup

Discussion in 'Windows 7 Blue Screen of Death (BSOD)' started by asoberanimal, Jun 3, 2011.

  1. asoberanimal

    asoberanimal New Member

    Joined:
    Jun 3, 2011
    Messages:
    6
    Likes Received:
    0
    A couple of weeks ago my computer started to randomly freeze up, anywhere from immediately after the login screen to 2+ hrs of uptime. Now, I can't get past the login screen without the computer freezing. I'm able to get into safe mode without any errors, and after some research I've done the following:

    This thread showed a similar problem, so I've removed Daemon tools and disabled SPTD:
    http://windows7forums.com/blue-screen-death-bsod/54654-no-crash-safe-mode-seemingly-random-crashes-otherwise.html

    I then analyzed my most recent .dmp file, and this was the exact error that popped up:
    Bsod video_tdr_timeout_detected - Windows 7 Forums

    I then downloaded the most recent nvidia drivers and via the .exe, updated my drivers. Now, when I attempt to boot up my machine, after the login screen I get the BSOD for a second, and the computer resets. I'm at a loss on where to go from here.

    Any help would be appreciated, thanks.

    View attachment Seven Forums.zip

    EDIT: Attached SF diagnostic tool zip.
     
    #1 asoberanimal, Jun 3, 2011
    Last edited: Jun 3, 2011
  2. asoberanimal

    asoberanimal New Member

    Joined:
    Jun 3, 2011
    Messages:
    6
    Likes Received:
    0
    Tried a clean install of my video drivers using drive sweeper and at least now windows loads, but back to the random crashes. If I let the computer sit idle nothing happens, but any soft of activity crashes it.
    This is the copy of my most recent crash:

    Code:
    ********************************************************************************                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    Use !analyze -v to get detailed debugging information.
    
    
    BugCheck 116, {fffffa8004161010, fffff880106b0f10, 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+801f10 )
    
    
    Followup: MachineOwner
    ---------
    
    
    6: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************
    
    
    VIDEO_TDR_FAILURE (116)
    Attempt to reset the display driver and recover from timeout failed.
    Arguments:
    Arg1: fffffa8004161010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
    Arg2: fffff880106b0f10, 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+801f10
    fffff880`106b0f10 4883ec28        sub     rsp,28h
    
    
    DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
    
    
    CUSTOMER_CRASH_COUNT:  1
    
    
    BUGCHECK_STR:  0x116
    
    
    PROCESS_NAME:  System
    
    
    CURRENT_IRQL:  0
    
    
    STACK_TEXT:  
    fffff880`067d1b88 fffff880`0433d000 : 00000000`00000116 fffffa80`04161010 fffff880`106b0f10 ffffffff`c000009a : nt!KeBugCheckEx
    fffff880`067d1b90 fffff880`04310867 : fffff880`106b0f10 fffffa80`05d59000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
    fffff880`067d1bd0 fffff880`0433ce0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`04161010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
    fffff880`067d1c80 fffff880`04237ec1 : fffffa80`0652a260 00000000`00000080 00000000`00000000 fffffa80`05d1e410 : dxgkrnl!TdrResetFromTimeout+0x23
    fffff880`067d1d00 fffff800`031687c6 : 00000000`02b51e7c fffffa80`059eab60 fffffa80`036629e0 fffffa80`059eab60 : dxgmms1!VidSchiWorkerThread+0x101
    fffff880`067d1d40 fffff800`02ea3c26 : fffff800`0303fe80 fffffa80`059eab60 fffff800`0304dc40 fffff880`012162b4 : nt!PspSystemThreadStartup+0x5a
    fffff880`067d1d80 00000000`00000000 : fffff880`067d2000 fffff880`067cc000 fffff880`0678bb70 00000000`00000000 : nt!KxStartSystemThread+0x16
    
    
    
    
    STACK_COMMAND:  .bugcheck ; kb
    
    
    FOLLOWUP_IP: 
    nvlddmkm+801f10
    fffff880`106b0f10 4883ec28        sub     rsp,28h
    
    
    SYMBOL_NAME:  nvlddmkm+801f10
    
    
    FOLLOWUP_NAME:  MachineOwner
    
    
    MODULE_NAME: nvlddmkm
    
    
    IMAGE_NAME:  nvlddmkm.sys
    
    
    DEBUG_FLR_IMAGE_TIMESTAMP:  4dd73a68
    
    
    FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    
    BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
    
    
    Followup: MachineOwner
    
    
    
    Any ideas?
     

Share This Page

Loading...