Windows 7 Forums
Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Freeze and crash


26 Aug 2010   #1

Windows 7 Ultimate x64
 
 
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...
Quote:
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
---------
This is other mini dump. This is a 117 error.

Quote:
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
---------
I will appreciate any ideas.


My System SpecsSystem Spec
.

27 Aug 2010   #2

Windows 7 Ultimate x64, Mint 9
 
 

Both point to your graphics driver. Give it an update or reinstall.

~Lordbob
My System SpecsSystem Spec
27 Aug 2010   #3

Windows Server 2008 R2
 
 

Lordbob is right - either the driver's got a problem, or the hardware underneath may be bad. We've got a whole section on troubleshooting systems when a 116 or 117 bugcheck is encountered here, so I'd suggest you head over there and have a look.
My System SpecsSystem Spec
.


27 Aug 2010   #4

Windows 7 Ultimate x64
 
 

If the hardware is bad then the i can't seem to prove that. For example I have tested intensively the graphic card with occt, the video card ram and the gpu stress I for a long while. Also this is happening when Im doing not so demanding 3d task like launching a video or a YouTube video and on a loading screen of stracraft 2.
So I don't know about a hardware issue on the nvidia card, as I say the video card ram tests ok.

I will run a memtest for the ram of my system. And then a clean reinstall of drivers.

Also I have changed the psu to a more powerfully corsair 650w. The eurocase i had gave me the dame issue.

I will report back later n
My System SpecsSystem Spec
27 Aug 2010   #5

Windows Server 2008 R2
 
 

I've heard going back a few months' drivers has also helped some folks, so consider either the latest driver, or a driver version that predates this particular issue, as another test. I don't think this is a RAM issue.
My System SpecsSystem Spec
27 Aug 2010   #6

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by cluberti View Post
I've heard going back a few months' drivers has also helped some folks, so consider either the latest driver, or a driver version that predates this particular issue, as another test. I don't think this is a RAM issue.
I agree I dint think there is a ram problem. Anyway I'm running memtest now. Hope to have some results in a while.
Is sort of strange. It doesn't crash on graphic intensive applications, some videos, and that sort ofstuff.
Also I have stressed the gpu with occt and it was stable.

I'm trying to figure this out.

What would be the correct steps to uninstall a nvidia driver?
My System SpecsSystem Spec
27 Aug 2010   #7

Windows 7 Ultimate 32 bit
 
 

What I did was download five drivers to my desktop. Those were the ones I wanted to try. In Device Manager, I uninstalled the current driver and installed the driver I wanted try. If you have the installer with the driver on your desktop, uninstall in Device Manager, exit Device Manager and click on the installer of the the driver you wish to try. Reboot.

Edited to add: I ended up using the third or fourth driver down the list.
My System SpecsSystem Spec
27 Aug 2010   #8

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by CarlTR6 View Post
What I did was download five drivers to my desktop. Those were the ones I wanted to try. In Device Manager, I uninstalled the current driver and installed the driver I wanted try. If you have the installer with the driver on your desktop, uninstall in Device Manager, exit Device Manager and click on the installer of the the driver you wish to try. Reboot.

Edited to add: I ended up using the third or fourth driver down the list.
Can you tell me what nvidia driver you are using now?

I will try to uninstall and reinstall other driver.

The thing is I have tested the ram, is ok. Both the nvidia ram and the pc ram.

EDIT: What do you guys think about tunning the Windows 7 registry about the TDR? For example with these keys:

Registry Keys

The following registry keys are documented for testing purposes only. These registry keys should not be manipulated by any applications outside targeted testing or debugging.
The TDR-related registry keys are located under HKLM\System\CurrentControlSet\Control\GraphicsDrivers.
TdrLevel: REG_DWORD. The initial level of recovery. The possible values are:
•TdrLevelOff (0). – Detection disabled.
•TdrLevelBugcheck (1) – Bug check on detected timeout, for example, no recovery.
•TdrLevelRecoverVGA (2) – Recover to VGA (not implemented).
•TdrLevelRecover(3) – Recover on timeout. This is the default value.
TdrDelay: REG_DWORD. The number of seconds that the GPU is allowed to delay the preempt request from the scheduler. This is effectively the timeout threshold. The default value is 2.
TdrDdiDelay: REG_DWORD. The number of seconds that the operating system allows threads to leave the driver. After a specified time, the operating system bug checks the system with the code VIDEO_TDR_FAILURE (0x116). The default value is 5.
TdrTestMode: REG_DWORD: Internal test usage.
TdrDebugMode: REG_DWORD: The debugging-related behavior of the TDR process.
•TDR_DEBUG_MODE_OFF (0) breaks to kernel debugger before the recovery to allow investigation of the timeout.
•TDR_DEBUG_MODE_IGNORE_TIMEOUT (1) ignores any timeout.
•TDR_DEBUG_MODE_RECOVER_NO_PROMPT (2) recovers without break into the debugger. This is the default value.
•TDR_DEBUG_MODE_RECOVER_UNCONDITIONAL (3) recovers even if some recovery conditions are not met (for example, recovers on consecutive timeouts).
TdrLimitTime: REG_DWORD (Windows Vista SP1 and later versions only): The default time within which a "TdrLimitCount" number of TDRs are allowed without crashing the system.
TdrLimitCount: REG_DWORD (Windows Vista SP1 and later versions only): The default number of TDRs (0x117) that are allowed in "TdrLimitTime" without crashing the system.
My System SpecsSystem Spec
28 Aug 2010   #9

Windows 7 Ultimate 32 bit
 
 

I do not recommend tuning the registry. That is asking for big trouble and a system reinstall. Win 7 handles the registry much differently than XP. Do not mess with the registry unless you know precisely what your are dong, make a log of your changes and the values before the changes, and backup your registry. The registry is not the problem here. I would try a different card rather than mess with the registry.

I have a different card than you do; so the driver I ended up using will not apply. You will just have to experiment. Unfortunately, there is no shortcut to this process.
My System SpecsSystem Spec
28 Aug 2010   #10

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by CarlTR6 View Post
I do not recommend tuning the registry. That is asking for big trouble and a system reinstall. Win 7 handles the registry much differently than XP. Do not mess with the registry unless you know precisely what your are dong, make a log of your changes and the values before the changes, and backup your registry. The registry is not the problem here. I would try a different card rather than mess with the registry.

I have a different card than you do; so the driver I ended up using will not apply. You will just have to experiment. Unfortunately, there is no shortcut to this process.
got it. I will roll back.
Is annoying, the freeze occurs without a blue screen on windows start up sometimes, not always. Sometimes when playing starcraft 2 but only on loading screen, once it stars is fine.

I mean, I have checked the ram, the hdd, changed the psu to a more powerfull one and even checked the nvidia ram and gpu on several stress programs. Everything seems to be fine hardware side.
My System SpecsSystem Spec
Reply

 Freeze and crash




Thread Tools



Similar help and support threads for2: Freeze and crash
Thread Forum
Crash / freeze playing Starcraft2 BSOD Help and Support
Freeze + Crash BSOD Help and Support
Freeze & Crash In-Game BSOD Help and Support
Windows 7 pro 64 bit freeze/crash BSOD Help and Support
Random Freeze/Crash BSOD Help and Support
Strange crash, freeze BSOD Help and Support
Can DEP crash, freeze comp? General Discussion

Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:31 PM.
Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App
  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33