windows version: Windows 7 Service Pack 1, 6.1, build: 7601
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17153769472 total
VM: 2147352576, free: 1899110400
 
 
 
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
 
Crash dump directory: C:\Windows\Minidump
 
Crash dumps are enabled on your computer.
 
 
On Thu 27/10/2011 16:03:56 GMT your computer crashed
crash dump file: C:\Windows\Minidump\102711-15787-01.dmp
This was probably caused by the following module: nvlddmkm.sys (nvlddmkm+0x170CD8)  
Bugcheck code: 0x116 (0xFFFFFA80127BB010, 0xFFFFF8800FF75CD8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\nvlddmkm.sys
product: NVIDIA Windows Kernel Mode Driver, Version 280.26  
company: NVIDIA Corporation
description: NVIDIA Windows Kernel Mode Driver, Version 280.26  
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.  
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: nvlddmkm.sys (NVIDIA Windows Kernel Mode Driver, Version 280.26 , NVIDIA Corporation).  
Google query: nvlddmkm.sys NVIDIA Corporation VIDEO_TDR_ERROR
 
 
 
 
On Thu 27/10/2011 16:03:56 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgkrnl.sys (dxgkrnl!TdrResetFromTimeout+0x214)  
Bugcheck code: 0x116 (0xFFFFFA80127BB010, 0xFFFFF8800FF75CD8, 0x0, 0x2)
Error: VIDEO_TDR_ERROR
file path: C:\Windows\system32\drivers\dxgkrnl.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics Kernel
Bug check description: This indicates that an attempt to reset the display driver and recover from a timeout failed.  
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system which cannot be identified at this time.