error stop: 0x0000008E

Debes arrancar el Windwbg y abrir el memory.dmp con la opcion del menur
File: "Open Crash Dump".
Dejame aquí la salida

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:

BUeno, configure el volcado de mem en intermedio, no reiniciar,
ya me a dado el error de PAGE_FAULT_IN_NONPAGED_AREA STOP:0X50(), se
me
creo un archivo c:\windows\memory.dmp (57Megas), descarge WinDbg lo abri
hice
lo de los simbolos se me creo una carpeta de 3 megas y algo en el c: abri
el
archivo y no se q ver u hacer aparecen muchas letras y simbolos y
demasiados
palitos(verticales).
Saludos.




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

Mirate esto, y configura para obtener un DUMP válido (de Kernel a ser
posible), con ese dump y las herramientas estas, se puede proceder a
analizarlo en detalle. Hazlo y cuandi hayas pasado el !analize -v dejame
aquí la salida.

http://www.multingles.net/docs/jmt/bsod.htm

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:
> Bueno windows sigue dando errores igual,
> KERNEL_DATA_INPAGE_ERROR
> y otros.
>
>
>
>
> "JM Tella Llop [MVP Windows]" escribió:
>
>> Quizá estuviesen antel mal pinchadas o con suciedad. Si ahora no te da
>> fallos el test de memoria, tampoco te los debe dar windows. Si windows
>> te
>> diese de nuevo, inmediatamente vuelve a pasarle un test de memoria
>> para
>> descartar o no el problema hardware.
>>
>> 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 otra vez,
>> > mira volvi a poner mis antiguas 256Mb 400mhz en dual channel y pase
>> > el
>> > testeador de la manera q te dije y da todo bien ni un failed en 4h
>> > 10min,
>> > vos
>> > me diras. Saludos.
>> >
>> > "JM Tella Llop [MVP Windows]" escribió:
>> >
>> >> Si te el testaedor de memoria da UN solo error de memoria en 4
>> >> horas
>> >> esas memorias no sirvern.
>> >> Revisa en la web del fabricante el tipo de memoria (y las marcas)
>> >> que
>> >> son
>> >> compatibles con la 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:
>> >> > 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
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

Te referis a esto?:


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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel 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: Sat Jun 4 00:58:48.859 2005 (GMT-3)
System Uptime: 0 days 2:34:47.548
Loading Kernel Symbols
.
Loading unloaded module list
...
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {f2f1d390, 0, f2f1d390, 0}

Probably caused by : hardware

Followup: MachineOwner

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




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

Debes arrancar el Windwbg y abrir el memory.dmp con la opcion del menur
File: "Open Crash Dump".
Dejame aquí la salida

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:
> BUeno, configure el volcado de mem en intermedio, no reiniciar,
> ya me a dado el error de PAGE_FAULT_IN_NONPAGED_AREA STOP:0X50(), se
> me
> creo un archivo c:\windows\memory.dmp (57Megas), descarge WinDbg lo abri
> hice
> lo de los simbolos se me creo una carpeta de 3 megas y algo en el c: abri
> el
> archivo y no se q ver u hacer aparecen muchas letras y simbolos y
> demasiados
> palitos(verticales).
> Saludos.
>
>
>
>
> "JM Tella Llop [MVP Windows]" escribió:
>
>> Mirate esto, y configura para obtener un DUMP válido (de Kernel a ser
>> posible), con ese dump y las herramientas estas, se puede proceder a
>> analizarlo en detalle. Hazlo y cuandi hayas pasado el !analize -v dejame
>> aquí la salida.
>>
>> http://www.multingles.net/docs/jmt/bsod.htm
>>
>> 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:
>> > Bueno windows sigue dando errores igual,
>> > KERNEL_DATA_INPAGE_ERROR
>> > y otros.
>> >
>> >
>> >
>> >
>> > "JM Tella Llop [MVP Windows]" escribió:
>> >
>> >> Quizá estuviesen antel mal pinchadas o con suciedad. Si ahora no te da
>> >> fallos el test de memoria, tampoco te los debe dar windows. Si windows
>> >> te
>> >> diese de nuevo, inmediatamente vuelve a pasarle un test de memoria
>> >> para
>> >> descartar o no el problema hardware.
>> >>
>> >> 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 otra vez,
>> >> > mira volvi a poner mis antiguas 256Mb 400mhz en dual channel y pase
>> >> > el
>> >> > testeador de la manera q te dije y da todo bien ni un failed en 4h
>> >> > 10min,
>> >> > vos
>> >> > me diras. Saludos.
>> >> >
>> >> > "JM Tella Llop [MVP Windows]" escribió:
>> >> >
>> >> >> Si te el testaedor de memoria da UN solo error de memoria en 4
>> >> >> horas
>> >> >> esas memorias no sirvern.
>> >> >> Revisa en la web del fabricante el tipo de memoria (y las marcas)
>> >> >> que
>> >> >> son
>> >> >> compatibles con la 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:
>> >> >> > 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
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

