Solución a los pantallazos azules, también llamados pantallazos de la muerte

En más de una ocasión os habréis encontrado con que vuestro PC en algún momento determinado sin saber el porqué se os va todo el sistema y provoca un pantallazo azul. Aquí tenéis un ejemplo del mismo

Blue Screen View Solution

Bien, pues para poder solucionar dicho error/problema  de los pantallazos azules seguimos los pasos que a continuación os expongo

ATENCIÓN!!! si el problema es de software,driver,librerías dinámicas corruptas,archivos del sistema operativo,virus ect ,ect…el problema se solucionará en el 95% de los casos

Si fuera problema de Hardware obviamente será el de ir quitando de la placa base dispositivos e ir probando cuál es el que provoca el pantallazo por incompatibilidad o porque dicho hardware esté dañado

(DICHA OPERACIÓN) Únicamente debe ser realizada por expertos en el tema, ya que el daño podría ser irreversible para tu placa base y dispositivos si no supieras realizar dichas tareas y sobre todo siempre estar protegido POR SEGURIDAD con la pulsera antiestática, pero REPITO!! esta opción es únicamente si el problema fuera de Hardware/dispositivos Físicos Y para asegurarte si el problema es de Hardware deberás grabar un CD LIVE de Linux Bootable y arrancar con el y dejarlo funcionando al menos unas cuantas horas.

De esa forma sabrás si te siguen dando más pantallazos que el problema es de Hardware y no se software, ya que todo el sistema está en el CD, os dejo que escojáis la distribución que queráis si fuera este vuestro caso, por ejemplo, Ubuntu.

Seguimos,lo primero que debemos hacer para localizar de dónde proviene dicho error /pantallazo azul de nuestro PC/Sistema. En el escritorio en el icono MI PC pulsamos sobre el mismo Ratón derecho/Propiedades y como muestra la foto pulsamos en la ficha Opciones avanzadas/configuración:

Veréis que por defecto trae la casilla “Reiniciar automáticamente activada”, pues la desactivaremos como os muestro en la foto. Más abajo cambiamos la opción “volcado de memoria pequeña (64)KB” por “Volcado de memoria de núcleo” y aceptamos.

analizar pantallazos azules windows foto

Con esto provocamos que cuando salga de nuevo el pantallazo azul, el PC no se reinicie y se quede estático con la pantalla azul y que a su vez el volcado de memoria recopile toda la información necesaria para ser leída por el programa “Microsoft Debugging Tools”.

IMPORTANTE!! deberéis dejar que el volcado de memoria llegue al cien por cien y después reiniciar el PC con el botón reset y si no lo tenéis, dejar pulsado el botón de apagado del PC unos segundos sin soltarlo para que el PC se apague.

Ahora lo más importante es descargar un programa que es el que nos dará la información del archivo que Windows guarda llamado Minidump, que es el lugar donde se archiva los errores del pantallazo y sus posibles causas, su directorio es C:\Windows\Minidump

Bueno descargamos el programa Debugging Tools for Windows desde la web principal de Microsoft.si.

Una vez instalado el programa y habiendo realizado los pasos anteriores que os comenté en el tutorial ,ejecutamos el programa en la ruta

INICIO/PROGRAMAS/Debugging Tools for Windows (X86)/windbg y cargamos el pantallazo más reciente guardado.

analizar pantallazos azules windows foto 2

Una vez abierto el archivo Minidump desde el programa como indican las fotos anteriores en la parte de abajo en la barra escribiremos el comando !analyze -v y pulsaremos ENTER , nos dará toda la información recopilada , ahora sólo nos queda copiarla en un block de notas como indica la foto y ponerla en el FORO DE SOFTWARE para que os ayudemos y os digamos la más que posible causa del pantallazo ya sea un driver del sistema, de algún hardware instalado por no ser éste compatible el controlador, archivos corruptos, virus, etc, etc.

Compártelo. ¡Gracias!

Comentarios

