[FONT="Lucida Console"]
Microsoft (R) Windows Debugger Version 6.2.9200.20512 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\USER\Downloads\Compressed\debug-YASMIN-VAIO-01_11_2014_194015,91\110114-151632-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 Personal
Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
Machine Name:
Kernel base = 0xfffff800`0364c000 PsLoadedModuleList = 0xfffff800`0388f890
Debug session time: Sun Nov 2 03:00:41.700 2014 (UTC + 6:00)
System Uptime: 0 days 9:44:54.580
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, fffff8800d05cfc6, fffff8800db8c898, fffff8800db8c0f0}
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: fffff8800d05cfc6, The address that the exception occurred at
Arg3: fffff8800db8c898, Exception Record Address
Arg4: fffff8800db8c0f0, 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`0d05cfc6 45396924 cmp dword ptr [r9+24h],r13d
EXCEPTION_RECORD: fffff8800db8c898 -- (.exr 0xfffff8800db8c898)
ExceptionAddress: fffff8800d05cfc6 (lvrs64+0x0000000000002fc6)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 000000000291b3f4
Attempt to read from address 000000000291b3f4
CONTEXT: fffff8800db8c0f0 -- (.cxr 0xfffff8800db8c0f0)
rax=0000000000000000 rbx=fffffa80079a58f0 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800d05cfc6 rsp=fffff8800db8cad0 rbp=000000000291b3d0
r8=0000000000000000 r9=000000000291b3d0 r10=0000000000000002
r11=000000000291b3d0 r12=fffffa8006ced050 r13=0000000000000000
r14=000000000291b3d0 r15=000000000291b3d0
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`0d05cfc6 45396924 cmp dword ptr [r9+24h],r13d ds:002b:00000000`0291b3f4=????????
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: 000000000291b3f4
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff800038f9100
GetUlongFromAddress: unable to read from fffff800038f91c0
000000000291b3f4 Nonpaged pool
FOLLOWUP_IP:
lvrs64+2fc6
fffff880`0d05cfc6 45396924 cmp dword ptr [r9+24h],r13d
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 0000000000000001 to fffff8800d05cfc6
STACK_TEXT:
fffff880`0db8cad0 00000000`00000001 : fffffa80`00000000 00000000`00000000 00000000`00000000 fffffa80`04634210 : lvrs64+0x2fc6
fffff880`0db8cad8 fffffa80`00000000 : 00000000`00000000 00000000`00000000 fffffa80`04634210 00000000`00000000 : 0x1
fffff880`0db8cae0 00000000`00000000 : 00000000`00000000 fffffa80`04634210 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 0xfffff8800db8c0f0 ; 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`0d05a000 fffff880`0d0ae000 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[/FONT]
