Hard rebooting BSOD issues that have been hounding me forever!

jamesleecartel · 01 Dec 2012

Hi There,

I have been struggling to figure out what has been causing my computer reboots.
It happens mainly during games and i've heard the same sort of problem from many people on forums.
I have been trying to solve the issue for about 7months off and on.
I have tried replacing power supply, hard-drives, wireless adapters, pretty much everything.
I pretty much stopped using my powerful computer for ages because it basically became useless!

The games run so beautifully up until they just bomb out it's heartbreaking!

If anyone can help me determine what the problem is i will be forever in their debt!

I have recently read up on how to save my .dmp files and .zip them up so that hopefully one of you kind, intelligent peeps can read the info and give me a clue as to where the problem lies?

I've attached the special log file .zip that i followed the instructions to generate and i've been told to upload!

I have everything crossed that one of you kind folk can help me out here...i'm willing to do anything to fix my comp, but i just need to know where to start!

thanks in advance for any tips!

James

koolkat77 · 01 Dec 2012

Welcome

Follow: STOP 0x116: VIDEO_TDR_ERROR troubleshooting for your bugcheck

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`03066000 PsLoadedModuleList = 0xfffff800`032a3e50
Debug session time: Sun Dec  2 03:30:20.149 2012 (UTC + 6:00)
System Uptime: 42 days 1:25:52.311
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800b64d010, fffff88010b5b330, 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+cff330 )

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: fffffa800b64d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88010b5b330, 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+cff330
fffff880`10b5b330 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`04bf0b48 fffff880`04147cbc : 00000000`00000116 fffffa80`0b64d010 fffff880`10b5b330 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`04bf0b50 fffff880`0411b867 : fffff880`10b5b330 fffffa80`08b08000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04bf0b90 fffff880`04147acb : fffffa80`ffffd87b 00000000`00000000 fffffa80`0b64d010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`04bf0c40 fffff880`0fe37ec1 : fffffa80`068809e0 00000000`00000080 00000000`00000000 fffffa80`08b03010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`04bf0cc0 fffff800`0337b166 : 00000000`0377ad30 fffffa80`08b23770 fffffa80`066d5040 fffffa80`08b23770 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`04bf0d00 fffff800`030b6486 : fffff800`03250e80 fffffa80`08b23770 fffff800`0325ec40 fffff880`0124e534 : nt!PspSystemThreadStartup+0x5a
fffff880`04bf0d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+cff330
fffff880`10b5b330 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+cff330

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4eece814

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`0fe5c000 fffff880`10bd6000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Sun Dec 18 01:05:56 2011 (4EECE814)
    CheckSum:         00D612A0
    ImageSize:        00D7A000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4