| |||||||
| Foro de Windows Todo lo relacionado con los sistemas operativos Windows 95/98/2000/Me/NT/XP |
 |
| | Enviar a: | Herramientas |
 | 
06/11/09, 23:58:01
|  |
| ||||
| No puedo entrar a S.O. XP (Terminado/Formateo) Que tal amigos, bueno les escribia porque tengo un problemazo, bueno primeramente tengo 2 SO el XP y Windows 7, a la hora de entrar al XP ( suelo trabajar en este SO ) me bota, me sale una pantalla azul muy rapida que no me deja leer lo que dice, luego se me reinicia la PC y le seleccion XP y me sale una pantalla negra diciendome que no se pudo iniciar la sesion en XP debido a que hubo algun cambio en un hardware o software, etc y que no puedo, etc, bueno le doy a iniciar normalmente y vuelve a salir esta misa, porfavor necesito ayuda porque mas trabajo en el XP, y ahora estoy escribiendo este mi problema desde el Windows 7, si alguien puede ayudarme, les agradecere infinitamente, Saludos Cordiales! |
| InfoSpyware | ||
| |
|
07/11/09, 04:02:14
| |
| ||||
| re: No puedo entrar a S.O. XP (Terminado/Formateo) Clic derecho sobre Mi PC > Propiedades > pestaña Opciones Avanzadas > abajito en Inicio y recuperación clic > Buscas donde dice Inicio de sistema y desactivas donde dice: Reiniciar automaticamente... Con esto podrás ver q dice el pantallazo azul. Suerte!! |
|
07/11/09, 11:46:53
| |
| ||||
| re: No puedo entrar a S.O. XP (Terminado/Formateo) Bueno ahora lo que pasa es que ya pude entrar al XP si nproblemas, luego la volvi a reiniciar y me mandaba lo mismo, no puedo lograr entrar al XP, estuve leyendo sobre el disco de arranque de XP, lo que pasa es que tengo el archivo de arranque guardado pero creo que se necesita el Cd, si alguien me ayuda con esto?? , Saludos! Cordiales... |
|
07/11/09, 12:00:25
| |
| ||||
| re: No puedo entrar a S.O. XP (Terminado/Formateo) Hola Veamos que proceso genera el pantallazo Desde Windows 7 realiza lo siguiente: Descarga la siguiente herramienta Debugging Tools for Windows Al abrir el programa principal, escoger "Open Crash Dump", y escoges un fichero, lo tienes en [B]D:\Windows\Minidump\/B]. Se te abre entonces una ventana de depuración, que te permite meter comandos. Tienes que meter el comando !analyze -v Código: NOTA: Toma encuenta que D:\ es la unidad donde está instalado Windows XP Un saludo |
|
07/11/09, 16:10:19
| |
| ||||
| re: No puedo entrar a S.O. XP (Terminado/Formateo) Cita:
Que tal amigo no entiendo esta parte mi xp esta instalado en el disco C No entiendo esta parte Código: NOTA: Toma encuenta que D:\ es la unidad donde está instalado Windows XP |
|
07/11/09, 16:29:23
| |
| ||||
| re: No puedo entrar a S.O. XP (Terminado/Formateo) Bueno amigo aqui esta el reporte de lo que me dijiste: Código: Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini110709-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Fri Nov 6 23:20:51.531 2009 (GMT-5)
System Uptime: 0 days 0:00:29.328
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Unable to load image ntoskrnl.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
Loading Kernel Symbols
...............................................................
.................................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck C0000218, {e1b7a4c8, 0, 0, 0}
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : ntoskrnl.exe ( nt+22f43 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Unknown bugcheck code (c0000218)
Unknown bugcheck description
Arguments:
Arg1: e1b7a4c8
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000
Debugging Details:
------------------
***** 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 ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4a784394
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0xC0000218
LAST_CONTROL_TRANSFER: from 806573f6 to 804f9f43
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
b964a864 806573f6 0000004c c0000218 b964a8a0 nt+0x22f43
b964aa18 8061413c c0000218 00000001 00000001 nt+0x1803f6
b964abc4 806143c0 c0000218 00000001 00000001 nt+0x13d13c
b964ac34 80626fd8 c0000218 00000001 00000001 nt+0x13d3c0
b964adac 805cff72 00000002 00000000 00000000 nt+0x14ffd8
b964addc 805460ee 80626df0 00000002 00000000 nt+0xf8f72
00000000 00000000 00000000 00000000 00000000 nt+0x6f0ee
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+22f43
804f9f43 5d pop ebp
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+22f43
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
|
|
07/11/09, 22:49:23
| |
| ||||
| re: No puedo entrar a S.O. XP (Terminado/Formateo) Hola El informe que me pusiste apunta que el error se produjo por este proceso ntoskrnl.exe Es un proceso crítico del sistema, si tienes mas archivos dump analízalos todos y pega su reporte para ver si hay mas fallas Aunque también puede ser por una infeccion. Un saludo |
|
07/11/09, 23:00:58
| |
| ||||
| re: No puedo entrar a S.O. XP (Terminado/Formateo) Hola Pueden ser dos causas: 1. Error de del sistema (ya sabes, es Windows) 2. Posiblemente una infección No puede ser error de ningún dispositivo o de hardware porque Windows 7 funciona bien Para descartar una posible infección analiza con Panda Active Scan2 siguiendo su manual. Pega su reporte aquí en tu próxima respuesta (si no puedes hazlo desde Windows 7) Otra solución puede ser actualizar al último Service Pack de Windows XP Un saludo |
|
« Tema Anterior
|
Próximo Tema »
| Herramientas | |
| |
| 
Temas Similares | |
| Tema | Autor | Foro | Respuestas | Último mensaje |
| No puedo entrar en modo seguro, y la pc no entra mas | fogb259 | Foro de Virus y Spywares | 15 | 20/12/08 08:51:52 |
| No puedo entrar en modo seguro | lmar | Foro de Virus y Spywares | 7 | 17/03/08 15:06:28 |
| no puedo entrar a los foros | gauchoedu | Problemas con el foro | 1 | 10/04/07 10:29:14 |
| no puedo entrar a infospyware (Solucionado) | lalo_a_link | Problemas con el foro | 4 | 09/04/07 22:10:45 |
| Ayuda: no puedo entrar a Windows XP | fluken | Foro de Windows | 1 | 09/06/06 22:12:06 |
Todas las horas son GMT -4. La hora es 20:00:55.