Efectivamente. Fijate que una vez que eso te la salido, te aconseja hacer:

!analyze -v

Escribe esa sentencia en la linea inferior y dejame la salida.

(de todas formas, hasta el momento, te está indicando que: Probably caused
by : hardware

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:

Te referis a esto?:


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


Loading Dump File [C:\WINDOWS\MEMORY.DMP]
Kernel Summary Dump File: Only kernel 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: Sat Jun 4 00:58:48.859 2005 (GMT-3)
System Uptime: 0 days 2:34:47.548
Loading Kernel Symbols
.
Loading unloaded module list
...
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffda00c). Type ".hh dbgerr001" for details
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {f2f1d390, 0, f2f1d390, 0}

Probably caused by : hardware

Followup: MachineOwner

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




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

Debes arrancar el Windwbg y abrir el memory.dmp con la opcion del menur
File: "Open Crash Dump".
Dejame aquí la salida

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:
> BUeno, configure el volcado de mem en intermedio, no reiniciar,
> ya me a dado el error de PAGE_FAULT_IN_NONPAGED_AREA STOP:0X50(),
> se
> me
> creo un archivo c:\windows\memory.dmp (57Megas), descarge WinDbg lo
> abri
> hice
> lo de los simbolos se me creo una carpeta de 3 megas y algo en el c:
> abri
> el
> archivo y no se q ver u hacer aparecen muchas letras y simbolos y
> demasiados
> palitos(verticales).
> Saludos.
>
>
>
>
> "JM Tella Llop [MVP Windows]" escribió:
>
>> Mirate esto, y configura para obtener un DUMP válido (de Kernel a ser
>> posible), con ese dump y las herramientas estas, se puede proceder a
>> analizarlo en detalle. Hazlo y cuandi hayas pasado el !analize -v
>> dejame
>> aquí la salida.
>>
>> http://www.multingles.net/docs/jmt/bsod.htm
>>
>> 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:
>> > Bueno windows sigue dando errores igual,
>> > KERNEL_DATA_INPAGE_ERROR
>> > y otros.
>> >
>> >
>> >
>> >
>> > "JM Tella Llop [MVP Windows]" escribió:
>> >
>> >> Quizá estuviesen antel mal pinchadas o con suciedad. Si ahora no te
>> >> da
>> >> fallos el test de memoria, tampoco te los debe dar windows. Si
>> >> windows
>> >> te
>> >> diese de nuevo, inmediatamente vuelve a pasarle un test de memoria
>> >> para
>> >> descartar o no el problema hardware.
>> >>
>> >> 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 otra vez,
>> >> > mira volvi a poner mis antiguas 256Mb 400mhz en dual channel y
>> >> > pase
>> >> > el
>> >> > testeador de la manera q te dije y da todo bien ni un failed en
>> >> > 4h
>> >> > 10min,
>> >> > vos
>> >> > me diras. Saludos.
>> >> >
>> >> > "JM Tella Llop [MVP Windows]" escribió:
>> >> >
>> >> >> Si te el testaedor de memoria da UN solo error de memoria en 4
>> >> >> horas
>> >> >> esas memorias no sirvern.
>> >> >> Revisa en la web del fabricante el tipo de memoria (y las
>> >> >> marcas)
>> >> >> que
>> >> >> son
>> >> >> compatibles con la 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:
>> >> >> > 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
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

Microsoft (R) Windows Debugger Version 6.4.0007.2

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C:\WINDOWS\MEMORY.DMP]

Kernel Complete Dump File: Full address space is available

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

WARNING: Dump file has been truncated. Data may be missing.

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

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

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

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

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

Unable to read PsLoadedModuleList

KdDebuggerDataBlock not available!

KdDebuggerData.KernBase < SystemRangeStart

Windows XP Kernel Version 2600 UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x00000000 PsLoadedModuleList = 0x8055a420

