New
#1
Freeze and crash
Hi, Im having an issue with my nvidia gtx260. For some time now whenever I run starcraft 2 the PC just freezes, always on the loading screen prior to a game. And I have to do a hard reboot. This has also happened when watching some youtube videos on the firefox browser. A freeze and I have to hard reboot.
No BSOD, but I have managed to get some mini dump files on the Windbg and I need some help with those.
Win 7 Ultimate x64, core i5, 4gb ram. Nvidia gtx260. My PSU is a corsair 650w. I have the latest nvidia drivers. Also I have already updated my asus motherboard bios.
Leave you with the dump...
This is other mini dump. This is a 117 error.Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Velt\Documents\descarga\081910-21356-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02819000 PsLoadedModuleList = 0xfffff800`02a56e50
Debug session time: Thu Aug 19 17:45:29.707 2010 (UTC - 3:00)
System Uptime: 0 days 0:01:01.753
Loading Kernel Symbols
.
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.
..............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8006b064e0, fffff880049676c0, 0, d}
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+d06c0 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8006b064e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880049676c0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 000000000000000d, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+d06c0
fffff880`049676c0 803db1899c0000 cmp byte ptr [nvlddmkm+0xa99078 (fffff880`05330078)],0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`05cca9c8 fffff880`040a7ef8 : 00000000`00000116 fffffa80`06b064e0 fffff880`049676c0 00000000`00000000 : nt!KeBugCheckEx
fffff880`05cca9d0 fffff880`040a7c7f : fffff880`049676c0 fffffa80`06b064e0 fffffa80`06ac77f0 fffffa80`05812010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05ccaa10 fffff880`0414ef07 : fffffa80`06b064e0 00000000`00000000 fffffa80`06ac77f0 fffffa80`05812010 : dxgkrnl!TdrIsRecoveryRequired+0x21f
fffff880`05ccaa40 fffff880`04178b75 : 00000000`ffffffff 00000000`00000ee1 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05ccab20 fffff880`041772bb : 00000000`00000102 00000000`00000000 00000000`00000ee1 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05ccab50 fffff880`0414a2c6 : ffffffff`ff676980 fffffa80`05812010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05ccabf0 fffff880`04176e7a : 00000000`00000000 fffffa80`069d2010 00000000`00000080 fffffa80`05812010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05ccad00 fffff800`02b2dc06 : 00000000`fffffc32 fffffa80`057f1770 fffffa80`036e6040 fffffa80`057f1770 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05ccad40 fffff800`02867c26 : fffff880`009ea180 fffffa80`057f1770 fffff880`009f4fc0 fffff880`0121e534 : nt!PspSystemThreadStartup+0x5a
fffff880`05ccad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+d06c0
fffff880`049676c0 803db1899c0000 cmp byte ptr [nvlddmkm+0xa99078 (fffff880`05330078)],0
SYMBOL_NAME: nvlddmkm+d06c0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c8387
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
I will appreciate any ideas.Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Velt\Documents\descarga\082410-14617-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\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.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`0281d000 PsLoadedModuleList = 0xfffff800`02a5ae50
Debug session time: Tue Aug 24 21:12:26.798 2010 (UTC - 3:00)
System Uptime: 0 days 0:00:40.234
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 117, {fffffa8006baa010, fffff8801000dcf8, 0, 0}
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
Probably caused by : nvlddmkm.sys ( nvlddmkm+119cf8 )
Followup: MachineOwner
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_TIMEOUT_DETECTED (117)
The display driver failed to respond in timely fashion.
(This code can never be used for real bugcheck).
Arguments:
Arg1: fffffa8006baa010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8801000dcf8, The pointer into responsible device driver module (e.g owner tag).
Arg3: 0000000000000000, The secondary driver specific bucketing key.
Arg4: 0000000000000000, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+119cf8
fffff880`1000dcf8 ?? ???
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT
TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x117
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`033e8400 fffff880`0fe5b4ef : fffffa80`06baa010 102906c9`a00038bf 00000000`00000000 fffffa80`06049901 : watchdog!WdDbgReportRecreate+0xa3
fffff880`033e8920 fffff880`0fe5bf6d : fffff8a0`01d5cffc fffff8a0`01309520 fffff8a0`01c07bcb 00000000`00155431 : dxgkrnl!TdrUpdateDbgReport+0xcb
fffff880`033e8970 fffff880`0fe5cbda : fffffa80`06baa010 fffffa80`06baa010 fffffa80`060e8830 fffffa80`06049010 : dxgkrnl!TdrCollectDbgInfoStage1+0x92d
fffff880`033e8a10 fffff880`10b97f07 : fffffa80`06baa010 00000000`00000000 fffffa80`060e8830 fffffa80`06049010 : dxgkrnl!TdrIsRecoveryRequired+0x17a
fffff880`033e8a40 fffff880`10bc1b75 : 00000000`ffffffff 00000000`00000933 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`033e8b20 fffff880`10bc02bb : 00000000`00000102 00000000`00000000 00000000`00000933 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`033e8b50 fffff880`10b932c6 : ffffffff`ff676980 fffffa80`06049010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`033e8bf0 fffff880`10bbfe7a : 00000000`00000000 fffffa80`060e8830 00000000`00000080 fffffa80`06049010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`033e8d00 fffff800`02b31c06 : 00000000`025cd651 fffffa80`0603d060 fffffa80`036e6040 fffffa80`0603d060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`033e8d40 fffff800`0286bc26 : fffff880`02f63180 fffffa80`0603d060 fffff880`02f6dfc0 fffff880`01218a90 : nt!PspSystemThreadStartup+0x5a
fffff880`033e8d80 00000000`00000000 : fffff880`033e9000 fffff880`033e3000 fffff880`07a4d8a0 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+119cf8
fffff880`1000dcf8 ?? ???
SYMBOL_NAME: nvlddmkm+119cf8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c37918e
FAILURE_BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x117_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------