BSOD during graphically intense games. BCCODE 116

bobdog14 · 06 Dec 2013

I recently purchased another graphics card (geforce gtx660) for my computer. After about 4 weeks of using it without any problems, my computer started to Blue Screen during newer games such as Battlefield, Metro 2033 and even The Sims 3.The computer will run simpler games such as Counter Strike Source without any problems. I did notice that my CPU was running at about 120F and my Mobo at 85F. They seemed to be a little high, but nothing terrible. I am fairly new to the world of computers, this is my first build, so any help would be greatly appreciated. Attached are they last few dump files that my computer gave me. Thanks in advance!

Arc · 08 Dec 2013

Hi bobdog14.

Are you overclocking? As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

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

As the heats you reported, those should not be any problem, not asking anything more about it right now.

When a GTX 660 is having BSODs with the latest version of the display driver, it is best to observe the situation with a known good earlier version.
Install the NVIDIA DRIVERS 314.22WHQL only.

Uninstall All nvidia items in Control Panel > Programs and features
- 3D Vision Control Driver
- 3D Vision Driver
- Graphics Driver
- HD Audio Driver
- PhysX
- nvidia Update
(Are you using nvidia chipset drivers? If so, dont uninstall anything other than those are listed).
Now follow Drivers - Clean Left over Files after Uninstalling
Download NVIDIA DRIVERS 314.22WHQL. While installing, Select Custom (Advanced) install. In the next page, follow this settings:

Let us know the results.
______________________________________________________________________________________

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800835d010, fffff8801223e2bc, ffffffffc000009a, 4}

*** 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+99b2bc )

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: fffffa800835d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8801223e2bc, 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+99b2bc
fffff880`1223e2bc 803de6fceeff00  cmp     byte ptr [nvlddmkm+0x88afa9 (fffff880`1212dfa9)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02dc7a48 fffff880`12541140 : 00000000`00000116 fffffa80`0835d010 fffff880`1223e2bc ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02dc7a50 fffff880`12514867 : fffff880`1223e2bc fffffa80`05ff6000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02dc7a90 fffff880`12540f4f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0835d010 fffff880`11837f3c : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02dc7b40 fffff880`1183803d : fffffa80`03821d50 00000000`00000080 00000000`00000000 fffffa80`05f40410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02dc7bc0 fffff800`033642ea : 00000000`05bb654e fffffa80`05d06b50 fffffa80`036a0740 fffffa80`05d06b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02dc7c00 fffff800`030b88e6 : fffff800`03242e80 fffffa80`05d06b50 fffff800`03250cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02dc7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+99b2bc
fffff880`1223e2bc 803de6fceeff00  cmp     byte ptr [nvlddmkm+0x88afa9 (fffff880`1212dfa9)],0

SYMBOL_NAME:  nvlddmkm+99b2bc

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5280da75

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`118a3000 fffff880`124e4000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon Nov 11 18:54:05 2013 (5280DA75)
    CheckSum:         00C10283
    ImageSize:        00C41000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4