Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (3 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0324b000 PsLoadedModuleList = 0xfffff800`03490670
Debug session time: Sat Nov  5 00:58:49.024 2011 (UTC - 5:00)
System Uptime: 0 days 0:15:56.210
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols

Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7E, {ffffffffc0000005, fffff88007e20435, fffff8800278e9d8, fffff8800278e230}

*** ERROR: Module load completed but symbols could not be loaded for lvrs64.sys
Probably caused by : lvrs64.sys ( lvrs64+10435 )

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

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

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88007e20435, The address that the exception occurred at
Arg3: fffff8800278e9d8, Exception Record Address
Arg4: fffff8800278e230, 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+10435
fffff880`07e20435 894620          mov     dword ptr [rsi+20h],eax

EXCEPTION_RECORD:  fffff8800278e9d8 -- (.exr 0xfffff8800278e9d8)
ExceptionAddress: fffff88007e20435 (lvrs64+0x0000000000010435)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000001
   Parameter[1]: 00000000025f1ec0
Attempt to write to address 00000000025f1ec0

CONTEXT:  fffff8800278e230 -- (.cxr 0xfffff8800278e230)
rax=00000000000003c0 rbx=fffffa80068df010 rcx=fffffa80062666b0
rdx=0000000000000001 rsi=00000000025f1ea0 rdi=fffffa8003d28550
rip=fffff88007e20435 rsp=fffff8800278ec10 rbp=fffffa8006266650
 r8=0000000000000001  r9=0000000000000000 r10=0000000000000000
r11=fffff8000343de80 r12=0000000000000002 r13=0000000000000000
r14=0000000000000001 r15=fffff88007e5a870
iopl=0         nv up ei pl nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010206
lvrs64+0x10435:
fffff880`07e20435 894620          mov     dword ptr [rsi+20h],eax ds:002b:00000000`025f1ec0=????????
Resetting default scope

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:  0000000000000001

EXCEPTION_PARAMETER2:  00000000025f1ec0

WRITE_ADDRESS:  00000000025f1ec0 

FOLLOWUP_IP: 
lvrs64+10435
fffff880`07e20435 894620          mov     dword ptr [rsi+20h],eax

BUGCHECK_STR:  0x7E

LAST_CONTROL_TRANSFER:  from fffff80003562fee to fffff88007e20435

STACK_TEXT:  
fffff880`0278ec10 fffff800`03562fee : fffffa80`06001040 fffffa80`00000001 fffffa80`00000002 fffffa80`06740cf0 : lvrs64+0x10435
fffff880`0278ed40 fffff800`032b95e6 : fffff880`009e8180 fffffa80`06001040 fffff880`009f2f80 fffff880`0122bcb0 : nt!PspSystemThreadStartup+0x5a
fffff880`0278ed80 00000000`00000000 : fffff880`0278f000 fffff880`02789000 fffff880`0278e740 00000000`00000000 : nt!KxStartSystemThread+0x16


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  lvrs64+10435

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: lvrs64

IMAGE_NAME:  lvrs64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d955c33

STACK_COMMAND:  .cxr 0xfffff8800278e230 ; kb

FAILURE_BUCKET_ID:  X64_0x7E_lvrs64+10435

BUCKET_ID:  X64_0x7E_lvrs64+10435

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