BSOD-sad panda- Please help.

Hey meepzzz

just do the 1st aid of it...
do a driver update of every driver installed in ur pc...n then checkout....
so do these simple 1st aid job and den if everything is ok dont go 4 the dump...
see if this works...

All the BSoDs are exactly the same, caused by your NVidia Graphics driver, nvlddmkm.sys.

Update the driver, hopefully that will fix it.
More information on the x116 stop code here: [2-Int] STOP 0x116: VIDEO_TDR_ERROR troubleshooting - Windows 7 Forums

Code:

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\David\AppData\Local\Temp\Temp1_Minidump-4.zip\Minidump\062310-22089-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
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02e4a000 PsLoadedModuleList = 0xfffff800`03087e50
Debug session time: Wed Jun 23 15:16:26.532 2010 (UTC - 7:00)
System Uptime: 0 days 1:25:02.374
Loading Kernel Symbols
...............................................................
................................................................
.................................................
Loading User Symbols
Loading unloaded module list
...........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa800b5f1010, fffff88004a40110, 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+15110 )

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800b5f1010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004a40110, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+15110
fffff880`04a40110 48895c2420      mov     qword ptr [rsp+20h],rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`06dcb9c8 fffff880`03e5cef8 : 00000000`00000116 fffffa80`0b5f1010 fffff880`04a40110 00000000`00000000 : nt!KeBugCheckEx
fffff880`06dcb9d0 fffff880`03e5cc02 : fffff880`04a40110 fffffa80`0b5f1010 fffffa80`0c194d50 fffffa80`0c187410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06dcba10 fffff880`05560f07 : fffffa80`0b5f1010 00000000`00000000 fffffa80`0c194d50 fffffa80`0c187410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06dcba40 fffff880`0558ab75 : 00000000`ffffffff 00000000`0004fcc3 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06dcbb20 fffff880`055892bb : 00000000`00000102 00000000`00000000 00000000`0004fcc3 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06dcbb50 fffff880`0555c2c6 : ffffffff`ff676980 fffffa80`0c187410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06dcbbf0 fffff880`05588e7a : 00000000`00000000 fffffa80`070785b0 00000000`00000080 fffffa80`0c187410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06dcbd00 fffff800`0315fa86 : 00000000`fffffc32 fffffa80`0bbba060 fffffa80`03cd1740 fffffa80`0bbba060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06dcbd40 fffff800`02e98b06 : fffff800`03034e80 fffffa80`0bbba060 fffff800`03042c40 fffff880`01459534 : nt!PspSystemThreadStartup+0x5a
fffff880`06dcbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+15110
fffff880`04a40110 48895c2420      mov     qword ptr [rsp+20h],rbx

SYMBOL_NAME:  nvlddmkm+15110

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac791b5

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

~Lordbob