Random Crashes/BSOD - Please Debug

[Afck91]

Hello, I recently posted on here with minidumps a few weeks ago, which Yowan debugged for me - which was lead down to my graphics card video driver. I was recommended to uninstall with driver sweeper, re-install etc but that still didn't work.

To fix this, I re-installed windows 7, and the problem went away. I have recently starting getting this problem back, with the same driver popping up now and again in the minidumps. My graphics card is definitely not overheating btw.

Some of my minidumps are starting to show different 'probably caused by' drivers, so if someone will kindly debug my new minidump files (the most recent 2), it will be gladly appreciated.

I have uploaded them HERE.

I am just about to run Memtest86 over night, and will report back in the morning.

Just to add, the problem that caused my BSOD to crash and create these dump files, is my computer totally freezing up for a few seconds, display goes off and then back on, and everything is fine apart from mouse movement. I can navigate all the menus, task manager etc lag free via my keyboard etc.

My system specs are filled out.

Thanks guys,
Adam

 

[Afck91]

Ok, I ran memtest for 8hours 40mins, and they all passed.

Not sure what the problem could be... Anyway, while I wait for someone to come along and debug I am going to run Prime95 for a few hours.

Thanks,
Adam

 

[DeanP]

Hello Afck91. If you have reinstalled Windows - sounds like a hardware issue, not Windows.

Good to see you have check for memory errors with memtest.
Run Prime95 as you said (if you need help, you can use Jonathan's tutorial: http://www.sevenforums.com/tutorials/100352-cpu-stress-test-prime95.html)

I am currently analyzing your dumps - please be patient. My Internet Speed is decent - only goes 17kb/sec as I had exceeded my Internet usage.

To be correct, just check with your Video Card for issues or/and overheating: http://www.sevenforums.com/tutorials/100356-video-card-stress-test-furmark.html

 

[Shadowjk]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception

Debugging Details:
------------------


EXCEPTION_CODE: (Win32) 0 (0) - The operation completed successfully.

FAULTING_IP: 
+58752faf035fd864
00000000`00000000 ??              ???

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

ERROR_CODE: (NTSTATUS) 0 - STATUS_WAIT_0

BUGCHECK_STR:  0x1E_0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff8000307d46e to fffff80003085710

STACK_TEXT:  


STACK_COMMAND:  kb

FOLLOWUP_IP: 
Lycosa+1267
fffff880`051ab267 ??              ???

SYMBOL_STACK_INDEX:  6

SYMBOL_NAME:  Lycosa+1267

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Lycosa

IMAGE_NAME:  Lycosa.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ac2e27e

FAILURE_BUCKET_ID:  X64_0x1E_0_Lycosa+1267

BUCKET_ID:  X64_0x1E_0_Lycosa+1267

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

Hello Your Dump Reports to Lycosa.sys

Lycosa.sys is a Keyboard Driver or another Hardware Driver - Open up Device Manger and Uninstall any Keyboard or Human Interface Drivers and restart your Computer

After that Run an System File Checker Scan and a Full system Scan with your Anti-Virus

See http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html?ltr=S For More Information

Please be advised that a Minidump only has a Possible answer and you may experience more if so please Upload so the more you Upload and the more we Debug the better the Chance of finding the Problem

Hope This Helps,
Josh

 

[Afck91]

Hello Afck91. If you have reinstalled Windows - sounds like a hardware issue, not Windows.

Hi, sorry if I did not make it clear enough in my last post.

What it was, is this has happened to me before, where minidumps gave me the probably caused by: nvlddmkm.sys. I un-installed all my graphics drivers, used driver sweeper etc, and installed new drivers - but this still did not solve the problem.

I managed to solve the problem in the end by re-installing Windows 7.

This worked perfectly fine for weeks, but the problem has now come back, and I have posted the minidumps in the original post which you are currently downloading.

My graphics card is definitely not overheating, and I will run furmark now to test.

Thanks,
Adam

 

[Afck91]

Thanks Josh.

Strangely enough, I had a feeling it was either my keyboard or mouse causing this problem, as it is always my mouse that starts lagging before my system crashes.

I have just updated the firmware on my Razer mouse, and I will check if all my Razer drivers are up to date.

Can you confirm if thats the same problem in the last 2 minidumps?

Thanks,
Adam

 

[Shadowjk]

I would Update them then Uninstall them Just to be sure that is the most likely cause but please Upload any more Dumps if you receive any I am happy to Debug them for you

 

[Afck91]

Thanks, much aprechiated Josh!

Could you confirm that it was Razer showing up in both recent minidumps?

Is it Razer in all them minidumps?

Thanks again,
Adam

 

[Shadowjk]

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800b0fb4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8801080f5b0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+7605b0
fffff880`1080f5b0 803da1c3530000  cmp     byte ptr [nvlddmkm+0xc9c958 (fffff880`10d4b958)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7605b0
fffff880`1080f5b0 803da1c3530000  cmp     byte ptr [nvlddmkm+0xc9c958 (fffff880`10d4b958)],0

