Foro de InfoSpyware - Foro de Hijackthis - Foro de Virus

ha continuacion se ha parado la grabacion que estaba realizando, del discoduro al disco de DVD, ya que era una pelicula, dicho esto me ha salido el siguiente mensaje en ingles: A problem has benn detected and windows has been shut down to prevent damage to your computer
KERNEL_STACK_INPAGE_ERROR.
If this stop error screen, restart yor computer.If this screen appears again,follow these steps:
Check to make sure any new hardware or software is properly installation, ask yor hardware or software.
Disable BIOS memory options such as caching or shadowing. If you need to use safe mode to remove or disable componentes, restart, you computer, pres f8 to select advanced startup options, and then select safe mode. Technical information:
Begining dump of physical memory physical memoy dump complete. Contact yor system administrator or technical support group for further assistance.

Mi pregunta ¿que debo de hacer? ¿por que se ha producido? espero vuestras respuestas. GRACIAS.

Hola. Ese es un pantallazo azul, cuya única solución es reiniciar 'a la fuerza' (con el botón de power)

Te dejo información sobre el error:

• Solucionar los errores "Stop 0x00000077" o "KERNEL_STACK_INPAGE_ERROR"
• Solucionar "stop 0x00000077" o "KERNEL_STACK_INPAGE_ERROR"

Saludos

Claw, gracias por interesarte, ¿pero solamente se trataria de reiniciar el equipo y el problema ya esta solucionado? disculpa por mi torpeza en estos asuntos, ya que como he comentado anteriormente mis conocimientos en informatica son nulos, y cuando me ha salido el pantallazo no sabia como solucionarlo. Y volviendo a la pregunta, y haciendo incapie, ¡SOLAMENTE CON REINICIAR EL EQUIPO EL PROBLEMA ESTA SOLUCIONADO!.Gracias.

Con reiniciar lo que conseguimos es poder volver a trabajar con el ordenador, pero el problema aún sigue vigente.

Te comento como podríamos mirar a qué se debe el problema.

Descarga e instala éste programa proporcionado por Microsoft. Es un depurador (o debugger), con el que nos podremos acercar más a donde se podría encontrar el fallo.

Abrimos el programa (por defecto en INICIO -> PROGRAMAS -> windbg) para, posteriormente, abrir el DUMP (archivo con el contenido del volcado de memoria). Para ello, vamos al menú "File" y hacemos click en la opción "Open Crash Dump". El archivo que abriremos se suele encontrar en C:\Windows\Minidump. Abriremos el último que nos aparezca.

Tras un primer chequeo de nuestro archivo, en la parte inferior nos aparece una pequeña barra sobre la que podremos escribir. Tecleamos !analyze -v

Nos deberán aparecer más código en la pantalla.

Copias y pegas aquí el contenido de ese fichero pero a partir de donde pone

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

Espero que no sea complicado (no lo es )

Saludos y cualquier duda la preguntas

Claw me he bajado el programa como tu indicas (debugging tools for windows)y dentro de éste se encuentra windbs, lo he abierto y he pinchado en file, para a continuación pinchar en OPEN CRASH DUMP, pero aquí no me aparece ningún archivo con el nombre C:/WINDOWS/MINIDUMP, por el contrario me aparece una ventana que dice BUSCAR EN:y dentro de un recuadro una carpeta "DEBUGGING TOOLS FOR WINDOWS". y a continuación y fuera del recuadro aparecen varias carpetas en la cuales dice:
1939.
clr10
nt4cht
nt4fre
symproxy
themes
triage
usb
w2kcht
w2kfre
winext
winxp.
Como podrás comprobar no aparece el archivo C:/WINDOWS/MINIDUMP. ¿que pasos debo seguir?.Espero tus noticias. GRACIAS

En la carpeta c:\windows\minidump debe haber un archivo .dmp

Ese es el que debes abrir

Claw:gracias por responderme tan rapido, me comentas:En la carpeta c:\windows\minidump debe haber un archivo .dmp.
Pero el caso es que no me aparece la carpeta c:windows/minidump como te he comentado en el post anterior, todo lo que me sale es lo que te he puesto anteriormente, lo he mirado y remirado y nada de nada, lo que me origina incertidumbre, ya que no se que hacer. Espero tu respuesta.

Claw, ya he podido entrar donde tu me dices, pero no puedo mandartelo porque no me deja copiar y pegar, si me dices que opcion tengo para mandartelo me lo dices. ya que no se me ocurre ninguna. Se que algunos mandan pantallazos pero no se como se hace. SALUDOS.

YA HE PODIDO COPIAR, ESTO ES EL ANALISIS EFECTUADO.
ESPERO TU RESPUESTA. GRACIAS

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

Use !analyze -v to get detailed debugging information.

BugCheck 77, {1, 47c, 0, aa6b0c4c}

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
Probably caused by : ntoskrnl.exe ( nt+22f13 )

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

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

KERNEL_STACK_INPAGE_ERROR (77)
The requested page of kernel data could not be read in. Caused by
bad block in paging file or disk controller error.
In the case when the first arguments is 0 or 1, the stack signature
in the kernel stack was not found. Again, bad hardware.
An I/O status of c000009c (STATUS_DEVICE_DATA_ERROR) or
C000016AL (STATUS_DISK_OPERATION_FAILED) normally indicates
the data could not be read from the disk due to a bad
block. Upon reboot autocheck will run and attempt to map out the bad
sector. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and the paging
file is on a SCSI disk device, then the cabling and termination should be
checked. See the knowledge base article on SCSI termination.
Arguments:
Arg1: 00000001, (page was retrieved from disk)
Arg2: 0000047c, value found in stack where signature should be
Arg3: 00000000, 0
Arg4: aa6b0c4c, address of signature on kernel stack

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!KPRCB ***
*** ***
************************************************** ***********************
************************************************** ***********************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
************************************************** ***********************

MODULE_NAME: nt

Claw, te mande ayer copia del análisis realizado, desconozco si lo has mirado, si no lo has hecho dale un vistazo por favor, tal vez se te ha pasado por alto, te digo esto porque ayer me salio otra vez la "pantallita" azul. Agradecido por tu interés