como checo la memoria de referencia?

03/07/2005 - 01:48 por joy | Informe spam
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or
it
is pointing at freed memory.
Arguments:
Arg1: fa66a01c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: f5733465, If non-zero, the instruction address which referenced the
bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:



READ_ADDRESS: fa66a01c Nonpaged pool expansion

FAULTING_IP:
vsdatant+2a465
f5733465 66837f1c00 cmp word ptr [edi+0x1c],0x0

MM_INTERNAL_CODE: 0

IMAGE_NAME: vsdatant.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 404f7fe5

MODULE_NAME: vsdatant

FAULTING_MODULE: f5709000 vsdatant

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from f57165d5 to f5733465

TRAP_FRAME: f5324b44 -- (.trap fffffffff5324b44)
ErrCode = 00000000
eax000102 ebx=fa67c540 ecx000000 edx€010031 esi800000 edi=fa66a000
eip=f5733465 esp=f5324bb8 ebp=f5324c08 iopl=0 nv up ei ng nz ac pe nc
cs08 ss10 ds23 es23 fs30 gs00 efl010292
vsdatant+0x2a465:
f5733465 66837f1c00 cmp word ptr [edi+0x1c],0x0 ds:0023:fa66a01c=????
Resetting default scope

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
f5324c08 f57165d5 fa66a000 f5324c34 00010042 vsdatant+0x2a465
f5324d64 7c91eb93 badb0d00 0012f208 f4e4bd98 vsdatant+0xd5d5
0012f328 77e7dafb 0014add8 00000000 00000001 ntdll!KiFastSystemCallRet+0x4
0012f368 77e7da7c 0014add8 00000000 00000001
RPCRT4!LRPC_CASSOCIATION::ActuallyDoBinding+0x55
0012f3e0 77e5be9e 0014add8 0012f468 0012f4cc
RPCRT4!LRPC_CASSOCIATION::AllocateCCall+0x18c
0012f448 77e5bdb0 0012f468 76ee2dc8 0012f4cc
RPCRT4!LRPC_BINDING_HANDLE::AllocateCCall+0x202
0012f474 77e58dc9 0012f4cc 0012f4f8 00000001
RPCRT4!LRPC_BINDING_HANDLE::NegotiateTransferSyntax+0xd3
0012f48c 77e58e00 0012f4cc 00000000 0012f4ac
RPCRT4!I_RpcGetBufferWithObject+0x5b
0012f49c 77e5942d 0012f4cc 0012f8a8 0012f88c RPCRT4!I_RpcGetBuffer+0xf
0012f4ac 77ed360b 0012f4f8 00000020 0014add8 RPCRT4!NdrGetBuffer+0x28
0012f88c 76ee802c 76ee2d78 76ee2c30 0012f8a8 RPCRT4!NdrClientCall2+0x195
0012f8a0 76ee7fed 00000000 0012f8d8 00000000
DNSAPI!R_ResolverGetLocalAddrInfoArray+0x1b
0012f8f4 76ee7f67 00149710 00000000 001422d4
DNSAPI!GetLocalAddrArrayFromResolver+0x48
0012f904 76ee7f53 00000004 00000000 0012f954 DNSAPI!LocalIp_GetIp4Array+0xa
0012f914 719da118 00010004 00000000 00000000 DNSAPI!DnsQueryConfigAllocEx+0x7c
0012f954 719dc88e 00000000 001422c8 7c80ac78 mswsock!myhostent_W+0x2b
0012f970 719dc9cc 001487dc 001422d4 0012fbcc mswsock!RNRPROV_NSPStartup+0x5a
0012f980 71a34b53 001487dc 001422d4 00000000 mswsock!NSPStartup+0x60
0012fbcc 71a34a7b 001487ec 001487dc 0012fc74
WS2_32!NSPROVIDER::Initialize+0xc7
0012fbec 71a34a16 001487b8 00148758 00148a80
WS2_32!NSCATALOG::LoadProvider+0x4a
0012fc2c 71a32ba9 0012fc74 001487b8 00148a00
WS2_32!LookupBeginEnumerationProc+0x61
0012fc48 71a33455 71a3355b 0012fc74 00148a00
WS2_32!NSCATALOG::EnumerateCatalogItems+0x25
0012fca0 71a3338b 00148a00 00000000 00000210
WS2_32!NSQUERY::LookupServiceBegin+0xce
0012fccc 71a35319 00148f98 00000210 0012fd14
WS2_32!WSALookupServiceBeginW+0x92
0012fcf0 71a35255 00000064 00000210 0012fd14
WS2_32!WSALookupServiceBeginA+0x72
0012fd18 71a35066 0012fd48 0000013c 00438f7c WS2_32!getxyDataEnt+0x5b
0012ff54 00408347 00438f7c 0040888a 0041302c WS2_32!gethostbyname+0xb4
0012ff88 0041162e 00400000 00000000 00142374 esclavo!_GetExceptDLLinfo+0x72d3
0012ffb8 00000000 0041302c 7c816d4f 7c925db4
esclavo!__unlockDebuggerData$qv+0x63b6


