Can anyone analyze dump files?

[timsull]

Hey all, new to the forums. I have an issue that's been around for a long time:

'nvlddmkm has stopped responding and has recovered'

I've been through the ringer trying to pin this down on my specific system the past few weeks (I received the system less than a month ago).

From updating drivers to running one video card at a time to a bunch of researched 'fixes', I've tried to narrow it down to no avail.

One big issue I had that I believe I solved was when starting a game called 'Dragon Age: Origins'. The game would blue screen on me 50%-80% of the time I'd try to start it up. It ended up being a problem with the drivers on my Xeno Killer NIC. I had the newest drivers but they must have been corrupted as re-downloading and re-installing them seemed to fix it. I no longer have the issue.

However, the nvlddmkm issue has been there since the beginning with any of the games I'm playing and no amount of driver installs, both new and old, have seemed to help. Drive sweeper has helped a bunch to clean out any offending leftover files between installs. I was hoping the Xeno drivers were responsible for it as well but it came back yesterday and dashed my hopes.

I used WhoCrashed to get an idea of what was going on in the dump files to help me remedy it, but it's information is sparse at best and I know that there are those out there able to glean more from them than I can.

I have two from yesterday that I was wondering if anyone can look at for me. If there is anything in there to give me a direction to go in, I would be most appreciative. If not, I'll have to move on to physically swapping memory sticks one at a time as that's about the only thing left I haven't tried. Memory tests came back clean but that doesn't prove it enough to me that it can't be the memory for sure.

I'd be grateful for any information and/or advice concerning this issue.

Thank you!

 

[zigzag3143]

Hey all, new to the forums. I have an issue that's been around for a long time:

'nvlddmkm has stopped responding and has recovered'

I've been through the ringer trying to pin this down on my specific system the past few weeks (I received the system less than a month ago).

From updating drivers to running one video card at a time to a bunch of researched 'fixes', I've tried to narrow it down to no avail.

One big issue I had that I believe I solved was when starting a game called 'Dragon Age: Origins'. The game would blue screen on me 50%-80% of the time I'd try to start it up. It ended up being a problem with the drivers on my Xeno Killer NIC. I had the newest drivers but they must have been corrupted as re-downloading and re-installing them seemed to fix it. I no longer have the issue.

However, the nvlddmkm issue has been there since the beginning with any of the games I'm playing and no amount of driver installs, both new and old, have seemed to help. Drive sweeper has helped a bunch to clean out any offending leftover files however. I was hoping the Xeno drivers were responsible for it as well but it came back yesterday and dashed my hopes.

I used WhoCrashed to get an idea of what was going on in the dump files to help me remedy it, but it's information is sparse at best and I know that there are those out there able to glean more from them than I can.

I have two from yesterday that I was wondering if anyone can look at for me. If there is anything in there to give me a direction to go in, I would be most appreciative. If not, I'll have to move on to physically swapping memory sticks one at a time as that's about the only thing left I haven't tried. Memory tests came back clean but that doesn't prove it enough to me that it can't be the memory for sure.

I'd be grateful for any information and/or advice concerning this issue.

Thank you!

Bot of these crashes had both your video driver and your network driver ndiswan.sys


First you must un-install all remnants of the video driver and install a new fresh driver. Then you should update your network driver.

Finally run a system file check to verify and repair your system files
type cmd in search>right click and run as admin>sfc /scannow

Let us know if you need help

Ken

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\WD-20100309-2025.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`0425f000 PsLoadedModuleList = 0xfffff800`0449ce50
Debug session time: Tue Mar  9 20:25:28.193 2010 (GMT-5)
System Uptime: 0 days 1:35:38.161
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, {fffffa800f58a010, fffff88010128230, 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+10d230 )

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

1: 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: fffffa800f58a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88010128230, 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+10d230
fffff880`10128230 ??              ???

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`037b9630 fffff880`04b1b4ef : fffffa80`0f58a010 fffff880`04b67c80 fffffa80`0f58a010 fffff880`04ae9843 : watchdog!WdDbgReportRecreate+0xa3
fffff880`037b9b50 fffffa80`0f58a010 : fffff880`04b67c80 fffffa80`0f58a010 fffff880`04ae9843 00000000`00000000 : dxgkrnl+0x5b4ef
fffff880`037b9b58 fffff880`04b67c80 : fffffa80`0f58a010 fffff880`04ae9843 00000000`00000000 00000000`00000000 : 0xfffffa80`0f58a010
fffff880`037b9b60 fffffa80`0f58a010 : fffff880`04ae9843 00000000`00000000 00000000`00000000 fffffa80`11701010 : dxgkrnl+0xa7c80
fffff880`037b9b68 fffff880`04ae9843 : 00000000`00000000 00000000`00000000 fffffa80`11701010 fffff8a0`11496671 : 0xfffffa80`0f58a010
fffff880`037b9b70 00000000`00000000 : 00000000`00000000 fffffa80`11701010 fffff8a0`11496671 fffffa80`10ff0010 : dxgkrnl+0x29843


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+10d230
fffff880`10128230 ??              ???

SYMBOL_NAME:  nvlddmkm+10d230

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b07613e

FAILURE_BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x117_IMAGE_nvlddmkm.sys

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

 

[timsull]

Thank you so much for the quick response and helpful information, I really do appreciate it.

A question for you, if you don't mind.

If I were to use the onboard NIC, would I most likely still end up with this error because the ndiswan.sys file is a general Windows network file not specifically related to the Xeno NIC?

I only ask because if the problem persists afterwards, I wouldn't be upset to lose the Xeno NIC in favor of the onboard NIC if it's always going to cause a problem with my specific configuration.

Forgive me if this is an ambiguous or unanswerable question as I'm still new to a lot of this and have been using the same old XP machine for the last 6 years with no issues. (I see no reason to give it up as it runs so well!)

 

[timsull]

Hey there. I did as instructed and uninstalled the drivers for both the video cards and the network card and swept any remnants in safe mode using 2 different drive sweeper programs. I re-installed both with the latest drivers and ran the file system check which came up with no errors.

So far everything seems fine. I did run into one problem later in the evening. I was away from the keyboard for a bit and of course that's when the game stopped responding. I came back and I was on the desktop. I went into the Event Viewer and noticed the failing display message but I also noticed the defrag had run at the same time this occurred. It's a little strange since there's not an automatic defrag enabled.

I've attached the newest dump file in the hopes it can be analyzed as well. I'm trying to see if the problem with the ndiswan.sys file is still occurring or if this a different problem possibly related to the defrag happening at the same time.

Would there be any other reason a defrag would run if it's not in the task scheduler?

I'd appreciate any insight into this as I'm hoping the original problem I posted about has stopped happening.

Thank you.

Edit: I also have Norton Internet Security 2010 running as well. Does anyone know if this would cause a defrag to trigger even while a game is running?

 

[timsull]

Bump.