BSOD Randomly happening all of a sudden, no exact reason.

Withing the last 2 days my PC has blue screened 2 times, no big deal I have come to live with errors with PCs as is, but my problem now is I can't figure out why it's doing this, I pasted my error code into google and it all leads back to video card, surprise surprise! So I am 6 versions late on my Nvidia driver, don't blame me I have been busy, I just updated them but I would like a further view of my minidumps, thanks.

Specs:

CPU: AMD Athlon II X4 635 - 4th core unlocked - Not overclocked
Ram: 4gb DDR3 Corsair.
PSU: 600W
Video Card: Nvidia Geforce 9600GSO - I know it's bad my new one is on RMA it's a Nvidia Zotac 560 Ti
OS: Windows 7 64 Bit, Ultimate.

Minidumps here.

Maguscreed said:

What I'm seeing is blaming the crashes on a logitech camera driver in use.

Quickest fix is to update the driver from logitech if possible. Remove it if not.
Crash report follows.

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000007E, {ffffffffc0000005, fffff8800938ef8a, fffff880069c8898, fffff880069c80f0}

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

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: fffff8800938ef8a, The address that the exception occurred at
Arg3: fffff880069c8898, Exception Record Address
Arg4: fffff880069c80f0, 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+2f8a
fffff880`0938ef8a 45396924        cmp     dword ptr [r9+24h],r13d

EXCEPTION_RECORD:  fffff880069c8898 -- (.exr 0xfffff880069c8898)
ExceptionAddress: fffff8800938ef8a (lvrs64+0x0000000000002f8a)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 00000000005db1e4
Attempt to read from address 00000000005db1e4

CONTEXT:  fffff880069c80f0 -- (.cxr 0xfffff880069c80f0)
rax=0000000000000000 rbx=fffffa80059ab5b0 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800938ef8a rsp=fffff880069c8ad0 rbp=00000000005db1c0
 r8=0000000000000000  r9=00000000005db1c0 r10=0000000000000002
r11=00000000005db1c0 r12=fffffa80059a8770 r13=0000000000000000
r14=00000000005db1c0 r15=00000000005db1c0
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+0x2f8a:
fffff880`0938ef8a 45396924        cmp     dword ptr [r9+24h],r13d ds:002b:00000000`005db1e4=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_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:  00000000005db1e4

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002d0f100
 00000000005db1e4 

FOLLOWUP_IP: 
lvrs64+2f8a
fffff880`0938ef8a 45396924        cmp     dword ptr [r9+24h],r13d

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff8800938ef8a

STACK_TEXT:  
fffff880`069c8ad0 00000000`00000000 : fffffa80`05091088 00000000`00000000 00000000`00000000 fffffa80`050910d0 : lvrs64+0x2f8a


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  lvrs64+2f8a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: lvrs64

IMAGE_NAME:  lvrs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4f166964

STACK_COMMAND:  .cxr 0xfffff880069c80f0 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+2f8a

BUCKET_ID:  X64_0x7E_lvrs64+2f8a

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

Thank you, I got that webcam for Christmas and just installed the software, I am going to look for an update and if there is none, I may have to find a 3rd party software to use it, I can keep screening, thank!