Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Jonathan\Desktop\032810-28609-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 7600 UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16481.x86fre.win7_gdr.091207-1941
Machine Name:
Kernel base = 0x83448000 PsLoadedModuleList = 0x83587570
Debug session time: Sun Mar 28 05:34:18.250 2010 (GMT-4)
System Uptime: 0 days 0:31:03.346
Loading Kernel Symbols
...............................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {c0000005, 8927743f, 93de7a8c, 93de7670}
Unable to load image \SystemRoot\system32\drivers\mfewfpk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for mfewfpk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfewfpk.sys
Probably caused by : NETIO.SYS ( NETIO!ClassifyContextCleanupRoutine+4c )
Followup: MachineOwner
---------
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: c0000005, The exception code that was not handled
Arg2: 8927743f, The address that the exception occurred at
Arg3: 93de7a8c, Exception Record Address
Arg4: 93de7670, 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:
tcpip!InetResolveSockAddrToAf+9
8927743f 66837b0c17 cmp word ptr [ebx+0Ch],17h
EXCEPTION_RECORD: 93de7a8c -- (.exr 0xffffffff93de7a8c)
ExceptionAddress: 8927743f (tcpip!InetResolveSockAddrToAf+0x00000009)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 043a0014
Attempt to read from address 043a0014
CONTEXT: 93de7670 -- (.cxr 0xffffffff93de7670)
eax=93de7bbf ebx=043a0008 ecx=854f5020 edx=854f5084 esi=93de7be6 edi=93de7bdc
eip=8927743f esp=93de7b54 ebp=93de7b58 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
tcpip!InetResolveSockAddrToAf+0x9:
8927743f 66837b0c17 cmp word ptr [ebx+0Ch],17h ds:0023:043a0014=????
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: 00000000
EXCEPTION_PARAMETER2: 043a0014
READ_ADDRESS: GetPointerFromAddress: unable to read from 835a7700
Unable to read MiSystemVaType memory at 835870c0
043a0014
FOLLOWUP_IP:
NETIO!ClassifyContextCleanupRoutine+4c
88f96a1f 8b4508 mov eax,dword ptr [ebp+8]
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 892fcc2e to 8927743f
STACK_TEXT:
93de7b58 892fcc2e 893177c0 043a0008 86664008 tcpip!InetResolveSockAddrToAf+0x9
93de7b90 892ba332 893177c0 043a0008 86664008 tcpip!InetResolveSockAddrPairToPathAndAf+0x3d
93de7bfc 8926a4a1 856e3670 93de7c18 862e3430 tcpip!TcpResolveModifiedConnectRequestToPathAndAf+0x2f1
93de7c1c 892d6665 856e3670 00000000 00000001 tcpip!TcpCreateAndConnectTcbInspectConnectRequestComplete+0xe2
93de7c44 88f96a1f 869ba460 83579d7c 88f969d3 tcpip!AlepReleaseConnectRequestInspectContext+0x42
93de7c58 88f969a1 854f2008 93de7c74 88f96bef NETIO!ClassifyContextCleanupRoutine+0x4c
93de7c64 88f96bef 854f2008 854c3ed0 93de7c84 NETIO!WfpObjectDereference+0x1e
93de7c74 8936fa6e 0000018b 0000018b 93de7c94 NETIO!FeReleaseClassifyHandle+0x2c
93de7c84 8939ba36 0000018b 0000018b 93de7cb4 fwpkclnt!FwpsReleaseClassifyHandle0+0x18
WARNING: Stack unwind information not available. Following frames may be wrong.
93de7c94 893a2a83 0000018b 0000018b 854c3ed0 mfewfpk+0x1a36
93de7cb4 8939ff4d 854c3ed0 86385b30 00000000 mfewfpk+0x8a83
93de7cec 83634f34 86385b30 869bfab8 855f4020 mfewfpk+0x5f4d
93de7d00 834a3083 87851600 00000000 855f4020 nt!IopProcessWorkItem+0x23
93de7d50 8362fd16 80000001 8c80a04d 00000000 nt!ExpWorkerThread+0x10d
93de7d90 834d1159 834a2f76 80000001 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: NETIO!ClassifyContextCleanupRoutine+4c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETIO
IMAGE_NAME: NETIO.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bbf63
STACK_COMMAND: .cxr 0xffffffff93de7670 ; kb
FAILURE_BUCKET_ID: 0x7E_NETIO!ClassifyContextCleanupRoutine+4c
BUCKET_ID: 0x7E_NETIO!ClassifyContextCleanupRoutine+4c
Followup: MachineOwner
---------