View Single Post
12 Mar 2010  
zigzag3143

Win 8 Release candidate 8400
 
 

Quote   Quote: Originally Posted by timsull View Post
Hey all. I'm trying to narrow down an issue that's plagued me since I got this PC less than a month ago. When playing any 3D games, I'm getting booted to the desktop seemingly randomly with this message appearing in the Event Viewer as the cause: 'nvlddmkm has stopped responding and has successfully recovered'. Sometimes the games come back, most times they crash at this point.

I had thought it was an issue with my Xeno NIC card since earlier dumps pointed to the ndiswan.sys file. I've tried reinstalling the drivers for the NIC but it made no difference. I have since removed all traces of the NIC and its drivers and started using the onboard NIC but the problem persists.

I've been monitoring the temperatures of the CPU and GPU as well while running the games but they all stay within acceptable ranges.

I've tried different diplay driver versions as well but have since used a drive sweeper program in safe mode to clear out all the nvidia files and re-installed the latest 196.21 drivers again with no change.

It was suggested to run a system file check as well which I did and it came up with no errors found.

I have tried removing one of the video cards and running the other solo and then swapping them to see if it's related to one of them but I still get this message.

I've run memtest on all the memory with no issues but the last thing I was going to try was to pull out all the memory and run one stick at a time and see if I can trace it back to that but haven't had a chance to yet.

If testing the physical memory fails to resolve this then I am at a loss. I'm hoping for some insight or suggestions from anyone that may have had experience with this issue as I've reseached it and seen that it's been around for quite some time.

I've attached the latest dump files that were created when the driver stopped responding. I would appreciate anyone able to anaylze these files and maybe point me in a direction as I'm not sure which way to go with this now.

Thank you!
Hi and welcome

Well There are two causes for your crashes. The first and most obvious is the directx portion of your video driver. The second somewhat more hidden is your Norton (either NIS, or 360)

I would COMPLETELY remove your video driver and install a fresh copy. You have to remove all traces of the current one including and control panel etc

Then I would uninstall Norton (use their removal tool). If the problem persists run a system file check
(type cmd in search>right click and run as admin>sfc /scannow)

Let us know the results

Ken


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\New folder (3)\WD-20100311-2101.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`04213000 PsLoadedModuleList = 0xfffff800`04450e50
Debug session time: Thu Mar 11 21:01:09.443 2010 (GMT-5)
System Uptime: 0 days 3:34:08.411
Loading Kernel Symbols
...............................................................
................................................................
..............................
Loading User Symbols
Mini Kernel Dump does not contain unloaded driver list
Unable to load image dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 117, {fffffa8011f8c4e0, fffff88010156a20, 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+112a20 )

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

6: 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: fffffa8011f8c4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88010156a20, 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+112a20
fffff880`10156a20 ??              ???

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_TIMEOUT

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


BUGCHECK_STR:  0x117

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`04236630 fffff880`04cd44ef : fffffa80`11f8c4e0 fffff880`04d20c80 fffffa80`11f8c4e0 fffff880`04ca2843 : watchdog!WdDbgReportRecreate+0xa3
fffff880`04236b50 fffffa80`11f8c4e0 : fffff880`04d20c80 fffffa80`11f8c4e0 fffff880`04ca2843 00000000`00000000 : dxgkrnl+0x5b4ef
fffff880`04236b58 fffff880`04d20c80 : fffffa80`11f8c4e0 fffff880`04ca2843 00000000`00000000 00000000`00000000 : 0xfffffa80`11f8c4e0
fffff880`04236b60 fffffa80`11f8c4e0 : fffff880`04ca2843 00000000`00000000 00000000`00000000 fffffa80`1243a0a0 : dxgkrnl+0xa7c80
fffff880`04236b68 fffff880`04ca2843 : 00000000`00000000 00000000`00000000 fffffa80`1243a0a0 fffff8a0`0e471354 : 0xfffffa80`11f8c4e0
fffff880`04236b70 00000000`00000000 : 00000000`00000000 fffffa80`1243a0a0 fffff8a0`0e471354 fffffa80`112e7010 : dxgkrnl+0x29843


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+112a20
fffff880`10156a20 ??              ???

SYMBOL_NAME:  nvlddmkm+112a20

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b4c080b

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------
My System SpecsSystem Spec