error stop: 0x0000008E

Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP Volcado de mem completo]
Kernel Complete Dump File: Full address space is available

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Fri Jun 3 22:20:57.140 2005 (GMT-3)
System Uptime: 0 days 0:38:01.831
Loading Kernel Symbol
...
Loading unloaded module list
...
Loading User Symbol
..
*******************************************************************************
*
*
* Bugcheck Analysis
*
*

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {bfe05390, 0, bfe05390, 0}

*** WARNING: Unable to verify checksum for imon.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols for
imon.dll -
Probably caused by : hardware

Followup: MachineOwner

*** Possible invalid call from f2e06c6f (
afd!AfdFastConnectionReceive+0x364 )
*** Expected target f2e05390 ( afd!AfdReturnBuffer+0x0 )

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

*******************************************************************************

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: bfe05390, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bfe05390, If non-zero, the instruction address which referenced the
bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:



OVERLAPPED_MODULE: srv

READ_ADDRESS: bfe05390 Nonpaged pool

FAULTING_IP:
+ffffffffbfe05390
bfe05390 ?? ???

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from f2e06c74 to bfe05390

TRAP_FRAME: edaa5a30 -- (.trap ffffffffedaa5a30)
ErrCode = 00000000
eaxf6fd2c ebx=edaa5b1c ecxf6fd20 edx=fffff000 esid54a58 edi=edaa5c9c
eip=bfe05390 esp=edaa5aa4 ebp=edaa5b10 iopl=0 nv up ei pl zr na po nc
cs08 ss10 ds23 es23 fs30 gs00 efl010246
bfe05390 ?? ???
Resetting default scope

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
edaa5aa0 f2e06c74 81f6fd20 81da4af8 00000000 0xbfe05390
edaa5b1c f2dfd492 81da3b40 edaa5be0 000001fc
afd!AfdFastConnectionReceive+0x369
edaa5c5c 80587013 818aa038 00000001 0212fdf4 afd!AfdFastIoDeviceControl+0x713
edaa5d00 8058709e 00000544 0000096c 00000000 nt!IopXxxControlFile+0x255
edaa5d34 804dd99f 00000544 0000096c 00000000 nt!NtDeviceIoControlFile+0x2a
edaa5d34 7c91eb94 00000544 0000096c 00000000 nt!KiFastCallEntry+0xfc
0212fdb4 7c91d8ef 719d4413 00000544 0000096c ntdll!KiFastSystemCallRet
0212fdb8 719d4413 00000544 0000096c 00000000 ntdll!ZwDeviceIoControlFile+0xc
0212fe48 20b0d14e 00000544 0212febc 00000001 mswsock!WSPRecv+0x1a0
0212febc 01f334b0 00d5ad38 00000000 0212fef0 imon!NOD32Ioctl+0x8f6e
000001fc 00000000 00000000 00000000 00000000 0x1f334b0


FAILED_INSTRUCTION_ADDRESS:
+ffffffffbfe05390
bfe05390 ?? ???

POSSIBLE_INVALID_CONTROL_TRANSFER: from f2e06c6f to f2e05390

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .trap ffffffffedaa5a30 ; kb

BUCKET_ID: CPU_CALL_ERROR

Followup: MachineOwner

*** Possible invalid call from f2e06c6f (
afd!AfdFastConnectionReceive+0x364 )
*** Expected target f2e05390 ( afd!AfdReturnBuffer+0x0 )

Tambien puede ser que el zocalo de la memoria este mal. No la memoria en si,
sino el zocalo (o sea, canvio de placa madre al tanto)
"Ivan" escribió en el mensaje
news:

Vuelvo con el tema,
Para solucionar el tema me compre 2 mem DDR de 512Mb 400mhz(nuevas), las
probe(de a una) 3 pasadas(loop) con el testeador y las 3 FAILED(da error
siempre el MATS+...FAIL), pero apreto ESc para pararlo y luego F5 para
reiniciar (lo dejo 2 pasadas) y sale todo bien, q puede ser?
Despues si las pongo a las 2 mem juntas la maquina aparentemente no inicia
el monitor no tiene señal, la apago le saco una mem y me inicia y el bios
pone la alerta de cuanto hay algun problema(F3 - load default seting or F2
Run setup) miro el bios todo en default y e inicia normalmente. Tenes idea
q
pasa?
Y bueno y luego usando windowsXP todo normal aunque algunas veces se me
reinicio la maquina sin dar mensaje de error de pantalla azul ni nada, y
se
me reinicia siempre q carga y estoy comenzando a jugar al Rise Of Nation
T&P,
Bueno espero tus respuestas para ver si podemos solucionar este problema q
ya me costo 2 mem nuevas, Saludos.

