Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\060711-12698-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;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16792.amd64fre.win7_gdr.110408-1633
Machine Name:
Kernel base = 0xfffff800`02e02000 PsLoadedModuleList = 0xfffff800`0303fe50
Debug session time: Wed Jun 8 00:46:47.880 2011 (GMT-4)
System Uptime: 0 days 0:41:48.285
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
................
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, fffff80002e75905, fffff88004163628, fffff88004162e90}
Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : aswSP.SYS ( aswSP+102c4 )
Followup: MachineOwner
---------
5: 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: fffff80002e75905, The address that the exception occurred at
Arg3: fffff88004163628, Exception Record Address
Arg4: fffff88004162e90, 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!ExpInterlockedPopEntrySListFault16+0
fffff800`02e75905 498b08 mov rcx,qword ptr [r8]
EXCEPTION_RECORD: fffff88004163628 -- (.exr 0xfffff88004163628)
ExceptionAddress: fffff80002e75905 (nt!ExpInterlockedPopEntrySListFault16)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff88004162e90 -- (.cxr 0xfffff88004162e90)
rax=0000000968460003 rbx=0000000000000001 rcx=fffffa8006a358a0
rdx=e16d655302080001 rsi=fffff880030a4180 rdi=fffffa8006a358a0
rip=fffff80002e75905 rsp=fffff88004163860 rbp=fffff88004163ca8
r8=e16d655302080000 r9=0000000000000000 r10=fffffa8006a358a0
r11=fffff88004163a48 r12=0000000000000000 r13=fffffa8006a239f0
r14=0000000000000000 r15=fffff88004163970
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
nt!ExpInterlockedPopEntrySListFault16:
fffff800`02e75905 498b08 mov rcx,qword ptr [r8] ds:002b:e16d6553`02080000=????????????????
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 fffff800030aa0e0
ffffffffffffffff
FOLLOWUP_IP:
aswSP+102c4
fffff880`03dbc2c4 ?? ???
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from fffff8000316f900 to fffff80002e75905
STACK_TEXT:
fffff880`04163860 fffff800`0316f900 : fffffa80`00000000 fffffa80`07252c20 00000000`00000000 fffff880`01084600 : nt!ExpInterlockedPopEntrySListFault16
fffff880`04163870 fffff800`03176527 : 00000000`000007ff 00000000`00000001 fffffa80`09669900 fffff880`04163938 : nt!ObOpenObjectByName+0x70
fffff880`04163920 fffff800`0318f378 : fffff880`04163c90 fffff8a0`00100080 fffff8a0`092940e0 fffff880`04163c98 : nt!IopCreateFile+0x2b7
fffff880`041639c0 fffff800`02e71953 : fffffa80`06a12040 00000000`00000000 fffffa80`07528040 fffff800`03187164 : nt!NtOpenFile+0x58
fffff880`04163a50 fffff800`02e6def0 : fffff880`03dbc2c4 fffff880`02f68fc0 00000000`00000000 fffff880`00000000 : nt!KiSystemServiceCopyEnd+0x13
fffff880`04163c58 fffff880`03dbc2c4 : fffff880`02f68fc0 00000000`00000000 fffff880`00000000 00000000`00000000 : nt!KiServiceLinkage
fffff880`04163c60 fffff880`02f68fc0 : 00000000`00000000 fffff880`00000000 00000000`00000000 fffff880`00000001 : aswSP+0x102c4
fffff880`04163c68 00000000`00000000 : fffff880`00000000 00000000`00000000 fffff880`00000001 fffff800`00000060 : 0xfffff880`02f68fc0
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: aswSP+102c4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswSP
IMAGE_NAME: aswSP.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4dc929b6
STACK_COMMAND: .cxr 0xfffff88004162e90 ; kb
FAILURE_BUCKET_ID: X64_0x7E_aswSP+102c4
BUCKET_ID: X64_0x7E_aswSP+102c4
Followup: MachineOwner
---------
