BSOD during Skype call

Welcome to the forum.

BSOD was caused by Logitech Camera driver. Please update it to the latest version available and see if that solves the problem.

Driver Reference Table - lvrs64.sys

Perform a clean install of a driver following: How to Clean Left Over Driver Files with Driver Sweeper

Code:

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


Loading Dump File [C:\Users\Usra\Downloads\LadyRaine\SF_24-01-2014\012414-35521-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18247.amd64fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0xfffff800`02e1b000 PsLoadedModuleList = 0xfffff800`0305e6d0
Debug session time: Sat Jan 25 09:58:01.340 2014 (UTC + 6:00)
System Uptime: 8 days 19:39:22.573
Loading Kernel Symbols
...............................................................
................................................................
...................................
Loading User Symbols
Loading unloaded module list
...........................................
*** WARNING: Unable to verify timestamp for lvrs64.sys
*** ERROR: Module load completed but symbols could not be loaded for lvrs64.sys
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff88005a02fc6, fffff88005154758, fffff88005153fb0}

Probably caused by : lvrs64.sys ( lvrs64+2fc6 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88005a02fc6, The address that the exception occurred at
Arg3: fffff88005154758, Exception Record Address
Arg4: fffff88005153fb0, Context Record Address

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
lvrs64+2fc6
fffff880`05a02fc6 45396924        cmp     dword ptr [r9+24h],r13d

EXCEPTION_RECORD:  fffff88005154758 -- (.exr 0xfffff88005154758)
ExceptionAddress: fffff88005a02fc6 (lvrs64+0x0000000000002fc6)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000002893b54
Attempt to read from address 0000000002893b54

CONTEXT:  fffff88005153fb0 -- (.cxr 0xfffff88005153fb0)
rax=0000000000000000 rbx=fffffa800b36a2d0 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88005a02fc6 rsp=fffff88005154990 rbp=0000000002893b30
 r8=0000000000000000  r9=0000000002893b30 r10=0000000000000002
r11=0000000002893b30 r12=fffffa800b005df0 r13=0000000000000000
r14=0000000002893b30 r15=0000000002893b30
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
lvrs64+0x2fc6:
fffff880`05a02fc6 45396924        cmp     dword ptr [r9+24h],r13d ds:002b:00000000`02893b54=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  0

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000002893b54

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800030c8100
GetUlongFromAddress: unable to read from fffff800030c81c0
 0000000002893b54 Nonpaged pool

FOLLOWUP_IP: 
lvrs64+2fc6
fffff880`05a02fc6 45396924        cmp     dword ptr [r9+24h],r13d

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000000000001 to fffff88005a02fc6

STACK_TEXT:  
fffff880`05154990 00000000`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`0df01220 : lvrs64+0x2fc6
fffff880`05154998 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0df01220 00000000`00000000 : 0x1
fffff880`051549a0 00000000`00000000 : 00000000`00000000 fffffa80`0df01220 00000000`00000000 00000000`00000000 : 0xfffffa80`00000000


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  lvrs64+2fc6

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: lvrs64

IMAGE_NAME:  lvrs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  505cb9b9

STACK_COMMAND:  .cxr 0xfffff88005153fb0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+2fc6

BUCKET_ID:  X64_0x7E_lvrs64+2fc6

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

1: kd> lmvm lvrs64
start             end                 module name
fffff880`05a00000 fffff880`05a54000   lvrs64   T (no symbols)           
    Loaded symbol image file: lvrs64.sys
    Image path: \SystemRoot\system32\DRIVERS\lvrs64.sys
    Image name: lvrs64.sys
    Timestamp:        Sat Sep 22 01:02:17 2012 (505CB9B9)
    CheckSum:         000612AC
    ImageSize:        00054000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Reduce items at start-up: Startup Programs - Change

Perform a clean boot: Troubleshoot Application Conflicts by Performing a Clean Startup

Run a System file check (SFC): SFC /SCANNOW Command - System File Checker

Run Disk Check on your Hard Drive(s): Disk Check

Scan with Kaspersky TDSSKiller:Anti-rootkit utility TDSSKiller

ESET online scanner: Free Online Virus Scanner | ESET