BSOD playing Black Ops 2 and World of Warcraft

This is the message Microsoft sent me after the BSOD:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA8007627010
BCP2: FFFFF8800FB71004
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\120712-27424-01.dmp
C:\Users\Tyler\AppData\Local\Temp\WER-43477-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

Here is my ZIP file of my compressed Minidump info using the SF Diagnostic Tool:

Attachment 245005

PLEASE HELP ME FIGURE OUT WHAT DRIVER IS FAILING, I'VE UNINSTALLED ALL UNNECESSARY PROGRAMS AND EVEN DID A FRESH OS RESTART WITH ALL UP TO DATE DRIVERS!!!
I've already ruled out overheating and RAM malfunction and to describe what happens is usually while playing pretty much any game and at some times while doing nothing at all my laptop has gone into a black or sometimes white screen.

Hello Torraz, welcome aboard.

Upload the files generated after executing SF diag tool, not the tool itself :)

Sorry, thanks for a quick response I re-posted the right ZIP file. Also I downloaded a driver that was outdated that I missed yesterday and I didn't get the BSOD the rest of the day, however turning on my computer today and leaving it on the log in screen it went black when I came back to it. The driver was ST Microelectronics-Driver for the ATA.

Here is an updated SF after updating 104+ windows updates and the ST Microelectronics-Driver and a Seagate-Firmware update for my hard drive:

Attachment 245020

First, update your display driver, following the option two of Drivers - Download NVIDIA Drivers. Then follow the guide: STOP 0x116: VIDEO_TDR_ERROR troubleshooting.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800ac93010, fffff8800fd4e004, 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+ad6004 )

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: fffffa800ac93010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fd4e004, 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+ad6004
fffff880`0fd4e004 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`042f3a48 fffff880`044c6000 : 00000000`00000116 fffffa80`0ac93010 fffff880`0fd4e004 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`042f3a50 fffff880`04499867 : fffff880`0fd4e004 fffffa80`09bea000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`042f3a90 fffff880`044c5e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`0ac93010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`042f3b40 fffff880`04594ec1 : fffffa80`078d7a10 00000000`00000080 00000000`00000000 fffffa80`09bd6010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`042f3bc0 fffff800`03529e5a : 00000000`038e28a0 fffffa80`09be8060 fffffa80`06ff7740 fffffa80`09be8060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`042f3c00 fffff800`03283d26 : fffff800`03405e80 fffffa80`09be8060 fffff800`03413cc0 00000000`00000004 : nt!PspSystemThreadStartup+0x5a
fffff880`042f3c40 00000000`00000000 : fffff880`042f4000 fffff880`042ee000 fffff880`042f34d0 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+ad6004
fffff880`0fd4e004 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+ad6004

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  503f8bb8

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`0f278000 fffff880`0ff60000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Aug 30 21:20:16 2012 (503F8BB8)
    CheckSum:         00CCA304
    ImageSize:        00CE8000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4