Code:
......
*** 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, fffff8800933cf8a, fffff880033a2758, fffff880033a1fb0}
Probably caused by : lvrs64.sys ( lvrs64+2f8a )
Followup: MachineOwner
---------
3: 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: fffff8800933cf8a, The address that the exception occurred at
Arg3: fffff880033a2758, Exception Record Address
Arg4: fffff880033a1fb0, 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`0933cf8a 45396924 cmp dword ptr [r9+24h],r13d
EXCEPTION_RECORD: fffff880033a2758 -- (.exr 0xfffff880033a2758)
ExceptionAddress: fffff8800933cf8a (lvrs64+0x0000000000002f8a)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000044e144
Attempt to read from address 000000000044e144
CONTEXT: fffff880033a1fb0 -- (.cxr 0xfffff880033a1fb0)
rax=0000000000000000 rbx=fffffa80085ea920 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800933cf8a rsp=fffff880033a2990 rbp=000000000044e120
r8=0000000000000000 r9=000000000044e120 r10=0000000000000002
r11=000000000044e120 r12=fffffa8009dc9d10 r13=0000000000000000
r14=000000000044e120 r15=000000000044e120
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`0933cf8a 45396924 cmp dword ptr [r9+24h],r13d ds:002b:00000000`0044e144=????????
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: 000000000044e144
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff8000f0fe100
GetUlongFromAddress: unable to read from fffff8000f0fe1c0
000000000044e144 Nonpaged pool
FOLLOWUP_IP:
lvrs64+2f8a
fffff880`0933cf8a 45396924 cmp dword ptr [r9+24h],r13d
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff8800933cf8a
STACK_TEXT:
fffff880`033a2990 00000000`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`0c6830d0 : lvrs64+0x2f8a
fffff880`033a2998 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`0c6830d0 00000000`00000000 : 0x1
fffff880`033a29a0 00000000`00000000 : 00000000`00000000 fffffa80`0c6830d0 00000000`00000000 00000000`00000000 : 0xfffffa80`00000000
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 0xfffff880033a1fb0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_lvrs64+2f8a
BUCKET_ID: X64_0x7E_lvrs64+2f8a
Followup: MachineOwner
---------
3: kd> lmvm lvrs64
start end module name
fffff880`0933a000 fffff880`0938da80 lvrs64 T (no symbols)
Loaded symbol image file: lvrs64.sys
Image path: \SystemRoot\system32\DRIVERS\lvrs64.sys
Image name: lvrs64.sys
Timestamp: Wed Jan 18 12:10:36 2012 (4F166964)
CheckSum: 00061E9E
ImageSize: 00053A80
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Your logitech camera drivers seem to be causing BSOD-s for you. You might want to check for an update on its driver from
here and see how it goes. If not, you can unplug it from the computer and see if it still blue screens.