well i have a problem computer works fine when in windows but when i start playing it it freezes and screen goes nuts with grahpic.. and than i have to restart pc :/ in any game...
Hi and welcome
As you surmised three of the four dmps were caused by the vidoe driver and the DX component. Another thing that i noticed was you have drivers that are 2 years old that need to be updated
I would update the drivers
If you are overclocking stop
If you are running a raid update its driver
Since system files are involved it cant hurt to run a system file check to verify and fix your system files
type cmd in search>right click and run as admin>SFC /SCANNOW
Hope this helps and of course if you have more upload them
Ken J+
Lachesis.sys fffff880`057af000 fffff880`057b6680 0x00007680 0x46c552dc 8/17/2007 2:48:44 AM
nvstor64.sys fffff880`010a2000 fffff880`010c4000 0x00022000 0x472236fc 10/26/2007 1:50:36 PM
nvmfdx64.sys fffff880`04415000 fffff880`0457dc80 0x00168c80 0x473f7dad 11/17/2007 6:47:57 PM
Lycosa.sys fffff880`0560e000 fffff880`05612980 0x00004980 0x4790689e 1/18/2008 3:51:42 AM
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\101009-23015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02851000 PsLoadedModuleList = 0xfffff800`02a8ee50
Debug session time: Fri Oct 9 23:51:20.328 2009 (GMT-5)
System Uptime: 0 days 0:00:30.078
Loading Kernel Symbols
...............................................................
................................................................
...........
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80049794e0, fffff88004960220, 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+e7220 )
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: fffffa80049794e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88004960220, 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+e7220
fffff880`04960220 803d31c0960000 cmp byte ptr [nvlddmkm+0xa53258 (fffff880`052cc258)],0
DEFAULT_BUCKET_ID:
GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`03d5f9c8 fffff880`042f9cbc : 00000000`00000116 fffffa80`049794e0 fffff880`04960220 00000000`00000000 : nt!KeBugCheckEx
fffff880`03d5f9d0 fffff880`042f99c6 : fffff880`04960220 fffffa80`049794e0 fffffa80`046f9d50 fffffa80`046f6010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03d5fa10 fffff880`043a0f07 : fffffa80`049794e0 00000000`00000000 fffffa80`046f9d50 fffffa80`046f6010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03d5fa40 fffff880`043cab75 : 00000000`ffffffff 00000000`000005c9 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03d5fb20 fffff880`043c92bb : 00000000`00000102 00000000`00000000 00000000`000005c9 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`03d5fb50 fffff880`0439c2c6 : ffffffff`ff676980 fffffa80`046f6010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`03d5fbf0 fffff880`043c8e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0441dc68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`03d5fd00 fffff800`02b66166 : 00000000`03bb0af3 fffffa80`047174d0 fffffa80`018c5b30 fffffa80`047174d0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`03d5fd40 fffff800`028a1486 : fffff800`02a3be80 fffffa80`047174d0 fffff800`02a49c40 fffff880`0126b534 : nt!PspSystemThreadStartup+0x5a
fffff880`03d5fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+e7220
fffff880`04960220 803d31c0960000 cmp byte ptr [nvlddmkm+0xa53258 (fffff880`052cc258)],0
SYMBOL_NAME: nvlddmkm+e7220
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4abfff56
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
now instead of the usual bug the screen turns it self off.. sound and every thing works...