KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
- From: Devang <devang.it@xxxxxxxxx>
- Date: Thu, 18 Dec 2008 06:50:06 -0800 (PST)
Hi
WinDbg gives following information regarding my driver crash.
I am able to track the line of code which causes that exception.
But I am not able to find any fault in code.
It works fine for about half and hour and after that is crashes.
kd> !analyze -v
ERROR: FindPlugIns 8007007b
*******************************************************************************
*
*
* 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: fb523f26, The address that the exception occurred at
Arg3: f919d738, 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:
Plg1!CList::list_add+a [c:\vmfw\packetengine\plugins\idsfw\clist.cpp @
38]
fb523f26 894204 mov dword ptr [edx+4],eax
TRAP_FRAME: f919d738 -- (.trap 0xfffffffff919d738)
ErrCode = 00000002
eax=ffba0598 ebx=ffba0598 ecx=ffa5e218 edx=00000000 esi=ffb9144a
edi=f919d7e8
eip=fb523f26 esp=f919d7ac ebp=f919d810 iopl=0 nv up ei pl zr
na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00010246
Plg1!CList::list_add+0xa:
fb523f26 894204 mov dword ptr [edx+4],eax ds:
0023:00000004=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 3
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: inetinfo.exe
LAST_CONTROL_TRANSFER: from fb52449d to fb523f26
STACK_TEXT:
f919d7a8 fb52449d ffba0598 ffa5e218 fb52552e Plg1!CList::list_add+0xa
[c:\vmfw\packetengine\plugins\idsfw\clist.cpp @ 38]
f919d7b4 fb52552e ffba0598 000000ff 000000b6 Plg1!
TCPHashTable::tch_set_relatedq+0x13 [c:\vmfw\packetengine\plugins\idsfw
\tcphashtable.cpp @ 511]
f919d810 fb526061 ffb91436 c0a80438 0000c9d1 Plg1!
TCPSessionHandler::tcm_handle_packet+0x390 [c:\vmfw\packetengine
\plugins\idsfw\tcpsessionhandler.cpp @ 631]
f919d864 fb526611 ffb91436 00000000 81203620 Plg1!
CPacketDecoder::tcp_decode+0x521 [c:\vmfw\packetengine\plugins\idsfw
\packetdecoder.cpp @ 766]
f919d89c fb526a76 ffb91428 00000000 81203620 Plg1!
CPacketDecoder::ip_decode+0x1ef [c:\vmfw\packetengine\plugins\idsfw
\packetdecoder.cpp @ 133]
f919d8b4 fb5d435e ffb92428 ffbdcc20 81203620 Plg1!
PacketHandler::IDSFWSendHandler+0x3e [c:\vmfw\packetengine\plugins
\idsfw\packethandler.cpp @ 284]
f919d8f4 f96b6d40 ffb92428 ffbdcc20 ffb92640 Nx!
PNDISXtender::NewSendHandler+0xee [c:\vmfw\packetengine\ndisext
\pndisxtender.cpp @ 954]
f919d91c f96b6916 ffb92640 ffbdcc20 81230348 tcpip!ARPSendData+0x198
f919d948 f96b665a ffb92640 f919d900 00000001 tcpip!ARPTransmit+0x193
f919d978 f96b679f ffb90d50 3804a8c0 ffbdcc20 tcpip!SendIPPacket+0x193
f919dac4 f96bf934 f96f4b98 00000000 ff98b2e0 tcpip!IPTransmit+0x289e
f919db18 f96bf500 ff2805b4 00000000 ffb290c8 tcpip!SendSYN+0x28d
f919db5c f96bf6ce 0819db80 00000001 00000000 tcpip!TdiConnect+0x3ab
f919db98 f96b97a0 ff025d10 ff025dc8 ff025d10 tcpip!TCPConnect+0xa8
f919dbb4 804e37f7 8113a728 ff025d10 ff023a3c tcpip!
TCPDispatchInternalDeviceControl+0x13f
f919dbc4 f966cec4 00012007 f966cc55 ff025d10 nt!IopfCallDriver+0x31
f919dc24 f96742d7 ff43a838 ffbc78e8 f919dc58 afd!AfdConnect+0x3a8
f919dc34 804e37f7 ffbc77d0 ff025d10 806f02d0 afd!
AfdDispatchDeviceControl+0x53
f919dc44 80567f81 ff025dec ff43a838 ff025d10 nt!IopfCallDriver+0x31
f919dc58 8057aa9f ffbc77d0 ff025d10 ff43a838 nt!
IopSynchronousServiceTail+0x70
f919dd00 8058efe3 00000890 0000019c 00000000 nt!IopXxxControlFile
+0x611
f919dd34 804de7ec 00000890 0000019c 00000000 nt!NtDeviceIoControlFile
+0x2a
f919dd34 7c90e4f4 00000890 0000019c 00000000 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be
wrong.
00d6f9f4 00000000 00000000 00000000 00000000 0x7c90e4f4
STACK_COMMAND: kb
FOLLOWUP_IP:
Plg1!CList::list_add+a [c:\vmfw\packetengine\plugins\idsfw\clist.cpp @
38]
fb523f26 894204 mov dword ptr [edx+4],eax
FAULTING_SOURCE_CODE:
34: * This is good for implementing stacks.
35: */
36: void CList::list_add(CList *New, CList *head)
37: {
38: __list_add(New, head, head->next);39: }
40:
41: /**
42: * list_add_tail - add a New entry
43: * @New: New entry to be added
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: Plg1!CList::list_add+a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Plg1
IMAGE_NAME: Plg1.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 494a5097
FAILURE_BUCKET_ID: 0x8E_Plg1!CList::list_add+a
BUCKET_ID: 0x8E_Plg1!CList::list_add+a
Followup: MachineOwner
---------
Thanks
Regards,
Devang
.
- Follow-Ups:
- Re: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
- From: Günter Prossliner
- Re: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
- From: daniel
- Re: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
- Prev by Date: Re: Calling inf file or installing .sys file from DriverEntry func
- Next by Date: Re: Preventing Multiple Outstanding Transactions on PCIe
- Previous by thread: How to access return codes from Directx 10 DDI functions ?
- Next by thread: Re: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
- Index(es):
Relevant Pages
|