FOLLOWUP_IP:
vsdatant+2a465
f5733465 66837f1c00 cmp word ptr [edi+0x1c],0x0

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: vsdatant+2a465

STACK_COMMAND: .trap fffffffff5324b44 ; kb

FAILURE_BUCKET_ID: 0x50_vsdatant+2a465

BUCKET_ID: 0x50_vsdatant+2a465

Followup: MachineOwner

llegue hasta aqui gracias al articulo de José Manuel Tella Llop
MS MVP - DTS

ya no supe como checar la memoria de referencia fa66a01c, para poder ir màs
a fondo en el error, ¿existe alguna pagina donde podamos encontrar como
ejecutar los diferentes error?

ejemplo de Jose Manuel Tella

0: kd> !IRP 87e5a490

con ello se profundiza y se va a obtener donde esta el error, eso quiero
encontrar yo

gracias..
 

Leer las respuestas

#1 Ramón Sola [MVP Windows - Shell/User]
03/07/2005 - 06:32 | Informe spam
Hash: SHA1

Ahí te dice que el fallo se ha producido en Vsdatant.sys. Ese controlador
probablemente pertenece a Zone Alarm.

Ramón Sola / / MVP Windows - Shell/User
Para obtener la dirección correcta no hacen falta los sellos.
Por favor, usar el correo sólo para cuestiones ajenas a los
grupos de noticias, gracias.

Cuentan que "joy" escribió en el mensaje
news: lo siguiente:
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by
try-except, it must be protected by a Probe. Typically the address is
just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fa66a01c, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: f5733465, If non-zero, the instruction address which referenced the
bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:



READ_ADDRESS: fa66a01c Nonpaged pool expansion

FAULTING_IP:
vsdatant+2a465
f5733465 66837f1c00 cmp word ptr [edi+0x1c],0x0

MM_INTERNAL_CODE: 0

IMAGE_NAME: vsdatant.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 404f7fe5

MODULE_NAME: vsdatant

FAULTING_MODULE: f5709000 vsdatant

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from f57165d5 to f5733465

TRAP_FRAME: f5324b44 -- (.trap fffffffff5324b44)
ErrCode = 00000000
eax000102 ebx=fa67c540 ecx000000 edx€010031 esi800000
edi=fa66a000 eipõ733465 espõ324bb8 ebpõ324c08 iopl=0 nv up
ei ng nz ac pe nc cs08 ss10 ds23 es23 fs30 gs00
efl010292 vsdatant+0x2a465:
f5733465 66837f1c00 cmp word ptr [edi+0x1c],0x0
ds:0023:fa66a01c=???? Resetting default scope

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be
wrong.
f5324c08 f57165d5 fa66a000 f5324c34 00010042 vsdatant+0x2a465
f5324d64 7c91eb93 badb0d00 0012f208 f4e4bd98 vsdatant+0xd5d5
0012f328 77e7dafb 0014add8 00000000 00000001
ntdll!KiFastSystemCallRet+0x4 0012f368 77e7da7c 0014add8 00000000
00000001 RPCRT4!LRPC_CASSOCIATION::ActuallyDoBinding+0x55


[...]

Preguntas similares