BSOD when plugging in Logitech webcam

[corywf]

I'm getting a BSOD when I plug in a logitech pro 9000 or a c270. The PC starts to install the drivers then I get a BSOD for ks.sys. I don't have any Western Digital software installed. Attached are the logs. Thanks in advance!

Windows 7 Enterprise
6.1.7601 Service Pack 1 Build 7601
Dell Latitude E6420
Bios: Dell A04, 5/11/2011

 

[nckfrtg28]

Have you updated your bios?

 

[James7679]

Please fill in system specs and tell us current BIOS revision.

Thanks

 

[corywf]

Updated system specs above. Bios is now at A08

 

[nckfrtg28]

Have you made sure there is now virus on the computer?

 

[writhziden]

Problem Devices:

INTF1	USB\VID_15EB&PID_0001&MI_01\9&37092586&0&0001	This device is not configured correctly.
INTF2	USB\VID_15EB&PID_0001&MI_02\9&37092586&0&0002	This device is not configured correctly.

Security Software:

rtvscan.exe	c:\program files\symantec\symantec endpoint protection\rtvscan.exe	2468	8	200	1380	3/20/2012 3:44 PM	11.0.6200.513	1.75 MB (1,839,776 bytes)	2/18/2011 9:36 AM
smc.exe	c:\program files\symantec\symantec endpoint protection\smc.exe	1480	8	200	1380	3/20/2012 3:44 PM	11.0.6200.530	1.81 MB (1,893,728 bytes)	2/18/2011 9:36 AM
smcgui.exe	c:\program files\symantec\symantec endpoint protection\smcgui.exe	4360	8	200	1380	3/20/2012 3:45 PM	11.0.6200.530	1.39 MB (1,459,568 bytes)	2/18/2011 9:36 AM

Possible out of date drivers:

mdmxsdk	b7b5c000	b7b5f180	Mon Jun 19 15:26:59 2006 (449716a3)	0000c5ae		mdmxsdk.sys
omci	9c4b1000	9c4bc000	Tue Aug 19 07:02:13 2008 (48aac455)	0000588e		omci.sys
UltraMonUtility	8d688000	8d68a900	Thu Nov 13 18:09:26 2008 (491ccfc6)	00010568		UltraMonUtility.sys
HSX_CNXT	9f51d000	9f5d2000	Fri Feb 13 13:57:25 2009 (4995deb5)	000a26b8		HSX_CNXT.sys
HSXHWAZL	9ed38000	9ed75000	Fri Feb 13 13:58:15 2009 (4995dee7)	000384c4		HSXHWAZL.sys
HSX_DPV	9f41b000	9f51d000	Fri Feb 13 14:00:17 2009 (4995df61)	000f4620		HSX_DPV.sys
dsNcAdpt	9eae2000	9eaed000	Mon Mar 30 20:39:02 2009 (49d18246)	00008e2a		dsNcAdpt.sys
radiamsi	b8ee0000	b8ee5c80	Mon Apr 27 14:06:09 2009 (49f61031)	0000afc7		radiamsi.sys
XAudio32	9f600000	9f608000	Wed Apr 29 12:20:55 2009 (49f89a87)	00007cc4		XAudio32.sys
[COLOR="Red"][B]SYMTDI	8c1ac000	8c1d8480	Wed Jun 17 15:11:02 2009 (4a395be6)	00038832		SYMTDI.SYS
SYMREDRV	b8fc8000	b8fccd00	Wed Jun 17 15:11:33 2009 (4a395c05)	0000bd74		SYMREDRV.SYS[/B][/COLOR]

mdmxsdk.sys
omci.sys
UltraMonUtility.sys
HSX_CNXT.sys
HSXHWAZL.sys
HSX_DPV.sys
dsNcAdpt.sys
radiamsi.sys
XAudio32.sys
Update your Symantec Endpoint Protection software. It is out of date!! Symantec - AntiVirus, Anti-Spyware, Endpoint Security, Backup, Storage Solutions

[list=1][*]
Loading Dump File [D:\Kingston\BSODDmpFiles\corywf\Windows_NT6_BSOD_jcgriff2\032012-32573-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0x82e50000 PsLoadedModuleList = 0x82f994d0
Debug session time: Tue Mar 20 13:42:04.112 2012 (UTC - 6:00)
System Uptime: 0 days 0:16:34.618
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...............
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000006, 9ebc748b, bce77950, 0}