Debug session time: Mon Jun 6 10:03:33.765 2005 (GMT+2)

System Uptime: 0 days 0:02:21.328

Unable to read PsLoadedModuleList

KdDebuggerDataBlock not available!

KdDebuggerData.KernBase < SystemRangeStart

Loading Kernel Symbols

Unable to read PsLoadedModuleList

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

CS descriptor lookup failed

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {d021ebfc, 0, 8056744e, 0}

***** Debugger could not find nt in module list, module list might be
corrupt.

***** Followup with Debugger team

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

Unable to read selector for PCR for processor 0

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

Probably caused by : Unknown_Image

Followup: MachineOwner



GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

?: kd> !analyze -v

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

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

* *

* 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: d021ebfc, memory referenced.

Arg2: 00000000, value 0 = read operation, 1 = write operation.

Arg3: 8056744e, If non-zero, the instruction address which referenced the
bad memory

address.

Arg4: 00000000, (reserved)

Debugging Details:



***** Debugger could not find nt in module list, module list might be
corrupt.

***** Followup with Debugger team

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

Unable to read selector for PCR for processor 0

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get MmPageSize (0x0) - probably bad symbols

d021ebfc

FAULTING_IP:

+ffffffff8056744e

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

8056744e ?? ???

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

STACK_TEXT:



FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

BUCKET_ID: CORRUPT_MODULELIST

Followup: MachineOwner

THIS DUMP FILE IS PARTIALLY CORRUPT.

No vale ese dump. y ademas es un dump completo.
Los motivos por lo que un dump completo esté corrupot son:

1) El fichero de paginacion en diferente unidad fisica a la unidad de
windows.

2) O bien: memoria dañada, disco dañado, en resumen, hardaware, el que sea,
dañado que impide incluso el volcado (escritura) correcta a un disco.

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.



"ABC" wrote in message
news:u$qFQ%

Microsoft (R) Windows Debugger Version 6.4.0007.2

Copyright (c) Microsoft Corporation. All rights reserved.



Loading Dump File [C:\WINDOWS\MEMORY.DMP]

Kernel Complete Dump File: Full address space is available

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

WARNING: Dump file has been truncated. Data may be missing.

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

Symbol search path is:
SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols

Executable search path is:

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

THIS DUMP FILE IS PARTIALLY CORRUPT.

KdDebuggerDataBlock is not present or unreadable.

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

Unable to read PsLoadedModuleList

KdDebuggerDataBlock not available!

KdDebuggerData.KernBase < SystemRangeStart

Windows XP Kernel Version 2600 UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x00000000 PsLoadedModuleList = 0x8055a420

Debug session time: Mon Jun 6 10:03:33.765 2005 (GMT+2)

System Uptime: 0 days 0:02:21.328

Unable to read PsLoadedModuleList

KdDebuggerDataBlock not available!

KdDebuggerData.KernBase < SystemRangeStart

Loading Kernel Symbols

Unable to read PsLoadedModuleList

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

CS descriptor lookup failed

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

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

* *

* Bugcheck Analysis *

* *

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {d021ebfc, 0, 8056744e, 0}

***** Debugger could not find nt in module list, module list might be
corrupt.

***** Followup with Debugger team

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

Unable to read selector for PCR for processor 0

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

Probably caused by : Unknown_Image

Followup: MachineOwner



GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

?: kd> !analyze -v

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

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

* *

* 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: d021ebfc, memory referenced.

Arg2: 00000000, value 0 = read operation, 1 = write operation.

Arg3: 8056744e, If non-zero, the instruction address which referenced the
bad memory

address.

Arg4: 00000000, (reserved)

Debugging Details:



***** Debugger could not find nt in module list, module list might be
corrupt.

***** Followup with Debugger team

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

Unable to read selector for PCR for processor 0

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

READ_ADDRESS: unable to get nt!MmSpecialPoolStart

unable to get nt!MmSpecialPoolEnd

unable to get MmPageSize (0x0) - probably bad symbols

d021ebfc

FAULTING_IP:

+ffffffff8056744e

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

GetContextState failed, 0x80004005

8056744e ?? ???

MM_INTERNAL_CODE: 0

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0x50

STACK_TEXT:



FOLLOWUP_NAME: MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

STACK_COMMAND: kb

BUCKET_ID: CORRUPT_MODULELIST

Followup: MachineOwner