Pantalla azul (ya formateé... y sigue el problema)

#1
Hola a todos, permítanme exponer mi problema, tengo una computadora armada con:
AMD Phenom II x6 1100T
ASUS M4A89TD PRO/USB3
2x4Gb G.SKILL 1600 MHz DDR 3 (F3-12800CL9D-8GBSR)
HDD WD 640 Gb SATA 3
ATI Radeon™ HD 5450
Cooloer Hyper TX3
con Windows 7 Ultimate x64


Tiraba pantallas azules sin patrón alguno, entonces:

- le cambié el cooler original por el Hyper TX3 (por la temperatura),

pero siguió tirando pantallas azules!!!!

Hice un post en ADSLZone (http://www.adslzone.net/modules.php?nam ... 63#1975863)

Siguiendo este post fantástico (http://www.softzone.es/manuales-softwar ... os-azules/)

y seguí los consejos... (bueno el HDD Regenerator no lo corri, usé el discCheck de TuneUp2012) :

Pasa memtest86+ durante varias horas a tu memoria RAM y HDD Regenerator a tu disco duro para ver si
tuvieran errores.

Bájate todos los drivers actuales desde las páginas web de los fabricantes. Luego desinstala por completo todos
los drivers de tu sistema. Para ello, crea primero un punto de restauración del sistema y desinstala todos los
drivers instalados con Driver Cleaner o Driver Sweeper , reinicia el sistema e instala los nuevos drivers en
este orden:
1. Chipset
2. Tarjeta gráfica
3. Tarjeta de sonido
4. Tarjeta de red
5. Resto

pero siguió tirando pantallas azules!!!!

- luego formateé, reinstalé todo, corrí el prime 95 con varios test que encontré en internet: el más largo de casi 20h: y las memorias bien!!!

pero sigue tirando pantallas azules!!!!

Siguiendo el mismo método del post obtuve la siguiente info que les comparto a ver si alguien puede ayudarme:


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


Loading Dump File [C:\Users\Nahuel\Desktop\Minidump\090213-37346-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 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff800`0300d000 PsLoadedModuleList = 0xfffff800`032506d0
Debug session time: Mon Sep 2 07:35:12.392 2013 (UTC - 3:00)
System Uptime: 0 days 0:00:10.594
*********************************************************************
* 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
Mini Kernel Dump does not contain unloaded driver list
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8008097788, 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Unable to load image PSHED.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for PSHED.dll
*** ERROR: Module load completed but symbols could not be loaded for PSHED.dll
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 : hardware

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

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

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8008097788, Address of the WHEA_ERROR_RECORD structure.
Arg3: 0000000000000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000000, Low order 32-bits of the MCi_STATUS value.

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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_SECTION_DESCRIPTOR ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************

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.

FAULTING_MODULE: fffff8000300d000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUGCHECK_STR: 0x124_AuthenticAMD

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

CURRENT_IRQL: 0

STACK_TEXT:
fffff880`0376f6f0 fffffa80`08097788 : 00000000`00000001 00000000`00000000 00000000`00000001 fffffa80`08097788 : nt+0x4ade7c
fffff880`0376f6f8 00000000`00000001 : 00000000`00000000 00000000`00000001 fffffa80`08097788 00000000`00000000 : 0xfffffa80`08097788
fffff880`0376f700 00000000`00000000 : 00000000`00000001 fffffa80`08097788 00000000`00000000 00000000`00000000 : 0x1


STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: hardware

IMAGE_NAME: hardware

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------
 
#2
El link que dices de ese pantallazo azul que comentas es distinto al tuyo.

Esta vez tu pantallazo es debido a Hardware, el log es bastante claro.

Código:
Probably caused by : hardware
Lo que ocurre, es que lo mismo puede ser por el fimware de un disco duro que por cualquier componente del ordenador, incluidos los drivers, (aunque normalmente si sería de un controlador se vería en el log que subes). Además ya has actualizado como dices todos los drivers.

Yo tenía hace tiempo ese mismo log con pantallazos azules cada cierto tiempo y al final me dí cuenta que era del firmware de un disco SSD, un OCZ Agility3 que tenía el famoso fimware que daba problemas a todos. Fue actualizarlo y hasta ahora sin pantallazos ni problemas, para esos log hay que mirar componente por componente hasta dar con el culpable.

¿Cual es el último componente que has instalado?, sin contar el disipador que dices.. Yo empezaría a mirar por ahí.


Saludos...
 
#3
Instalé todo junto, todo el hardware junto!!... excepto una lecto-grabadora de CD/DVD; podrías ser eso, no? la desenchufo y pruebo unos días!!
Muy buena idea, gracias!!

Otras curiosidades: con la última versión del FinalWare AIDA64 Extreme Engineer v3.00.250

- las temperaturas delos núcleos dan 0º !!!!
- el test de stress de RAM, CPU y DISCOS lo soportó sin problemas ni recalentar por espacio de 10 minutos, varias veces
 
#5
Es que por la grabadora es muy raro que sea, a no ser que lleve algún tipo de firmware o programa y no suelen llevarlos.









Saludos...
 
#6
Descartado memoría, software y temperatura yo apostaría por placa base o por tarjeta grafica, mira a ver si con otra tarjeta grafica o la que lleva la placa integrada te sigue saltando la pantalla azul.

Si te sigue saltando descartariamos también grafica y si te deja de saltar pues ya vemos un poco de luz al final del tunel, si te dejan de saltar, o bien el fallo esta en la placa base (ranura donde pones la grafica) o en la propia grafica, yo cambiaria la grafica a otra ranura y si siguen saltando directamente probaria con otra grafica, si siguen saltando es placa o fuente así que probaria con otra fuente...

Vamos, cambiar componentes poco a poco e ir probando, si cambiando todo siguen tirandote pantallazos es la placa.


Saludos!
 
#7
Hola.

Podrías probar resetear la BIOS (desconectando la toma de corriente y quitando la pila durante 1, o 2 min.)
para dejarla por defecto (predeterminada) y probar si continúan los pantallazos,
aunque después tengas que volver a configurar algunos parámetros.

Si continúan los errores, prueba con un live/cd de Ubuntu (por ejemplo)
para descartar software y disco duro.

un saludo.
 
#8
También puede volver a predeterminados los valores de la bios en la placa cambiando el jumper de posición (Clear CMOS), de esta forma:





Consulta el manual de tu placa base para saber donde está el jumper, pero es muy sencillo de hacer y fácil verlo, ya que está a la vista, normalmente al lado de la propia pila.

Lo levantas con una pinza o con la mano y lo cambias de posición a la otra. Esperas 15 segundos más o menos y lo tienes.


No obstante, pueba también lo que te comenta jesusteck con un CD Live De linux/Ubuntu a ver si te sigue dando errores.



Saludos...
 
#9
Hay una instrucción en las Herramientas de Depuración de Windows que es:

!errrec

Esta mira el problema específico del WHEA (Windows Hardware Error Architecture) es el sistema que tiene Windows para controlar los errores de hardware.

La instrucción !analyze -v se pone primero como en tu caso ya se hizo, si te fijas pone siempre como segundo argumento:

Arg2: fffffa8008097788, Address of the WHEA_ERROR_RECORD structure.

Pués en este caso se debe poner:

!errrec fffffa8008097788

Para saber que tipo de problema es.

http://www.sysnative.com/forums/bsod-ke ... 0x124.html

Salu2
 
#10
Antes que nada, quiero agradecer la atención y dedicación que me dispensaron: probé unas cuantas cosas más, incluidas las que me sugirieron en el foro y llegué a la siguiente solución, aunque no sé en qué se fundamenta: desactivé el Turvo V-evo, clavé los multiplicadores a mano (200x18.5=3.7 GHz) y SANTO REMEDIO!!!! ni un poquito más, las memorias quedaron en 1338 MHz.... y la máquina serenita, corrí el prime95 y el memtest86, el test de stress de AIDA.... y nada, no más pantallazos azules

por mi parte cierro la pregunta que hice en un principioy si mi experiencia la sirve a alguien, vinvenido sea!!

MIL GRACIAS A TODOS !!
 
#11
Ok, me alegro que lo hayas solucionado. ;)

El log que subiste anteayer era bastante claro al respecto, ya que mostraba un pantallazo azul por Hardware, pero lo que no aclara es debido a qué o el componente que falla, ya que Windows no lo sabe (cuando es por hardware).

Cuando ocurre, el usuario es quien debe investigar y recordar que es lo que ha instalado recientemente, si ha hecho overclock, etc, ya que nosotros no lo sabemos desde aquí, sólo podemos ver el log del minidump que nos muestras.


Saludos...
 
#12
NAlonso74 dijo:
Antes que nada, quiero agradecer la atención y dedicación que me dispensaron: probé unas cuantas cosas más, incluidas las que me sugirieron en el foro y llegué a la siguiente solución, aunque no sé en qué se fundamenta: desactivé el Turvo V-evo, clavé los multiplicadores a mano (200x18.5=3.7 GHz) y SANTO REMEDIO!!!! ni un poquito más, las memorias quedaron en 1338 MHz.... y la máquina serenita, corrí el prime95 y el memtest86, el test de stress de AIDA.... y nada, no más pantallazos azules

por mi parte cierro la pregunta que hice en un principioy si mi experiencia la sirve a alguien, vinvenido sea!!

MIL GRACIAS A TODOS !!
Me alegro mucho que lo hayas solucionado. Cualquier cosa ya sabes. ;)

Salu2
 
Arriba