*** WARNING: Unable to verify timestamp for lvrs.sys
*** ERROR: Module load completed but symbols could not be loaded for lvrs.sys
Probably caused by : ks.sys ( ks!KsDispatchIrp+ac )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000006, The exception code that was not handled
Arg2: 9ebc748b, The address that the exception occurred at
Arg3: bce77950, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000006 - The instruction at 0x%p referenced memory at 0x%p. The required data was not placed into memory because of an I/O error status of 0x%x.

FAULTING_IP: 
ks!KsDispatchIrp+ac
9ebc748b 8b00            mov     eax,dword ptr [eax]

TRAP_FRAME:  bce77950 -- (.trap 0xffffffffbce77950)
ErrCode = 00000000
eax=eae3b483 ebx=862b7a70 ecx=0000000e edx=862b7a70 esi=85acc648 edi=8b4535b4
eip=9ebc748b esp=bce779c4 ebp=bce779cc iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
ks!KsDispatchIrp+0xac:
9ebc748b 8b00            mov     eax,dword ptr [eax]  ds:0023:eae3b483=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x8E

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 9ebb70ba to 9ebc748b

STACK_TEXT:  
bce779cc 9ebb70ba 85c072e0 862b7a70 85c072e0 ks!KsDispatchIrp+0xac
bce779e4 82e875be 85c072e0 862b7a70 862b7a70 ks!CKsDevice::PassThroughIrp+0x46
bce779fc 8d247cac 862b7a70 8b4535b4 00000000 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
bce77a30 8d24847b 862b7a70 8b5baa28 862589a0 lvrs+0x12cac
bce77a98 8d23c300 862b7cfc bce77af8 8b5baa28 lvrs+0x1347b
bce77afc 82e875be 862589a0 862b7a70 862b7a70 lvrs+0x7300
bce77b14 8307aac9 8b5baa28 862b7a70 862b7cfc nt!IofCallDriver+0x63
bce77b34 8307dc9b 862589a0 8b5baa28 00000000 nt!IopSynchronousServiceTail+0x1f8
bce77bd0 830c45c4 862589a0 862b7a70 00000000 nt!IopXxxControlFile+0x6aa
bce77c04 82e8e28a 000001f0 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
bce77c04 77c37094 000001f0 00000000 00000000 nt!KiFastCallEntry+0x12a
01a9f084 00000000 00000000 00000000 00000000 0x77c37094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ks!KsDispatchIrp+ac
9ebc748b 8b00            mov     eax,dword ptr [eax]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ks!KsDispatchIrp+ac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ks

IMAGE_NAME:  ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799d9

FAILURE_BUCKET_ID:  0x8E_ks!KsDispatchIrp+ac

BUCKET_ID:  0x8E_ks!KsDispatchIrp+ac

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\corywf\Windows_NT6_BSOD_jcgriff2\032012-51979-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.x86fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0x82e09000 PsLoadedModuleList = 0x82f524d0
Debug session time: Tue Mar 20 12:42:27.527 2012 (UTC - 6:00)
System Uptime: 0 days 0:37:23.335
Loading Kernel Symbols
...............................................................
................................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
......
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: eae3b483, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 9d9db48b, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000002, (reserved)

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

*** WARNING: Unable to verify timestamp for lvrs.sys
*** ERROR: Module load completed but symbols could not be loaded for lvrs.sys

Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from 82f72848
Unable to read MiSystemVaType memory at 82f51e20
 eae3b483 

FAULTING_IP: 
ks!KsDispatchIrp+ac
9d9db48b 8b00            mov     eax,dword ptr [eax]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

CURRENT_IRQL:  0

TRAP_FRAME:  ce76b950 -- (.trap 0xffffffffce76b950)
ErrCode = 00000000
eax=eae3b483 ebx=86274008 ecx=0000000e edx=86274008 esi=87ebb7c0 edi=863fd894
eip=9d9db48b esp=ce76b9c4 ebp=ce76b9cc iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
ks!KsDispatchIrp+0xac:
9d9db48b 8b00            mov     eax,dword ptr [eax]  ds:0023:eae3b483=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82e4a478 to 82e973ff

