C
Chandra
We get the following error on a machine running Microsoft
Window 2000 Advanced Server 5.00.2195 Service Pack 4.
"STOP: 0x000000cb (0xbf138610b, 0xbf1447e8, 0x8888b2a8,
0x88c7aaf4)
DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
Probably caused by : afd.sys ( afd!
AfdAllocateMdlChain+d0 )"
I ran WinDbg on the memory dump and ran the command '!
analyze -v' which produced the following out given below.
Has any body seen this type of problem?
The server runs a Java baed network management
application being develioped my team.
Microsoft claims to have fixed a memory leak ( see
Knowledge base article 296265) but there seems to another
meomry leak in the networking stack.
Are there any known workarounds or guidelines for using
Winsock?
thanks,
Chandra.
WinDbg Output:
---------------------------------------------------------
DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (cb)
Caused by a driver not cleaning up completely after an
I/O.
When possible, the guilty driver's name (Unicode string)
is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: bf1386db, The calling address in the driver that
locked the pages or if the
IO manager locked the pages this points to the
dispatch routine of
the top driver on the stack to which the IRP was
sent.
Arg2: bf1447e8, The caller of the calling address in the
driver that locked the
pages. If the IO manager locked the pages this
points to the device
object of the top driver on the stack to which
the IRP was sent.
Arg3: 8888b2a8, A pointer to the MDL containing the
locked pages.
Arg4: 88c7aaf4, The number of locked pages.
Debugging Details:
------------------
FAULTING_IP:
afd!AfdAllocateMdlChain+d0
bf1386db 8937 mov [edi],esi
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xCB
LAST_CONTROL_TRANSFER: from 804e4b88 to 8043fe2c
STACK_TEXT:
be47bc50 804e4b88 804e4618 c000013a 800654f0 nt!
MmCleanProcessAddressSpace+0x438
be47bd00 804e4632 c000013a 87c5e488 8042fa04 nt!
PspExitThread+0x4d4
be47bd0c 8042fa04 87c5e488 be47bd48 be47bd3c nt!
PsExitSpecialApc+0x1a
be47bd4c 804663f4 00000001 00000000 be47bd64 nt!
KiDeliverApc+0x174
be47bd4c 77f94091 00000001 00000000 be47bd64 nt!
KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following
frames may be wrong.
0e22fc24 00000000 00000000 00000000 00000000 0x77f94091
FOLLOWUP_IP:
afd!AfdAllocateMdlChain+d0
bf1386db 8937 mov [edi],esi
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: afd!AfdAllocateMdlChain+d0
MODULE_NAME: afd
IMAGE_NAME: afd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 3eaf8d29
STACK_COMMAND: kb
BUCKET_ID: 0xCB_afd!AfdAllocateMdlChain+d0
Followup: MachineOwner
Window 2000 Advanced Server 5.00.2195 Service Pack 4.
"STOP: 0x000000cb (0xbf138610b, 0xbf1447e8, 0x8888b2a8,
0x88c7aaf4)
DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
Probably caused by : afd.sys ( afd!
AfdAllocateMdlChain+d0 )"
I ran WinDbg on the memory dump and ran the command '!
analyze -v' which produced the following out given below.
Has any body seen this type of problem?
The server runs a Java baed network management
application being develioped my team.
Microsoft claims to have fixed a memory leak ( see
Knowledge base article 296265) but there seems to another
meomry leak in the networking stack.
Are there any known workarounds or guidelines for using
Winsock?
thanks,
Chandra.
WinDbg Output:
---------------------------------------------------------
DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (cb)
Caused by a driver not cleaning up completely after an
I/O.
When possible, the guilty driver's name (Unicode string)
is printed on
the bugcheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: bf1386db, The calling address in the driver that
locked the pages or if the
IO manager locked the pages this points to the
dispatch routine of
the top driver on the stack to which the IRP was
sent.
Arg2: bf1447e8, The caller of the calling address in the
driver that locked the
pages. If the IO manager locked the pages this
points to the device
object of the top driver on the stack to which
the IRP was sent.
Arg3: 8888b2a8, A pointer to the MDL containing the
locked pages.
Arg4: 88c7aaf4, The number of locked pages.
Debugging Details:
------------------
FAULTING_IP:
afd!AfdAllocateMdlChain+d0
bf1386db 8937 mov [edi],esi
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xCB
LAST_CONTROL_TRANSFER: from 804e4b88 to 8043fe2c
STACK_TEXT:
be47bc50 804e4b88 804e4618 c000013a 800654f0 nt!
MmCleanProcessAddressSpace+0x438
be47bd00 804e4632 c000013a 87c5e488 8042fa04 nt!
PspExitThread+0x4d4
be47bd0c 8042fa04 87c5e488 be47bd48 be47bd3c nt!
PsExitSpecialApc+0x1a
be47bd4c 804663f4 00000001 00000000 be47bd64 nt!
KiDeliverApc+0x174
be47bd4c 77f94091 00000001 00000000 be47bd64 nt!
KiServiceExit+0x59
WARNING: Frame IP not in any known module. Following
frames may be wrong.
0e22fc24 00000000 00000000 00000000 00000000 0x77f94091
FOLLOWUP_IP:
afd!AfdAllocateMdlChain+d0
bf1386db 8937 mov [edi],esi
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: afd!AfdAllocateMdlChain+d0
MODULE_NAME: afd
IMAGE_NAME: afd.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 3eaf8d29
STACK_COMMAND: kb
BUCKET_ID: 0xCB_afd!AfdAllocateMdlChain+d0
Followup: MachineOwner