BSOD - Tried Most Everything

dchobanik · 19 Dec 2009

Ok I did remove the antivirus and went about 2-3 days with no problem then yesterday I checked and had this issue.

The minidump is attached.

Thanks

Devin

zigzag3143 · 19 Dec 2009

dchobanik said:

Ok I did remove the antivirus and went about 2-3 days with no problem then yesterday I checked and had this issue.

The minidump is attached.

Thanks

Devin

Hi Devin

this one is pretty clear cut. You vid driver (nvlddmkm.sys and dxgkrnl.sys) probably caused it. the dxgkrnl is the direct x component so you might want to consider updating that as well

I would update that and the other old drivers listed below
run a system file check to verify and repair your system fiels
type cmd in search>right click and run as admin>sfc /scannow

Of course if you are overclocking stop
if you have a raid update its driver

Code:

secdrv.SYS        fffff880`06195000    fffff880`061a0000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
lmimirr.sys        fffff880`044a4000    fffff880`044ab000    0x00007000    0x461c108d    4/10/2007 5:32:45 PM                        
RaInfo.sys        fffff880`04bb5000    fffff880`04bbc000    0x00007000    0x477e818a    1/4/2008 1:57:14 PM                        
LMIRfsDriver.sys        fffff880`04a00000    fffff880`04a13000    0x00013000    0x487b7e50    7/14/2008 11:26:56 AM

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\121709-42089-01.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 (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c5b000 PsLoadedModuleList = 0xfffff800`02e98e50
Debug session time: Thu Dec 17 20:13:31.283 2009 (GMT-5)
System Uptime: 1 days 9:37:00.546
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image \SystemRoot\System32\drivers\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 116, {fffffa800876d4e0, fffff8801031d230, 0, 2}

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+10d230 )

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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

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


FAULTING_IP: 
nvlddmkm+10d230
fffff880`1031d230 803d39d3b60000  cmp     byte ptr [nvlddmkm+0xc7a570 (fffff880`10e8a570)],0

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`055e69c8 fffff880`0450bef8 : 00000000`00000116 fffffa80`0876d4e0 fffff880`1031d230 00000000`00000000 : nt!KeBugCheckEx
fffff880`055e69d0 00000000`00000116 : fffffa80`0876d4e0 fffff880`1031d230 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
fffff880`055e69d8 fffffa80`0876d4e0 : fffff880`1031d230 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
fffff880`055e69e0 fffff880`1031d230 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`0876d4e0
fffff880`055e69e8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`0450bc02 : nvlddmkm+0x10d230


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+10d230
fffff880`1031d230 803d39d3b60000  cmp     byte ptr [nvlddmkm+0xc7a570 (fffff880`10e8a570)],0

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+10d230

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4b07613e

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

dchobanik · 31 Dec 2009

Hello I'm back and included is the latest dump, I have had a few recent crashes and have also checked to ensure all my drivers are up to date and I replaced my video card with a new one. Please let me know what is happening here.

Thanks

File is now included.

Thanks

zigzag3143 · 31 Dec 2009

dchobanik said:

Hello I'm back and included is the latest dump, I have had a few recent crashes and have also checked to ensure all my drivers are up to date and I replaced my video card with a new one. Please let me know what is happening here.

Thanks

Nothing attached try again

usasma · 01 Jan 2010

The last 2 dumps blame the OS kernel.

Please update or remove these older drivers that were loaded at the time of the crash. Don't use Windows Update or the Update drivers function of Device Manager. Please use the following instructions to locate the most current drivers:

How To Find Updated Drivers:
- search Google for the name of the driver
- compare the Google results with what's installed on your system to figure out which device/program it belongs to
- visit the web site of the manufacturer of the hardware/program to get the latest drivers (DON'T use Windows Update or the Update driver function of Device Manager).
- if there are difficulties in locating them, post back with questions and someone will try and help you locate the appropriate program.

Here's the older drivers:

Code:

LHidFilt.Sys Tue Jan 23 18:41:13 2007
lmimirr.sys  Tue Apr 10 18:32:45 2007
LMIRfsDriver.sys Mon Jul 14 12:26:56 2008
LMouFilt.Sys Tue Jan 23 18:41:16 2007
RaInfo.sys   Fri Jan 04 13:57:14 2008

Once you've updated everything, please try running Driver Verifier according to these instructions:

Using Driver Verifier is an iffy proposition. Most times it'll crash and it'll tell you what the driver is. But sometimes it'll crash and won't tell you the driver. Other times it'll crash before you can log in to Windows. If you can't get to Safe Mode, then you'll have to resort to offline editing of the registry to disable Driver Verifier.

So, I'd suggest that you first backup your stuff and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Win7 Startup Repair feature).

Then, here's the procedure:
- Go to Start and type in "verifier" (without the quotes) and press Enter
- Select "Create custom settings (for code developers)" and click "Next"
- Select "Select individual settings from a full list" and click "Next"
- Select everything EXCEPT FOR "Low Resource Simulation" and click "Next"
- Select "Select driver names from a list" and click "Next"
Then select all drivers NOT provided by Microsoft and click "Next"
- Select "Finish" on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out.

Reboot into Windows (after the crash) and turn off Driver Verifier by going back in and selecting "Delete existing settings" on the first page, then locate and zip up the memory dump file and upload it with your next post.

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
If that doesn't work, post back and we'll have to see about fixing the registry entry off-line.

More info on this at this link: Using Driver Verifier to identify issues with Windows drivers for advanced users

Here's a summary of the last 2 BSOD's:

Code:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sun Dec 27 04:31:27.197 2009 (GMT-5)
System Uptime: 0 days 4:29:13.295
BugCheck 7F, {8, 80050031, 6f8, fffff80001ead4d4}
Probably caused by : ntkrnlmp.exe ( nt!KiDoubleFaultAbort+b2 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Thu Dec 31 08:31:21.835 2009 (GMT-5)
System Uptime: 1 days 9:31:20.694
BugCheck 1E, {ffffffffc0000005, fffff800021880f1, 0, 1}
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+21 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  LogMeIn.exe

BSOD - Tried Most Everything

Updated Minidump

The Saga Continues