STACK_TEXT:  
ce76b938 82e4a478 00000000 eae3b483 00000000 nt!MmAccessFault+0x106
ce76b938 9d9db48b 00000000 eae3b483 00000000 nt!KiTrap0E+0xdc
ce76b9cc 9d9cb0ba 8631a8a0 86274008 8631a8a0 ks!KsDispatchIrp+0xac
ce76b9e4 82e405be 8631a8a0 86274008 86274008 ks!CKsDevice::PassThroughIrp+0x46
ce76b9fc e203fcac 86274008 863fd894 00000000 nt!IofCallDriver+0x63
WARNING: Stack unwind information not available. Following frames may be wrong.
ce76ba30 e204047b 86274008 8b442440 87f44020 lvrs+0x12cac
ce76ba98 e2034300 86274294 ce76baf8 8b442440 lvrs+0x1347b
ce76bafc 82e405be 87f44020 86274008 86274008 lvrs+0x7300
ce76bb14 83033ac9 8b442440 86274008 86274294 nt!IofCallDriver+0x63
ce76bb34 83036c9b 87f44020 8b442440 00000000 nt!IopSynchronousServiceTail+0x1f8
ce76bbd0 8307d5c4 87f44020 86274008 00000000 nt!IopXxxControlFile+0x6aa
ce76bc04 82e4728a 00000154 00000000 00000000 nt!NtDeviceIoControlFile+0x2a
ce76bc04 76f67094 00000154 00000000 00000000 nt!KiFastCallEntry+0x12a
0113f69c 00000000 00000000 00000000 00000000 0x76f67094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
ks!KsDispatchIrp+ac
9d9db48b 8b00            mov     eax,dword ptr [eax]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  ks!KsDispatchIrp+ac

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ks

IMAGE_NAME:  ks.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ce799d9

FAILURE_BUCKET_ID:  0x50_ks!KsDispatchIrp+ac

BUCKET_ID:  0x50_ks!KsDispatchIrp+ac

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


[/list]

1. Blames the system kernel CSA library driver, but it is most likely caused by lvrs.sys, which is your Logicool Qcam driver.
2. Also due to the Qcam driver.

Remove the Logitech webcam drivers, software, and then the device itself. Try installing the software first, then insert the webcam when the software installation gives instructions to do so.

Clean install of Logitech camera software for Windows may also be good further reading

Webcam Pro 9000

HD Webcam C270

 

[corywf]

I updated symantec and completely removed all traces of logitech from my PC. I then installed the software using your instructions and plugged in the camera. Got the same BSOD. I don't have any more time to troubleshoot this as it's my work laptop so I grabbed a HP webcam we had and it installed no problem. I'm going to use it but it's going to bug me that I couldn't get the logitech one working.

Thanks for the help.

 

[James7679]

FYI, your Logitech webcam, and other variations of it, have an extremely large number of hits for causing BSODs. The driver in particular is noted on all of them as the culprit.

 

[writhziden]

I updated symantec and completely removed all traces of logitech from my PC. I then installed the software using your instructions and plugged in the camera. Got the same BSOD. I don't have any more time to troubleshoot this as it's my work laptop so I grabbed a HP webcam we had and it installed no problem. I'm going to use it but it's going to bug me that I couldn't get the logitech one working.

Thanks for the help.

I would recommend contacting Logitech regarding this problem. Especially given the very helpful additional information provided by jamesandalexis:

FYI, your Logitech webcam, and other variations of it, have an extremely large number of hits for causing BSODs. The driver in particular is noted on all of them as the culprit.

 

[corywf]

I updated symantec and completely removed all traces of logitech from my PC. I then installed the software using your instructions and plugged in the camera. Got the same BSOD. I don't have any more time to troubleshoot this as it's my work laptop so I grabbed a HP webcam we had and it installed no problem. I'm going to use it but it's going to bug me that I couldn't get the logitech one working.

Thanks for the help.

I would recommend contacting Logitech regarding this problem. Especially given the very helpful additional information provided by jamesandalexis:

FYI, your Logitech webcam, and other variations of it, have an extremely large number of hits for causing BSODs. The driver in particular is noted on all of them as the culprit.

While researching this issue I found a ton of hits as well. Logitech hardware is good, their drivers, not so much. I gave the camera to a coworker and it worked with no problems on his computer so I'm guessing there's still something screwy with my PC.

 

[James7679]

Not all PC components play well with other PC components. It's not at all unusual that one webcam won't work on your PC, but works fine on another. This is also a common problem with Creative Labs. Don't sweat it, it happens.

 

[corywf]

I have a creative sound card in my win7 pc at home. It was fun to get the drivers working for that. I didn't know about this forum until I had the webcam problem so something good came out of it.

 

[writhziden]

You could see if it is an application conflict causing the crashes: http://www.sevenforums.com/tutorial...ation-conflicts-performing-clean-startup.html

 

[James7679]

We are glad to have you. You will find no greater compilation of knowledge and kindness than what is available here.