Any Info on this INETINFO.exe Crash (Access Violation) wit..

We have had a few inetinfo crash [c0000005 (access violation)] recently on
two of our IIS5 server on Windows 2000 SP4 server.

DrWtsn32 generated a User.dmp file for the crash. With symbol path points
to the Microsoft Symbol server, windbg.exe reports the following stack trace
for the crashing thread.

ChildEBP RetAddr Args to Child
0246eb90 65f1dc7e 00000000 00000200 00000005
w3svc!FILTER_LIST::NotifyFilters+0x6d (FPO: [Non-Fpo])
0246ebb0 65f1c4fb 0246f3f4 65f05818 01dd2570
w3svc!HTTP_FILTER::NotifyLogFilters+0x30 (FPO: [Non-Fpo])
0246f480 65f060c1 65f05818 01dd2570 0246f4c4
w3svc!HTTP_REQ_BASE::WriteLogRecord+0x17f (FPO: [Non-Fpo])
0246f494 65f05b3b 00000000 00e49ff8 00000000
w3svc!WAM_REQUEST::~WAM_REQUEST+0x51 (FPO: [EBP 0x0246f4c4] [0,0,4])
0246f4a4 65f04cd2 01dd2570 00000000 00000000 w3svc!WAM_REQUEST::Release+0x99
(FPO: [1,0,3])
0246f4c4 65f03d71 02bd3558 02bd407c 02bd4010
w3svc!CWamInfo::ProcessWamRequest+0x18d (FPO: [Non-Fpo])
0246fcfc 65f03c49 00000000 02bd407c 02bd4010
w3svc!WAM_DICTATOR::ProcessWamRequest+0x1e5 (FPO: [Non-Fpo])
0246fd20 65f03aa2 02bd407c 02bd4010 0246feb0
w3svc!HTTP_REQUEST::DoWamRequest+0x75 (FPO: [Non-Fpo])
0246fd44 65f0249e 02bd4010 0246feb0 0246fedc
w3svc!HTTP_REQUEST::ProcessBGI+0x166 (FPO: [Non-Fpo])
0246fec4 65f01d97 0246fedc 0116ef80 0246ff20
w3svc!HTTP_REQUEST::DoWork+0x43f (FPO: [Non-Fpo])
0246fee4 65f06be5 00000000 00000000 00000000 w3svc!CLIENT_CONN::DoWork+0x1aa
(FPO: [Non-Fpo])
0246ff08 65f06b58 0246ff20 7c5737e2 0116ef80 w3svc!CreateClient+0x7b (FPO:
[Non-Fpo])
0246ff4c 6d701ad2 0116ef80 0000006f 01f51140 w3svc!W3OnConnectEx+0x118 (FPO:
[Non-Fpo])
0246ff80 6d7029a6 00000000 0000006f 0116ef84 ISATQ!AtqpProcessContext+0x23e
(FPO: [Non-Fpo])
0246ffb4 7c57438b 00000000 01eb3e13 01eb3e1d ISATQ!AtqPoolThread+0x1a8 (FPO:
[EBP 0x0246ffec] [1,4,4])
0246ffec 00000000 6d709470 00000000 00000000 KERNEL32!BaseThreadStart+0x52
(FPO: [Non-Fpo])


I would appreciate any information about this crash.

Since we just released a change to our own ISAPI filter, we want to know if
this crash is caused by our own ISAPI filter.

Thanks,
Wenbin Zhang

It is highly likely that this was caused by an ISAPI filter. The thread is
basically walking through the ISAPI filter list.

Pat

"Wenbin Zhang" <wzhang.RemoveThis@onesource.com> wrote in message
news:OmJoBs6rEHA.3428@TK2MSFTNGP11.phx.gbl...
 > We have had a few inetinfo crash [c0000005 (access violation)] recently on
 > two of our IIS5 server on Windows 2000 SP4 server.
 >
 > DrWtsn32 generated a User.dmp file for the crash. With symbol path points
 > to the Microsoft Symbol server, windbg.exe reports the following stack
 > trace
 > for the crashing thread.
 >
 > ChildEBP RetAddr Args to Child
 > 0246eb90 65f1dc7e 00000000 00000200 00000005
 > w3svc!FILTER_LIST::NotifyFilters+0x6d (FPO: [Non-Fpo])
 > 0246ebb0 65f1c4fb 0246f3f4 65f05818 01dd2570
 > w3svc!HTTP_FILTER::NotifyLogFilters+0x30 (FPO: [Non-Fpo])
 > 0246f480 65f060c1 65f05818 01dd2570 0246f4c4
 > w3svc!HTTP_REQ_BASE::WriteLogRecord+0x17f (FPO: [Non-Fpo])
 > 0246f494 65f05b3b 00000000 00e49ff8 00000000
 > w3svc!WAM_REQUEST::~WAM_REQUEST+0x51 (FPO: [EBP 0x0246f4c4] [0,0,4])
 > 0246f4a4 65f04cd2 01dd2570 00000000 00000000
 > w3svc!WAM_REQUEST::Release+0x99
 > (FPO: [1,0,3])
 > 0246f4c4 65f03d71 02bd3558 02bd407c 02bd4010
 > w3svc!CWamInfo::ProcessWamRequest+0x18d (FPO: [Non-Fpo])
 > 0246fcfc 65f03c49 00000000 02bd407c 02bd4010
 > w3svc!WAM_DICTATOR::ProcessWamRequest+0x1e5 (FPO: [Non-Fpo])
 > 0246fd20 65f03aa2 02bd407c 02bd4010 0246feb0
 > w3svc!HTTP_REQUEST::DoWamRequest+0x75 (FPO: [Non-Fpo])
 > 0246fd44 65f0249e 02bd4010 0246feb0 0246fedc
 > w3svc!HTTP_REQUEST::ProcessBGI+0x166 (FPO: [Non-Fpo])
 > 0246fec4 65f01d97 0246fedc 0116ef80 0246ff20
 > w3svc!HTTP_REQUEST::DoWork+0x43f (FPO: [Non-Fpo])
 > 0246fee4 65f06be5 00000000 00000000 00000000
 > w3svc!CLIENT_CONN::DoWork+0x1aa
 > (FPO: [Non-Fpo])
 > 0246ff08 65f06b58 0246ff20 7c5737e2 0116ef80 w3svc!CreateClient+0x7b (FPO:
 > [Non-Fpo])
 > 0246ff4c 6d701ad2 0116ef80 0000006f 01f51140 w3svc!W3OnConnectEx+0x118
 > (FPO:
 > [Non-Fpo])
 > 0246ff80 6d7029a6 00000000 0000006f 0116ef84
 > ISATQ!AtqpProcessContext+0x23e
 > (FPO: [Non-Fpo])
 > 0246ffb4 7c57438b 00000000 01eb3e13 01eb3e1d ISATQ!AtqPoolThread+0x1a8
 > (FPO:
 > [EBP 0x0246ffec] [1,4,4])
 > 0246ffec 00000000 6d709470 00000000 00000000 KERNEL32!BaseThreadStart+0x52
 > (FPO: [Non-Fpo])
 >
 >
 > I would appreciate any information about this crash.
 >
 > Since we just released a change to our own ISAPI filter, we want to know
 > if
 > this crash is caused by our own ISAPI filter.
 >
 > Thanks,
 > Wenbin Zhang
 >
 ><!-- ~MESSAGE_AFTER~ -->