113 comentarios
  1. Arsenio 23 may, 08 13:23

    Muchas gracias por la información, me ha ayudado mucho.
    ¿Sabés si en algún lado existe más imformación sobre como usar la máquina de Debugging de windows?

    0
  2. leo 18 jun, 08 3:08

    quisiera que me mandaran un poco mas de informacion hacerca de la pantalla azul de la muerte a mi correo para tener un poco mas de informacion basica de ello no quiero decir que no esta bien lo que estan mostrando en esta pagina pero un poco mas desglosada para mayor entendimento.

    atte leo gracias por la informacion aqui descrita.

    0
  3. WWE Lita 20 jun, 08 0:43

    Hello…I Googled for vb6 protection, but found your page about nnial 2007 – salvatore iaconesi – del.icio.us poetry…and have to say thanks. nice read.

    0
  4. Puma 20 jun, 08 18:07

    Hola, yo tuve un problema con la pantalla azul, como la ultima vez que utilice mi equipo estaba conectado con mi modem, al iniciarlo con el modo de prueba de errores, deshabilite el modem y ya no me presenta el problema. Instale y corrí el windbg como lo explican y me apareció el siguiente mensaje :

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\WINDOWS\Minidump\Mini061808-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 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) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Tue Jun 17 16:27:19.859 2008 (GMT-5)
    System Uptime: 0 days 0:00:25.531
    *********************************************************************
    * 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 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

    Unable to load image HSFHWBS2.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for HSFHWBS2.sys
    *** ERROR: Module load completed but symbols could not be loaded for HSFHWBS2.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000007E, {c0000005, 823242d0, a9ca2c7c, a9ca2978}

    ***** 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : HSFHWBS2.sys ( HSFHWBS2+1c0ec )

    Followup: MachineOwner
    ———

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

    SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
    This is a very common bugcheck. Usually the exception address pinpoints
    the driver/function that caused the problem. Always note this address
    as well as the link date of the driver/image that contains this address.
    Some common problems are exception code 0x80000003. This means a hard
    coded breakpoint or assertion was hit, but this system was booted
    /NODEBUG. This is not supposed to happen as developers should never have
    hardcoded breakpoints in retail code, but …
    If this happens, make sure a debugger gets connected, and the
    system is booted /DEBUG. This will let us see why this breakpoint is
    happening.
    Arguments:
    Arg1: c0000005, The exception code that was not handled
    Arg2: 823242d0, The address that the exception occurred at
    Arg3: a9ca2c7c, Exception Record Address
    Arg4: a9ca2978, Context Record Address

    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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 40d22194

    EXCEPTION_CODE: (NTSTATUS) 0xc0000005 – La instrucci n en “0x%08lx” hace referencia a la memoria en “0x%08lx”. La memoria no se puede “%s”.

    FAULTING_IP:
    +ffffffff823242d0
    823242d0 2807 sub byte ptr [edi],al

    EXCEPTION_RECORD: a9ca2c7c — (.exr 0xffffffffa9ca2c7c)
    ExceptionAddress: 823242d0
    ExceptionCode: c0000005 (Access violation)
    ExceptionFlags: 00000000
    NumberParameters: 2
    Parameter[0]: 00000001
    Parameter[1]: 00000001
    Attempt to write to address 00000001

    CONTEXT: a9ca2978 — (.cxr 0xffffffffa9ca2978)
    eax=0a060001 ebx=00800000 ecx=81e459f0 edx=80563c50 esi=81e6faf0 edi=00000001
    eip=823242d0 esp=a9ca2d44 ebp=00000000 iopl=0 nv up ei pl nz na po cy
    cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010203
    823242d0 2807 sub byte ptr [edi],al ds:0023:00000001=??
    Resetting default scope

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0x7E

    LAST_CONTROL_TRANSFER: from f792b0ec to 823242d0

    STACK_TEXT:
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    a9ca2d40 f792b0ec 0a060002 81e459f0 00000006 0x823242d0
    00000000 00000000 00000000 00000000 00000000 HSFHWBS2+0x1c0ec

    FOLLOWUP_IP:
    HSFHWBS2+1c0ec
    f792b0ec ?? ???

    SYMBOL_STACK_INDEX: 1

    SYMBOL_NAME: HSFHWBS2+1c0ec

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: HSFHWBS2

    IMAGE_NAME: HSFHWBS2.sys

    STACK_COMMAND: .cxr 0xffffffffa9ca2978 ; kb

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
    ———

    ¿Me podrían ayudar a decirme a que se refiere?

    Gracias y Saludos

    0
  5. jose 22 jun, 08 0:18

    Hola,buenas,queria comentarte que un tio mio no tiene el xp original y pensabamos si habria algun tipo de problema al instalar tantas cosas.Gracias.

    0
  6. Gohuca 22 jun, 08 12:01

    Lo mejor es comprar el sistema operativo, tener un sistema operativo pirata solo puede traerte mas que problemas

    0
  7. Sergio 22 jun, 08 19:41

    Hola, hice los pasos que dijistes y en el informe me sale la sig leyenda

    Probably caused by : Ntfs.sys

    esto a que se refiere?

    Gracias
    Sergio

    0
  8. Puma 24 jun, 08 20:53

    Hola ya realica los pasos arriba explicados y me manda el siguiente mensaje :

    Probably caused by : HSFHWBS2.sys ( HSFHWBS2+1c0e9 )

    ¿A que se debe?

    Gracias y Saludos

    0
  9. Manuel 25 jun, 08 20:58

    Hola he bajado el programita (el de 64 bits) y me dice que el tipo de procesador no es compatible con ese software, tengo un Amd Athlon dual core 64oo ¿que puedo hacer? el equipo es recien montado arranca perfecto pero a cada rato….pantallazo.

    0
  10. Friedrich 22 ago, 08 4:15

    Muchas gracias por la informacion,me ayudo muchisimo,ahora mi Pc ya no tiene mas pantallazos azules.
    Era el archivo “sptd.sys”,que es parte del Daemol Tools,lo elimine.
    Y al final,reinice la PC.
    Y trabaje con la pc durante 10 horas,y ningun PROBLEMAS!!!!

    0
  11. Matias 29 ago, 08 1:05

    me sale que el problema es originado por ntkrnlpa.exe , averiguando supe que es una aplicacion critica de windows, que puedo hacer?

    0
  12. Gohuca 29 ago, 08 1:37

    Puedes plantear todas las dudas que quieras en el foro de software:

    http://www.adslzone.net/forum51.html

    Te ayudaremos a solucionar el problema

    Salu2

    Gohuca

    0
  13. DANIEL 29 sep, 08 12:50

    Buenos días,

    Estoy desesperado, me acabo de comprar un portatil con vista y se me reinicia cada dos por tres.
    Después de seguir todos los pasos que indicáis, este es el error que me da.
    ¿Podéis ayudarme a solucionarlo?

    IMAGE-NAME: ntkrnlpa.exe
    SYMBOL-NAME: NT+CD163

    Muchas gracias

    0
  14. Radykall 01 oct, 08 15:08

    Hola.

    Mi caso es raro, porque con windows XP ni un solo pantallazo de este tipo y poner vista con todas las aplicaciones dejarlo descargando y fuala a la mañana siguiente equipo reseteado, motivo? PANTALLAZO AZUL…El widows es vista ultimate SP1

    Saludos

    0
  15. bone 03 oct, 08 23:05

    oye me funciono grasias ahora el problema es justo el que no queria que es el harware eso ya es mas complicado pero supe cual era el problema que ya es algo desde ya las grasias

    0
  16. kelvin añez 10 oct, 08 22:36

    mira esto es lo que me dice:
    Probably caused by : win32k.sys ( win32k+116327 )

    que debo hacer

    0
  17. Muy buen tutorial del pantallazo 12 oct, 08 5:14

    Fijense amiguitos que ya hice el procedemiento para quitar el pantallazo azul, pero al hechar andar el programa ami no me sale el archivo (mini050908-01.dmp) me sale otros ayudenme por favor.

    por sus atenciones muchisimas gracias.

    0
  18. Muy buen tutorial del pantallazo 12 oct, 08 5:21

    Perdon se me olvido decir que tengo el sistema operativo xp profesional sp1 y trate de bajar el programa dubuggning para 64 bits pero me manda el mensaje que mi procesador no es compatible baje el de 32 bits y ese si me acepto. por sus consejos gracias.

    0
  19. ozulosel 13 oct, 08 0:12

    amiguitos ya hice todo hasta bajar el programa debunning de 32 bits tengo el sistema operativo xp profesional sp1 pero no me aparece el archivo mini050908.01dmp y cuando quiero instalar algun programa bajado de internet me manda el siguiente pantallazo:

    SE A ENCONTRADO UN PROBLEMA Y WINDOWS HA SIDO APAGADO PARA EVITAR DAÑOS EN EL EQUIPO.

    DRIVER_IRQL_NOT_LESS_OR_EQUAL

    SI ES LA PRIMERA VEZ QUE VE ESTA PANTALLA DE ERROR DE DETENCIÓN REINICIE SU EQUIPO. SI ESTA PANTALLA APARECE OTRA VEZ, SIGA LOS SIGUIENTES PASOS:

    COMPRUEBE QUE CUALQUIERA HARDWARE O SOFWARE ESTA CORRECTAMENTE INSTALADOS.
    SI ES UNA NUEVA INSTALACIÓN, CONTACTE CON SU PROVEEDOR DE HARDWARE O SOFWARE PARA OBTENER ACTUALIZACIÓN DE WINDOWS QUE PUEDA NECESITAR
    SI LOS PROBLEMAS CONTINUAN, DESHABILITE LAS OPCIONES DE LA BIOS COMO CACHE O VIGILANCIA SI NECESITA UTILIZAR EL MODO A PRUEBA DE ERRORES, PARA QUITAR O DESAHABILITAR COMPONENTE, REINICIE SU EQUIPO, PRESIONANDO F8 PARA SELECIONAR OPCIONES DE INICIO AVANZADAS Y, A CONTINUACIÓN, SELECCIONE MODO A PRUEBA DE ERRORES;

    STOP: 0X000000D1(0X00000102, 0X00000006, 0X00000001, 0XF1ECFD64

    EMPESANDO EL VOLCADO DE MEMORIA FISICA
    DESACARGA DE MEMORIA FISICA COMPLETA
    PONGASE EN CONTACTO CON SU ADMINISTRADOR DE SISTEMA O GRUPO DE SOPORTE TECNICO PARA OBTENER AYUDA.

    0
  20. Guillermo 17 oct, 08 0:15

    Cuando hay que elegir en el WinDbg en la carpeta mindump, me aparesen un montón de archivos.dmp y cuando apreto abrir en alguno de ellos no me deja, dice que no tengo permiso. porfavor ayuda!!

    0
  21. Guillermo 17 oct, 08 0:18

    y ademas no me aparese justo ese mini05… me aparecen otros pero ese no!:(
    que puedo hacer
    ¡¡ayuda!!
    desde ya gracias

    0
  22. Marcos 08 nov, 08 19:22

    Tengo windows vista x64 me baje el archivo correspondiente y cuando lo quiero instalar me dice que mi procesador no es compatible, tengo un Athlon 64 x2 6000. Que puedo hacer?

    0
  23. daniel 14 nov, 08 0:03

    oo men se te agradece la raja men

    0
  24. luisjavier187 15 nov, 08 23:42

    tengo un celeron de 2,5 y desde hace poco me aparece el pantallazo azul y lo tengo que reiniciar unas tres veces pero me dice que el error esta en el archivo win32k.sys

    0
  25. luisjavier187 15 nov, 08 23:59

    instale el programa dbg y me dice que el problema es este Probably caused by : s3gnb.dll ( s3gnb+18f24 ) agradeceria si me digeran que debo hacer. gracias

    0
  26. Robert Gago 16 nov, 08 12:24

    #29 luisjavier187

    desinstala y actualiza los drivers de tu tarjeta gráfica.

    0
  27. tonyyy 16 nov, 08 12:49

    SiSGRV.dll ( SiSGRV+5b5b ) este error me da a mi alguna sugerencia???

    0
  28. tonyyy 16 nov, 08 12:51

    lo busco en las unidades y m sale este archivo SISGRV.dll debo borrarle¿??

    0
  29. Emiliano 18 nov, 08 15:42

    Me parecio excelente tu post, pero me gustaria saber donde me puedo orientar sobre como mejorar un driver ya que me aparece este error

    Probably caused by : f9d8aad3.sys ( f9d8aad3+724b )

    muchas gracias!!!!!

    0
  30. tonyyy 18 nov, 08 18:26

    por favorr kontestenmeee

    0
  31. Centurión 18 nov, 08 20:06

    tonyyy
    SiSGRV.dll corresponde a tu tarjeta gráfica integrada, desinstala los drivers REINICIA e instala de nuevo los drivers de tu gráfica actualizados

    0
  32. Centurión 18 nov, 08 20:06

    tonyyy

    SiSGRV.dll corresponde a tu tarjeta gráfica integrada, desinstala los drivers REINICIA e instala de nuevo los drivers de tu gráfica actualizados

    0
  33. Centurión 18 nov, 08 20:12

    Emiliano mírale las propiedades al supuesto driver, creo que es más bien algún spyware ya que no me suena a driver ni nada ques e le parecca, de todas formas para asegurarnos míralo entra en la carpeta del sistema de driver o donde te lleve el mismo y ratón derecho propiedades y mira qué fabricante te dice o a qué corresponde si pone (desconocido) sácalo de la misma y REINICIA

    0
  34. Harold 18 nov, 08 22:20

    Muy buen aporte el manual para encontara el error pero me parece q hace falta una lista de posibles errores.
    por ejemplo en mi analisis con el Dump me sale lo siguiente

    Probably caused by : NVTcp.sys ( NVTcp+119b8 )

    Followup: MachineOwner

    cual podria ser la razon? como solucionarlos o si alguien me puede decir a q mail mando esto para qme lo analices muchas gracias, saludos

    0
  35. Centurión 19 nov, 08 1:02

    NVTcp.sys es parte de los drivers de la targeta de red nVidia, aunque puede que la provocación haya sido afectada por la misma gráfica, desisntala los dirvers de gráfica REINICIA e instala los actualizados

    Si siguiera haz lo mismo con los de red de nvidia ya que concretamente NVTcp.sys son driver de red de nvidia

    0
  36. Monkey_c 19 nov, 08 2:04

    ahh ok! t refieres a solo instalar el driver de la tarjeta lan! y no de su controlador de red grafico…no es cierto? lo hice y el problema parece haberse ido, gracias por la pronta respuesta enrrique

    pero una pregunta mas, no se si esto esta relacionado con una carpeta q me aparece en cada disco (D: y E:)una con nombre “ZZZZZZZ.ZZZ” y dentro tiene un archivo “lpt3.This folder was created by Flash_Disinfector” no se puede borrar, y m e aparecio justo cuando empezo el problema con la pantalla azul

    tiene algo q ver? o puedes ayudarme a borrar esta molesta carpeta rebelde?

    0
  37. Centurión 19 nov, 08 23:03

    El Flash_Disinfector
    es una herramienta creada principalmente para eliminar el tan famoso virus
    BANTAI USA EZRAEL AL MUKHLIS STUDIOS
    eliminando script maliciosos cargadores autorun infectados de auto reproducción, ect, ect..

    Con los archivos script autorun
    autorun.inf
    win31.dll.vbs
    key.exe

    HKLM\Sofware\Microsoft\Windows\Current Version\Run\ Mcafee – Win31.dll.vbs

    Y la cual crea una carpeta en las unidades de disco físico o memorias USB, puedes eliminarlas sin problemas…

    Si no se deja utiliza unlocker
    http://software.adslzone.net/2008/01/13/miniguia-desbloqueo-de-archivos-con-unlocker/

    Saludos..

    0
  38. monkey_c 20 nov, 08 14:41

    muchas gracias por la informacion…. y segun tu experiencia, si se encargan de esos scripts maliciosos seria mejor ocultarlo y dejarlo ahi, para q siga con su tranajo¿? o borrarlos nomas, ahora con el trauma de ese pinche virus estoy con el kaspersky 8, y el avast4.8 amosactualizados y con llaves, no se si pueden trabajar juntos, te pederia por favor q me sugiera cual utilizar para sentir algo de tranquilidad, y q medida tomar con esa carpeta zzzzzzz.zzz y el flash desinfector

    gracias de antemano

    salu2

    0
  39. Centurión 20 nov, 08 21:52

    La carpeta carpeta zzzzzzz.zzz elimínala, como protección te recomiendo al 100% kaspersky sin duda alguna, y tener conjuntamente 2 antivirus no es recomendable para nada, puede casusar inestabilidad en el sistema , quita el Avast!! aunque es un buen antivirus no es comparable con el todopoderoso kaspersky y con él, te sobra

    Saludos..

    0
  40. alfredo 22 nov, 08 3:39

    Se hase igual en windowa vista

    0
  41. alfredo 22 nov, 08 3:40

    se has igual en windows vista

    0
  42. rarissssssimo 25 nov, 08 19:07

    Centurion, yo sigo todos los pesos, pero cuando busco el archivo .dmp no hay nada en la carpeta, sin embargo cada vez que juego el Lineage II (famoso juego MMORPG con altas exigencias graficas) por un rato, o sale el pantallazo, o se reinicia sola la maquina, no creo que sea por hardware, porque lñas compatibilidades que yo tenia estabas supuestamente solucionadas tengo una GeForce 7300 SE / 7200 GS, 2GBs de RAM, intel dual-core 1.8 Ghz.

    0
  43. rarissssssimo 25 nov, 08 19:09

    “porque lñas compatibilidades que yo tenia estaban supuestamente solucionadas”, error perdon xD. quise decir “porque las INcompatibilidades que yo tenia estaban supuestamente solucionadas” xDxDxDxDxD

    0
  44. rarissssssimo 26 nov, 08 17:22

    gente, ya me aparecio el archivo .dmp. el debugging tool me dice: Probably caused by : DSDrv4.sys ( DSDrv4+53c )

    AYUDA por favorrrrr!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Cenutrion, si no tenes tiempo de buscar, por lo menos decime la fuente de donde sacas las causas de los errores, gracias :S:S:S::SS

    0
  45. Diego 01 dic, 08 22:43

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\WINDOWS\Minidump\Mini120108-07.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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible
    Product: WinNt
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
    Debug session time: Mon Dec 1 19:31:15.812 2008 (GMT-3)
    System Uptime: 0 days 0:27:45.515
    *********************************************************************
    * 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    …………………………………………………………………………………………………
    Loading User Symbols
    Loading unloaded module list
    ………
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck D1, {0, ff, 8, 0}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** 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 ***
    *** ***
    *************************************************************************
    *********************************************************************
    * 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : ntkrnlpa.exe ( nt+6c950 )

    Followup: MachineOwner
    ———

    0: kd> !analize -v
    No export analize found
    0: kd> !analyze -v
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000000, memory referenced
    Arg2: 000000ff, IRQL
    Arg3: 00000008, value 0 = read operation, 1 = write operation
    Arg4: 00000000, address which referenced memory

    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 ***
    *** ***
    *************************************************************************
    *********************************************************************
    * 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************

    MODULE_NAME: nt

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 48a3f93a

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    00000000

    CURRENT_IRQL: ff

    FAULTING_IP:
    +0
    00000000 ?? ???

    CUSTOMER_CRASH_COUNT: 7

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from 00000000 to 80543950

    FAILED_INSTRUCTION_ADDRESS:
    +0
    00000000 ?? ???

    STACK_TEXT:
    b910ccd4 00000000 00000000 00000000 00000000 nt+0x6c950

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt+6c950
    80543950 ?? ???

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt+6c950

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ntkrnlpa.exe

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
    ———

    0: kd> g
    ^ No runnable debuggees error in ‘g’

    0
  46. Carlos 04 dic, 08 17:12

    Amigos!!!

    A mi me salio este problema:

    Probably caused by : PCIIDEX.SYS ( PCIIDEX+c91 )

    Followup: MachineOwner

    Alguien me puede ayudar?

    Gracias!!!!

    0
  47. Jesus 10 dic, 08 22:51

    hooola hize toodo y me saliio

    Probably caused by : nv4_mini.sys ( nv4_mini+1b380b )

    no se a que archivo se refiere
    por favor alguien me puede ayudar
    llevo semanas con la pantalla azul..

    muxasss gracias :D

    0
  48. manolillo 19 dic, 08 15:52

    os funciona gente?

    0
  49. Robert Gago 19 dic, 08 19:58

    Os recuerdo, que si teneis algún problema con la interpretación del resultado del análisis del programa, debeis realizar la consulta en el foro de ayuda:

    http://www.adslzone.net/forum85.html

    Salu2

    0
  50. david 27 dic, 08 19:43

    hola amigos necesito la ayuda de ustedes como ago para consegir un CD LIVE de Linux Bootable para pasarlo en mi laptop que es urgente recuperar mi maquina que se reinicia acada rato por favor responderme lo mas pronto posible y si pudieran mas informacion detallada para solucionar mi problema del reinicio de mi laptop de marca dell con el sistema operativo windows xp

    0
  51. Magi 29 dic, 08 3:57

    Hola ya realize el analisis me dice que el posible problema sea el hardware :S!!! muchas gracias por la ayuda!!

    0
  52. lolo 30 dic, 08 19:40

    Probably caused by : sisgrp.sys ( sisgrp+113d )

    aver ami me pone eso y ya no se q mas hacer ayudaaaa

    0
  53. lolo 30 dic, 08 19:42

    me sale la pantalla azul esa cuando abro el football manager 2009 o frets on fire

    Probably caused by : sisgrp.sys ( sisgrp+113d )

    0
  54. LOST 04 ene, 09 3:33

    Miren lo ke deben aser es buscar ese archivo y eliminarlo

    el archivo se encuentra en esta carpeta:

    C:\WINDOWS\system32\drivers

    hay busquen el archivo y eliminenlo xD

    0
  55. henryalv 04 ene, 09 14:12

    Gracias por el excelente tutorial y por el software que no brindas, michisimas gracias por tu valor altruista en enseñarnos como quitar la terrible pantalla azul (de la muerte) y para la persona que opina que solo los windows piratas traen ese error, le cuento que los windows modificados (Ue) ya traen desactivada la pantalla de la muerte, ji ji . deberia de testear todos los windows antes de dar opiniones absurdas. gracias por tu colaboracion.. saludos

    0
  56. Jose 08 ene, 09 5:42

    hola mi problema es que no se ve nada en la pantalla esta completamente nega, como si la tarjeta de video no mandara señal al monitor, porque la luz se enciende en verde al encender la pc y tres segundo despues se pone amarilla como cuando esta la pc apagada, ya e intentado de todo limpie los slop de las memorias y hasta las mismas memorias las e probado y todas funcionan correctamente tengo 512 en momoria ram, extraje la bateria del boar y lo deje 5 minutos desactivado y lo volvi a poner en su posicion la ensendi y nada, formatie los discos y nada la yompie y nada llegue a la conclusion q la targeta integrada no funciona porque le tengo una pci, pero hace unos años atras me paso lo mismo con una y solo la formatie y se compuso la q me esta dando problemas es una amd sempron(tm) 2200+ el boar es un asrock k7s41gx porq ni en las propiedades en administrador de dispositivos me aparece el adaptador no me pide el driver como si no existiera solo aparece el que le instale la targeta pci de video la integrada no.
    lo que hice despues fue entrar en el setup en una parte donde decia onboard vga algo haci y me decia automatic lo que hice que lo cambie a 32 mb la reinicie y me aparecio entonces el adaptador solo que pidiendo el driver de video, bueno busq el driver de video vga en la pagina asrock lo descarge lo trate de instalar se estaba instalando y me aparece un mensaje diciendo que nececita la ubicacion del archivo sisgrp.sys que es eso no se, pero bueno trate nuevamente de conectar el monitor en la integrada y sigue igual negra la pantalla. vere si descargo el archivo que me pide haber q pasa. y si me puedes ayudar t lo agradeceria mucho. gracias mi correo es ******

    0
  57. mishael mendoza 12 ene, 09 6:36

    BUGCHECK_STR: 0x8E

    LAST_CONTROL_TRANSFER: from bf3b3088 to 0844bb80

    POSSIBLE_INVALID_CONTROL_TRANSFER: from bf3b3083 to bf3e7620

    STACK_TEXT:
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    9c575648 bf3b3088 00000004 e34e25e8 bf3ed0cb 0x844bb80
    9c575654 bf3ed0cb 00000002 9c575ab4 9c5758fc igxpdx32!DrvEnableDirectDraw+0xc56b8
    9c5756e0 8054b6ed 00000000 89000000 8932d008 igxpdx32!DrvEnableDirectDraw+0xff6fb
    9c5756f4 804ff970 ffdff538 805458b4 9c575901 nt!ExFreePoolWithTag+0x40d
    9c5756fc 805458b4 9c575901 9c575720 00000001 nt!KiDeliverApc+0x1e0
    9c57570c 804ef586 00000000 00000000 8932d008 nt!KiUnexpectedInterrupt+0x3a
    9c575720 804f4e35 80000000 8932d048 88578338 nt!IoFreeIrp+0xf6
    9c575774 804ff843 8932d048 9c5757c0 9c57579c nt!IoVolumeDeviceToDosName+0xfbf
    9c5757c4 806e7ef2 00000000 bf63b5dc bf63b5d0 nt!KiDeliverApc+0xb3
    9c57580c b806e9b3 00232210 00000000 00000000 hal!HalClearSoftwareInterrupt+0x342
    9c575828 804f0f34 8932d048 88578338 00000000 VIDEOPRT!VideoPortUnmapMemory+0x16cb
    9c57584c 804fc4e7 8932d048 89320000 bf63da08 nt!IoAllocateErrorLogEntry+0x230
    9c5758a0 b806e9b3 002320ec bf63da08 00000000 nt!KeInsertQueueApc+0x6d
    9c575984 8054b6ed 9c575a08 9c5759d0 89e2b480 VIDEOPRT!VideoPortUnmapMemory+0x16cb
    9c575994 8054b6ed e343d368 e44be348 e3f14018 nt!ExFreePoolWithTag+0x40d
    9c5759d0 bf802a7d bf63da08 00000000 9c570000 nt!ExFreePoolWithTag+0x40d
    9c5759f0 bf2eecfb e44be358 bf3e7c35 e44be358 win32k+0x2a7d
    9c5759f8 bf3e7c35 e44be358 e343d368 bf63b5dc igxpdx32!DrvEnableDirectDraw+0x132b
    9c575ab0 bf3b3f8c e3f14018 e430ea28 00000000 igxpdx32!DrvEnableDirectDraw+0xfa265
    9c575b08 8053617d 9c575b00 e4479f70 00000001 igxpdx32!DrvEnableDirectDraw+0xc65bc
    9c575b30 bf802a7d e4479f30 00000000 9c575b50 nt!ExAcquireResourceExclusiveLite+0x67
    9c575b40 bf85b718 e4479f30 e4479f40 bf36246d win32k+0x2a7d
    9c575b68 bf36411d e1155000 e1155000 0300b048 win32k!EngFreeMem+0x1c
    9c575be4 bf35a67e 0300b044 bf334c02 9c575ce4 igxpdx32!DrvEnableDirectDraw+0x7674d
    9c575bec bf334c02 9c575ce4 e348a898 9c575c68 igxpdx32!DrvEnableDirectDraw+0x6ccae
    9c575c1c ae8f9622 9c575ce4 e391b5e8 00000000 igxpdx32!DrvEnableDirectDraw+0x47232
    9c575c2c bf9618f9 9c575ce4 00000020 00000207 watchdog!WdEnterMonitoredSection+0x10
    00000000 00000000 00000000 00000000 00000000 win32k!XLATEOBJ_hGetColorTransform+0x1a44a

    STACK_COMMAND: .trap 0xffffffff9c5755d8 ; kb

    FOLLOWUP_NAME: MachineOwner

    MODULE_NAME: hardware

    IMAGE_NAME: hardware

    BUCKET_ID: CPU_CALL_ERROR

    Followup: MachineOwner
    ———
    *** Possible invalid call from bf3b3083 ( igxpdx32!DrvEnableDirectDraw+0xc56b3 )
    *** Expected target bf3e7620 ( igxpdx32!DrvEnableDirectDraw+0xf9c50

    pues solo deseo saver k tipi de error es el k tengo y si lo puedo remediar con algun software mas compatinle o cambiando algun copntroladorsi alguien me puede ayudar se lo agradeceria

    0
  58. jawimb 22 ene, 09 18:22

    hola, hice lo que pone, pero cuando fui a abrir el DMP me dijo que no tenia acceso.
    ¿Que debo hacer?

    0
  59. mauricio 09 feb, 09 18:52

    me tira ese error tcpip.sys como lo soluciono grasias

    0
  60. mirnag27 21 feb, 09 23:12

    donde se bajan estos programasn microsoft dubugging tools 32 bit asi como eel otros, luego del analicsis que se hace con el pro problema,? con lo hecho anterior se eliminan los problemas si es el sofware???

    0
  61. acp4 28 feb, 09 17:35

    Hola a todos y gracias por hacer este foro tan interesante y agradezco toda la ayuda que me podais ofrecer, yo he seguido los pasos anteriores y mi problema es el siguiente:

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\WINDOWS\Minidump\Mini022809-70.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 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) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x80554040
    Debug session time: Sat Feb 28 08:06:48.718 2009 (GMT+1)
    System Uptime: 0 days 0:06:03.296
    *********************************************************************
    * 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 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
    ……….
    Unable to load image NVTcp.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for NVTcp.sys
    *** ERROR: Module load completed but symbols could not be loaded for NVTcp.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 100000D1, {38, 2, 1, b29caab6}

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

    *** WARNING: Unable to verify timestamp for usbohci.sys
    *** ERROR: Module load completed but symbols could not be loaded for usbohci.sys
    *************************************************************************
    *** ***
    *** ***
    *** 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : NVTcp.sys ( NVTcp+2ab6 )

    Followup: MachineOwner
    ———

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

    DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If kernel debugger is available get stack backtrace.
    Arguments:
    Arg1: 00000038, memory referenced
    Arg2: 00000002, IRQL
    Arg3: 00000001, value 0 = read operation, 1 = write operation
    Arg4: b29caab6, address which referenced memory

    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 ***
    *** ***
    *************************************************************************
    *********************************************************************
    * 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************

    MODULE_NAME: NVTcp

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 4253b85b

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    00000038

    CURRENT_IRQL: 2

    FAULTING_IP:
    NVTcp+2ab6
    b29caab6 8702 xchg eax,dword ptr [edx]

    CUSTOMER_CRASH_COUNT: 70

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0xD1

    LAST_CONTROL_TRANSFER: from b29d4131 to b29caab6

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    80549ad4 b29d4131 86c60720 85b129f4 863b60e2 NVTcp+0x2ab6
    80549b24 b29d5258 864147c0 80549b48 863b60ce NVTcp+0xc131
    80549b4c b29d65f8 86cb5d00 00000014 80549c54 NVTcp+0xd258
    80549b68 b29d02c7 86cb5d00 864147c0 86414720 NVTcp+0xe5f8
    80549bc8 870aa0e8 f782e490 00000206 804fa043 NVTcp+0x82c7
    80549bcc f782e490 00000206 804fa043 86db2778 0x870aa0e8
    80549bd0 00000000 804fa043 86db2778 86834008 usbohci+0x3490

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    NVTcp+2ab6
    b29caab6 8702 xchg eax,dword ptr [edx]

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: NVTcp+2ab6

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: NVTcp.sys

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner

    0
  62. ema92 02 mar, 09 17:41

    hola…tengo el vista ultimate x64…al instalar el programita este para la version de 64 bit me dice “el paquete de instalacion no es compatible con este procesador”…a varios q dejaron comentarios mas arriba le paso lo mismo…tengo un atlhon x2 al igual q ellos y a ninguno nos anda…¿que debemos hacer?

    0
  63. Luky 05 mar, 09 17:22

    hola exelente post… muy buena información y detalle de la solucion a este inconveniente… pero mi problema con esta bendita pantalla azul es que sale cuando inicio la laptop… y cuando esta arrancando el windows Xp…en la parte q sale el logo de MIcrosoft ..aparece el pantallazo alzul y se queda pegada…no me permite arrancar unCD Booteable nose q hacer… como comentario, les cuento q tengo mas de 4 años de experiencia en reparacion de PCs pero la reparacion de las laptops son nuevas para mi… la laptop es una DELL Pentium M de 1 GB de ram HD de 80GB con Xp Profesional Original..

    Muchas gracias por su atencion

    salu2

    0
  64. kevin 05 mar, 09 19:45

    MODULE_NAME: nt

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 48a4023c

    BUGCHECK_STR: 0x1a_41284

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    LAST_CONTROL_TRANSFER: from 80524df8 to 8053356e

    STACK_TEXT:
    WARNING: Stack unwind information not available. Following frames may be wrong.
    efdacb58 80524df8 0000001a 00041284 0333a001 nt+0x5c56e
    efdacb90 804ead87 00002831 0333a000 c0300030 nt+0x4ddf8
    efdacbc0 804eb07e c000cce8 0333a000 00000000 nt+0x13d87
    efdacc84 804eb174 000005e8 036bbfff 00000000 nt+0x1407e
    efdacca0 80568b1e 031c0000 036bbfff efdacd64 nt+0x14174
    efdacd4c 804de7ec ffffffff 006ffc5c 006ffc74 nt+0x91b1e
    efdacd64 7c91eb94 badb0d00 006ffba0 f065fd98 nt+0x77ec
    efdacd68 badb0d00 006ffba0 f065fd98 f065fdcc 0x7c91eb94
    efdacd6c 006ffba0 f065fd98 f065fdcc 00000000 0xbadb0d00
    efdacd70 f065fd98 f065fdcc 00000000 00000000 0x6ffba0
    efdacd74 f065fdcc 00000000 00000000 00000000 0xf065fd98
    efdacd78 00000000 00000000 00000000 00000000 0xf065fdcc

    STACK_COMMAND: kb

    FOLLOWUP_IP:
    nt+5c56e
    8053356e 5d pop ebp

    SYMBOL_STACK_INDEX: 0

    SYMBOL_NAME: nt+5c56e

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ntoskrnl.exe

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
    ———

    esto es lo que me salio ahora que hago

    0
  65. abe 09 mar, 09 23:09

    yo tengo el mismo prblema y sigo tus pasos pero no me sale en el minidum el archivo 050908-01dmp lo mas parecido es el 051908-01dmp me podias decir por que no lo tengo.
    hace tiempo que me sale la pantalla azul cuando trabajo con el ordenador un rato al monento sale el pantallazo azul. si estoy en internet pantallazo con mis programas pantallazo solo si no hace nada no sale. necesito ayuda. como la tuya que esta bien esplicada ya que soy novata

    0
  66. abe 12 mar, 09 23:16

    me sale siempre la pantalla azul desde hace tiempo cuando llevo un ratito trabajando o jugando he hecho lo que de3cias
    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\WINDOWS\Minidump\Mini031209-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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Wed Mar 11 22:56:42.547 2009 (GMT+1)
    System Uptime: 0 days 3:11:53.382
    *********************************************************************
    * 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ……………………………………………………………………………………………………………………
    Loading User Symbols
    Loading unloaded module list
    …………………………………..
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 7F, {d, 0, 0, 0}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** 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 ***
    *** ***
    *************************************************************************
    *********************************************************************
    * 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : ntkrnlpa.exe ( nt+6de7b )

    Followup: MachineOwner
    ———

    1: kd> !analyze-v
    No export analyze-v found
    y me sale la siguente pantalla decirme que significa todo esto es otro nº del que me decias pero en la informacion esa que sale para enviar a microsof me salia este archivo solo cambia un nº. por fa ayudarme

    0
  67. Andrea 13 mar, 09 21:39

    Hola! a mi me salio

    Probably caused by : NETIO.SYS ( NETIO+16516 )

    Q hago porfa!??

    0
  68. abe 14 mar, 09 20:11

    POR FAVOR DIME QUE DEBO HACER TE MANDE LO QUE ME SALE

    TENGO QUE ARREGLARLO DE ALGUNA MANERA

    0
  69. Leandro 14 mar, 09 20:53

    Hola! a mi me salio eso, por favor si alguien sabe como solucionarme aviseme
    muchas gracias!

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\WINDOWS\Minidump\Mini030509-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 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) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055b1c0
    Debug session time: Thu Mar 5 21:38:31.109 2009 (GMT-3)
    System Uptime: 0 days 1:00:47.726
    *********************************************************************
    * 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 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
    …………
    Unable to load image afd.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for afd.sys
    *** ERROR: Module load completed but symbols could not be loaded for afd.sys
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 1000000A, {166, 2, 0, 804e5433}

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

    *** WARNING: Unable to verify timestamp for avgtdix.sys
    *** ERROR: Module load completed but symbols could not be loaded for avgtdix.sys
    *** WARNING: Unable to verify timestamp for tcpip.sys
    *** ERROR: Module load completed but symbols could not be loaded for tcpip.sys
    *** WARNING: Unable to verify timestamp for wanarp.sys
    *** ERROR: Module load completed but symbols could not be loaded for wanarp.sys
    *** WARNING: Unable to verify timestamp for NDIS.sys
    *** ERROR: Module load completed but symbols could not be loaded for NDIS.sys
    *** WARNING: Unable to verify timestamp for psched.sys
    *** ERROR: Module load completed but symbols could not be loaded for psched.sys
    *** WARNING: Unable to verify timestamp for ndiswan.sys
    *** ERROR: Module load completed but symbols could not be loaded for ndiswan.sys
    *** WARNING: Unable to verify timestamp for adiusbaw.sys
    *** ERROR: Module load completed but symbols could not be loaded for adiusbaw.sys
    *** WARNING: Unable to verify timestamp for USBPORT.SYS
    *** ERROR: Module load completed but symbols could not be loaded for USBPORT.SYS
    *************************************************************************
    *** ***
    *** ***
    *** 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : avgtdix.sys ( avgtdix+1cb1 )

    Followup: MachineOwner

    0
  70. ABE 21 mar, 09 21:30

    me puede contestar alguien en este foro por favor di mi resultado y nadie me contesta

    0
  71. Jorge 09 abr, 09 4:40

    Hola! a mi me sale que el problema está en el archivo NETIO.SYS
    Lo elimine pero despues no me arranca windows
    Diganme que debo hacer por favor??

    0
  72. checho51 13 abr, 09 8:27

    me sale esto espero puedan ayudarme

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\Windows\Minidump\Mini041309-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 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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x81c3f000 PsLoadedModuleList = 0x81d56c70
    Debug session time: Mon Apr 13 01:16:57.474 2009 (GMT-5)
    System Uptime: 0 days 0:19:13.513
    *********************************************************************
    * 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 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 19, {20, a8d3a440, a8d3a450, a020288}

    *** WARNING: Unable to verify timestamp for PCTCore.sys
    *** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
    ***** 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!PVOID ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : PCTCore.sys ( PCTCore+19c1f )

    Followup: MachineOwner
    ———

    ya busque por muchos lados eso de pctcore.sys y segun que puede ser problemas del los drivers de video, los actualize a lo mas nuevo y nada =( ayuda no puedo usar mi programa favorito para hacer PCBs =(

    0
  73. checho51 13 abr, 09 8:28

    Probably caused by : PCTCore.sys ( PCTCore+19c1f )

    no se como arreglarlo ya busque en internet y ninguna solucion me a funcionado

    0
  74. checho51 14 abr, 09 3:26

    me sale esto alguien me puede ayudar??

    Loading Dump File [C:\Windows\Minidump\Mini041309-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 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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0x81c3f000 PsLoadedModuleList = 0x81d56c70
    Debug session time: Mon Apr 13 01:16:57.474 2009 (GMT-5)
    System Uptime: 0 days 0:19:13.513
    *********************************************************************
    * 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 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 19, {20, a8d3a440, a8d3a450, a020288}

    *** WARNING: Unable to verify timestamp for PCTCore.sys
    *** ERROR: Module load completed but symbols could not be loaded for PCTCore.sys
    ***** 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!PVOID ***
    *** ***
    *************************************************************************
    *************************************************************************
    *** ***
    *** ***
    *** 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : PCTCore.sys ( PCTCore+19c1f )

    Followup: MachineOwner
    ———

    0
  75. Rubene 19 abr, 09 23:28

    Hola, mi problema es q tengo un Toshiba Satellite A200 22-c venia con el windows vista y le cambie al Xp Professional 32b baje los drivers necesarios de la web oficial, etc etc… hasta ahi todo bien incluso despues de instalar todo lo necesario para su funcionamiento con windows XP. El problema es cuando intento entrar a juegos como lineage 2 o warrock, es ahi cuando me salta el maldito pantallazo azul y se reinicia el pc. Todas las actualizaciones de la grafica q e intentado buscar me dice aunk sean actualizaciones para la grafica del portatil me dice q el SO o el _Hardware no es el correcto y no puedo intentar actualizar de drivers ni nada.

    0
  76. Chechi 27 abr, 09 14:43

    Hola primero decirte grasias que es un gran aporte y segundo en el error que me sale es este:
    Probably caused by : ntoskrnl.exe ( nt+74f0f )
    uhm no se que puede ser lei en el inter que es una archivo importante y que puede haber sido modificado por algun virus … la verdad quisiera saber que se puede hacer graxias de antemano

    0
  77. campeon 28 abr, 09 20:46

    una pregunta en la computadora que tengo es una pc chips.. y sale la pantalla de azul tengo que correr todos los archivos mencionados… en esta pagina…
    o cual me recomiendan para bajarlo y hacerlo conforme al procedimiento que indican… y para que no salga la pantalla azul…

    0
  78. oscar sandoval 06 may, 09 0:50

    en la pantalla azul me sale 0x0000000A(0X000000E8,0X00000002,0X00000001,0X80702A16) QUE PUEDO HACER GRACIAS

    0
  79. neilrolando@hotmail.com 11 may, 09 1:42

    hola amigo, probé conlos 4 archivos minidump que estan alojados en la carpeta windows y me salen los siguientes probables
    errores :
    1.- win32k.sys( win32k+e2098 )

    2.-Probably caused by : hardware ( win32k+14143 )

    Followup: MachineOwner

    3.- Probably caused by : ntoskrnl.exe ( nt+7f76 )

    Followup: MachineOwner
    4.- Probably caused by : nv4_disp.dll ( nv4_disp+2a23 )

    Followup: MachineOwner
    5.- Probably caused by : nv4_disp.dll ( nv4_disp+2853f )

    Followup: MachineOwner

    como uds saben existen varios archivos minidump conmnumeros diferentes y probe con todo

    0
  80. neilrolando@hotmail.com 11 may, 09 1:45

    por favor respondanme al correo q tiene mi nombre de usuario

    hola amigo, probé conlos 4 archivos minidump que estan alojados en la carpeta windows y me salen los siguientes probables
    errores :
    1.- win32k.sys( win32k+e2098 )

    2.-Probably caused by : hardware ( win32k+14143 )

    Followup: MachineOwner

    3.- Probably caused by : ntoskrnl.exe ( nt+7f76 )

    Followup: MachineOwner
    4.- Probably caused by : nv4_disp.dll ( nv4_disp+2a23 )

    Followup: MachineOwner
    5.- Probably caused by : nv4_disp.dll ( nv4_disp+2853f )

    Followup: MachineOwner

    como uds saben existen varios archivos minidump conmnumeros diferentes y probe con todo

    0
  81. rayoni 22 may, 09 11:10

    muy bueno,pero si te dá el pantallazo azul,se supone que no puedes llegar al escritorio,y sinó llegas al escritorio,¿cómo bajas el programa?,
    saludos

    0
  82. diego 24 may, 09 13:22

    como hago para saber si tengo el sistema X86 32Bits o si tengo el sistema 64Bi?

    0
  83. carlos 27 may, 09 6:30

    Mira #89 diego

    Para saber que edición de sistema tienes, sólo haz lo siguiente:

    dirigete a tu escritorio o en dónde estes situado dentro del sistema.

    ahora:

    0.5.- Primero debes saber que sistema tienes; XP ó Windows Vista (los mas recientes) salvo windows 7 verdad?
    1.- Presiona sin soltar las teclas windows + pausa
    2.- ahora lee con atención lo que te muestra 32 ó 64 bit´s ( x86 ó x64)
    3.- disculpame, no recuerdo como averiguarlo para XP, pero lo anterior te servirá para Windows Vista ( cualquier Versión de 32 bits o 64 bit´s)
    Saludos…

    0
  84. emiliano 29 may, 09 7:54

    tengo este problema cuando voy a jugar fifa 08. solamente cuando quiero jugar despues anda bien. que podra ser??? gracias

    0
  85. Manuel 01 jun, 09 0:46

    Microsoft (R) Windows Debugger Version 6.9.0003.113 X86
    Copyright (c) Microsoft Corporation. All rights reserved.

    Loading Dump File [C:\WINDOWS\Minidump\Mini060109-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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
    Product: WinNt
    Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
    Debug session time: Sun May 31 17:59:32.312 2009 (GMT+2)
    System Uptime: 1 days 19:05:33.047
    *********************************************************************
    * 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntkrnlpa.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
    Loading Kernel Symbols
    ……………………………………………………………………………………………………………….
    Loading User Symbols
    Loading unloaded module list
    …………………………..
    *******************************************************************************
    * *
    * Bugcheck Analysis *
    * *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck A, {16, 1c, 0, 804fa276}

    *** WARNING: Unable to verify timestamp for mssmbios.sys
    *** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
    ***** 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 ***
    *** ***
    *************************************************************************
    *********************************************************************
    * 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : ntkrnlpa.exe ( nt+23276 )

    Followup: MachineOwner
    ———

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

    IRQL_NOT_LESS_OR_EQUAL (a)
    An attempt was made to access a pageable (or completely invalid) address at an
    interrupt request level (IRQL) that is too high. This is usually
    caused by drivers using improper addresses.
    If a kernel debugger is available get the stack backtrace.
    Arguments:
    Arg1: 00000016, memory referenced
    Arg2: 0000001c, IRQL
    Arg3: 00000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
    Arg4: 804fa276, address which referenced memory

    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 ***
    *** ***
    *************************************************************************
    *********************************************************************
    * 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************

    MODULE_NAME: nt

    FAULTING_MODULE: 804d7000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 498c11d3

    READ_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    00000016

    CURRENT_IRQL: 1c

    FAULTING_IP:
    nt+23276
    804fa276 ?? ???

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0xA

    LAST_CONTROL_TRANSFER: from 00000000 to 805446f0

    STACK_TEXT:
    bada7c08 00000000 00000016 0000001c 00000000 nt+0x6d6f0

    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_IP:
    nt+23276
    804fa276 ?? ???

    SYMBOL_NAME: nt+23276

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: ntkrnlpa.exe

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
    ———

    0
  86. khasgar 01 jun, 09 17:57

    me sale esto Probably caused by : s3gcil_inv.dll ( s3gcil_inv+102ecd ) q significa????

    0
  87. juan 05 jun, 09 7:10

    quitar windows .exe ya que no medeja emtrar en messenger.exe-could not loadon not lohad on non.windows nt systen

    0
  88. pakko 05 jun, 09 21:16

    hola que tal………………
    ps ize todos los pasos tal y como me los planteaste

    Y ME SALE:
    Probably caused by : ntoskrnl.exe ( nt+96b30 )

    que ago lo elimino o que??????????????????
    me podias ayudar……..
    por favor

    mi correo es: zimik_mr@hotmail.com

    0
  89. COUNTER 1.6 MI IP zoomgaming.servegame.com:27016 21 jun, 09 15:04

    hola gente buenA!

    bueno yo segui todos los pasos de del tutorian pero cuando kiero abrir el archivo Mini062109-01.dmp no lo abre y me dice que
    [Notiene permiso par abrir este archivo]
    solicite permiso al propietario del archivo o a un administrador

    eso es lo q me dice cuando lo kiero abrir eso mismo me aparece en un cuadrito! q ago alguno me daria la solucion ! gracias !

    0
    1. Hugo Gómez 21 jun, 09 18:31

      Plantea tu problema en nuestros foros, que seguro que entre todos encontramos una solución

      Saludos

      Hugo

      0
  90. marco 30 jun, 09 7:45

    hola ,bueno de antemano gracias por la informacion es muy interesante ,pero acabo de bajar el programa 64 bits pero mi pc dice que este equipo no esta en condiciones para realizar este programa .
    mi equipo es un olidata amd athlon x2 64.porfavoe me pueden ayudar. gracias .

    0
  91. anonimo 14 jul, 09 18:01

    me sale q el problema es un hardware ahi como hago?

    0
  92. papixulo 16 jul, 09 20:47

    Esto funciona en Windows vista tambien??

    0
  93. Angelo 23 jul, 09 6:49

    oigan por favorr kien me ayudaaaa me tiene arto esta pantalla azul

    Probably caused by : pci.sys ( pci+ae0 )

    eso fue lo q consegui ahora que hago?

    lo elimino?, si lo tengo que eliminar en q parte esta???

    Respondannn plis gracias!!!! <:(

    0
  94. florwerd 28 jul, 09 17:56

    usen linux, no sean degenerados utilizando esa mierda toda la vida!… tengo un pantallazo azul en mi computadora vieja hace 4 años ni el servicio técnico la pudo arreglar sin formateear de nuevo el disco duro

    0
  95. pavli 02 ago, 09 1:33

    a mi no me aparece la carpeta minidump. puede ser que este en otro lado? o con otro nombre?

    0
  96. alberto 19 ago, 09 4:10

    hey.. a mi me tiro el pantallazo azul durante la instalacion de windows.. especificamente cuando estaba instalando
    componentes… alguien me puede decir que significa esto?? al parecer es problema de hardware.. comenten pliz

    0
  97. poter 20 ago, 09 3:30

    hola ami me sale lo sigiente espero me digas cual es la solucion x q no encuentro la solucion
    por favor x favor contesta ahi sta mi correo

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

    Loading Dump File [C:\Windows\Minidump\Mini081909-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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\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 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Kernel base = 0xfffff800`0184e000 PsLoadedModuleList = 0xfffff800`01a13db0
    Debug session time: Wed Aug 19 09:39:58.762 2009 (GMT-6)
    System Uptime: 0 days 0:27:44.184
    *********************************************************************
    * 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Unable to load image \SystemRoot\system32\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 50, {fffff8800bf9d028, 1, fffffa60010b2538, 0}

    Unable to load image \SystemRoot\System32\Drivers\Ntfs.sys, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Ntfs.sys
    *** ERROR: Module load completed but symbols could not be loaded for Ntfs.sys
    ***** 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 ***
    *** ***
    *************************************************************************
    Probably caused by : Ntfs.sys ( Ntfs+ad538 )

    Followup: MachineOwner
    ———

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

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced. This cannot be protected by try-except,
    it must be protected by a Probe. Typically the address is just plain bad or it
    is pointing at freed memory.
    Arguments:
    Arg1: fffff8800bf9d028, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffffa60010b2538, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000000, (reserved)

    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 ***
    *** ***
    *************************************************************************

    MODULE_NAME: Ntfs

    FAULTING_MODULE: fffff8000184e000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP: 479190d1

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
    unable to get nt!MmSpecialPoolEnd
    unable to get nt!MmPoolCodeStart
    unable to get nt!MmPoolCodeEnd
    fffff8800bf9d028

    FAULTING_IP:
    Ntfs+ad538
    fffffa60`010b2538 ?? ???

    MM_INTERNAL_CODE: 0

    CUSTOMER_CRASH_COUNT: 1

    DEFAULT_BUCKET_ID: WRONG_SYMBOLS

    BUGCHECK_STR: 0x50

    LAST_CONTROL_TRANSFER: from fffff800018b2371 to fffff800018a3390

    STACK_TEXT:
    fffffa60`017bd208 fffff800`018b2371 : 00000000`00000050 fffff880`0bf9d028 00000000`00000001 fffffa60`017bd300 : nt+0x55390
    fffffa60`017bd210 00000000`00000050 : fffff880`0bf9d028 00000000`00000001 fffffa60`017bd300 00000000`00000000 : nt+0x64371
    fffffa60`017bd218 fffff880`0bf9d028 : 00000000`00000001 fffffa60`017bd300 00000000`00000000 00000000`00000000 : 0x50
    fffffa60`017bd220 00000000`00000001 : fffffa60`017bd300 00000000`00000000 00000000`00000000 fffffa80`066dfca0 : 0xfffff880`0bf9d028
    fffffa60`017bd228 fffffa60`017bd300 : 00000000`00000000 00000000`00000000 fffffa80`066dfca0 fffff800`019c7b00 : 0x1
    fffffa60`017bd230 00000000`00000000 : 00000000`00000000 fffffa80`066dfca0 fffff800`019c7b00 fffffa60`017bd300 : 0xfffffa60`017bd300
    fffffa60`017bd238 00000000`00000000 : fffffa80`066dfca0 fffff800`019c7b00 fffffa60`017bd300 fffffa80`05a43900 : 0x0
    fffffa60`017bd240 fffffa80`066dfca0 : fffff800`019c7b00 fffffa60`017bd300 fffffa80`05a43900 00000000`000001f1 : 0x0
    fffffa60`017bd248 fffff800`019c7b00 : fffffa60`017bd300 fffffa80`05a43900 00000000`000001f1 00000000`00000000 : 0xfffffa80`066dfca0
    fffffa60`017bd250 fffffa60`017bd300 : fffffa80`05a43900 00000000`000001f1 00000000`00000000 00000000`00000000 : nt+0x179b00
    fffffa60`017bd258 fffffa80`05a43900 : 00000000`000001f1 00000000`00000000 00000000`00000000 fffff6fb`7e2002f8 : 0xfffffa60`017bd300
    fffffa60`017bd260 00000000`000001f1 : 00000000`00000000 00000000`00000000 fffff6fb`7e2002f8 00000000`00000000 : 0xfffffa80`05a43900
    fffffa60`017bd268 00000000`00000000 : 00000000`00000000 fffff6fb`7e2002f8 00000000`00000000 fffff6fb`7dbf1000 : 0x1f1
    fffffa60`017bd270 00000000`00000000 : fffff6fb`7e2002f8 00000000`00000000 fffff6fb`7dbf1000 00000000`00000000 : 0x0
    fffffa60`017bd278 fffff6fb`7e2002f8 : 00000000`00000000 fffff6fb`7dbf1000 00000000`00000000 fffff6fc`4005fce8 : 0x0
    fffffa60`017bd280 00000000`00000000 : fffff6fb`7dbf1000 00000000`00000000 fffff6fc`4005fce8 000071f8`00000000 : 0xfffff6fb`7e2002f8
    fffffa60`017bd288 fffff6fb`7dbf1000 : 00000000`00000000 fffff6fc`4005fce8 000071f8`00000000 00000980`00000000 : 0x0
    fffffa60`017bd290 00000000`00000000 : fffff6fc`4005fce8 000071f8`00000000 00000980`00000000 0000007f`fffffff8 : 0xfffff6fb`7dbf1000
    fffffa60`017bd298 fffff6fc`4005fce8 : 000071f8`00000000 00000980`00000000 0000007f`fffffff8 ffffff80`0bf9d028 : 0x0
    fffffa60`017bd2a0 000071f8`00000000 : 00000980`00000000 0000007f`fffffff8 ffffff80`0bf9d028 00000000`00000001 : 0xfffff6fc`4005fce8
    fffffa60`017bd2a8 00000980`00000000 : 0000007f`fffffff8 ffffff80`0bf9d028 00000000`00000001 fffff880`001a4b30 : 0x71f8`00000000
    fffffa60`017bd2b0 0000007f`fffffff8 : ffffff80`0bf9d028 00000000`00000001 fffff880`001a4b30 00000000`00000121 : 0x980`00000000
    fffffa60`017bd2b8 ffffff80`0bf9d028 : 00000000`00000001 fffff880`001a4b30 00000000`00000121 00000000`000e4b69 : 0x7f`fffffff8
    fffffa60`017bd2c0 00000000`00000001 : fffff880`001a4b30 00000000`00000121 00000000`000e4b69 fffffa80`05a46c08 : 0xffffff80`0bf9d028
    fffffa60`017bd2c8 fffff880`001a4b30 : 00000000`00000121 00000000`000e4b69 fffffa80`05a46c08 00000000`000e4b69 : 0x1
    fffffa60`017bd2d0 00000000`00000121 : 00000000`000e4b69 fffffa80`05a46c08 00000000`000e4b69 fffffa60`017bd380 : 0xfffff880`001a4b30
    fffffa60`017bd2d8 00000000`000e4b69 : fffffa80`05a46c08 00000000`000e4b69 fffffa60`017bd380 fffff800`018a1f19 : 0x121
    fffffa60`017bd2e0 fffffa80`05a46c08 : 00000000`000e4b69 fffffa60`017bd380 fffff800`018a1f19 00000000`00000001 : 0xe4b69
    fffffa60`017bd2e8 00000000`000e4b69 : fffffa60`017bd380 fffff800`018a1f19 00000000`00000001 00000000`00000000 : 0xfffffa80`05a46c08
    fffffa60`017bd2f0 fffffa60`017bd380 : fffff800`018a1f19 00000000`00000001 00000000`00000000 00000000`00000000 : 0xe4b69
    fffffa60`017bd2f8 fffff800`018a1f19 : 00000000`00000001 00000000`00000000 00000000`00000000 fffffa80`05a46c08 : 0xfffffa60`017bd380
    fffffa60`017bd300 00000000`00000001 : 00000000`00000000 00000000`00000000 fffffa80`05a46c08 00000000`00000000 : nt+0x53f19
    fffffa60`017bd308 00000000`00000000 : 00000000`00000000 fffffa80`05a46c08 00000000`00000000 00001f80`01010000 : 0x1
    fffffa60`017bd310 00000000`00000000 : fffffa80`05a46c08 00000000`00000000 00001f80`01010000 fffff880`0bf7c000 : 0x0
    fffffa60`017bd318 fffffa80`05a46c08 : 00000000`00000000 00001f80`01010000 fffff880`0bf7c000 00000000`00001601 : 0x0
    fffffa60`017bd320 00000000`00000000 : 00001f80`01010000 fffff880`0bf7c000 00000000`00001601 00000000`00004203 : 0xfffffa80`05a46c08
    fffffa60`017bd328 00001f80`01010000 : fffff880`0bf7c000 00000000`00001601 00000000`00004203 00000000`00000000 : 0x0
    fffffa60`017bd330 fffff880`0bf7c000 : 00000000`00001601 00000000`00004203 00000000`00000000 00000000`00000000 : 0x1f80`01010000
    fffffa60`017bd338 00000000`00001601 : 00000000`00004203 00000000`00000000 00000000`00000000 090308ff`08ec0900 : 0xfffff880`0bf7c000
    fffffa60`017bd340 00000000`00004203 : 00000000`00000000 00000000`00000000 090308ff`08ec0900 00000000`00000c4c : 0x1601
    fffffa60`017bd348 00000000`00000000 : 00000000`00000000 090308ff`08ec0900 00000000`00000c4c 00000000`00000000 : 0x4203
    fffffa60`017bd350 00000000`00000000 : 090308ff`08ec0900 00000000`00000c4c 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd358 090308ff`08ec0900 : 00000000`00000c4c 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd360 00000000`00000c4c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x90308ff`08ec0900
    fffffa60`017bd368 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xc4c
    fffffa60`017bd370 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd378 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd380 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd388 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd390 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd398 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd3a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd3a8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd3b0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff880`0bf9d028 : 0x0
    fffffa60`017bd3b8 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff880`0bf9d028 00000000`00000000 : 0x0
    fffffa60`017bd3c0 00000000`00000000 : 00000000`00000000 fffff880`0bf9d028 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd3c8 00000000`00000000 : fffff880`0bf9d028 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd3d0 fffff880`0bf9d028 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
    fffffa60`017bd3d8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff880`0bf9d028
    fffffa60`017bd3e0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`000e4b69 : 0x0
    fffffa60`017bd3e8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`000e4b69 00000000`000e4b69 : 0x0
    fffffa60`017bd3f0 00000000`00000000 : 00000000`00000000 00000000`000e4b69 00000000`000e4b69 fffffa80`05a46c08 : 0x0
    fffffa60`017bd3f8 00000000`00000000 : 00000000`000e4b69 00000000`000e4b69 fffffa80`05a46c08 00000000`00000001 : 0x0
    fffffa60`017bd400 00000000`000e4b69 : 00000000`000e4b69 fffffa80`05a46c08 00000000`00000001 fffffa80`05a46180 : 0x0
    fffffa60`017bd408 00000000`000e4b69 : fffffa80`05a46c08 00000000`00000001 fffffa80`05a46180 00000000`00000001 : 0xe4b69
    fffffa60`017bd410 fffffa80`05a46c08 : 00000000`00000001 fffffa80`05a46180 00000000`00000001 fffffa80`05a46c08 : 0xe4b69
    fffffa60`017bd418 00000000`00000001 : fffffa80`05a46180 00000000`00000001 fffffa80`05a46c08 fffffa60`010b2746 : 0xfffffa80`05a46c08
    fffffa60`017bd420 fffffa80`05a46180 : 00000000`00000001 fffffa80`05a46c08 fffffa60`010b2746 fffffa80`05a46180 : 0x1
    fffffa60`017bd428 00000000`00000001 : fffffa80`05a46c08 fffffa60`010b2746 fffffa80`05a46180 00000000`000e4b69 : 0xfffffa80`05a46180
    fffffa60`017bd430 fffffa80`05a46c08 : fffffa60`010b2746 fffffa80`05a46180 00000000`000e4b69 fffffa60`017bd498 : 0x1
    fffffa60`017bd438 fffffa60`010b2746 : fffffa80`05a46180 00000000`000e4b69 fffffa60`017bd498 00000000`00000971 : 0xfffffa80`05a46c08
    fffffa60`017bd440 fffffa80`05a46180 : 00000000`000e4b69 fffffa60`017bd498 00000000`00000971 00000000`00000002 : Ntfs+0xad746
    fffffa60`017bd448 00000000`000e4b69 : fffffa60`017bd498 00000000`00000971 00000000`00000002 fffffa60`010b2538 : 0xfffffa80`05a46180
    fffffa60`017bd450 fffffa60`017bd498 : 00000000`00000971 00000000`00000002 fffffa60`010b2538 00000000`00000010 : 0xe4b69
    fffffa60`017bd458 00000000`00000971 : 00000000`00000002 fffffa60`010b2538 00000000`00000010 00000000`00010202 : 0xfffffa60`017bd498

    STACK_COMMAND: .bugcheck ; kb

    FOLLOWUP_IP:
    Ntfs+ad538
    fffffa60`010b2538 ?? ???

    FOLLOWUP_NAME: MachineOwner

    IMAGE_NAME: Ntfs.sys

    SYMBOL_NAME: Ntfs+ad538

    BUCKET_ID: WRONG_SYMBOLS

    Followup: MachineOwner
    ———

    0
  98. guaimarock 21 ago, 09 2:41

    hola amigo tengo un problema mi windows no tiene carpeta Minidump que hago en ese caso

    0
  99. centurion12 31 ago, 09 12:18

    #106 guaimarock
    Si en tu caso no tiene Minidump suele ser error de volumen

    Haz una reparación

    Inicio/ejecutar/cmd

    chkdsk /r y pulsa ENTER

    Te dirá que al reiniciar se hará la comprobación/reparación
    S/N Pulsa S y enter

    Al reiniciar empezará y tardará dependiendo del tamaño del disco..

    Saludos..

    0
  100. KARLA 10 sep, 09 4:10

    COMO SE SI ES O NO DE HARDWARE????

    0
  101. clonica39 10 sep, 09 18:40

    Hola, a mi tb me sale la dixosa pantallita azul; dice q el error es de un driver equol o algo asi, no entiendo muxo de ordenadores. Mi PC tiene windows xp professional, si me podeis ayudar os lo agradezco, un saludo.

    0
  102. ¬¬ 10 sep, 09 19:55

    mi problema es de este archivo igxpdx32.dll.. por ahi man dicho que se deve descargar otro archivo y remplasar pero nose si hacerlo I.I

    0
  103. RICARDO 11 sep, 09 6:43

    Holaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa…mannnnnnnnnnn…ayudaaaaaaaaaaaaaaa…xfavor..no puedo instalar…esta en ingles..i me sale tres opciones..i no se que hacer me pide..el numero de una tarjeta …osea..no es gratis el programa?????????? vd???’ xfavor..necesito tu respuestaaaaaaa…!!prontooooooooo..

    0
  104. lucas 11 sep, 09 17:40

    amigo necesito ayuda no me aparece el la carpetaminidump en windows donde tengo ke buscarla ??? o por que no aparecE?:s.

    0
  105. Zaratustra 25 sep, 09 21:47

    Bueno y como madres voy a acceder a todas las opciones que se comentan si se supone que no puedo entrar al Windows

    0
  106. bau 10 oct, 09 5:05

    la puta madre
    como ases para lo primer cuadro q t aparece a mi no me sale la concha

    0
  107. Víctor 01 nov, 09 15:19

    Probably caused by : win32k.sys ( win32k!EngEraseSurface+2737 )

    Bueno la frase lo dice todo
    causado por el win32k ese d mierda jajaj

    nose lo que es me podriais ayudar?

    e buscado y no encuentro el archivo

    0
  108. Edgar 04 nov, 09 9:56

    gracias amigo mi error era sobre esto
    * 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 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 argument when starting the debugger. *
    * using .sympath and .sympath+ *
    *********************************************************************
    Probably caused by : Thpevm.SYS ( Thpevm+8e2 )

    Followup: MachineOwner

    pero en realidad es un software malicioso que segun proteje tu disco duro grax amigo te debo la vida

    0
  109. oscar 07 nov, 09 22:18

    gracias muy importante este tutorial reitero muchas gracias

    0
  110. ale 09 nov, 09 18:17

    HOla despues de que apreto aceptar cuando saco la opcion de reiniciar automaticamente en el segundo paso, me salta un cartel q dice q no se puede o algo asi..sigo los pasos y o pasa nada no me da las opiciones del cuadro:, dice: windows no puede enviar alertas administrativas ecepto q se este ejecutando el servicio de alerta, agradeceria un monton q me ayurdaran ya q hace un año q tng eñl problema de la pantalla azul y ya no se q hacer. gracias !!!!!!!!!!!!

    0