Asus p4S800D
Intel P4 3.0ghz 800mhz 1mb socket478
Hds 160gb SATA y 120gb IDE
XFX Geforce 6200 256Mb agp
Sound Blaster Live
Winfast tvr 2000
Lectoras y grabadora
Fuente de 520w

"JM Tella Llop [MVP Windows]" escribió:

Lo importante es que las memorias sean compatibles con tu placa madre.
Eso
es lo que puede causar el problema actual.
(lo de menos, en la actualidad, es la marca de memoria ya que es
dificil
que las den dañadas)

Jose Manuel Tella Llop
MVP - Windows
(quitar XXX)
http://www.multingles.net/jmt.htm

Este mensaje se proporciona "como está" sin garantías de ninguna clase,
y no otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use.



"Ivan" wrote in message
news:
> Entiendo q me tengo q compprar memorias nuevas no?,
> ahora me pudes decir por q razones se pueden dañar las mem te digo pq
> yo
> no
> he hecho ningun overcolc ni nada de ese:
> Te digo pq si me compro nuevas mem como creo q recomendaras vos, para
> saber
> q cosas las dañan y asi cuidarlas mejor.
> Saludos.
>
> "JM Tella Llop [MVP Windows]" escribió:
>
>> FAILED:21.
>>
>> Pues la memoria para tirarlo. FAILED debería ser cero. Cianquier cosa
>> distinta de cero indica memoria dañada o no compatible con tu placa
>> madre.
>>
>> Jose Manuel Tella Llop
>> MVP - Windows
>> (quitar XXX)
>> http://www.multingles.net/jmt.htm
>>
>> Este mensaje se proporciona "como está" sin garantías de ninguna
>> clase,
>> y no otorga ningún derecho.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> You assume all risk for your use.
>>
>>
>>
>> "Ivan" wrote in message
>> news:
>> > Hola denuevo,
>> > Pase el testeador por 10:20hs y bueno, en ese listado de la parte
>> > inferior
>> > izquierda todo figuraba como PASS y en la parte inf. der. en el
>> > cuadrito
>> > Test
>> > counter decia PASSED:0 FAILED:21.
>> > Vos me diras q es esto.
>> > Saludos.
>> >
>> > "JM Tella Llop [MVP Windows]" escribió:
>> >
>> >> Ejecuta el testeador de DocMemory...
>> >>
>> >> Si te sca un error... uno solo... ya puedes parar: memoria dañada.
>> >> Si
>> >> no
>> >> saca errores, para ser fiable debe estar 4 horas.
>> >>
>> >> Jose Manuel Tella Llop
>> >> MVP - Windows
>> >> (quitar XXX)
>> >> http://www.multingles.net/jmt.htm
>> >>
>> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> clase,
>> >> y no otorga ningún derecho.
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >> You assume all risk for your use.
>> >>
>> >>
>> >>
>> >> "Ivan" wrote in message
>> >> news:
>> >> > Es igual si uso el testeador de mem de microsot? 4hs tiene q ser?
>> >> >
>> >> > Ahora volvi a conectar todo, y tengo un error stop: D1
>> >> > y aveces aparece arriba DRIVER_IRQL_NOT_LESS_OR_EQUAL
>> >> > saludos.
>> >> >
>> >> >
>> >> > "JM Tella Llop [MVP Windows]" wrote:
>> >> >
>> >> >> Pasa el DocMemory de www.simmtester.com para revisar la memoria.
>> >> >> Al
>> >> >> ejecutarlo te generará un disquete de arranque, arrancas con el
>> >> >> y
>> >> >> lo
>> >> >> mantienes en ejhecucion 4 horas. No debe enviarte ningun mensaje
>> >> >> de
>> >> >> error
>> >> >> en
>> >> >> ese tiempo.
>> >> >>
>> >> >> Si no hay problemas de memoria, comentame y analizamos el
>> >> >> ficheros
>> >> >> de
>> >> >> dump a
>> >> >> ver quien es el causante.
>> >> >>
>> >> >> Jose Manuel Tella Llop
>> >> >> MVP - Windows
>> >> >> (quitar XXX)
>> >> >> http://www.multingles.net/jmt.htm
>> >> >>
>> >> >> Este mensaje se proporciona "como está" sin garantías de ninguna
>> >> >> clase,
>> >> >> y no otorga ningún derecho.
>> >> >>
>> >> >> This posting is provided "AS IS" with no warranties, and confers
>> >> >> no
>> >> >> rights.
>> >> >> You assume all risk for your use.
>> >> >>
>> >> >>
>> >> >>
>> >> >> "Ivan" wrote in message
>> >> >> news:
>> >> >> > Hola gente estoy recibiendo este mensaje de error:
>> >> >> >
>> >> >> > stop: 0x0000008E (0xc0000005, este numero varia, este numero
>> >> >> > varia,
>> >> >> > 0x0)
>> >> >> >
>> >> >> > Saque placas y mi hd slave y el error sigue apareciendo, no
>> >> >> > hace
>> >> >> > referencia
>> >> >> > a ningun archivo(ni .sys ni nada) solo aparece la pantazalla
>> >> >> > azul
>> >> >> > y
>> >> >> > abajo
>> >> >> > este stop.
>> >> >> > Saludos espero su respuesta.
>> >> >> >
>> >> >> > WinXP Pro Sp2
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

