*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: 9798caee, The address that the exception occurred at
Arg3: ab6657e4, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
HTTP!UxTlDisconnectRequest+a
9798caee 8bb088000000 mov esi,dword ptr [eax+88h]
TRAP_FRAME: ab6657e4 -- (.trap 0xffffffffab6657e4)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=9798cae4 edx=00000004 esi=88093460 edi=855ca900
eip=9798caee esp=ab665858 ebp=ab665860 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
HTTP!UxTlDisconnectRequest+0xa:
9798caee 8bb088000000 mov esi,dword ptr [eax+88h] ds:0023:00000088=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: svchost.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 9798564a to 9798caee
STACK_TEXT:
ab665860 9798564a 00000000 00000001 00000000 HTTP!UxTlDisconnectRequest+0xa
ab66588c 979b9a8a 855fd648 00000001 00000000 HTTP!UlCloseConnection+0x71
ab665ae8 97977233 88093460 8809353c 87431f08 HTTP!UlSendHttpResponseIoctl+0x605
ab665afc 82e8b593 87431f08 88093460 88093460 HTTP!UlDeviceControl+0x39
ab665b14 8307e98f 87d265f0 88093460 8809353c nt!IofCallDriver+0x63
ab665b34 83081b61 87431f08 87d265f0 00000000 nt!IopSynchronousServiceTail+0x1f8
ab665bd0 830c83fc 87431f08 88093460 00000000 nt!IopXxxControlFile+0x6aa
ab665c04 82e921ea 00000370 0000049c 00000000 nt!NtDeviceIoControlFile+0x2a
ab665c04 770070b4 00000370 0000049c 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
00edf598 00000000 00000000 00000000 00000000 0x770070b4
STACK_COMMAND: kb
FOLLOWUP_IP:
HTTP!UxTlDisconnectRequest+a
9798caee 8bb088000000 mov esi,dword ptr [eax+88h]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: HTTP!UxTlDisconnectRequest+a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: HTTP
IMAGE_NAME: HTTP.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ce78971
FAILURE_BUCKET_ID: 0x8E_HTTP!UxTlDisconnectRequest+a
BUCKET_ID: 0x8E_HTTP!UxTlDisconnectRequest+a
Followup: MachineOwner
---------