SYMBOL_NAME:  nvlddmkm+7605b0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4bd8c41a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

A Navidia Driver did occur - If you have a spare Graphics card replace it if not please Reinstall the Navidia Graphics card Driver and restart your Computer

Hope This Helps,
Josh

 

[richc46]

Your dump reports are consistent. They show that the graphics card is the cause. Code 116 indicates
STOP 0x00000116: VIDEO_TDR_ERROR Usual causes: Video driver, overheating, bad video card, ?BIOS, ?Power to card

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

Loading Dump File [C:\Users\richc46\AppData\Local\Temp\Temp12_Windows_NT6_BSOD_jcgriff2[1].zip\Windows_NT6_BSOD_jcgriff2\010411-9531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\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
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`03011000 PsLoadedModuleList = 0xfffff800`0324ee50
Debug session time: Mon Jan  3 20:39:02.119 2011 (GMT-5)
System Uptime: 0 days 1:33:05.165
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8009f37010, fffff880107895b0, ffffffffc000009a, 4}
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+7605b0 )
Followup: MachineOwner
---------
5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009f37010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880107895b0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.
Debugging Details:
------------------

FAULTING_IP: 
nvlddmkm+7605b0
fffff880`107895b0 803da1c3530000  cmp     byte ptr [nvlddmkm+0xc9c958 (fffff880`10cc5958)],0
DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT:  1
BUGCHECK_STR:  0x116
PROCESS_NAME:  System
CURRENT_IRQL:  0
STACK_TEXT:  
fffff880`02acbb88 fffff880`02e7fef8 : 00000000`00000116 fffffa80`09f37010 fffff880`107895b0 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02acbb90 fffff880`02e53867 : fffff880`107895b0 fffffa80`08a71000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02acbbd0 fffff880`02e7fd07 : 00000000`ffffd87b ffffffff`fffe7960 fffffa80`09f37010 fffff880`02f57dc0 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02acbc80 fffff880`02f57ec1 : fffffa80`086a8260 00000000`00000080 00000000`00000000 fffffa80`08a70010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02acbd00 fffff800`03325c06 : 00000000`017dcd25 fffffa80`08710b60 fffffa80`054ee040 fffffa80`08710b60 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02acbd40 fffff800`0305fc26 : fffff800`031fbe80 fffffa80`08710b60 fffff800`03209c40 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02acbd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16

STACK_COMMAND:  .bugcheck ; kb
FOLLOWUP_IP: 
nvlddmkm+7605b0
fffff880`107895b0 803da1c3530000  cmp     byte ptr [nvlddmkm+0xc9c958 (fffff880`10cc5958)],0
SYMBOL_NAME:  nvlddmkm+7605b0
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME:  nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP:  4bd8c41a
FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------

I have not spotted any outdated drivers or any that are known to cause BSOD
May I suggest at least for a tes that you rollback to the earlier version of the graphics driver?
For whatever reason, I am seeing a larger than average problem with graphics. May be something that has to be corrected in the future.

 

[Afck91]

Hi, I have just run Furmark for 1hour, and it maxxed out at 70-72degree's max, which is fine for a GTX470.

I am now going to run Prime95 and will post back with results.

Thanks
Adam

 

[Afck91]

Ok guys, I’m currently posting on my laptop whilst Prime95 is still running.

It has currently been running 6hours doing small fft's, as I have already run memtest86 over night. So far its stable, so I think we can rule out my CPU/RAM as I have also ran Prime95 blend test previously for 12hours + with the same bios settings etc and it was stable.

If memtest passes
prime95 appears stable
gpu can run furmark fine

Does this mean it’s definitely a driver error?

Can anyone else find anything other than the razer/nvidia errors in my minidumps?


Thanks,
Adam

 

[Jonathan_King]

I see your nVidia graphics drivers are on the old side:

nvlddmkm.sys    Wed Apr 28 19:26:18 2010 (4BD8C41A)

Install these updated ones, if you have not done so already: NVIDIA DRIVERS 260.99 WHQL

Your Yukon wireless drivers are old too:

yk62x64.sys     Wed May 20 04:14:06 2009 (4A13BBCE)

You should be able to find an update to them on the device manufacturer's (not chipset MFR!) site; I doubt they relate to this problem though.