¿el unico simbolo que no te encuentra es este: imon.dll?

¿a quien pertenece esa dll?

Por si acaso... ¿todos los dump son iguales?.¿pasaste un test de
memoria?

Jose Manuel Tella Llop
MVP - Windows
(quitar XXX)
http://www.multingles.net/jmt.htm

Este mensaje se proporciona "como está" sin garantías de ninguna clase,
y no otorga ningún derecho.

This posting is provided "AS IS" with no warranties, and confers no
rights.
You assume all risk for your use.



"Ivan" wrote in message
news:

Microsoft (R) Windows Debugger Version 6.4.0007.2
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\MEMORY.DMP Volcado de mem completo]
Kernel Complete Dump File: Full address space is available

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86
compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp2_gdr.050301-1519
Kernel base = 0x804d7000 PsLoadedModuleList = 0x805624a0
Debug session time: Fri Jun 3 22:20:57.140 2005 (GMT-3)
System Uptime: 0 days 0:38:01.831
Loading Kernel Symbols
...
Loading unloaded module list
...
Loading User Symbols
...
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {bfe05390, 0, bfe05390, 0}

*** WARNING: Unable to verify checksum for imon.dll
*** ERROR: Symbol file could not be found. Defaulted to export symbols
for
imon.dll -
Probably caused by : hardware

Followup: MachineOwner

*** Possible invalid call from f2e06c6f (
afd!AfdFastConnectionReceive+0x364 )
*** Expected target f2e05390 ( afd!AfdReturnBuffer+0x0 )

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

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: bfe05390, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: bfe05390, If non-zero, the instruction address which referenced the
bad memory
address.
Arg4: 00000000, (reserved)

Debugging Details:



OVERLAPPED_MODULE: srv

READ_ADDRESS: bfe05390 Nonpaged pool

FAULTING_IP:
+ffffffffbfe05390
bfe05390 ?? ???

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

LAST_CONTROL_TRANSFER: from f2e06c74 to bfe05390

TRAP_FRAME: edaa5a30 -- (.trap ffffffffedaa5a30)
ErrCode = 00000000
eaxf6fd2c ebx=edaa5b1c ecxf6fd20 edx=fffff000 esid54a58
edi=edaa5c9c
eip=bfe05390 esp=edaa5aa4 ebp=edaa5b10 iopl=0 nv up ei pl zr na po
nc
cs08 ss10 ds23 es23 fs30 gs00
efl010246
bfe05390 ?? ???
Resetting default scope

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
edaa5aa0 f2e06c74 81f6fd20 81da4af8 00000000 0xbfe05390
edaa5b1c f2dfd492 81da3b40 edaa5be0 000001fc
afd!AfdFastConnectionReceive+0x369
edaa5c5c 80587013 818aa038 00000001 0212fdf4
afd!AfdFastIoDeviceControl+0x713
edaa5d00 8058709e 00000544 0000096c 00000000 nt!IopXxxControlFile+0x255
edaa5d34 804dd99f 00000544 0000096c 00000000 nt!NtDeviceIoControlFile+0x2a
edaa5d34 7c91eb94 00000544 0000096c 00000000 nt!KiFastCallEntry+0xfc
0212fdb4 7c91d8ef 719d4413 00000544 0000096c ntdll!KiFastSystemCallRet
0212fdb8 719d4413 00000544 0000096c 00000000
ntdll!ZwDeviceIoControlFile+0xc
0212fe48 20b0d14e 00000544 0212febc 00000001 mswsock!WSPRecv+0x1a0
0212febc 01f334b0 00d5ad38 00000000 0212fef0 imon!NOD32Ioctl+0x8f6e
000001fc 00000000 00000000 00000000 00000000 0x1f334b0


FAILED_INSTRUCTION_ADDRESS:
+ffffffffbfe05390
bfe05390 ?? ???

POSSIBLE_INVALID_CONTROL_TRANSFER: from f2e06c6f to f2e05390

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: .trap ffffffffedaa5a30 ; kb

BUCKET_ID: CPU_CALL_ERROR

Followup: MachineOwner

*** Possible invalid call from f2e06c6f (
afd!AfdFastConnectionReceive+0x364 )
*** Expected target f2e05390 ( afd!AfdReturnBuffer+0x0 )