Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`01c56000 PsLoadedModuleList = 0xfffff800`01e93e50
Debug session time: Thu Oct 21 10:01:01.337 2010 (GMT-4)
System Uptime: 0 days 3:44:41.430
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
...............
Unable to load image \SystemRoot\System32\Drivers\L6UX264.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for L6UX264.sys
*** ERROR: Module load completed but symbols could not be loaded for L6UX264.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff88004a9bba1, fffff880047b39d8, fffff880047b3240}
Probably caused by : L6UX264.sys ( L6UX264+19ba1 )
Followup: MachineOwner
---------
0: 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: fffff88004a9bba1, The address that the exception occurred at
Arg3: fffff880047b39d8, Exception Record Address
Arg4: fffff880047b3240, 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:
L6UX264+19ba1
fffff880`04a9bba1 66814b0a0020 or word ptr [rbx+0Ah],2000h
EXCEPTION_RECORD: fffff880047b39d8 -- (.exr 0xfffff880047b39d8)
ExceptionAddress: fffff88004a9bba1 (L6UX264+0x0000000000019ba1)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000001
Parameter[1]: 000000000000000a
Attempt to write to address 000000000000000a
CONTEXT: fffff880047b3240 -- (.cxr 0xfffff880047b3240)
rax=fffffa800422a3b0 rbx=0000000000000000 rcx=fffffa800727d3a8
rdx=0000000000000000 rsi=fffffa800422a3b0 rdi=fffffa800727d0b8
rip=fffff88004a9bba1 rsp=fffff880047b3c10 rbp=fffff88009ae3750
r8=fffffa800407e100 r9=0000000000000000 r10=0000000000000000
r11=0000000000000000 r12=fffffa8007f17790 r13=0000000000000000
r14=0000000000000000 r15=fffff88001cd0f40
iopl=0 nv up ei ng nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00210282
L6UX264+0x19ba1:
fffff880`04a9bba1 66814b0a0020 or word ptr [rbx+0Ah],2000h ds:002b:00000000`0000000a=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
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: 000000000000000a
WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff80001efe0e0
000000000000000a
FOLLOWUP_IP:
L6UX264+19ba1
fffff880`04a9bba1 66814b0a0020 or word ptr [rbx+0Ah],2000h
BUGCHECK_STR: 0x7E
DEFAULT_BUCKET_ID: NULL_CLASS_PTR_DEREFERENCE
LAST_CONTROL_TRANSFER: from fffffa8008abc490 to fffff88004a9bba1
STACK_TEXT:
fffff880`047b3c10 fffffa80`08abc490 : fffff880`09ae3750 fffffa80`03f455a0 fffffa80`0727d0b8 fffff880`047b3c40 : L6UX264+0x19ba1
fffff880`047b3c18 fffff880`09ae3750 : fffffa80`03f455a0 fffffa80`0727d0b8 fffff880`047b3c40 fffffa80`07f03680 : 0xfffffa80`08abc490
fffff880`047b3c20 fffffa80`03f455a0 : fffffa80`0727d0b8 fffff880`047b3c40 fffffa80`07f03680 fffffa80`000001b9 : 0xfffff880`09ae3750
fffff880`047b3c28 fffffa80`0727d0b8 : fffff880`047b3c40 fffffa80`07f03680 fffffa80`000001b9 00000000`00000000 : 0xfffffa80`03f455a0
fffff880`047b3c30 fffff880`047b3c40 : fffffa80`07f03680 fffffa80`000001b9 00000000`00000000 00000000`00000000 : 0xfffffa80`0727d0b8
fffff880`047b3c38 fffffa80`07f03680 : fffffa80`000001b9 00000000`00000000 00000000`00000000 fffff800`01ccfcff : 0xfffff880`047b3c40
fffff880`047b3c40 fffffa80`000001b9 : 00000000`00000000 00000000`00000000 fffff800`01ccfcff fffff880`01cd0f40 : 0xfffffa80`07f03680
fffff880`047b3c48 00000000`00000000 : 00000000`00000000 fffff800`01ccfcff fffff880`01cd0f40 00000000`00000000 : 0xfffffa80`000001b9
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: L6UX264+19ba1
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: L6UX264
IMAGE_NAME: L6UX264.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4963e541
STACK_COMMAND: .cxr 0xfffff880047b3240 ; kb
FAILURE_BUCKET_ID: X64_0x7E_L6UX264+19ba1
BUCKET_ID: X64_0x7E_L6UX264+19ba1
Followup: MachineOwner
---------