Reinicio automatico

Estado
Cerrado para nuevas respuestas

loko_yague

Nuevo Miembro
Miembro
#1
Ola Buenas felicidades por el foro esta mui currado I nada aquí expongo mi problema que me sucede desde que volví a usar el ordenador ya que utilizaba otro y este llevaba 4 o 5 meses parado.

Mi Pc un p4 2,40mhz 512mb ati radeon 7000/VE, un disco duro interno de 60 gigas y uno externo de 360 gigas por usb. Pos desde que volví a usar el ordenador y formatearlo no paro de tener problemas reinicios automaticos con pantallas azules de errores, errores tipo 0x0000000A. Al entrar a Windows posteriormente cuando me deja me sale una ventana diciendo que sa tenio que reparar el registro porque tubo un error grave, el error producido por:

C:\DOCUME~1\YAGE~1\CONFIG~1\Temp\WER49bd.dir00\Mini060707-02.dmp

C:\DOCUME~1\YAGE~1\CONFIG~1\Temp\WER49bd.dir00\sysdata.xml

Nose ni que es si alguien me pudiera ayudar con el problema... e formateado escaneado en busca del virus haxdoor, reparado el registro, aumentado la ram a 512 y me sigue dando problemas ;) si alguien me pudiera ayudar se lo agradeceria.

Gracias de antemano. :eek:
 

jbex

El que peca y reza empata
Administrador
#2
Descarga el Debugging

Una vez que lo tengas instalado lo ejecutas vas a File->Open crash dump, navega a C:Windows y busca la carpeta llamada Minidump, ábrela encontraras un archivo ejemplo: Mini060707-02.dmp le das abrir y esperas a que lo analice.

Una vez que termine de analizarlo copias y pegas su contenido aquí, para analizarlo.

Un saludo, jbex
 

loko_yague

Nuevo Miembro
Miembro
#3
Me baje el debuging que me dijistes pero de poco me sirve porque dentro de la carpeta minidump no ai ningún archivo, esta vacia. Cual es el problema?

Gracias de todos modos
 

loko_yague

Nuevo Miembro
Miembro
#4
Encontre el archivo que me dijistes pero no en la carpeta Minidump de Windows sino donde siempre se me pone después de un error en los archivos temporales después del mensaje de inicio de que el sistema sa recuperado de un error grave de regitro. Al picar no enviar información a microsoft automáticamente desaparece, antes de que lo iciera lo analice y salio esto:

Microsoft ® Windows Debugger Version 6.7.0005.0

Copyright © Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Documents and Settings\Yagüe\Configuración local\Temp\WER86d2.dir00\Mini060807-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 2) UP Free x86 compatible

Product: WinNt, suite: TerminalServer SingleUserTS

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055a820

Debug session time: Fri Jun 8 06:30:10.601 2007 (GMT+2)

System Uptime: 0 days 0:00:22.171

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

* 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 1000008E, {c0000005, 81afcc1b, 81afca98, 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 ***

*** ***

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

Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

Followup: MachineOwner

---------
 
Estado
Cerrado para nuevas respuestas
Arriba Pie