none
pantallazos azules continuos y aleatorios en mi pc al instalar windows 7

    Question

  • desde hace ya mucho tiempo he tenido problemas al instalar windows 7 puesto que cuando lo hago de un momento a otro me aparecen pantallazos azules y no se que los causan.

    he intentado de todo ... primero pensé que era la tarjeta gráfica y la cambie, pero este no era el problema, luego fue el disco duro, cambie mi modesto disco duro de 80 Gb por uno de 500 Gb pero esto no soluciono el problema, luego intente cun el prosesador , la ram y la placa base y la fuente de poder , pero ninguno me soluciono el problema....

    ya no se que mas hacer ... formateo en limpio y aun así me aparecen los pantallazos azules, he cambiado hardware como loco y eso no ha solucionado el problema , pero lo que ha cambiado son los mesajes de las pantallas azules ... ahora solo me aparecen 2 mensajes :

     

     page fault in nonpage area y memory managament pero en ocaciones no hay un titulo como estos en la pantalla azul

    me he descargado el Debugging Tools for Windows (x86) y esto es lo que analiza en dos de estos errores:

     

     

    Microsoft (R) Windows Debugger Version 6.11.0001.402 X86

    Copyright (c) Microsoft Corporation. All rights reserved.

     

     

    Loading Dump File [C:\Windows\Minidump\020212-21828-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

     

    Symbol search path is: *** Invalid ***

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

    * Symbol loading may be unreliable without a symbol search path.           *

    * Use .symfix to have the debugger choose a symbol path.                   *

    * After setting your symbol path, use .reload to refresh symbol locations. *

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

    Executable search path is: 

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

    * Symbols can not be loaded because symbol path is not initialized. *

    *                                                                   *

    * The Symbol Path can be set by:                                    *

    *   using the _NT_SYMBOL_PATH environment variable.                 *

    *   using the -y <symbol_path> argument when starting the debugger. *

    *   using .sympath and .sympath+                                    *

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

    Unable to load image \SystemRoot\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 7 Kernel Version 7600 MP (4 procs) Free x86 compatible

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 7600.16385.x86fre.win7_rtm.090713-1255

    Machine Name:

    Kernel base = 0x8284f000 PsLoadedModuleList = 0x82997810

    Debug session time: Thu Feb  2 21:54:40.718 2012 (GMT-5)

    System Uptime: 0 days 0:00:49.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 <symbol_path> argument when starting the debugger. *

    *   using .sympath and .sympath+                                    *

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

    Unable to load image \SystemRoot\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

    ....

    0: kd> !analyze -v

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

    *                                                                             *

    *                        Bugcheck Analysis                                    *

    *                                                                             *

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

     

    CRITICAL_OBJECT_TERMINATION (f4)

    A process or thread crucial to system operation has unexpectedly exited or been

    terminated.

    Several processes and threads are necessary for the operation of the

    system; when they are terminated (for any reason), the system can no

    longer function.

    Arguments:

    Arg1: 00000003, Process

    Arg2: 86dc97c0, Terminating object

    Arg3: 86dc992c, Process image file name

    Arg4: 82a77d50, Explanatory message (ascii)

     

    Debugging Details:

    ------------------

     

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

     

    unable to get nt!KiCurrentEtwBufferOffset

    unable to get nt!KiCurrentEtwBufferBase

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

    ***                                                                   ***

    ***                                                                   ***

    ***    Your debugger is not using the correct symbols                 ***

    ***                                                                   ***

    ***    In order for this command to work properly, your symbol path   ***

    ***    must point to .pdb files that have full type information.      ***

    ***                                                                   ***

    ***    Certain .pdb files (such as the public OS symbols) do not      ***

    ***    contain the required information.  Contact the group that      ***

    ***    provided you with these symbols if you need this command to    ***

    ***    work.                                                          ***

    ***                                                                   ***

    ***    Type referenced: nt!_KPRCB                                     ***

    ***                                                                   ***

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

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

    ***                                                                   ***

    ***                                                                   ***

    ***    Your debugger is not using the correct symbols                 ***

    ***                                                                   ***

    ***    In order for this command to work properly, your symbol path   ***

    ***    must point to .pdb files that have full type information.      ***

    ***                                                                   ***

    ***    Certain .pdb files (such as the public OS symbols) do not      ***

    ***    contain the required information.  Contact the group that      ***

    ***    provided you with these symbols if you need this command to    ***

    ***    work.                                                          ***

    ***                                                                   ***

    ***    Type referenced: nt!_KPRCB                                     ***

    ***                                                                   ***

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

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

    ***                                                                   ***

    ***                                                                   ***

    ***    Your debugger is not using the correct symbols                 ***

    ***                                                                   ***

    ***    In order for this command to work properly, your symbol path   ***

    ***    must point to .pdb files that have full type information.      ***

    ***                                                                   ***

    ***    Certain .pdb files (such as the public OS symbols) do not      ***

    ***    contain the required information.  Contact the group that      ***

    ***    provided you with these symbols if you need this command to    ***

    ***    work.                                                          ***

    ***                                                                   ***

    ***    Type referenced: nt!_KPRCB                                     ***

    ***                                                                   ***

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

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

    * Symbols can not be loaded because symbol path is not initialized. *

    *                                                                   *

    * The Symbol Path can be set by:                                    *

    *   using the _NT_SYMBOL_PATH environment variable.                 *

    *   using the -y <symbol_path> argument when starting the debugger. *

    *   using .sympath and .sympath+                                    *

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

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

    * Symbols can not be loaded because symbol path is not initialized. *

    *                                                                   *

    * The Symbol Path can be set by:                                    *

    *   using the _NT_SYMBOL_PATH environment variable.                 *

    *   using the -y <symbol_path> argument when starting the debugger. *

    *   using .sympath and .sympath+                                    *

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

     

    ADDITIONAL_DEBUG_TEXT:  

    Use '!findthebuild' command to search for the target build information.

    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

     

    MODULE_NAME: csrss

     

    FAULTING_MODULE: 00000000 

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

     

    PROCESS_OBJECT: 86dc97c0

     

    IMAGE_NAME:  csrss.exe

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    BUGCHECK_STR:  0xF4

     

    CURRENT_IRQL:  0

     

    STACK_TEXT:  

    WARNING: Stack unwind information not available. Following frames may be wrong.

    9ae2fc9c 82b2b07b 000000f4 00000003 86dc97c0 nt+0xdcd10

    9ae2fcc0 82aaee44 82a77d50 86dc992c 86dc9a30 nt+0x2dc07b

    9ae2fcf0 82ab0cdf 86dc97c0 86e03d48 c0000005 nt+0x25fe44

    9ae2fd24 8289242a ffffffff c0000005 0057ebf0 nt+0x261cdf

    9ae2fd34 76e464f4 badb0d00 0057ebb8 00000000 nt+0x4342a

    9ae2fd38 badb0d00 0057ebb8 00000000 00000000 0x76e464f4

    9ae2fd3c 0057ebb8 00000000 00000000 00000000 0xbadb0d00

    9ae2fd40 00000000 00000000 00000000 00000000 0x57ebb8

     

     

    STACK_COMMAND:  kb

     

    FOLLOWUP_NAME:  MachineOwner

     

    BUCKET_ID:  WRONG_SYMBOLS

     

    Followup: MachineOwner

    ---------

     

     

    y este es el otro alalisis


    Microsoft (R) Windows Debugger Version 6.11.0001.402 X86

    Copyright (c) Microsoft Corporation. All rights reserved.

     

     

    Loading Dump File [C:\Windows\Minidump\020212-22109-01.dmp]

    Mini Kernel Dump File: Only registers and stack trace are available

     

    Symbol search path is: *** Invalid ***

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

    * Symbol loading may be unreliable without a symbol search path.           *

    * Use .symfix to have the debugger choose a symbol path.                   *

    * After setting your symbol path, use .reload to refresh symbol locations. *

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

    Executable search path is: 

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

    * Symbols can not be loaded because symbol path is not initialized. *

    *                                                                   *

    * The Symbol Path can be set by:                                    *

    *   using the _NT_SYMBOL_PATH environment variable.                 *

    *   using the -y <symbol_path> argument when starting the debugger. *

    *   using .sympath and .sympath+                                    *

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

    Unable to load image \SystemRoot\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 7 Kernel Version 7600 MP (4 procs) Free x86 compatible

    Product: WinNt, suite: TerminalServer SingleUserTS

    Built by: 7600.16385.x86fre.win7_rtm.090713-1255

    Machine Name:

    Kernel base = 0x82815000 PsLoadedModuleList = 0x8295d810

    Debug session time: Thu Feb  2 21:53:05.000 2012 (GMT-5)

    System Uptime: 0 days 0:00:48.578

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

    * Symbols can not be loaded because symbol path is not initialized. *

    *                                                                   *

    * The Symbol Path can be set by:                                    *

    *   using the _NT_SYMBOL_PATH environment variable.                 *

    *   using the -y <symbol_path> argument when starting the debugger. *

    *   using .sympath and .sympath+                                    *

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

    Unable to load image \SystemRoot\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

    ....

    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: a90cfebc, memory referenced.

    Arg2: 00000001, value 0 = read operation, 1 = write operation.

    Arg3: 82886de3, If non-zero, the instruction address which referenced the bad memory

    address.

    Arg4: 00000002, (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                                     ***

    ***                                                                   ***

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

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

    ***                                                                   ***

    ***                                                                   ***

    ***    Your debugger is not using the correct symbols                 ***

    ***                                                                   ***

    ***    In order for this command to work properly, your symbol path   ***

    ***    must point to .pdb files that have full type information.      ***

    ***                                                                   ***

    ***    Certain .pdb files (such as the public OS symbols) do not      ***

    ***    contain the required information.  Contact the group that      ***

    ***    provided you with these symbols if you need this command to    ***

    ***    work.                                                          ***

    ***                                                                   ***

    ***    Type referenced: nt!_KPRCB                                     ***

    ***                                                                   ***

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

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

    ***                                                                   ***

    ***                                                                   ***

    ***    Your debugger is not using the correct symbols                 ***

    ***                                                                   ***

    ***    In order for this command to work properly, your symbol path   ***

    ***    must point to .pdb files that have full type information.      ***

    ***                                                                   ***

    ***    Certain .pdb files (such as the public OS symbols) do not      ***

    ***    contain the required information.  Contact the group that      ***

    ***    provided you with these symbols if you need this command to    ***

    ***    work.                                                          ***

    ***                                                                   ***

    ***    Type referenced: nt!_KPRCB                                     ***

    ***                                                                   ***

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

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

    * Symbols can not be loaded because symbol path is not initialized. *

    *                                                                   *

    * The Symbol Path can be set by:                                    *

    *   using the _NT_SYMBOL_PATH environment variable.                 *

    *   using the -y <symbol_path> argument when starting the debugger. *

    *   using .sympath and .sympath+                                    *

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

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

    * Symbols can not be loaded because symbol path is not initialized. *

    *                                                                   *

    * The Symbol Path can be set by:                                    *

    *   using the _NT_SYMBOL_PATH environment variable.                 *

    *   using the -y <symbol_path> argument when starting the debugger. *

    *   using .sympath and .sympath+                                    *

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

     

    ADDITIONAL_DEBUG_TEXT:  

    Use '!findthebuild' command to search for the target build information.

    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

     

    MODULE_NAME: nt

     

    FAULTING_MODULE: 82815000 nt

     

    DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc007

     

    WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart

    unable to get nt!MmSpecialPoolEnd

    unable to get nt!MmPoolCodeStart

    unable to get nt!MmPoolCodeEnd

     a90cfebc 

     

    FAULTING_IP: 

    nt+71de3

    82886de3 a5              movs    dword ptr es:[edi],dword ptr [esi]

     

    MM_INTERNAL_CODE:  2

     

    CUSTOMER_CRASH_COUNT:  1

     

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

     

    BUGCHECK_STR:  0x50

     

    CURRENT_IRQL:  0

     

    LAST_CONTROL_TRANSFER:  from 8285b5f8 to 8289a8e3

     

    STACK_TEXT:  

    WARNING: Stack unwind information not available. Following frames may be wrong.

    8fcf3c2c 8285b5f8 00000001 a90cfebc 00000000 nt+0x858e3

    8fcf3c88 82886ebf 8fcf3d14 00000030 a90cfebc nt+0x465f8

    8fcf3d24 fd85842a 00000000 a90cfebc 010cff68 nt+0x71ebf

    8fcf3d34 2d7464f4 badb0d00 140cfe10 00000000 0xfd85842a

    8fcf3d38 badb0d00 140cfe10 00000000 71000000 0x2d7464f4

    8fcf3d3c 140cfe10 00000000 71000000 00000000 0xbadb0d00

    8fcf3d40 00000000 71000000 00000000 6f000000 0x140cfe10

     

     

    STACK_COMMAND:  .bugcheck ; kb

     

    FOLLOWUP_IP: 

    nt+71de3

    82886de3 a5              movs    dword ptr es:[edi],dword ptr [esi]

     

    SYMBOL_NAME:  nt+71de3

     

    FOLLOWUP_NAME:  MachineOwner

     

    IMAGE_NAME:  ntkrnlpa.exe

     

    BUCKET_ID:  WRONG_SYMBOLS

     

    Followup: MachineOwner

    ---------

    espero que me puedan ayudar con este error que me tiene demasiado desesperado

    gracias 

     

    Friday, February 03, 2012 3:22 AM

Answers

  • Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA

    Este código de error se refiere a problemas de memoria, podria ser  memoria RAM o memoria de video. Algunos antivirus muy conocidos tambien son  capaces de ocasionar este fallo.
    Te aconsejaria, para comenzar que ejecutaras el diagnóstico de  memoria de Windows.
    Tambien dinos que antivirus tienes instalado y una pequeña  descripcion del PC: Procesador, memoria, motherboard y tarjeta grafica.

    Por cierto, a lo largo del análisis se ve una alerta de windbg, los  símbolos no se pudieron cargar porque no se les ha señalado la ruta, para  ello puede guiarte por este artículo:

    BSOD - Pantalla azul. Cómo analizar el error
    http://www.multingles.net/docs/jmt/bsod.htm


    Saludos cordiales. Ivan
    Saturday, February 04, 2012 12:52 AM

All replies

  • Bug Check 0x50: PAGE_FAULT_IN_NONPAGED_AREA

    Este código de error se refiere a problemas de memoria, podria ser  memoria RAM o memoria de video. Algunos antivirus muy conocidos tambien son  capaces de ocasionar este fallo.
    Te aconsejaria, para comenzar que ejecutaras el diagnóstico de  memoria de Windows.
    Tambien dinos que antivirus tienes instalado y una pequeña  descripcion del PC: Procesador, memoria, motherboard y tarjeta grafica.

    Por cierto, a lo largo del análisis se ve una alerta de windbg, los  símbolos no se pudieron cargar porque no se les ha señalado la ruta, para  ello puede guiarte por este artículo:

    BSOD - Pantalla azul. Cómo analizar el error
    http://www.multingles.net/docs/jmt/bsod.htm


    Saludos cordiales. Ivan
    Saturday, February 04, 2012 12:52 AM
  • gracias por responder 

    tengo un ADM phenom II X4 955 processor 3.20 GHz

    RAM 4 GB 

    placa madre ASROCK n68-vs3 ucc

    tarjeta de vídeo ati HD 5450

    mi antivirus es el norton 360 

    y gracias por el articulo , lo leeré cuidadosamente, lo que si me sorprende es que sea la ram , porque no tiene ni dos meses ... por lo tanto tengo garantía de ella, del disco duro de la placa base y del procesador. por esto necesito saber cual es el problema exactamente para cambiar la parte defectuosa ...

    saludos.

    Saturday, February 04, 2012 1:53 AM
  • Realiza el chequeo de la memoria. Hay que tener paciencia pues se toma su tiempo. A ver que resultados arroja.

    Aunque muchos tiene afecto por algun antivirus y muchas veces se molestan, no queda mas remedio que decirlo, Norton es uno de los antivirus capaces de ocasionar esos pantallazos. Yo te aconsejaria que pensaras seriamente en sustituirlo.

     


    Saludos cordiales. Ivan
    Saturday, February 04, 2012 4:11 PM