BSOD NVLDDMKM.sys

[Feyerman]

I think I have narrowed down some issues atleast for me and this nvlddmkm.sys I have the geforce 9100 card and win7 professional. I have tried to hook up 2 different USB PC TV Tuners. i have tried the AMD 600usb and the Pinnacle Ministick HD PCTV. Both seem to cause the BSOD. I have done fresh installs and worked a few days on it before adding the usb tuners stepping up software and adding my second monitor. The BSODs dont start until after installing the tv tuners.

Any Ideas on how to fix this? I have installed the latest drivers via windows update and via HP and Nvidia as well.

 

[Tews]

please upload the .dmp file for analysis...

 

[Feyerman]

Here are 2 of my .Dmp files.

 

[zigzag3143]

Here are 2 of my .Dmp files.

Hi feyerman and welcome

Both dumps are virtually identical. Of course it is the video driver spefically nvlddmkm.sys but in addition the directx component is failing

I would reinstall the video driver and directx. In addition I would upgrade the other drivers listed below

Not much more info to be gleaned from these two sorry

Ken J+

122109-21637-01.dmp    12/21/2009 9:40:50 PM        0x00000116    fffffa80`0ff784e0    fffff880`0486e490    00000000`00000000    00000000`00000002    dxgkrnl.sys    dxgkrnl.sys+5cef8                    
122209-22183-01.dmp    12/22/2009 9:49:44 AM        0x00000116    fffffa80`0e1b7010    fffff880`04847b10    00000000`00000000    00000000`00000002    dxgkrnl.sys    dxgkrnl.sys+5cef8

secdrv.SYS        fffff880`07d9d000    fffff880`07da8000    0x0000b000    0x4508052e    9/13/2006 8:18:38 AM                        
Intensity.sys        fffff880`04400000    fffff880`04440000    0x00040000    0x48ce09ab    9/15/2008 2:07:23 AM                        
deckaud.sys        fffff880`04821000    fffff880`0482c000    0x0000b000    0x48ce09b2    9/15/2008 2:07:30 AM                        
nvsmu.sys        fffff880`03feb000    fffff880`03ff6000    0x0000b000    0x49f27e62    4/24/2009 10:07:14 PM                        
nvstor64.sys        fffff880`00c00000    fffff880`00c3d000    0x0003d000    0x49f9058a    4/29/2009 8:57:30 PM                        
dump_nvstor64.sys        fffff880`01200000    fffff880`0123d000    0x0003d000    0x49f9058a    4/29/2009 8:57:30 PM                        
nvmf6264.sys        fffff880`040e6000    fffff880`04137380    0x00051380    0x49f9fff7    4/30/2009 2:45:59 PM                        
nvBridge.kmd        fffff880`0533c000    fffff880`0533d180    0x00001180    0x49fa89ca    5/1/2009 12:34:02 AM                        
nvlddmkm.sys    nvlddmkm.sys+12b10    fffff880`04835000    fffff880`0533b980    0x00b06980    0x49fa9da5    5/1/2009 1:58:45 AM

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


Loading Dump File [C:\Users\K\Desktop\122109-21637-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*d:\symbols*[URL="http://msdl.microsoft.com/download/symbols"]Symbol information[/URL]
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a0f000 PsLoadedModuleList = 0xfffff800`02c4ce50
Debug session time: Mon Dec 21 21:39:13.864 2009 (GMT-5)
System Uptime: 0 days 1:32:45.111
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, {fffffa800ff784e0, fffff8800486e490, 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+13490 )

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: fffffa800ff784e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800486e490, 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+13490
fffff880`0486e490 48895c2420      mov     qword ptr [rsp+20h],rbx

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`02e359c8 fffff880`04471ef8 : 00000000`00000116 fffffa80`0ff784e0 fffff880`0486e490 00000000`00000000 : nt!KeBugCheckEx
fffff880`02e359d0 00000000`00000116 : fffffa80`0ff784e0 fffff880`0486e490 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
fffff880`02e359d8 fffffa80`0ff784e0 : fffff880`0486e490 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
fffff880`02e359e0 fffff880`0486e490 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`0ff784e0
fffff880`02e359e8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`04471c02 : nvlddmkm+0x13490


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nvlddmkm+13490
fffff880`0486e490 48895c2420      mov     qword ptr [rsp+20h],rbx

SYMBOL_STACK_INDEX:  4

SYMBOL_NAME:  nvlddmkm+13490

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a620657

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

 

[Martin]

You have the same pc as I do, specifications are differents but follow this link and apply the hotfix

http://www.sevenforums.com/crashes-debugging/46852-bsod-new-install-2.html#post452277

apply this hotfix that will do it!
ftp://ftp.hp.com/pub/softlib/software11/COL31608/pv-78469-1/sp44620.exe