Windows 7 Ultimate x68 BSOD during Skype (v 4.2.0.169) video call with Logitec Orbit/Sphere AF
I have gotten two BSODs within a week when using Skype. I ran as much analysis as I could on the memory dump and the results follow. What would you suggest I do? Log this error with Skype? Follow up with Logitech? I do remember getting a driver update from Logitec sometime Here is the driver information that I found for the camera: Driver Name: Logitech USB Camera (Orbit/Sphere AF) Driver Provider: Logitech Driver Date: 5/14/2010 Driver Version: 13.0.1783.0 Driver Signer: Microsoft Windows Hardware Compatibility Publisher The USB driver file is: usbccgp.sys, provider is Microsoft and the file version is 6.1.7600.16385 (win7_rtm.090713-1255) The imaging device info is: === Start of device information ======================= Device name: QuickCam Orbit/Sphere AF USB Vendor ID (VID): 0x046D USB Product ID (PID): 0x0994 USB Revision (BCD): 0x0006 Firmware Version: 2.90.9018 Firmware CRC: 0x7615 EEPROM Version: 2.110 Sensor Type: 2.6 Driver Version: 13.0.1783.0 === End of device information ========================= When I search for an updated driver, Windows tells me that it already has the latest update. Here is the memory dump analysis info: 1: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* UNEXPECTED_KERNEL_MODE_TRAP (7f) This means a trap occurred in kernel mode, and it's a trap of a kind that the kernel isn't allowed to have/catch (bound trap) or that is always instant death (double fault). The first number in the bugcheck params is the number of the trap (8 = double fault, etc) Consult an Intel x86 family manual to learn more about what these traps are. Here is a *portion* of those codes: If kv shows a taskGate use .tss on the part before the colon, then kv. Else if kv shows a trapframe use .trap on that value Else .trap on the appropriate frame will show where the trap was taken (on x86, this will be the ebp that goes with the procedure KiTrap) Endif kb will then show the corrected stack. Arguments: Arg1: 0000000000000008, EXCEPTION_DOUBLE_FAULT Arg2: 0000000080050033 Arg3: 00000000000006f8 Arg4: fffff80002d973e8 Debugging Details: ------------------ BUGCHECK_STR: 0x7f_8 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT PROCESS_NAME: Skype.exe CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from fffff80002ab9b69 to fffff80002aba600 STACK_TEXT: fffff880`009f9c68 fffff800`02ab9b69 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx fffff880`009f9c70 fffff800`02ab8032 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`009f9db0 fffff800`02d973e8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 fffff880`076effc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpKcbCacheLookup+0x58 STACK_COMMAND: kb FOLLOWUP_IP: nt!KiDoubleFaultAbort+b2 fffff800`02ab8032 90 nop SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: nt!KiDoubleFaultAbort+b2 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe DEBUG_FLR_IMAGE_TIMESTAMP: 4b88cfeb FAILURE_BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 BUCKET_ID: X64_0x7f_8_nt!KiDoubleFaultAbort+b2 Followup: MachineOwner --------- 1: kd> !thread GetPointerFromAddress: unable to read from fffff80002cf2000 THREAD fffffa800c4b8b60 Cid 10e8.0908 Teb: 000000007ef89000 Win32Thread: fffff900c08f4c30 RUNNING on processor 1 IRP List: Unable to read nt!_IRP @ fffffa800b192010 Not impersonating GetUlongFromAddress: unable to read from fffff80002c30b74 Owning Process fffffa800c428a30 Image: Skype.exe Attached Process N/A Image: N/A fffff78000000000: Unable to get shared data Wait Start TickCount 11340238 Context Switch Count 320377 LargeStack ReadMemory error: Cannot get nt!KeMaximumIncrement value. UserTime 00:00:00.000 KernelTime 00:00:00.000 Win32 Start Address 0x0000000000867940 Stack Init fffff880076f8db0 Current fffff880076f09e0 Base fffff880076f9000 Limit fffff880076f0000 Call 0 Priority 8 BasePriority 6 UnusualBoost 0 ForegroundBoost 2 IoPriority 1 PagePriority 3 Child-SP RetAddr : Args to Child : Call Site fffff880`009f9c68 fffff800`02ab9b69 : 00000000`0000007f 00000000`00000008 00000000`80050033 00000000`000006f8 : nt!KeBugCheckEx fffff880`009f9c70 fffff800`02ab8032 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69 fffff880`009f9db0 fffff800`02d973e8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDoubleFaultAbort+0xb2 (TrapFrame @ fffff880`009f9db0) fffff880`076effc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpKcbCacheLookup+0x58 1: kd> !prc No export prc found 1: kd> !pcr Cannot get PRCB address 1: kd> !cpuinfo CP F/M/S Manufacturer MHz PRCB Signature MSR 8B Signature Features 1 6,15,6 GenuineIntel 1864 000000c600000000 211b3ffe Cached Update Signature 000000cb00000000 Initial Update Signature 000000c600000000 1: kd> !pcitree *** ERROR: Module load completed but symbols could not be loaded for pci.sys Error retrieving address of PciFdoExtensionListHead
July 7th, 2010 5:15am

Download the latest driver from the logitec werbsite.
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2010 9:22am

Thanks but I already had the latest driver installed when the BSODs happened. Actually, they both happened after I install latest driver (it came through the automatic windows update). The driver was released on 6/10/2010, the two crashes happened on 6/29 and 7/6 respectively. I just downloaded and reinstalled the driver from Logitech and there is no change to the file or driver versions, confirming that I already had the latest one available. Here are the memory dumps: http://cid-bbe542103b2fe396.office.live.com/browse.aspx/Memory%20Dumps Thanks
July 7th, 2010 4:36pm

I found the following information in Microsoft's KB: http://support.microsoft.com/kb/842465/en-us Plus these forum postings there: http://social.answers.microsoft.com/Forums/en-US/w7repair/thread/e94de527-183f-4227-9749-072ba0e7769... They recommend switching the AV (I am using Avast) or disabling NetBIOS. In my case though the dump analysis shows the error being produced within Skype during video calls and being caused by a driver, hence trying to get help here .
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2010 4:38pm

On the logitec driver, did it actually install or did windows refuse it not being the latest if so roll back the one you currently have and install the one from Logitec.
July 8th, 2010 12:02am

Update your NIC drivers and test the issue. Uninstall the Juniper VPN software and test the issue. Uninstall LogMeIn and test the issue. Update the Intel Matrix Storage Manager software and test the issue.
Free Windows Admin Tool Kit Click here and download it now
July 8th, 2010 4:54pm

Should be the webcam. How does it work if you remove the webcam?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
July 9th, 2010 11:25am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics