Arno Garrels wrote:

> Arrgh, after uploading 40.000 files w/o any problem ( all uploads
> used the same listening passive port ) the server rebooted and I now
> need to debug the Minidump it created. Will have a look at that
> file tomorrow :-((

I suspect either the patched tcpip.sys (patch from http://www.xp-AntiSpy.org)
or ProcessExplorer (running at that time). Has anybody seen similiar crashes?

--
Arno Garrels [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
   

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 100000D1, {c, 2, 0, aabf9c02}

Probably caused by : tcpip.sys ( tcpip!ReadNextTCB+d2 )

Followup: MachineOwner
---------

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 0000000c, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: aabf9c02, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS:  0000000c 

CURRENT_IRQL:  2

FAULTING_IP: 
tcpip!ReadNextTCB+d2
aabf9c02 8b400c           mov     eax,[eax+0xc]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0xD1

LAST_CONTROL_TRANSFER:  from aabea6c5 to aabf9c02

STACK_TEXT:  
a9db38f0 aabea6c5 025ac460 a9db3a90 859a5880 tcpip!ReadNextTCB+0xd2
806e5830 05c7fffe fffe0080 00000041 0f04eac1 tcpip!TdiQueryInformationEx+0x7e5
WARNING: Frame IP not in any known module. Following frames may be wrong.
a9db3bec aabc703c 859a5880 859a58f0 859a58f0 0x5c7fffe
a9db3c08 aabc6ff4 859a5880 859a58f0 85c88230 
tcpip!TCPDispatchDeviceControl+0x129
a9db3c40 804ef095 861feb98 859a5880 806e5410 tcpip!TCPDispatch+0x127
a9db3c50 8057e70a 859a58f0 85bb5ef8 859a5880 nt!IopfCallDriver+0x31
a9db3c64 8057f56d 861feb98 859a5880 85bb5ef8 nt!IopSynchronousServiceTail+0x60
a9db3d00 805780c2 00000038 000001d8 00000000 nt!IopXxxControlFile+0x5c5
a9db3d34 8054086c 00000038 000001d8 00000000 nt!NtDeviceIoControlFile+0x2a
a9db3d34 7c91eb94 00000038 000001d8 00000000 nt!KiFastCallEntry+0xfc
00aafe20 00000000 00000000 00000000 00000000 0x7c91eb94


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
tcpip!ReadNextTCB+d2
aabf9c02 8b400c           mov     eax,[eax+0xc]

FAULTING_SOURCE_CODE:  


SYMBOL_STACK_INDEX:  0

FOLLOWUP_NAME:  MachineOwner

SYMBOL_NAME:  tcpip!ReadNextTCB+d2

MODULE_NAME:  tcpip

IMAGE_NAME:  tcpip.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  444775d3

FAILURE_BUCKET_ID:  0xD1_tcpip!ReadNextTCB+d2

BUCKET_ID:  0xD1_tcpip!ReadNextTCB+d2

Followup: MachineOwner
---------
-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

Reply via email to