Reboot from bugcheck

I was playing Lost Planet2 and had been for quite a while with not problems, using dx9 version. Screen randomly goes into sleep mode and sounds stutters and loops and I have to reset and I get back "windows has recovered from a serious error" and the diagnose options. System log had
"The computer has rebooted from a bugcheck. The bugcheck was: 0x00000116 (0xfffffa800670b010, 0xfffff8801061723c, 0xffffffffc000009a, 0x0000000000000004). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 050711-19905-01."

With that size, it may be Kernel Memory dump.
You can configure the system to create Minidump.
Set MiniDump

Several problems:
1. Remove Daemon/Alcohol software and remove sptd driver with this tools:
DuplexSecure - Downloads
For alternative Software you may use MagicIso.

2. Reinstall your Graphic driver.
Use Driversweeper to remove current driver then install a fresh copy.

3. Update these drivers:

Code:

Rt64win7.sys Fri May 22 06:52:30 2009 → Realtek NIC driver
RTKVHD64.sys Fri May 22 10:04:20 2009 → Realtek HD Audio

4. See if the problem persist then test your VGA
Video Card - Stress Test with Furmark


Log

Code:

Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03257000 PsLoadedModuleList = 0xfffff800`03494e50
Debug session time: Sat May  7 15:16:51.607 2011 (GMT-8)
System Uptime: 1 days 5:14:13.762
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800670b010, fffff8801061723c, 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+7b723c )

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: fffffa800670b010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8801061723c, 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+7b723c
fffff880`1061723c 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`0858bb88 fffff880`10b19ef8 : 00000000`00000116 fffffa80`0670b010 fffff880`1061723c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0858bb90 fffff880`10aed867 : fffff880`1061723c fffffa80`07d6f000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0858bbd0 fffff880`10b19d07 : fffffa80`ffffd87b ffffffff`fffe7960 fffffa80`0670b010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0858bc80 fffff880`10be8ec1 : fffffa80`09183400 00000000`00000080 00000000`00000000 fffffa80`07cab410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0858bd00 fffff800`0356ca86 : 00000000`027cc79b fffffa80`07cb0b60 fffffa80`05506040 fffffa80`07cb0b60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0858bd40 fffff800`032a5b06 : fffff800`03441e80 fffffa80`07cb0b60 fffff800`0344fc40 fffff880`01241a90 : nt!PspSystemThreadStartup+0x5a
fffff880`0858bd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7b723c
fffff880`1061723c 4883ec28        sub     rsp,28h

SYMBOL_NAME:  nvlddmkm+7b723c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d27c6da

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------