STOP 0x00000116: VIDEO_TDR_ERROR
Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card.
Your latest dump file lists
nvlddmkm.sys as the probable cause (graphics driver).
For now, while you are still getting BSOD's uninstall
Avast! as it has been known to cause issues on some Win 7 systems.
Uninstall Avast then use the Avast
Link Removed to clear up. Download BSOD friendly
Link Removed due to 404 Error as its replacement. Make sure Windows firewall is enabled!
Once everything has settled feel free to re-install Avast.
Update:
AsUpIO.sys Mon Jul 06 03:21:27 2009
Link Removed hardware monitoring software related.
Run
sfc /scannow to check your system files are in good order.
Physically re-seat your graphics card in your machine. Can you then stress test it.
Bugcheck Analysis:
Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {84dba510, 8f542b2c, 0, 2}
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+11fb2c )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 84dba510, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8f542b2c, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+11fb2c
8f542b2c 55 push ebp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
8a18db74 8fee107b 00000116 84dba510 8f542b2c nt!KeBugCheckEx+0x1e
8a18db98 8fed5937 8f542b2c 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
8a18dbbc 8ff1192c 00000000 00000102 8767a788 dxgkrnl!TdrIsRecoveryRequired+0xb8
8a18dc34 8ff3b944 fffffcfb 00004635 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8a18dc5c 8ff3c065 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8a18dc98 8ff188f0 8a18dc90 8512e9f8 86450270 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8a18dd28 8ff3d3c9 8767a788 82e4c50e 8767a788 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8a18dd3c 8ff3d485 8767a788 00000000 87687d48 dxgmms1!VidSchiRun_PriorityTable+0xf
8a18dd50 8301df64 8767a788 a843fa6b 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8a18dd90 82ec6219 8ff3d406 8767a788 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+11fb2c
8f542b2c 55 push ebp
SYMBOL_NAME: nvlddmkm+11fb2c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a6b
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
There's an interesting (if old) thread regarding 116 errors on the
nVidia Forum
I meant when I try and manually install the driver, Windows would refuse to update it saying it was update. Swine machine I said! It bloody is not!
) and has been behaving fine on that system. 
(Good ole HS204!)
)
