Hello!
I come here to please you to help me.
Here is my system :
[FONT=Segoe UI, Arial]
computer name: OWNER-PC
windows version: Windows 7 Ultimate Service Pack 1, 6.1, build: 7601 and 32bit!
windows dir: C:\Windows
CPU: GenuineIntel Intel(R) Core(TM)2 CPU 4400 @ 2.00GHz Intel586, level: 6
NVIDIA CARD 8500
2 logical processors, active mask: 3
RAM: 1072128000 total
VM: 2147352576, free: 1993306112
Here are the report and the .dmb files!
P.S : Please add a ' to Im , because i forget it , sorry 
[/FONT]
These are virtually identical they are all 116 errors or
The VIDEO_TDR_ ERROR bug check has a value of 0x00000116. This indicates that an attempt to reset the display driver and recover from a timeout failed.
You should start by re-installing the video driver using the below.
When upgrading your graphic driver you MUST remove all traces of the current driver. In order to do that we recommend using
Guru3D - Driver Sweeper
When it is removed then download and install the fresh copy.
"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception.
Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.
As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.
If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.
If playing with video driver versions hasn't helped, make sure the box is not overheating.
Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.
Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.
If so, it might be as simple as dust buildup and subsequently inadequate cooling.
I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Forums
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\041211-18844-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17514.x86fre.win7sp1_rtm.101119-1850
Machine Name:
Kernel base = 0x82a55000 PsLoadedModuleList = 0x82b9f850
Debug session time: Tue Apr 12 12:03:59.791 2011 (GMT-4)
System Uptime: 0 days 0:00:43.945
Loading Kernel Symbols
...............................................................
................................................................
.....
Loading User Symbols
Loading unloaded module list
....
1: kd>
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 868a2008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 9030877e, 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:
------------------
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
FAULTING_IP:
nvlddmkm+10877e
9030877e 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:
894d7b74 8cb1a07b 00000116 868a2008 9030877e nt!KeBugCheckEx+0x1e
894d7b98 8cb0e937 9030877e 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
894d7bbc 8cb4a92c 00000000 00000102 86733528 dxgkrnl!TdrIsRecoveryRequired+0xb8
894d7c34 8cb74944 fffffcfb 00000864 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
894d7c5c 8cb75065 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
894d7c98 8cb518f0 894d7c90 82a8c50e 86733528 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
894d7d28 8cb763c9 86733528 82a8c50e 86733528 dxgmms1!VidSchiScheduleCommandToRun+0xaa
894d7d3c 8cb76485 86733528 00000000 86742710 dxgmms1!VidSchiRun_PriorityTable+0xf
894d7d50 82c5ef5e 86733528 91755a36 00000000 dxgmms1!VidSchiWorkerThread+0x7f
894d7d90 82b06219 8cb76406 86733528 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+10877e
9030877e 55 push ebp
SYMBOL_NAME: nvlddmkm+10877e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4d27c60e
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
1: kd> lmvm nvlddmkm
start end module name
90200000 90bf9ee0 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Fri Jan 07 21:03:58 2011 (4D27C60E)
CheckSum: 00A07628
ImageSize: 009F9EE0
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
.
