Ayuda pantallazo azul y reinicio

Invitado

Hola wenas.
Tengo un problema con mi pc y es k me sale un pantallazo y luego se reinicia, lo hace cuando le da la gana, he probado ya mil cosas, hasta he formateado el pc xo hace lo mismo.
Encontre un post donde ponia como hacer un volcado de memoria y luego pasarlo por un programa k teoricamente te da el error, luego decia k lo colgara aki.
Weno aki os dejo el bloc de notas y gracias, espero k podais ayudarme.

Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
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: *** 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Windows XP Kernel Version 2600 (Service Pack 3) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 2600.xpsp_sp3_gdr.100216-1514
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Thu Jul 29 13:41:13.890 2010 (GMT+2)
System Uptime: 0 days 0:12:16.515
WARNING: Process directory table base 0B300020 doesn't match CR3 00795000
WARNING: Process directory table base 0B300020 doesn't match CR3 00795000
*********************************************************************
* 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+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrpamp.exe -
Loading Kernel Symbols
...................................................................................................................................
Loading User Symbols

Loading unloaded module list
...............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, b8340d70, 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 : ntkrpamp.exe ( nt!Kei386EoiHelper+16a5 )

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

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

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 00000008, EXCEPTION_DOUBLE_FAULT
Arg2: b8340d70
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+ *
*********************************************************************

MODULE_NAME: nt

FAULTING_MODULE: 804d7000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 4b7a9cac

BUGCHECK_STR: 0x7f_8

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

LAST_CONTROL_TRANSFER: from 00000000 to 80543571

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 nt!Kei386EoiHelper+0x16a5

STACK_COMMAND: kb

FOLLOWUP_IP:
nt!Kei386EoiHelper+16a5
80543571 ebee jmp nt!Kei386EoiHelper+0x1695 (80543561)

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!Kei386EoiHelper+16a5

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: ntkrpamp.exe

BUCKET_ID: WRONG_SYMBOLS

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

Administrador Registrado: Oct 21, 2008 Mensajes: 10438

¿Es una versión desatendida o lite de Windows XP?

Prueba a reparar el sistema con el CD de Windows XP (no pierdes datos ni documentos):

http://www.softzone.es/manuale...ema-en-xp/

Saludos.

Invitado

Hola wenas.
Si es una version desatendida, es un xp eu6 mas concretamente

Invitado

Acabo de acerle el reparar y nada mas encenderlo otra vez me ha salido la pantalla y se ha reiniciado.
Yo creo k tiene k ser algo de hardware xq como he dicho antes formatee el pc y seguia igual.

Administrador Registrado: Oct 21, 2008 Mensajes: 10438

Pasa HDD Regenerator a tu disco duro y memtest86+ a tu memoria RAM para ver si tienen errores o no, aunque me temo que el problema va a ser la versión desatendida.

Saludos.

Publicado: Jueves 29 Julio 2010, 13:41

Testea la ram con memtest

¿que antivirus tienes? desactiva el antivirus y mira si te tira pantallazo

Has instalado algún programa justo antes de aparecer los pantallazos

Te recomiendo que no uses versiones desatendidas, algunas dan problemas

Salu2

Gohuca

Invitado

Hace un par de dias ya le pase el hdd regenerator de hirens boot y el memtest y no me dio ningun error, respecto a lo de la version desatendida es extraño xq hace mas de 4 años k monte el pc y siempre he utilizado esta version y nunca me dio este error, no se, es algo muy raro.

Gracias por responder, os agradeceria k me aportarais mas posibles soluciones

Invitado

El antivirus es el k siempre he usado, el NOD32, voy a probar de desactivarlo, xo el problema es k no sabes cuando puede a volver a hacerlo, puede estar 2 o 3 dias sin hacerlo y al dia siguiente al encender el pc hacerlo mas de 10 veces seguidas.

ZoNeR@ Registrado: Jul 06, 2010 Mensajes: 2

Me pasó lo mismo y también me volví loco,formateando,pasando antivirus...etc.Hasta pensé en cambiarme el PC.
Yo lo pude solucionar, cambiando el adaptador USB de telefónica (unos 40€) por un D-Link (14,50 €).Ya llevo un año y no ha vuelto a dar ni un solo problema.Espero que te sirva.Un saludo

Invitado

Wenas.
Entonces dices k el problema era tu adaptador usb de telefonica?? Yo tambien tengo uno, como era el tuyo?? El mio tiene un cable de 1 metro mas o menos y es un aparatito pequeño con una antena plegable.

Mira el mio es como este:
http://www.movistar.es/on/io/e...20%3C/a%3E

Gracias

ZoNeR@ Registrado: Jul 06, 2010 Mensajes: 2

Efectivamente,en mi caso ése fué el malo de la película.Observé ,que mientras no me conectara a internet,no se reiniciaba,por lo que opté por hacer el cambio.(Lo único que me conecta,és el adaptador).No sé si sonó la flauta,pero a mi me sirvió.Deseo que lo puedas solucionar,si éste fuera tu caso.Un saludo.

Publicado: Viernes 30 Julio 2010, 15:41

Saludos a todos los usuarios de esta página, este es el primer post que JOLLS ponemos y queremos intentar ayudar en lo que podamos.

Efectivamente como se ha indicado anteriormente, algunos modems usb dan problemas de pantallazo azul con algunas actualizaciones de windows xp.

Muchos usuarios han tenido el modem durante meses sin problemas, hasta que el windows carga una actualizacion y entonces el sistema comienza a fallar.

El fallo que relatas parece muy aleatorio y aunque no podemos descartar que la memoria, la cpu o la fuente de alimentación tengan algo que ver en el mismo, lo mas facil es que desinstales el driver del modem y no lo conectes y pruebes a ver si funciona.

Si formateas y vuelves a instalar, no pongas el modem, trabaja un par de días con el equipo y comprueba si falla o no.

Un saludo

Invitado

Wenas, gracias por vuestras respuestas.

Estoy probando aver si me lo hace sin el adaptador instalado, ya os comento k tal..

Invitado

Hola wenas.
He comprobado lo k os comente y he podido comprobar k efectivamente solo me lo hace cuando la conexion inalambrica esta conectada, lo k necesito saber es si puede ser el adaptador inalambrico o alguna otra cosa relacionada con la conexion.
Gracias

Administrador Registrado: Oct 21, 2008 Mensajes: 10438

Tiene toda la pinta de que el culpable es el adaptador inalámbrico, aunque no puedo asegurártelo al 100%.

Saludos.