Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\033011-18064-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a1a000 PsLoadedModuleList = 0xfffff800`02c57e50
Debug session time: Wed Mar 30 19:54:56.227 2011 (UTC - 4:00)
System Uptime: 0 days 4:42:25.991
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002a9795f, fffff880031cba78, fffff880031cb2e0}
Probably caused by : ntkrnlmp.exe ( nt!KxStartSystemThread+16 )
Followup: MachineOwner
---------
2: 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: fffff80002a9795f, The address that the exception occurred at
Arg3: fffff880031cba78, Exception Record Address
Arg4: fffff880031cb2e0, 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:
nt!ExpWorkerThread+10f
fffff800`02a9795f ffd3 call rbx
EXCEPTION_RECORD: fffff880031cba78 -- (.exr 0xfffff880031cba78)
ExceptionAddress: fffff80002a9795f (nt!ExpWorkerThread+0x000000000000010f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880031cb2e0 -- (.cxr 0xfffff880031cb2e0)
rax=0000000000000001 rbx=b2e0fffff880014d rcx=1b5cfffffa8006a8
rdx=00002b0c00000000 rsi=fffffa8005218040 rdi=1b5cfffffa8006a8
rip=fffff80002a9795f rsp=fffff880031cbcb0 rbp=fffff80002c2f5f8
r8=000000007f215548 r9=0000000000da7a64 r10=00000000000b1aa1
r11=fffffa8006a8b2e0 r12=fffffa8006a8b2e0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!ExpWorkerThread+0x10f:
fffff800`02a9795f ffd3 call rbx {b2e0ffff`f880014d}
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: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc20e0
ffffffffffffffff
FOLLOWUP_IP:
nt!KxStartSystemThread+16
fffff800`02a68c26 48c7c10e000000 mov rcx,0Eh
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002d2d7c6 to fffff80002a9795f
STACK_TEXT:
fffff880`031cbcb0 fffff800`02d2d7c6 : 0000056e`00000000 fffffa80`05218040 00000000`00000080 fffffa80`0518f9e0 : nt!ExpWorkerThread+0x10f
fffff880`031cbd40 fffff800`02a68c26 : fffff880`02f64180 fffffa80`05218040 fffff880`02f6efc0 0000056e`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031cbd80 00000000`00000000 : fffff880`031cc000 fffff880`031c6000 fffff880`031cb9f0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KxStartSystemThread+16
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
STACK_COMMAND: .cxr 0xfffff880031cb2e0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!KxStartSystemThread+16
BUCKET_ID: X64_0x7E_nt!KxStartSystemThread+16
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\DMP\033011-20170-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16695.amd64fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0xfffff800`02a54000 PsLoadedModuleList = 0xfffff800`02c91e50
Debug session time: Wed Mar 30 15:11:32.444 2011 (UTC - 4:00)
System Uptime: 1 days 23:39:07.834
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002ad195f, fffff880031b6a78, fffff880031b62e0}
Probably caused by : ntkrnlmp.exe ( nt!KxStartSystemThread+16 )
Followup: MachineOwner
---------
2: 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: fffff80002ad195f, The address that the exception occurred at
Arg3: fffff880031b6a78, Exception Record Address
Arg4: fffff880031b62e0, 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:
nt!ExpWorkerThread+10f
fffff800`02ad195f ffd3 call rbx
EXCEPTION_RECORD: fffff880031b6a78 -- (.exr 0xfffff880031b6a78)
ExceptionAddress: fffff80002ad195f (nt!ExpWorkerThread+0x000000000000010f)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff880031b62e0 -- (.cxr 0xfffff880031b62e0)
rax=0000000000000001 rbx=d2e0fffff8800148 rcx=9c34fffffa8006a6
rdx=0001b3c600000000 rsi=fffffa8005201040 rdi=9c34fffffa8006a6
rip=fffff80002ad195f rsp=fffff880031b6cb0 rbp=fffff80002c695f8
r8=00000000e63c4e20 r9=0000000000da7a64 r10=000000000004ced3
r11=fffffa8006a6d2e0 r12=fffffa8006a6d2e0 r13=0000000000000001
r14=0000000000000000 r15=0000000000000001
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0000 ds=002b es=002b fs=0053 gs=002b efl=00010202
nt!ExpWorkerThread+0x10f:
fffff800`02ad195f ffd3 call rbx {d2e0ffff`f8800148}
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: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfc0e0
ffffffffffffffff
FOLLOWUP_IP:
nt!KxStartSystemThread+16
fffff800`02aa2c26 48c7c10e000000 mov rcx,0Eh
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff80002d677c6 to fffff80002ad195f
STACK_TEXT:
fffff880`031b6cb0 fffff800`02d677c6 : 00000000`00000000 fffffa80`05201040 00000000`00000080 fffffa80`0518f9e0 : nt!ExpWorkerThread+0x10f
fffff880`031b6d40 fffff800`02aa2c26 : fffff880`02f63180 fffffa80`05201040 fffff880`02f6dfc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`031b6d80 00000000`00000000 : fffff880`031b7000 fffff880`031b1000 fffff880`031b69f0 00000000`00000000 : nt!KxStartSystemThread+0x16
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KxStartSystemThread+16
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4cc791bd
STACK_COMMAND: .cxr 0xfffff880031b62e0 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nt!KxStartSystemThread+16
BUCKET_ID: X64_0x7E_nt!KxStartSystemThread+16
Followup: MachineOwner
---------