Reply
Logi Nu
Ambient13
Posts: 1
Registered: ‎09-24-2011
0

Skype BSOD crash during video call, caused by webcam drivers; Vista SP2

[ Edited ]


Description: BSOD occurred during video conference on non-logitech application (Skype). I initially thought that it might've had something to do with the Graphics driver update I applied this morning.

 

However, based on the dump file, the error was evidently caused by the webcam drivers - for some reason the webcam stopped working DURING the conversation, thus the crash. I had to restart the PC and reconnect the USB for the webcam to work again; the next conversation went well but I would still like to troubleshoot this problem so as to avoid it in the future.

 

-------------------

 

Webcam info:

 

M/N: V-UBE 43

 

Series no. (P/N): 861235-0000

 

PID: LZ729BQ

 

USB\VID ID: USB\VID_046D&PID_0992 ; Super Sulley 1.3, QuickCam Communicate Deluxe

 

Driver version: 12.10.1110.0 (OR LWS 1.1)

 

-------------

 

PC Info:

 

OS: Windows Vista SP2 32-bit

 

PC model: HP m9040n

 

CPU: Intel Core 2 Quad Q6600 - 4 cores @ 2.40Ghz

 

RAM: 3.00 GB DDR2

 

HDD: 640 GB, 7200 rpm

 

Graphics Card: nVidia GT 220

 

Graphics Driver Version: 280.56, certified (Aug. 9, 2011)

 

Full PC Specs available @ the following link: http://h10010.www1.hp.com/wwpc/ca/en/ho/WF06b/12132708-12133156-12133158-12133158-12133158-80631744-...

 

Skype Version: 5.5.0.117 - latest version

 

-------------------------------------------------------

 

BlueScreenView renders the BSOD error screen as follows:

 

A problem has been detected and Windows has been shut down to prevent damage to your computer.


The problem seems to be caused by the following file: lvrs.sys


SYSTEM_THREAD_EXCEPTION_NOT_HANDLED


If this is the first time you've seen this stop error screen, restart your computer. If this screen appears again, follow these steps:


Check to make sure any new hardware or software is properly installed. If this is a new installation, ask your hardware or software manufacturer for any Windows updates you might need.


If problems continue, disable or remove any newly installed hardware or software. Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable components, restart your computer, press F8 to select Advanced Startup Options, and then select Safe Mode.


Technical Information:


*** STOP: 0x1000007e (0xc0000005, 0x9c09a625, 0x8b92bc34, 0x8b92b930)
*** lvrs.sys - Address 0x9c09a625 base at 0x9c08f000 DateStamp 0x4acc5102

 

 

---------------------

 

Debugging info:

 

Dump File: Mini092411-01.dmp

Crash Time: 24/09/2011 4:33:37 PM

Bug Check String: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

Bug Check Code: 0x1000007e

Parameter 1: 0xc0000005

Parameter 2: 0x9c09a625

Parameter 3: 0x8b92bc34

Parameter 4: 0x8b92b930

Caused By Driver: lvrs.sys

Caused By Address: lvrs.sys+b625

File Description: Logitech Kernel Audio Improvement Filter Driver

Product Name: Logitech Webcam Software

Company: Logitech Inc.

File Version: 12.10.1110.0

Processor: 32-bit

Crash Address: lvrs.sys+b625

Stack Address 1: ntkrnlpa.exe+1d5fe2

Stack Address 2:

Stack Address 3:

Computer Name:

Full Path: C:\Windows\Minidump\Mini092411-01.dmp

Processors Count : 4

Major Version : 15

Minor Version: 6002

Dump File Size: 154,768

 

Download DMP file @ the following link: http://www.mediafire.com/?9lcfstjwv6geqnn

 

---------------------

 

Please help me resolve this issue. Hopefully Logitech can come up with some sort of fix; but at the very least, I would be grateful to have some input on what the best course of action is. Thanks.

Retired Logitech Employee / Moderator (Inactive)
j_briggs
Posts: 315
Registered: ‎02-07-2011
0

Re: Skype BSOD crash during video call, caused by webcam drivers; Vista SP2

[ Edited ]

Hi Ambient,

 

The issue you experienced would normally be alleviated by reinstalling the software or upgrading to a newer version. The camera you are using however cannot use any higher software than you currently are LWS 1.1 Am I correct in assuming that everything has worked fine since then? If this is the case it may have simply been an anomaly or small conflict that caused the problem.

 

Regards,

Knowledgebase | Downloads + Get Parts | Contact Support | Manuals | Warranty | Rebate
If a reply adequately addresses your technical issue, please click on the "Accept as Solution" and "Give Kudos" button so this information can benefit other users via search.